From mboxrd@z Thu Jan 1 00:00:00 1970 From: crossd@gmail.com (Dan Cross) Date: Mon, 24 Apr 2017 20:44:43 -0400 Subject: [TUHS] was turmoil, moving to rm -rf / In-Reply-To: <20170424235930.GB24499@mcvoy.com> References: <20170424220603.883CB18C0D0@mercury.lcs.mit.edu> <20170424221840.GB4966@naleco.com> <20170424232328.GB27654@wopr> <20170424235930.GB24499@mcvoy.com> Message-ID: Am I the only one who mentally says, "f*ck recursively" whenever I type, "rm -fr" ? (f*ck being fsck, of course.) On Mon, Apr 24, 2017 at 7:59 PM, Larry McVoy wrote: > This is gonna seem like I'm tooting my own horn, and I am a little, but > here's an rm -rf / story. > > Clem will be amused because I was a junior or senior in college and a sys > admin for a Masscomp with a 40MB disk with 20 users. And I did some > version > of rm -rf /, realized part way through that I screwed up, and killed it. > But /bin and /dev were gone so putting things back together was hard. > > But I did it and wrote up this little note for the people who came after > me, if I was stupid enough to do this someone else would, was my thinking. > You can get a sense of how scared I was in it if you read it carefully. > It was a very long night. > > For an undergrad, I think it's not bad? Maybe? I dunno, I look at how > much I needed to have understood to get the system back up, that's a lot > of reading, playing, experience. Love that Geophysics department, they > pushed me. > > And it was during my (brief) foray into the *roff -me macros (I went > -ms and never looked back). Roff source on request to anyone who is > twisted enough to want it. > > http://mcvoy.com/lm/masscomp-restore.pdf > > Complete with all the typos. > > --lm > -------------- next part -------------- An HTML attachment was scrubbed... URL: