Hi

I somehow remember doing this via a relatively simple command (it was
upgradepkg or slapt-get) but have forgotten it.

How does one do it ?

Thanks.

Dnia Sun, 26 Sep 2004 03:19:06 -0400, Madhusudan Singh napisa³(a):
> I somehow remember doing this via a relatively simple command
> (it was
> upgradepkg or slapt-get) but have forgotten it.
>
> How does one do it ?

swaret --update && swaret --upgrade

Madhusudan Singh wrote:

> I*somehow*remember*doing*this*via*a*relatively*sim ple*command*(it*was
> upgradepkg or slapt-get) but have forgotten it.
>
> How*does*one*do*it*?

The upgradepkg command takes wildcards, so you can do "upgradepkg *tgz" to
install all packages in the current directory.

However, that's not really enough information I suspect. When you say
upgrade everything, are you talking about installing security patches?
Upgrading to Slackware-current from Slackware-10? Upgrading from some other
version to Slackware-10?

If you upgrade from release to another, or from Slackware-10 to
Slackware-current, you will have to do more than simply upgrade the
packages themselves, if you want to be left with a clean and fully working
system. If you are interested in the specific details of upgrading (which
unfortunately not even the official UPGRADE.TXT contains,) feel free to
check out the upgrading HOWTOs I maintain at:

http://uselesstree.org/tree/trunk/the_complete_slacker.


Jeffrey

Madhusudan Singh wrote:
> Hi
>
> I somehow remember doing this via a relatively simple command (it was
> upgradepkg or slapt-get) but have forgotten it.
>
> How does one do it ?
>
> Thanks.
Find the file:
slackupdate-0.6.1-noarch-1.tgz
Install it with Kpackage and in an su terminal run:
sh slackupdate.sh
This will get the files that need updating and show you how to install them with
just a short script line.


--
Leo (Bing) Whiteway in Canada:
Microsoft: Is that really small and soft toilet paper?
< running Slackware 10 >

Jeffrey Froman wrote:

Thanks for your response.

> The upgradepkg command takes wildcards, so you can do "upgradepkg *tgz" to
> install all packages in the current directory.
>
> However, that's not really enough information I suspect. When you say
> upgrade everything, are you talking about installing security patches?
> Upgrading to Slackware-current from Slackware-10? Upgrading from some
> other version to Slackware-10?

I wish to upgrade all the packages in Slack 10 (the release I am using).

And, yes, the main motivation is to install security patches as quickly as
possible by setting up a cron job that executes once a day.

On Mon, 27 Sep 2004 09:37:34 -0400, Madhusudan Singh wrote:
> Jeffrey Froman wrote:

>> However, that's not really enough information I suspect. When you say
>> upgrade everything, are you talking about installing security patches?
>> Upgrading to Slackware-current from Slackware-10? Upgrading from some
>> other version to Slackware-10?
>
> I wish to upgrade all the packages in Slack 10 (the release I am using).

echo "ftp://ftp.kpn.be/pub/slackware/slackware-10/" \
>>/etc/slackpkg/mirrors

slackpkg update gpg
slackpkg update
slackpkg upgrade slackware

> And, yes, the main motivation is to install security patches as quickly as
> possible by setting up a cron job that executes once a day.

I wouldn't automate it to that extent (unless the machine is expendable)
as something might brake the very functionality it exists to provide.
For me, either from the command-line, or tested beforehand. However:

slackpkg update
yes |slackpkg upgrade patches
lilo

--
-Menno.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Madhusudan Singh dared to utter,
> I wish to upgrade all the packages in Slack 10 (the release I am using).
> And, yes, the main motivation is to install security patches as quickly as
> possible by setting up a cron job that executes once a day.

I try to stay away from these automated means of upgrading whenever
possible, even for security updates. They might break whatever
functionality your box needs. The way I do it, I run an rsync daemon
that syncs nightly and keep a watch on the Changelog. There's an active
list for security patches and userlocal.net has a mailling list that
sends out all Changelog notifications. Whenever I get one, I patch.

Of course, I also keep a watch out on bugtraq and put my ear to the
ground for any vulnerabilities that might appear before Pat releases an
update.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBWFjelKR45I6cfKARAlxvAJ0UYQ5NK18EaqJz1/bGzhqr8aC33QCgsHmV
WmQxKBHNr6uTX3ru/G1xRHA=
=XmSy
-----END PGP SIGNATURE-----

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

+Alan Hicks+ <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Madhusudan Singh dared to utter,
>> I wish to upgrade all the packages in Slack 10 (the release I am using).
>> And, yes, the main motivation is to install security patches as quickly as
>> possible by setting up a cron job that executes once a day.
>
> I try to stay away from these automated means of upgrading whenever
> possible, even for security updates. They might break whatever
> functionality your box needs. The way I do it, I run an rsync daemon
> that syncs nightly and keep a watch on the Changelog. There's an active
> list for security patches and userlocal.net has a mailling list that
> sends out all Changelog notifications. Whenever I get one, I patch.
>
> Of course, I also keep a watch out on bugtraq and put my ear to the
> ground for any vulnerabilities that might appear before Pat releases an
> update.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFBWFjelKR45I6cfKARAlxvAJ0UYQ5NK18EaqJz1/bGzhqr8aC33QCgsHmV
> WmQxKBHNr6uTX3ru/G1xRHA=
> =XmSy
> -----END PGP SIGNATURE-----

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

pgp trash troll delete

Hicks, Alan
188 Shady Dale Dr
Lizella, GA 31052
478-935-8132

+Alan Hicks+ <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Madhusudan Singh dared to utter,
>> I wish to upgrade all the packages in Slack 10 (the release I am using).
>> And, yes, the main motivation is to install security patches as quickly as
>> possible by setting up a cron job that executes once a day.
>
> I try to stay away from these automated means of upgrading whenever
> possible, even for security updates. They might break whatever
> functionality your box needs. The way I do it, I run an rsync daemon
> that syncs nightly and keep a watch on the Changelog. There's an active
> list for security patches and userlocal.net has a mailling list that
> sends out all Changelog notifications. Whenever I get one, I patch.
>
> Of course, I also keep a watch out on bugtraq and put my ear to the
> ground for any vulnerabilities that might appear before Pat releases an
> update.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFBWFjelKR45I6cfKARAlxvAJ0UYQ5NK18EaqJz1/bGzhqr8aC33QCgsHmV
> WmQxKBHNr6uTX3ru/G1xRHA=
> =XmSy
> -----END PGP SIGNATURE-----