Re: oops! need help!

[Larry Snyder <larrys lexis-nexis com>]

Jeff Sturm <jeff.sturm@appnet.com> wrote:
> 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.
...but if there's a problem w/ the existing (or not) glibc, then
things like ls, df, cp, mv, mount, and all the other stuff you need
will likely be broken, as they're dynamically linked.  I wonder if
firing up an install in upgrade mode then switching to another VC
for a shell might be a better way to go...just my .02
-ls-

> 
> --
> 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