boot-floppies package contains all of the source code and
documentation for the installation floppies.
The rescue floppy has an Ext2 file system (or a FAT file system, depending on
your architecture), and you should be able to access it from anything else that
can mount Ext2 or FAT disks. The Linux kernel is in the file
linux.bin. The file
root.bin is a
gzip-compressed disk image of a 1.4MB Minix or Ext2 file system,
and will be loaded into the RAM disk and used as the root file system.
If you find it necessary to replace the kernel on the rescue floppy, you must configure your new kernel with these features linked in, not in loadable modules:
Be sure that the kernel you plan to use does NOT have CONFIG_DEVFS set. CONFIG_DEVFS is not compatible with the installer.
Download a set of boot floppies: root, rescue, and driver disks. You need to
know that bf2.4, idepci, and compact use flavored kernels. One reason to use
the idepci or compact sets, for instance, is that they have only 1 or 2 driver
disks and your custom kernel will likely have all the drivers you need built
in. The downside is that it requires an extra manual step unless you built
your custom kernel with the same flavor name (see make-kpkg in the
kernel-package). You may also see some error messages regarding
To compile a customised kernel, it is recommended to configure the kernel very similar to the one that you wish to replace. You should get the kernel-source package that have been used to build the kernel and copy the .config file from the rescue disk (see below).
Mount the rescue disk image, something like the following.
mount -t auto -o loop rescue.bin /mnt
Assuming you used
/mnt as the mount point, copy your custom kernel
/mnt/linux.bin. Next run the script
/mnt, which assumes it will find the kernel as
If you want to be complete about it, you'll also want to gzip the System.map
from your custom kernel as
sys_map.gz, and the config as
config.gz, and place them in
Now you can umount your disk image and burn your floppies. You will probably want to ``Install Kernel and Driver Modules'' using the floppies you just built to get your custom kernel installed on the hard drive. This is why having one driver disk is nice.
If you are using a disk set featuring a flavored kernel, you will need to make sure that the modules directory is accepted. Immediately after the step "Install Kernel and Modules", switch to tty2 by pressing Alt and F2 keys together, and hit Enter to get a prompt. Type ls /target/lib/modules to see where the driver disk put your modules. Then uname -r to find out where the modules should be. You'll then want to do something suitable like the following.
mv /target/lib/modules/* /target/lib/modules/`uname -r`
Now you may exit out of the shell and return to tty1. If you didn't perform the last step properly, then ``Configure Device Driver Modules'' won't find any modules and thus will be sad.
You'll also want to replace the
modules.tgz file on the driver
floppies. This file simply contains a
gzip-compressed tar file of
/lib/modules/kernel-version; make it from the root file
system so that all leading directories are in the tar file as well.
If you need an essential driver in order to access the harddisk or installation source device, you can use existing modules instead of recompiling the whole kernel. You can preload driver modules from a floppy disk before mounting the root partition. To prepare such a floppy, you will need:
Here are the steps to create the preload disk, assuming that you are on a Linux box and plan to use the bf2.4 flavor later:
su tar -zxvf /cdrom/debian/dists/woody/main/disks-i386/current/bf2.4/drivers.tgz tar -zxvf modules.tgz less lib/modules/2.4.18-bf2.4/modules.dep
modules.depfile, locate the modules that you are looking for, and note their dependencies. Note the order in which the modules depend on each other. Do the same for each dependency, unless you have a list of modules that can be loaded without dependencies.
booton the floppy disk. Copy all required modules to this directory.
Installing Debian GNU/Linux 3.0 For Intel x86version 3.0.24, 18 December, 2002