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
The Stallman Report - A Hit Piece on the Free Software Founder

An anonymous author. Strong political bias. Dubious motivation. Canceling an old man with cancer because he makes controversial statements.

00:49:07
October 14, 2024
Debian Linux Doesn't Want Straight White Men

Want to be a paid intern for Debian? Everyone is welcome! (Except Straight White Men. And Asians. Debian really doesn't want Asians.)

00:19:56
October 14, 2024
The Road to Skynet: Nuclear Powered, CAPTCHA Solving AI

Teach Al systems to beat CAPTCHAs and pretend to be people, then give them nuclear reactors. What could go wrong!?

00:12:02
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

I know The Register attacked Lunduke, but they have an interesting article about switching customers from Linux to BSD. https://www.theregister.com/2024/10/08/switching_from_linux_to_bsd/

6 hours ago

On this week in privacy, let's explore web apps and convenience.

Web apps are cool

Web apps are applications that run inside web browsers. As you probably already know, web apps have been around for years, most notably with in the form of electron apps, and have had varying levels of success. Whole frameworks like React and Vue are designed specifically to turn an ordinary web page into an interactive app that runs offline.

There are advantages and disadvantages of web apps. On the plus side, unless you allow notifications, they turn off when the browser is closed. There's no secret spying. They're also compatible with every operating system with a decent browser. On the negative size, native apps can be more feature rich, and better handle touch controls.

We can install web apps from the Brave menu. This creates a link on the app screen. Alternatively, we can just bookmark the site. Either works.

Logging in every time sucks

One of the biggest advantages of web apps in a secure browser is ...

PSA for the morning: I'm still getting this Ubuntu system set up and went to install Joplin which is an AppImage. Turns out 24.10 (maybe it's a thing in older version too, but I don't know) is missing a dependency for AppImages to work. In case anyone was going to move to Ubuntu 24.10 and run AppImages, install fuse2 first.

apt install libfuse2t64

October 14, 2024
post photo preview
Last week at The Lunduke Journal (Oct 6 - Oct 12, 2024)
GNOME Layoffs! Woke Software Alternatives! Internet Archive Hacks! Facebook Censorship Portal!

Whew!  Last week was another crazy one!

GNOME Foundation layoffs, Google breakup by the government, Facebook's custom developed web portal to help Biden censor Americans... oh, and that crazy Internet Archive hack (which is still going on!).  Wild times.

But, if you're going to watch just one show from last week, I would make it the one about LEGO parts on laptops.  Because that one made me smile.

The Shows

The Articles

Read full Article
October 13, 2024
post photo preview
Funny Programming Pictures Part LIX
Buckle up, Buttercup.

One of these is my favorite.  Youn know which one it is.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Read full Article
October 11, 2024
Today is the last day new Lifetime Subscriptions are available!

Whew!  It's the end of an era!

Today is the final day that new Lifetime Subscriptions to The Lunduke Journal can be picked up.

No rain checks.  No extensions.  These really and truly are the last few hours they will be available.

If you've ever wanted one, now is literally your last chance.

  • Lifetime Lunduke Journal Subscriptions are only available until Friday, October 11th, 2024.  That's... today!

  • Lifetime Subscriptions are discounted to $200 for these final hours.

  • Today is also the last day any subscription can be obtained via Bitcoin.

  • Obviously, all existing Lifetime Subscriptions (including those picked up in the final moments) will be honored.  For life.

You can find all of the details in this article (or this video) -- including the reasons why no new Lifetime Subscriptions will be offered after today, and details on the new Lunduke Journal Affiliate Program.

If you have picked up a Lifetime Sub in the last few hours and days, you will be receiving an email shortly (if you haven't already) with confirmation.  If you have questions, feel free to email me (bryan at lunduke.com).

How To Get a Lifetime Subscription

All the benefits of a Standard Monthly subscription... but pay once and never need to pay again.  $200.

  • Go to Lunduke.Locals.com/support.

  • Select "Give Once".

  • Enter "200" into the amount field.

  • After checking out, Lunduke will toss you an email once your account is set to full lifetime status.

How To Get a Lifetime Subscription (with Bitcoin)

You can also obtain a Lifetime Subscription via Bitcoin.

  • Make sure you have a Lunduke.Locals.com account (a free account works just fine).

  • Send $200 worth of Bitcoin (or more) to the following address:

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email "bryan at lunduke.com" with the following information: What time you made the transaction, how much was sent (in Bitcoin), and the email address you use (or plan to use) on Locals.com.

Here's a handy-dandy QR code you can scan that also has a Bitcoin Wallet Address for The Lunduke Journal:

102127_2uuarwwiqcds5s2.jpeg
 

 

 

 

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