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 was having some stability problems on my Slack11 box, and decided to upgrade some packages. This time round, i switched to slapt-get rather then using swaret like i usually do. Some bad stuff has happened though:
"/lib/tls/libc.so.6: version 'GLIBC_2.4' not found"
So im guessing its upgraded the glibc packages, and now everything that was compiled for the previous version has nerfed it. Slack still starts up, but commands like rm, find and the like dont work anymore (giving the above errors). X also wont start.
So given my folly, whats the best way to get back to a working system? Can i just uninstall all the glibc packages and re-install from my Slack DVD, or is there a bettera way to do it? or do i even need to do a complete re-install?
That would have happened regardless of whether you used swaret or slapt-get.
As props666999 suggested, my HOWTO should enable you to recover. Bear in mind that you don't upgrade "some" packages from the -current repos; running Slackware -current is an "all or nothing" proposition. If you're not prepared for some temporary instability due to running a *development* version of Slackware, then you need to use my HOWTO to restore everything back to the 11.0 packages.
I had read up on the slapt-get wiki, and there was a line in there "if you just want stability and security patches, the default slapt-get config should work fine for you" (or something like that). So figured it should be ok.
The slapt-getrc had been setup to exlcude the kernal, glibc and other default things, so didnt think i would get into to much trouble. But as the wiki says, pointing to -current was bad news all the same
I've since refined it to use SOURCE=ftp://mirror.aarnet.edu.au/pub/slackware/slackware-11.0/ (i have a slack 11 install). So should running this with --upgrade cause any dramas that i may have missed in the wiki?
I had read up on the slapt-get wiki, and there was a line in there "if you just want stability and security patches, the default slapt-get config should work fine for you" (or something like that). So figured it should be ok.
The slapt-getrc had been setup to exlcude the kernal, glibc and other default things, so didnt think i would get into to much trouble. But as the wiki says, pointing to -current was bad news all the same
I've since refined it to use SOURCE=ftp://mirror.aarnet.edu.au/pub/slackware/slackware-11.0/ (i have a slack 11 install). So should running this with --upgrade cause any dramas that i may have missed in the wiki?
It should be ok, as --upgrade should only download the updates that the stable version (11.0) gets from time to time.
I prefer slackpkg for this...
I've since refined it to use SOURCE=ftp://mirror.aarnet.edu.au/pub/slackware/slackware-11.0/ (i have a slack 11 install). So should running this with --upgrade cause any dramas that i may have missed in the wiki?
This will *usually* be fine, but it can cause problems on occasion. On occasion, there are glibc updates in the stable release /patches directory, and those are blacklisted by default in slapt-get, so you wouldn't get those upgrades. Also, on rare occasions, new packages are added to the stable release in /patches - for example, 11.0/patches/ has a new mozilla-nss package which gaim must have to work properly for MSN and some other protocols. Slapt-get won't install new (added) packages unless you explicitly tell it to do so (which is fine), so you'll need to read the ChangeLog either way.
Ultimately, the lesson here is simple - no matter how you upgrade, read the ChangeLog.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.