It's a pretty messy script anyway - rm'ing /usr/lib/nvidia-current/xorg/xorg doesn't strike me as the most delicate approach to the problem.
Ooops.
31–40 of 247 posts
Re: Ooops.
#32Here is the original bug report. https://github.com/MrMEEE/bumblebee/issues/123
I've never heard of BumbleBee, but it must be great if a user can have their machine wiped out and still thank the library author for their work.
Re: Ooops.
#33just tried to explain this to a few of my windows using coworkers.
...my co-workers using windows ftfy.
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.
#34I don't remember the exact details, but a few years ago there was a Perl module that did something like: my $path = something_that_can_return_undef_on_failure; `rm -rf /$path`; during the execution of its test suite. The author didn't catch it in testing because he never ran "make test" as root (who would?). But people on the Internet ran "make test" as root, with disastrous consequences.
I'm not sure if you're being sarcastic with the "who would?" portion of your comment, but doesn't cpan run tests, by default, whenever installing something? And, most people who aren't Perl developers with their own private Perl installation install CPAN modules as root, so they are available to all users. So, to answer the question seriously: Most people.
Re: Ooops.
#35That poor guy. But I appreciate the reminder to double-check any rm command.
Re: Ooops.
#36rm is like a knife where the handle has a sharp edge too...
A double edge knife/sword?
Re: Ooops.
#37just tried to explain this to a few of my windows using coworkers.
Just tell them it's the same as a Windows installer accidentally removing the entire Program Files directory.
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.
#38Earlier quoted context omitted.
Just tell them it's the same as a Windows installer accidentally removing the entire Program Files directory.
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....
Okay, that is not the pool of radiance I played as a kid.
Re: Ooops.
#39Earlier quoted context omitted.
Just tell them it's the same as a Windows installer accidentally removing the entire Program Files directory.
and the entire windows directory, and the entire users directory, and ...
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.
#40I don't remember the exact details, but a few years ago there was a Perl module that did something like: my $path = something_that_can_return_undef_on_failure; `rm -rf /$path`; during the execution of its test suite. The author didn't catch it in testing because he never ran "make test" as root (who would?). But people on the Internet ran "make test" as root, with disastrous consequences.
$ rm -rf /
rm: it is dangerous to operate recursively on `/'
rm: use --no-preserve-root to override this failsafe