On 3/11/06, Shane Hathaway <[EMAIL PROTECTED]> wrote: > Alex Esplin wrote: > > That must be a pretty sturdy computer to still say anything after that... :p > > Actually, that's what happens--I have experience. After the fatal > command, the kernel, bash, even the GUI all remained in RAM, and through > the magic of inodes, all of the loaded dynamic libraries remained on > disk. But nothing on disk linked to them, so the kernel lay waiting for > me to kill the running processes, at which time it would shred the last > bits of the filesystem. Yet the kernel's desire for carnage could never > be satisfied, because among the commands deleted were 'kill', 'umount', > and 'fsck'! I was also powerless to recover the files. The battle > ended with a brand new distribution and a scarred but slightly less > foolish user.
That's pretty interesting. Having never tried 'rm -rf /' I had no experience with that. I suppose I could have figured that out if I had thought about it. You really do learn something new every day. -- Alex Esplin /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
