SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would rather create an installation DVD with slackware(64)-current (this is clearly explained in isolinux/README.TXT), with an additional directory containing supplementary packages, and install it.
What do you mean by "update" if it is not bringing to current ?
I do everything by hand. So in this case I would go in the slackware-current/slackware directory, then
mv a/aaa_base* .
upgradepkg --install-new */*tgz
upgradepkg --install-new */*txz
mv aaa_base* a/
Then I would look in Changelog.txt to see which packages must be removed (I think there are about 25)
Then of course one would need to take care of the change of kernel and what that means for booting (run 'lilo -C /etc/lilo.conf' if lilo is used for ex.)
Are there any security updates for version 14.1? The iso file which I downloaded had a date of 04-Nov-2013. Generally release versions keep getting security updates. How do I manage that?
I would go to any of the mirrors and download the files in the slackware-14.1/patches/packages directory. I would then cd into the directory of the downloaded files and do an "upgradepkg *.txz" as root in order to bring you installation up to the most current configuration for 14.1 (32-bit).
The default for slackpkg is to download everything then install, so will have to have enough room on partition to download the packages.
At the end of installing updates will be asked to rerun lilo if the kernel is updated, and to replace configuration files with new ones.
Last edited by colorpurple21859; 11-11-2015 at 07:47 AM.
AlienBOB's rsync_slackware_patches.sh script is one of the options.
In a cron job you could schedule a daily check like this:
Code:
# Keep the Slackware patches up to date
33 5 * * * /usr/local/sbin/rsync_slackware_patches.sh -q -r 14.1
That script will be silent if no new patches are found and downloaded.
It will output a message when it does find updates. Cron wil send that text as an email to the user who is running the cron job.
Example:
Code:
Date: Sat, 7 Nov 2015 03:53:42 +0100
From: root@blah.local.net
To: root@blah.local.net
Subject: cron for user root /usr/local/sbin/rsync_slackware_patches.sh -q -r
14.1
[rsync_slackware_patches.sh:] New patches have arrived for Slackware 14.1
(x86)!
.......................................................................
0a1,15
> Fri Nov 6 01:15:43 UTC 2015
> patches/packages/mozilla-firefox-38.4.0esr-i486-1_slack14.1.txz:
Upgraded.
> This release contains security fixes and improvements.
> For more information, see:
> http://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
> (* Security fix *)
> patches/packages/mozilla-nss-3.20.1-i486-1_slack14.1.txz: Upgraded.
> Upgraded to nss-3.20.1 and nspr-4.10.10.
> This release contains security fixes and improvements.
> For more information, see:
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7181
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7182
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7183
> (* Security fix *)
> +--------------------------+
If you see that in your mailbox you know that it is patch time.
Probably the simplest way is to follow colorpurple21859's advice. However, since you're just looking to install patches, the install-new portion shouldn't be needed.
Just uncomment a 14.1 mirror in /etc/slackpkg/mirrors, then run
Code:
slackpkg update gpg #only needed one time to sync the server's gpg key
slackpkg update #checks the server to see what updates are out since the last check
slackpkg upgrade-all #provides you with a dialog box of all potential upgrades and allows you to select which ones to install
NOTE: slackpkg and upgradepkg see any version change as a potential upgrade, even if it is a lower version of the package. If you install newer versions of official Slackware software, you may want to add those packages to the blacklist, so you don't actually "upgrade" (downgrade) them.
Will the script rsync_slackware_patches.sh script work for any version of Slackware?
Code:
./rsync_slackware_patches.sh -h
-----------------------------------------------------------------
$Id: rsync_slackware_patches.sh,v 1.22 2015/07/01 12:51:17 root Exp root $
-----------------------------------------------------------------
[rsync_slackware_patches.sh:] Parameters are:
-a <arch> Architecture to mirror (defaults to 'x86',
can be 'x86_64' too).
-h This help.
-k Keep old local files even though they were
removed on the remote server.
-n Rsync dry-run (don't download anything).
-p Download packages only - not the sources.
-r <release> Act on Slackware version <release>. The default
is to download patches for Slackware 13.37
-q Non-verbose output (for cron jobs).
-s Download sources only - not the packages.
-X <xfile> File 'xfile' contains a list of exclude patterns
for packages that you do not want mirrored.
I was able to update the system using following commands (after selecting one mirror) as advised by @bassmadrigal :
Code:
slackpkg update gpg #only needed one time to sync the server's gpg key
slackpkg update #checks the server to see what updates are out since the last check
slackpkg upgrade-all #provides you with a dialog box of all potential upgrades and allows you to select which ones to install
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.