Sorry your browser is not supported!

https://github.com/MrMEEE/bumblebee/commit/a047be
Uninstall? Sure, let's just go rm -rf /usr.

The lesson being? I don't know, but it sure is hilarious.

I am bad at reading unix stuff, i am a noob to this stuff, so can anyone explain to me what is the epic fail /epic win/ lulz of this?

I think this program had a bug were it deleted an important system folder. Rather amusing. :3

/usr is pretty much like c:\windows + c:\Program Files in what it contains.

Ahahaha, anyone that is familiar with UNIX will find that rather amusing. Did a similar thing once, typed rm -r /dev/sdc instead of sdd... good-bye Windows partition :S

Just as well it wasn't the hard-drive with my music on, I would have been angered!

so what does rm -rf mean?

is he deleting the usr forler or something?

I know about usr from whatever little time i spent trying to figure out BSD but i still have troble associating the names of unix system folders. Like usr in my head associates with "user" and its kinda confusing. If i remember correctley the USERS are not stored in usr but somewhere else

another confusing thing is usr is both a system and programs directory i think system and programs should be in different directories. ... Well being unix i guess you can build your own variation of the filesystem to your own liking.

Looks like the script was supposed to uninstall a program by deleting its directory from the computer (rm -rf equates to delete folder), hence:


But because there was a space (typo) after /usr, Unix saw:


BOOM!

I laughed. A lot.

Then read the comments and proceeded to more amusement...ahhhh...

the rm command deletes a file. from the man pages:


rm -rf is the same as rm --force --recursive


Soo.... 1. Never prompt to make sure you really really want to delete a file. 2. delete all the files in the current directory and all subdirectories.

[edit]
also this is great xD

/usr contains programs used by users, pretty much all programs except system specific ones.

If you were to put windows in a unix file system, usr would contain things like internet explorer, notepad, calc, msn messenger, and so on.

/home contains user files and settings. For example, your favorites and your specific program settings.

/usr used to be where user home folders were, but not really anymore.

OHHH I GET IT HAHAHAHA he accedentally made it so instead of uninstalling the program he uninstalled the OS HAHAHAHA.:
I gotta let my friend see this he is a huge Free BSD junkie and he will definatley appreciate this lol

btw the names of the root directories still confuse me because in my mind i find it hard to associate the names of the system directories with what they are for.

if i would make a straight forward file system, it would be something like:

/ -root directory
/kernel -the kernel
/sys -OS files (gui, networking stuff. Kindof like the c:\windows)
/prog -programs that people install
/user -info about the users, permissions, settings (like docs & settings folder in win)
/drv -device drivers

maybe i forgot something. I am still new to UNIX, just played around with BSD a little and i am really liking the unix architecture, unlike windows its nice and orgonised. I associate unix systems with orgonised file cabinets. The way i see windows is like: ...

Bucket! first throw a pile of partition table info, boot record and file system stuff to the bottom. (like dont even orgonise it, just take all that info and randomly trow it just make sure its the first thing at the very bottom lol) Then throw in a pile of kernel stuff and low level OS files like NTLRD, Then take a bucket of windows folder and dump the whole bucket into the main win OS bucket Then take a bunch of registry, trow it into the windows OS bucket, and mix it all up a bit but not too much lol
On top of that trow in the user info files like user.dat or something and cover that with the docs & setttings stuff, and finally cover it all with a bunch of "program files". Put it in the oven for 30 minuites, and Vyala! you got yourself a nice hot fresh windows operating system!

seriosly, the structure of windows is really confusing. I noticed, that Unix specialists can diagnose fix problems with their OS much easier because everything in the OS is orgonised, and its easy to track down where the problem is coming from. Also what ive been told about how they teach windows specialists about solving problems with the OS (this is true because i was taught by this method). If this thingy mabober isnt working, then you have to tweak that thing to makie it work. Its like they teach cause and effect without actually understanding the actual mechanism of the OS. This may be a stereotype but ive been told that unix OS technitians are much better trained with their OS than windows technitians for who many of the problems are solved by reinstalling windows.