Craig P Prescott wrote:
> Have you tried to boot with "init=/sbin/sash"? sash is a statically
> linked shell ("stand-alone shell"), so at least *it* won't be affected
> by a hosed libc. It might help you get back into your system so that
> you can at least poke around.
That's a better suggestion that mine... I never heard of sash, but I do
have it on my RH6.2 box at least.
Note that if /sbin/sash comes up OK, you'll still have to remount / as
read/write to do anything useful:
mount -n -o remount,rw /
At that point you'll have no mounted filesystems and no network, but
most commands will be available so hopefully you can restore your
critical /lib files.
-- Jeff Sturm jeff.sturm@appnet.com-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail version 2a22 on Sat Jul 1 05:31:30 2000 PDT
Send any problems or questions about this archive to webmaster@alphalinux.org.