Lunduke
News • Science & Tech
The Fork Bomb: What it is, how it works, and where it originated
The idea started in 1969... and it's been causing computers to crash ever since.
December 03, 2023
post photo preview
:(){ :|:& };:

That simple line has been crashing systems in the Linux world for years — It is known as the (infamous) “BASH Fork Bomb”.

When run in a GNU/BASH shell, this BASH variant of the Fork Bomb will bring your average Linux system to its knees, lickety-split. A mere handful of characters that can cause a computer to cry “Uncle.”

But what, exactly, is a “Fork Bomb”? How do they work? And where on this green Earth of ours were they first created?

Come with me on a journey into the history, design, and usage of one of the most dastardly ideas in all of computing… of The Fork Bomb!

What is a Fork Bomb?

The idea of a Fork Bomb is simple: Create a piece of code that does one thing and one thing only: replicate running instances of itself. And do so as quickly as possible.

Here, a visual will help drive the idea home.

In this case each Bunny Rabbit represents one instance of the Fork Bomb. Each bunny makes two new bunnies. Quickly. Multiplying like, well, rabbits.

Each of those adorable little bunny rabbits may not take up much RAM… or much CPU time… but imagine 20 of them. Or 1000. Or, like, a bazillion?! That Fork Bomb will continue making running copies of itself just as long as the system allows it to (by continuing to have available memory or not fully crash).

With how quickly each Fork Bomb replicates itself… and the number of copies growing exponentially… you can see how they can become a problem in a hurry. Often causing a system to lock up quicker than you can say, “Maybe I shouldn't have pressed Enter.”

A real-world example… and how it works

Let’s take a look at that BASH version of the Fork Bomb again (as that is one of the most popular and famous examples).

(If you don’t know how BASH scripting works, no worries. I’ll break it down… make it nice and easy.)

:(){ :|:& };:

Ok. So how does this, ridiculous looking, collection of semi-random seeming characters, actually work?

Let’s break that apart into multiple lines to make it all easier to read.

: ( ) {

   : | : &

} ; :

This… is a BASH script function.

But there’s something… weird about it. Note the many usages of “:”? In this case “:” is being used as a function name.

“Why is using “:” as a function name weird,” you ask?

Because, on most UNIX-y systems, it is not allowed to use a character in a function name other than letters and numbers (and underscores). But the GNU version of BASH — which is commonly used on oh-so-many Linux systems — allows : and so many other characters to be used.

Why does GNU allow a “:”? Who knows. GNU be crazy.

Regardless…

Let’s replace the “:” in that BASH script with “rabbit”. That will, in addition to making it run on more UNIX systems, make this a bit easier to read.

rabbit() {
rabbit | rabbit &
}; rabbit

There. So much better. Here we go. Line by line.

Line 1: rabbit() {

That first line does something simple. It defines a function named “rabbit”. That’s it and that’s all.

Line 2: rabbit | rabbit &

Line 2 is the insidious part.

It calls the function named “rabbit”, and sends the output of that function to the function named “rabbit.”

But, here’s the thing, there really isn’t any output of the “rabbit” function. So this is really just a fancy way of calling the “rabbit” function twice… at the same time.

Yeah. The “rabbit” function calls itself, from within itself, then calls itself again.

Oh, and that “&” at the end? That's the BASH way of telling “rabbit” to run in the background.

The net result? Every “rabbit”, makes two new “rabbit”s.

Line 3: }; rabbit

That last nine simply ends the “rabbit” function… and then calls itself.

Note: I highly recommend not running this code on your system unless you do so in a virtual machine. Without taking the proper precautions… this will bring your system to its knees.

Every variation of a Fork Bomb operates in a roughly similar fashion. A small piece of code that creates copies of itself… repeatedly. Thus eternally replicating itself until the system runs out of resources.

The first Fork Bomb

The very first known usage of a “Fork Bomb” was way back in 1969 at the University of Washington.

There, a Burroughs B5500 computer had been installed three years earlier. A big computer that provided the first time-sharing system on the University of Washington campus (through a series of dial-up modems running at 110 baud). This was also the first computer at the University of Washington to provide disk storage for user files. Pretty cool.

A Burroughs B-5500. Not the one at the U of W, though. Classy looking machine, right?

On that big, beautiful Burroughs B-5500, someone reportedly wrote a small bit of code that would make two copies of itself — over and over again — until the memory of the machine was full and the entire system would crash.

That intrepid programmer named that tiny little program, appropriately: “RABBITS”

Fun historical tidbit: RABBITS for the Burroughs B-5500 was not, technically the first computer virus. That distinction appears to go to the 1971 “Creeper Virus”. While RABBITS predated Creeper by a good two years… RABBITS doesn’t really act like a virus. It requires a user to explicitly run it in order to cause its own mischeif.

The 1974 “Wabbit”

A similar piece of code was written on an IBM System/360, a few years later, in 1974. Clearly inspired by “RABBITS”, this new code was called “Wabbit” and was, as Elmer Fudd might say, quite “wascally”.

The IBM System/360 Model 22 control panel. That thing was awesome looking.

Legend has it that the individual who created “Wabbit” ran the program on the System/360 at work… causing the entire system to crash. The man, again according to legend, lost his job.

Fun bit-o-trivia: As years went on any program that would self-replicate when ran by the user… but wasn’t actually a virus… would become known as a "wabbit.” in honor of this particular event.

Some other variations on the Fork Bomb

