Recovery help (Maybe OT)
Quoted 1 line
I managed to do a rm -rf /
Oops. The easiest way to recover is probably to wipe what remains and start over. Having said that, rebuilding from something like that is a great learning experience :).
Quoted 2 lines
It erased my /bin /boot /dev
and something from /mnt
Are you sure that's all it got? Nothing out of /etc or /lib?
Quoted 8 lines
INIT: cannot execute
/etc/rc.d/rc.S
INIT: cannot execute/etc/rc.d/rc.M
INIT: cannot execute/sbin/agetty
INIT: respawning too fast, disabled for five minutesThose files _are_ there and _are_ executable. (I verified by booting from the slackware 8.0 install-cd and mounting the partitioin and ls -l)
The first two are interpreted by the shell. If /bin/sh has problems, they won't run, whether they're there or not. The failure to run agetty could be files missing from /lib, or it could be a /dev thing.
Quoted 3 lines
If I try to boot with init=/bin/sh
No init found -- kerne panic :-)
That would be consistent with damage to /lib. There are lots of other things it would be consistent with as well, but that's the most obvious. You might also like to try init=/bin/bash and (if its installed) init=/bin/sash or init=/bin/ash.
Also try booting from the install CD and going ``ldd /bin/bash''. All required libraries must be present, or the program can't run, so make sure you've restored anythat got zapped. You probably also want to run ldconfig again: ``$MNT/sbin/ldconfig -r $MNT'', replacing $MNT by the mount point of your old root filesystem on the install CD filesystem.
Quoted 1 line
From my experience this seems to be a
/dev/problem
That would certainly explain the agetty problem. I would ignore this until you get the shell working again - if you're using devfs, then it should correct itself once you've done that.
Steven Smith,
[email protected].