Building Tiny Linux Systems with Busybox, Part 2: Building the Kernel
You'll need the genromfs program to generate the ROM file system image. If you are using Debian or Red Hat, it's already packaged for you as part of the standard system; you'll just need to run the command to install it. If your Linux distribution doesn't include a prepackaged version, at this writing the program can be found at ftp://ibiblio.org/pub/Linux/system/recovery/genromfs-0.3.tar.gz. Install the program, change directory to the directory that contains tiny-linux and run these commands:
genromfs -d tiny-linux -f fs
This creates the ROM file system image in the file fs. Now, compress the file system image using the gzip command:
gzip -9 fsThat will create the file fs.gz, which is about half the size of the uncompressed version.
We'll need one more program to build our floppy: syslinux. This is an i386 bootstrap program that will load a kernel and a compressed root file system image from a floppy, hard disk or CD. Again, it's prepackaged with Debian or Red Hat and can be found, at this writing, at ftp://ibiblio.org/pub/Linux/system/boot/loaders/syslinux-1.48.tar.gz.
Create an MS-DOS file system on a floppy by using the Linux mformat command (or by another means). Put the floppy in your drive but don't mount it, and install the syslinux bootstrap with this command:
syslinux /dev/fd0
That will copy a first-stage bootstrap onto the first block of the floppy and a second-stage bootstrap into the file LDLINUX.SYS in the MS-DOS file system of the floppy. I'm assuming you have a directory called /mnt; substitute whatever directory you usually use for mounting floppy disks in the shell commands below. Now, it's time to copy our kernel and root file system onto the floppy:
mount -t msdos /dev/fd0 /mnt cp fs.gz /mnt cp /usr/src/linux/arch/i386/boot/bzImage /mnt/linuxCreate the configuration file /mnt/syslinux.cfg with an editor:
TIMEOUT 20
DEFAULT linux
LABEL linux
KERNEL linux
APPEND root=/dev/ram0 initrd=fs.gz
This tells syslinux to wait for two seconds and then boot the
default system. You can interrupt the default boot during those two
seconds by pressing the shift key. Typing linux at the prompt will
do the same thing as the default.
The kernel is booted with the arguments root=/dev/ram0 and initrd=fs.gz. These arguments tell the kernel that the root is a RAM disk, and that the RAM disk is loaded from the compressed ROM file system image fs.gz. Although the ``ROM'' root file system is actually in RAM, it will not be writable because the Linux ROM file system driver used in this example is meant to work with real ROMs and thus doesn't support writing.
Configure an i386 PC to boot from the floppy. Note that this is a setting in the BIOS preferences of most new PCs, and they are often configured to boot from the hard disk without first looking for a bootstrap on the floppy. Place the floppy in the first floppy drive, and restart the system. You should see something like the following:
SYSLINUX 1.48 1999-09-26 Copyright (C) 1994-1999 H. Peter Anvin loading fs.gz......... loading linux............... Uncompressing linux, OK, booting the kernel
Tons of cybercrud about every device driver and facility in the kernel race by too rapidly to read...
RAMDISK: Compressed image found at block 0. VFS: Mounted root (romfs file system) Please press Enter to activate this console.You've done it! Press Enter and you should see something like this:
Busybox v0.46 (2000-09-12-22:16+0000) built-in shell Enter 'help' for a list of built-in commands. / # _Pop out the floppy disk; it's not being used any longer. The root file system is entirely in RAM. You should be able to look around the system and try out commands, but you won't have any writable storage. This is the simplest, bootable-system, running busybox that I could think of, and thus I've left out the files in /dev that you'd need to mount writable RAM disks, floppies and hard disks. You now should be able to figure out what those devices are, add them and build a tiny Linux system specialized to your application.
email: bruce@perens.com
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
| Dart: a New Web Programming Experience | May 07, 2013 |
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Home, My Backup Data Center
- What's the tweeting protocol?
- One Hand Slapping
- The Secret Password Is...
- Trying to Tame the Tablet
- RSS Feeds
- Reply to comment | Linux Journal
5 hours 52 min ago - Reply to comment | Linux Journal
8 hours 24 min ago - Reply to comment | Linux Journal
9 hours 41 min ago - great post
10 hours 16 min ago - Google Docs
10 hours 39 min ago - Reply to comment | Linux Journal
15 hours 27 min ago - Reply to comment | Linux Journal
16 hours 14 min ago - Web Hosting IQ
17 hours 48 min ago - Thanks for taking the time to
19 hours 25 min ago - Linux is good
21 hours 22 min ago
Enter to Win an Adafruit Prototyping Pi Plate Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Prototyping Pi Plate Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.



