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 s

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 /etc/fstab had been written with the CD as sda and the hard drive as sdb. I couldn't create a mount point, like /tmp/foo because of the read only file system. (I tried to mount a floppy on /tmp, but got the same read-only-file system error. On a whim I dumped the strings from the mount command and noticed two hard coded paths: /tmp/mnta and /tmp/mntb. Sure enough I was able to mount the root file system (again) read-write to update the file. No emacs at this point but I did have vi, but it creates a /tmp/file and that directory isn't writable... So I ended up writing usomg sed to mangle my fatab.. Out of curiosity, how would windows deal with a similar problem (corrupted registry?). Any windows stories of triumphs?