News for hackers. Stuff that matters.
Re:Ooops. by orenmazor on Thursday June 16, 2011 @10:50AM (#2661461)
just tried to explain this to a few of my windows using coworkers.
Re:Ooops. by stephen_g on Thursday June 16, 2011 @11:03AM (#2661537)
Just tell them it's the same as a Windows installer accidentally removing the entire Program Files directory.
Re:Ooops. by arethuza on Thursday June 16, 2011 @11:41AM (#2661700)
I knew someone who, in the days of Windows 3.1, managed to accidentally invoke "format c:" from inside Microsoft Word - I was in the same room as them when they did it and heard the cries for help. What they couldn't do was explain to me what they had done to accompish such a feat.
Re:Ooops. by statictype on Thursday June 16, 2011 @11:50AM (#2661743)
As Windows was probably installed on C it probably didn't do any real damage, did it?
Re:Ooops. by srdjanjovcic on Thursday June 16, 2011 @12:20PM (#2661908)
If I remember correctly, that was before Windows started protecting boot volume.
Re:Ooops. by yuhong on Thursday June 16, 2011 @02:24PM (#2662535)
To be more precise, NT had file locking enforced by the OS unlike DOS.
Re:Ooops. by Splines on Thursday June 16, 2011 @11:16AM (#2661596)
Pool of Radiance had a bug where the uninstaller would wipe your hard drive. Oops.

http://arstechnica.com/reviews/01q4/pool_of_radiance/pool-1....

Re:Ooops. by aidenn0 on Thursday June 16, 2011 @11:45AM (#2661719)
Okay, that is not the pool of radiance I played as a kid.
Re:Ooops. by mikemaccana on Thursday June 16, 2011 @11:15AM (#2661587)
It's a DELTREE on %whateveritis%
Re:Ooops. by nuclear_eclipse on Thursday June 16, 2011 @11:21AM (#2661615)
and the entire windows directory, and the entire users directory, and ...
Re:Ooops. by stephen_g on Thursday June 16, 2011 @11:46AM (#2661726)
It was only deleting /usr, which doesn't contain home directories or config files.

I suppose that /usr does store a good chunk of what the Windows directory has in it though.

Re:Ooops. by uxp on Thursday June 16, 2011 @01:28PM (#2662287)
In other Unix flavors, /home may be an alias to /usr/home.
Re:Ooops. by nuclear_eclipse on Thursday June 16, 2011 @01:10PM (#2662174)
Sorry, was thinking of the awful `rm -rf /` variant...
Re:Ooops. by hvs on Thursday June 16, 2011 @11:05AM (#2661543)
"Tried?" Certainly it wasn't that hard to explain.
Re:Ooops. by Ixiaus on Thursday June 16, 2011 @11:10AM (#2661565)
Windows users that aren't privy to *nix culture generally don't find all of the "rm -rf ..." jokes all that funny. They get it, but it's sort of like telling a german joke in English to an English speaker only; they get it, but it looses it's humor if you aren't privy to the culture.
Re:Ooops. by orenmazor on Thursday June 16, 2011 @01:24PM (#2662251)
no, they got it. they just didn't get why its funny. I guess you have to fuck up rm -rf at least once to get these sort of jokes.

it's like explaining jeep jokes to non-jeep owners.

Re:Ooops. by djd on Thursday June 16, 2011 @11:17AM (#2661599)
If you explain it the humor evaporates
Re:Ooops. by httpitis on Thursday June 16, 2011 @11:09AM (#2661562)
...my co-workers using windows

ftfy.

Re:Ooops. by djackson on Thursday June 16, 2011 @11:31AM (#2661654)
Why would he need to explain it to the windows that are using his coworkers?

Also, it's very unclear to me what that the situation you are describing entails.

/s

Grammatically, your sentence is no less ambiguous.

Re:Ooops. by httpitis on Thursday June 16, 2011 @12:42PM (#2662020)
oh man, thursday evening, a couple of glasses of wine, and here I thought I was the grammar nazi :)
Re:Ooops. by ajscherer on Thursday June 16, 2011 @11:50AM (#2661748)
"my windows-using coworkers" would be a better fix.
Re:Ooops. by code_duck on Thursday June 16, 2011 @12:21PM (#2661911)
"...my coworkers who use Windows" makes more sense.
Re:Ooops. by austintaylor on Thursday June 16, 2011 @12:42PM (#2662023)
my windows-using coworkers.