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.
Just download the security updates from here and you'll be fine. You could keep up with Slackware-current but only if you feel like testing new packages and possibly breaking your system once in a while.
Also, you might want to subscribe to the slackware-security mailing list.
Last edited by 2.718281828; 03-09-2008 at 04:38 AM.
I don't think I'd like Slackware-current. I like the fact that Slackware is so stable and I wouldn't like to break it. VirtualBox is good enough for me to check out new packages.
So do I just install the packages I want to update the same way I install packages (installpkg). Looking at the descriptions of the packaged on the site you recommenced it does not say these are updates. Do you just know these guys host updates?
You install them using the upgradepkg command, which uninstalls the old version first but otherwise works the same was as installpkg. You can also download those files from slackware.com if you want, but the link I gave is one of the official mirrors and it's quite a bit faster. That mirror site is mentioned in the slackware-security emails.
Occasionally the upgrade instructions involve a little more than just typing "upgradepkg package_name.tgz". Mostly things like, if you're upgrading apache and currently running the old version of apache, you'll need to restart it afterwards or something like that. You could check the slackware-security mailing list archives and look over the emails because at the bottom of each email they list installation instructions.
Make sure you read the ChangeLog; there's a some new kernel packages in that lot, so if you just blindly do a upgradepkg *.tgz, you probably won't be able to boot afterwards.
This distribution amazes me every time I try to learn something new. It is so simple! (I don't like when the operating system thinks it knows what you are thinking and does stuff for you. Slackware does not do that!)
As my first attempt I want to update Thunderbird (from 2.0.0.4 to 2.0.0.12). I downloaded it from the link you provided (because slackware.com was pretty slow) but the MD5 is different to the one in slackware-security archive. Is this a problem?
Yes, the MD5 sums are supposed to match. I downloaded that package just now and it worked for me though. Did you run "md5sum mozilla-thunderbird-2.0.0.12-i686-1.tgz", i.e., do the checksum on the tgz file? It should give you 0c5bfc8c508e128b13c88311a6889879 according to the mailing list archive.
And pwc101 brought up a good point that I had forgotten -- be sure to follow the directions when upgrading your kernel your you'll have problems.
Last edited by 2.718281828; 03-09-2008 at 05:25 AM.
OK, I'll take care with the kernel. As a side note I will be upgrading my 2.6.21.5-smp soon. Playing with the compilation in a virtual machine.
I got the file again and the md5sum is good now (it was 3de6e96532f2ce6949e18b113aa5031e the first time). Upgrade was quick and easy. I have subscribed to slackware-security.
Keeping in mind what pwc101 said the change log does not tell me (might tell you) that there is any danger in doing the update. Is there? Can apply this update even though I have not applied any patched in 6 months (can I jump over the other patches)?
Quote:
Originally Posted by pwc101
Make sure you read the ChangeLog; there's a some new kernel packages in that lot, so if you just blindly do a upgradepkg *.tgz, you probably won't be able to boot afterwards.
Also, can you point me to one of these so I can have a look (I'm not sure what I am looking for in the change log).
Well, yes, the ChangeLog doesn't say a whole lot about the new kernel actually. It just mentions that "If you use lilo, don't forget to run it again after the upgrade." I just looked at the email that had been sent out about the kernel upgrade and that's about all it said too. So just run upgradepkg for the new kernel, then run lilo (with no command line options) and if lilo doesn't complain about any fatal errors, you should be fine. It's actually a bit simpler than I had expected but that's Slackware for you I guess. I've forgotten to run lilo in the past and my system wouldn't boot, but then I always just boot using my Slackware 12 DVD and it tells you how to boot into your system from there. So even if you forget to run lilo, it still shouldn't be that hard to boot up from a CD or DVD and try again.
Also, it shouldn't make any difference what order you apply the patches in. You should be able to just upgrade everything, run lilo and reboot. (And the only reason you'd need to reboot is if you want to start using the new kernel.)
Last edited by 2.718281828; 03-09-2008 at 06:04 AM.
Using install-new will add any new packages, of which there are now quite few.
Using clean-system will remove any obselete packages, (and also any custom packages you have added, so be careful!)
I am a convert to slackpkg. The latest version is even able to handle reversions, as I discovered on a recent update.
My warm thanks to PiterPunk for this excellent tool!
Just a reminder, I suggest that you always update the glibc and the kernel packages ( the kernel itself + modules + headers + source ) first. I do this manually and have these packages blacklisted in my /etc/slackpkg/blacklist file. This is probably unnecessary as slackpkg appears to do this for you anyway.
And the only reason you'd need to reboot is if you want to start using the new kernel.
So will every kernel patch make a new kernel? If it does will there be the old one to go back to if there is trouble?
In regards to slackpkg update and slackpkg upgrade-all: can I use the combination of both these commands and upgrading individual packages by myself like I did thunderbird just before?
Sorry, too many questions but you guys know so much and are very helpful.
Yes, you can upgrade individual packages with slackpkg. Even if you do upgrade-all, a box pops up allowing you to select which packages you want or do not want to upgrade.
I use Slackupdate, and then manually install them with 'upgradepkg'. Note that after you install the kernel update, run '/sbin/lilo' if you're using lilo as bootloader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.