There have been Fork Bomb type bits of code written in just about every language you can imagine. At the beginning we covered how to write a Fork Bomb in BASH. But, because this sort of mayhem is simply too much fun, below you will find code to create similar bits of functionality in several other programming languages.

Enjoy.

Just… you know… try not to get yourself fired.

Fork Bomb in C:

int main(void) {
for (;;) {
    fork();
}
}
Fork Bomb in Python:

#!/usr/bin/env python

    import os
    while True: os.fork()

Fork Bomb in Ruby:

#!/usr/bin/env ruby
loop { fork { bomb } }
community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
6
What else you may like…
Videos
Podcasts
Posts
Articles
November 19, 2026
GNOME Proposes Total AI Ban

“This policy works in the same way as the Code of Conduct: violations will first result in a warning, and repeated violations may result in a ban.”

The Lunduke Journal & LCOS:
https://lunduke.com/

00:11:00
November 17, 2026
System76 Pop!_OS Lead Dev to AI Users: "Fk Off"

Plus: Red Hat Dev says AI users are "Nazis" who "voted for Republicans" and are "unsafe to have around".

The Lunduke Journal & LCOS:
https://lunduke.com/

00:11:25
November 15, 2026
A RISC-V $1,599 Linux Smartphone From Purism?

Don't get too excited just yet: "RISC-V is not yet drop-in and boot-up ready for PureOS. Most peripherals are not supported in mainline Linux."

The Lunduke Journal & LCOS:
https://lunduke.com/

00:22:26
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Latest vulnerability; affects all OSes since 1971 - https://www.terminal2shell.com/

November 19, 2026

After the first day of trading, Anthropic is now worth $1.27 trillion dollars. That's trillion with a T.

https://www.theepochtimes.com/business/anthropic-makes-historic-2-trillion-debut-on-wall-street-6126991

November 18, 2026

LCOS running in vm

I have the latest LCOS running in a vm on my Beelink LinuxMint machine. The host machine has 64gig of ram. It was my unstable box but it's been running for 52 days now.

I gave the vm 4gig of ram and so far that's fine.

I have my LCOS Notes markdown app up and running. Try it folks: https://github.com/leebase/lcos-notes

And I have the Warp terminal running. It gives me my Linux Admin AI. I love having it although these days Claude Code and Codex could suffice - just not as elegant.

I have Claude Code, Codex, OpenCode and Herdr installed though haven't used them yet.

That Cool Retro Term is freaky to me ;)

I do have xrdp running and can remote directly into LCOS from my M5 Mac Air.

The day may come when I wipe of LinuxMint and make LCOS the host OS. But not yet.

post photo preview
October 28, 2026
post photo preview
3 Days Left to get your name into LCOS 1.0’s About Window!

Holy imminent operating system release, Batman!

Three things worth knowing:

  1. Saturday, October 31st is the last day to get your name into the LCOS About Window by picking up a Lifetime Lunduke Journal Subscription.

  2. Saturday, October 31st is also the last day when Lifetime Subscriptions are massively discounted. (Crazy, how those two dates line up! What a coincidence!)

  3. Sunday, November 1st is the official release date for LCOS 1.0!

Want your name in the About window for the Lunduke Computer Operating System 1.0? You’ve got about 3 days left to make it happen!

Here’s what to do:

  1. Go to this page and pick up a Lifetime Subscription (aka “One Time Contribution with Lots of Perks”).

  2. Within a few hours, you’ll receive a confirmation email from yours truly with all the details.

  3. Reply to that email with how you want your name displayed in the LCOS 1.0 About Window (nick name, first name, or full name are all aok).

Just be sure complete step 3 before midnight (Central Time) on Saturday, October 31st so it definitely makes it onto the final LCOS 1.0 build! My advice? Do this by Friday, October 30th so there’s no chance you miss it!

Huge thank you to everyone who has been supporting The Lunduke Journal and LCOS! You make all of this possible!

-Lunduke

Image
 
Read full Article
October 17, 2026
post photo preview
LCOS 1.0 Ships on November 1st!

A release date has officially been selected!

The Lunduke Computer Operating System (LCOS) 1.0 will ship on November 1st… just two weeks from now!

A few quick tidbits worth mentioning:

Worth repeating: If you want your name in the LCOS About Window (see the screenshot below), you only have through October 31st to grab a Lifetime Subscription to The Lunduke Journal and make that happen.

Huge thank you to everyone who has contributed with both hardware testing and financial support. We’ve had absolutely tremendous momentum over the last few months, and that wouldn’t have been possible without all of you.

-Lunduke

 
Read full Article
October 13, 2026
post photo preview
LCOS 0.9.3 has Landed! Plus: How to Help.

The Lunduke Computer Operating System (LCOS) is flying towards the official, 1.0 release — with version 0.9.3 now available for testing!

Between now and 1.0, LCOS is laser focused on a) fixing bugs and b) making sure it runs (and runs well) on as much hardware as possible.

Right now, LCOS needs your help. Here’s how:

  1. Test the latest LCOS release on your hardware. Hit any snags? Report them on GitHub, the Lunduke Forum, or via DM on X.

  2. Donate to LCOS (and The Lunduke Journal), so that we can expand our hardware testing lab (among other expenses).

If you haven’t already, watch the LCOS Roadmap video, to get an idea for where we’re heading (in 1.0 and beyond).

Then check out this page, for details on how to support LCOS & The Lunduke Journal (and get your name on the LCOS 1.0 About window in the process).

A huge thank you to everyone who has already contributed (in both ways)! With your help, we are making LCOS into the best gosh darned system in all the land.

-Lunduke

Image
 
Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals