There does not exist a static bash executable that is installed by default. This is asking for trouble when users blow up their system, as init=/bin/bash is then worthless. Perhaps we should add a static bash to the boot parition, although I would prefer to have it in /bin.
If /bin/bash isn't working then chances are ls, etc won't work either... unless I'm missing something :) sash makes a nice choice as an emergency shell. Everything built in and statically linked...
I wouldn't bet money on that assumption, as I ran into a case where bash didn't want to load (complained about a missing libdl.so.2) while cp,mv,ls,cat, etc worked nicely (presumably since they don't need dynamic linking). However, either using Busybox or sash is the preferred solution.
blocke@kodiak blocke $ ldd /bin/mv libc.so.6 => /lib/libc.so.6 (0x40026000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) blocke@kodiak blocke $ file /bin/mv /bin/mv: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped *shrugs* But back on topic, I forgot about busybox... Thats probably an even better choice then sash because it has a built in editor, etc. Maybe busybox should be installed as part of the 'system' profile and it be mentioned somewhere in the docs?
'sash' will be added to profile for use as our emergency static shell *** This bug has been marked as a duplicate of 993 ***
