Not rm related, by I was recently trying to revive a NeXTStation and inatalling from cd left me with a system that booted to single user with a read only file system. The &#x2F;etc&#x2F;fstab had been written with the CD as sda and the hard drive as sdb. I couldn&#x27;t create a mount point, like &#x2F;tmp&#x2F;foo because of the read only file system. (I tried to mount a floppy on &#x2F;tmp, but got the same read-only-file system error.<p>On a whim I dumped the strings from the mount command and noticed two hard coded paths:
&#x2F;tmp&#x2F;mnta and &#x2F;tmp&#x2F;mntb. Sure enough I was able to mount the root file system (again) read-write to update the file.<p>No emacs at this point but I did have vi, but it creates a &#x2F;tmp&#x2F;file and that directory isn&#x27;t writable...  So I ended up writing usomg sed to mangle my fatab..<p>Out of curiosity, how would windows deal with a similar problem (corrupted registry?). Any windows stories of triumphs?