Thanks Maya - really helpful steer. But it turned out that the real
problem was that etc/fstab on the new disk referred everything to
/dev/wd0 rather than /dev/wd2, and the layout of the two disks is
different. Elementary, really, but easily overlooked (epecially when
your fighting off bombardme
If you are at the point where getty is attempting to run, then you're clearly
multi-user.
If you have a filesystem that is supposed to be wd0 but is currently wd2
and that's where it booted from, the obvious thing to look for is what is in
/etc/fstab - you said that /usr (and /var) are mounted fil
After paying more attention:
things think that libc.so. is in /usr/lib sometimes, e.g.
/usr/bin/login:
-lutil.7 => /usr/lib/libutil.so.7
-lc.12 => /usr/lib/libc.so.12
-lcrypt.1 => /usr/lib/libcrypt.so.1
-lpam.4 => /usr/lib/libpam.so.4
/usr/lib/libc.so.12 is a sym
My go to for broken setups of any kind:
drop to boot prompt
type "boot -as" (ask, single user)
then pick /rescue/init as your init, and otherwise normal.
export PATH=/rescue
if you have a working /rescue that is all you need. it's a single
statically linked binary that can recover your setup, the