Comments
How Keyboard is working when no support provided in Linux
How Keyboard is working when no support provided in Linux ?
When i booted Linux from floppy and used the ramdisk as the rootfs, everything is working fine.
But i was wondering how the keyboard is working ? No loadable drivers provided.
Also no support in Linux provided>
I am not getting the # prompt instead i am getting the $ prompet
Hai Bruce Perens,
I have followed each and every step you told in this article but i am not getting the # prompt after booting it from the floppy. Instead i am getting the $ prompt.
How to get the # prompt can you tell me the error i am donig
Thanking you,
K.RajaSekahr
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
Luckily he provided the list of names in almost the right format for python.
An easier way to create those links to busybox:
import os
names=["ls","ar","basename","cat","chgrp","chmod","chown","chroot","chvt","clear","cp","cut","date","dc","dd","deallocvtdf","dirname","dmesg","du","dumpkmap","dutmp","echo","false","fbset","fdflush","find","free","freeramdisk","fsck.minix","grep","gunzip","gzip","halt","head","hostid","hostname","id","init","insmod","kill","killall","length","linuxrc","ln","loadacm","loadfont","loadkmap","logger","logname","lsmod","makedevs","md5sum","mkdir","mkfifo","mkfs.minix","mknod","mkswap","mktemp","more","mount","mt","mv","nc","nslookup","ping","poweroff","printf","ps","pwd","reboot","rm","rmdir","rmmod","sed","setkeycodes", "sh", "sleep", "sort","swapoff","swapon","syn", "csyslogd", "tail", "tar", "tee", "telnet", "test", "touch", "tri", "true", "tty", "umount", "uname", "uniq", "update", "uptime", "usleep", "uudecode", "uuencode", "wc", "which", "whoami", "yes", "zcat"]
for name in names:
os.system("ln busybox "+name)
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
I did this do create the links with a debian 'busybox-static'
#!/bin/sh
#
# Thorsten Strusch 2005-01-06
#
#########################################################################
#
BUSYBOX=$(which busybox)
#
Liste=$( $BUSYBOX 2>&1 | grep -A20 Currently | grep -v Curren | sed -e '{s/\t//}' -e '{s/\n//}' -e '{s/ //}' | grep -v ^$)
export IFS=','
for i in $Liste
do ln -s $BUSYBOX $i
done
unset IFS
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
Or even easier:
from the busybox build dir
$ make PREFIX=../tiny-linux install-hardlinks
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
Hi...
all went ok, kernel uncompressed, but then..kernel panic :(
kernel panic: unable to mount root fs on 01:00, what that is.. i gave my full memory, but .. nothing.. why? can u send me reply?
P.S.: best article(s).. thanx...
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
Im trying to make a mini floppy disk linux distro thing (if thats the right name) , i used a differant tutorial looks almost the same as this BUT .... i got the same boot error! that and something about VFS and "cramfs: wrong magic" so yeah. somethings up there, maybe i enabled some wrong options in the kernel and they are breaking each other.
Re: Building Tiny Linux Systems with Busybox, Part 2: Building t
did you enable ROM filesystem support in the kernel? if not you can try mkcramfs instead
ROM filesystem
I had a similar problem with romfs. In my case, I had to gzip the file system without "-9".