Just a shot in the dark, but....

I know that on a Gentoo system, when you change some of the build settings, or 
compiler/glibc library (i.e. USE flags) you have to update your shared 
libraries via the command env-update (Gentoo specific I think).  

Perhaps your shared libraries need to be updated?  I don't know how this would 
be done on Slackware though....

HTH

Shawn

On Thursday 15 July 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

Reply via email to