Hi Curtis. Check if you actually have the binaries on sight, see if you can still run rpm, i think suse is rpm based. See if you can dl glibc-2.3.2-i486-1 and put it on the disk, go at it with mc, open it and copy what is in , how i have to check an rpm file , ok so you should see a directory structure when you clic/enter on an rpm file, in your case it should be a lib or a usr/lib or whatever, you get the idea, select the files, and copy them over to where they whare supposed to be, now you should run ldconfig but you cant, becouse your bash is dead, so try to reboot the system again, and see if it works. if that does not help, then you have to compile a bash and a sed elsewhare using the --enable-static option with the ./configure and put them on the dead system overwriteing the once that where there, now reboot the system, and bash and sed should be working now, and you can rpm -i the old liberery back, it will not overwrite the newer one, but will go side-by-side, and will run ldconfig that would be fuctional hopefully (bash)... if that does not help, you have to dig-up your suse 9.1 disks, and reinstall(upgrade), it will just put everything back, but this is a long run... Cheers Szemir
On July 15, 2004 18:36, Curtis Sloan wrote: > I used swaret to upgrade Slackware 9.1 to 10.0 today (first time using > swaret). It installed everything up to and including glibc-2.3.2-i486-6 > (according to the logs). Immediately after that, the GNU portion of the > system stopped working (i.e. not the kernel, but everything else -- bash in > particular). So now the system won't respond to commands, won't INIT on > reboot, etc. > > What could cause the system to immediately stop working -- not running > ldconfig after? I'm afraid I don't have a full grasp on the inner workings > of a GNU/Linux system yet (accepting hardware donations for an LFS box ;-). > > Interestingly, the rev number of glibc is the same -- just the package > number is different (glibc-2.3.2-i486-1 is the old one). I did a diff on > the file listings for each package and the only real difference appears to > be locale information. Colour me confused. > > I read on a website that the way they did it is to upgrade glibc-solibs, > bash, and sed first, then the rest. I don't know if that gives anyone any > insight. > > To make matters worse, I can't chroot using a Live CD either. It gives me > 'chroot: /bin/bash: no such file or directory' which I am led to understand > means that the shared libraries that bash needs the system doesn't know > about. I ran ldd on bash but it doesn't help me much: > > libtermcap.so.2 > libdl.so.2 > libc.so.6 > /lib/ld-linux.so.2 > > I'm stuck with a half-upgraded system. Any ideas would be appreciated. > > Thanks, > Curtis > > > > _______________________________________________ > clug-talk mailing list > [EMAIL PROTECTED] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
