News for hackers. Stuff that matters.
Re:Yes `yes no` by duaneb on Wednesday March 13, 2013 @11:40PM (#5372950)
> Now if you really want to screw over your machine, the classic bash fork bomb is `:(){ :|:& };:`

Actually, you're wrong. At least on a mac (IIRC) it caps the process number so fork bombs just fill the console with errors. I'm sure you can get around it but that kind of defeats its simplicity.

EDIT: I mean, don't get me wrong, it still really bogs your computer down, but you can still kill the parent bash process in a few seconds.

Re:Yes `yes no` by ninetax on Wednesday March 13, 2013 @11:55PM (#5372992)
Crashed my machine running linux Mint. I couldn't Google it, so I had to try it. I don't know what I expected.

Can someone explain how it works?

Re:Yes `yes no` by cheeseprocedure on Thursday March 14, 2013 @12:37AM (#5373117)
Re:Yes `yes no` by gcr on Thursday March 14, 2013 @12:15AM (#5373056)
Be careful running commands that you don't understand! I've been bitten by that before...
Re:Yes `yes no` by duaneb on Thursday March 14, 2013 @12:32AM (#5373106)
I don't know about linux (and I really should in this case as it's my 'field'), but at least on mac, you can restrict the number of child processes a process can spawn with `ulimit -u`:

    zooey:~ duane$ ulimit -u
    709
Re:Yes `yes no` by eridius on Thursday March 14, 2013 @02:12AM (#5373361)
Depends on how much RAM you have. If your machine swaps everything out to disk before it hits the process limit, then you're pretty screwed anyway.