If /sbin/init is destroyed or corrupted, boot -s fails, you have no spare init to copy in, you are stuck ! Fix: Ideally, put an /sbin/init on fixit floppy, but no space: tunefs -m 0 /dev/rfd0c df /dev/rfd0c # 72 K free cp /sbin/init /tmp gzip /tmp/init # 109 K maybe there's room on the 2nd boot disc was introduced with 3.2 ? Or maybe we should introduce a fixit.extras floppy ? I suspect other files might also be needed on there ? How-To-Repeat: chmod -x /sbin/init boot -s # Fail to boot off hard disc Boot with fixit floppy, mount your hard drives find / -name init -print chmod +x /sbin/init # to rescue yourself from the simulation Now think: "how could I copy in a new init if mine was damaged ?"
State Changed From-To: open->closed Answered own question, yes the solution is a custom fixit.flp.