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'm running Slackware 9.1 and I was upgrading it with swaret, upon reboot I get an error -bash: /lib/libc.so.6: version 'GLIBC_2.3.4' not found (required by -bash). I can't log in as root or my user.
Is there anything I can do to get the system back up and running?
Here's what I'd do. Pull down Slackware 10 install disk and boot from that. Mount your drive's /usr partition and then copy the libc.so.6 from the install disks /lib directory to your /usr/lib and see if that fixes it.
Odds are that's just one of many libraries that you've broken in the process of upgrading. I'd suggest backing up any critical user data and do a full install/upgrade of Slackware, but you may be able to get by with just piecemealing the missing files.
Remember that if there's a file missing that you don't find in the mini boot install, you can always grep for the file in the slackware/l directory. Just "grep library.name *.txt" and you should find it. You can then use tar to extract the files you want and copy them down.
I was following a guide on here. now mind you, this wasn't a fresh install and I didn't need to do "swaret --dep". Also the files didn't end in .new they just installed. So yeah I'll say it...
Quote:
Originally Posted by shilo
Making Sure You've got the Latest & Greatest
7) Install SWareT. Go here http://www.swaret.org to get the package. The first thing you will want to do is edit the swaret.conf file. Change the version to current. Uncomment the line for linuxpackages.net. Enable slocate. Now type "swaret --update", then type "swaret --upgrade -a", Then "swaret --dep". This will take awhile. I run swaret --upgrade -a a few times, because you will usually have a few packages that didn't get downloaded the first few times.
Making Sure the Latest & Greatest Works!!!
8) Here's a step everyone seems to miss. Since you have done a fresh install, the configuration files should all still be stock. When you upgrade packages, you get a lot of files that end in .new. These are the new configuration files. The updaters that you have run didn't want to get rid of possibly custom configuration files. Since none of our configuration files are custom yet, it's pretty safe to do this: updatedb to update the search database. Now type "slocate .new" Go to each one of those files and drop the .new off of the filename. You'll have to also delete the other file with the same name first.
your idea worked.. and I'm now able to boot and log into my box.
there is a driver issue with the sound, but I don't use the sound on that box so its no big deal.
the only thing left to fix is this error:
/usr/sbin/httpd: error while loading shared libraries: libdb-4.4.so: cannot open shared object file: No such file or directory
/usr/sbin/apachectl start: httpd could not be started
I tried to install db4-4.2.52-i486-2, the script said it was running then dropped back to the prompt... to be honest I've never used installpkg before so I don't know if its suppose to show anything between saying the script is installing and the prompt.
Only if there's an error. You can use the -infobox so it'll display info about what it's doing, but for the most part you shouldn't get any messages unless it has a problem.
I take it apache didn't run after installing the db libs?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.