[back] [Abstract] [Copyright Notice] [Contents] [next]

Installing Debian GNU/Linux For Alpha - Chapter 5
Methods for Installing Debian


As you initially install Debian, there are several steps that you shall undergo, in order:

  1. booting the installation system

  2. initial system configuration

  3. installing the base system

  4. booting the newly installed base system

  5. installing the rest of the system

Booting the Debian installation system, the first step, is generally done with the Rescue Floppy or from the CD-ROM. The first boot is sometimes the hardest, depending on your hardware. Therefore, it is described in Booting the Installation System, chapter 6.

Once you've booted into Linux, the dbootstrap program will launch and guide you through the second step, the initial system configuration. This step is described in detail in Using dbootstrap for Initial System Configuration, chapter 7.

The ``Debian base system'' is a core set of packages which are required to run Debian in a minimal, stand-alone fashion. Once you have configured and installed the base system, your machine can ``stand on its own''. The Debian base system can be installed from the following media: floppies, hard disk, CD-ROM, or from an NFS server. dbootstrap will perform this installation; it is described in ``Install the Base System'', section 7.13.

The final step is the installation of the remainder of the Debian system. This would include the applications and documents that you actually use on your computer, such as the X Window System, editors, shells, and development environments. The rest of the Debian system can be installed from CD-ROM or any mirror of the Debian archive (on or off the Internet, via HTTP, FTP, or NFS). At this point, you'll be using the standard Debian package management tools, such as dselect or apt-get. This step is described in Installing the Rest of Your System, section 7.23.

Note that the media you use for one step and the media used for another step do not need to be the same. That is, you can boot from the Rescue Floppy, install the base system from NFS, and then install the remainder of the system from CD-ROM. If you're downloading the system from the archive, you'll generally boot and install the base system from floppies, installing the complete Debian system from the Internet.

The installation system, which is required for the first three installation steps, is divided into three parts: the ``Rescue Floppy'', the ``Drivers Floppy'', and the ``Base System''. Below you will find a description of the different installation methods, and a description of files which might be required for installation. Which files you use, and what steps you have to take to prepare your installation media, will vary with the method that you select to install Debian.


5.1 Choosing Your Installation Media

First, choose the media to use to boot the installation system. Next, choose the method you will use to install the base system.


5.1.1 Choosing Initial Boot Media

To boot the installation system, you have the following choices: floppies, bootable CD-ROM, or a non-Linux boot loader.

Booting from floppies is supported for most platforms, excepting Amigas and Macs. It is described in Booting from Floppies, section 5.6.

CD-ROM booting is one of the easiest ways to install. If you're unlucky and the kernel on the CD-ROM doesn't work for you, you'll have to fall back to another technique. Installing from CD-ROM is described in Installing from a CD-ROM, section 5.4.

Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation. This method is described in Installing from a Hard Disk, section 5.3.


5.1.2 Choosing Media for Installing Base

The base system can be installed in the following ways: from floppies (Installing Base from Floppies, section 5.7), from a CD-ROM (Installing from a CD-ROM, section 5.4), from an NFS server (Installing from NFS, section 5.5), or from a local hard disk (Installing from a Hard Disk, section 5.3). You should choose whatever method matches the media you have, and whatever is the most convenient.


5.2 Description of Installation System Files

This section contains an annotated list of files you will find in the disks-alpha directory. You may not need to download these at all; it all depends on the booting and base system installation media you have chosen.

Most files are floppy disk images; that is, a single file which can be written to a disk to create the necessary floppy disk. These images are, obviously, dependent on the size of the target floppy, such as 1.44MB, 1.2MB, or 720KB. Which sizes are available depends on your platform (i.e., 720KB drives are Atari-specific). The images for 1.44MB drives have `14' embedded in their filenames, 1.2MB images have `12' somewhere in their filename, 720KB drives have `72' in their filename.

If you are using a web browser on a networked computer to read this document, you can probably retrieve the files by selecting their names in your web browser. Depending on your browser you may need to take special action to download directly to a file, in raw binary mode. For example, in Netscape you need to hold the shift key when clicking on the URL to retrieve the file. Files can be downloaded from the URLs in this document, or you can retrieve them from ftp://ftp.debian.org/debian/dists/slink/main/disks-alpha/current/, or the corresponding directory on any of the Debian mirror sites.

alcor/resc1440.bin, avanti/resc1440.bin, book1/resc1440.bin, cabriolet/resc1440.bin, eb64p/resc1440.bin, eb66/resc1440.bin, eb66p/resc1440.bin, eb164/resc1440.bin, jensen/resc1440.bin, lx164/resc1440.bin, noname/resc1440.bin, noritake/resc1440.bin, noritake-p/resc1440.bin, miata/resc1440.bin, mikasa/resc1440.bin, mikasa-p/resc1440.bin, ruffian/resc1440.bin, pc164/resc1440.bin, sable/resc1440.bin, sable-g/resc1440.bin, sx164/resc1440.bin, ruffian/resc1440.bin, takara/resc1440.bin, xl/resc1440.bin, xlt/resc1440.bin -- the Rescue Floppy images
These are the Rescue Floppy disk images. The Rescue Floppy is used for initial setup and for emergencies, such as when your system doesn't boot for some reason. Therefore it is recommended you write the disk image to the floppy even if you are not using floppies for installation. Select the floppy image for your supported sub-architecture, as indicated in CPU, Mainboards, and Video Support, subsection 2.1.2.

alcor/drv1440.bin, avanti/drv1440.bin, book1/drv1440.bin, cabriolet/drv1440.bin, eb64p/drv1440.bin, eb66/drv1440.bin, eb66p/drv1440.bin, eb164/drv1440.bin, jensen/drv1440.bin, lx164/drv1440.bin, noname/drv1440.bin, noritake/drv1440.bin, miata/drv1440.bin, miata-s/drv1440.bin, mikasa/drv1440.bin, mikasa-p/drv1440.bin, ruffian/drv1440.bin, pc164/drv1440.bin, sable/drv1440.bin, sable-g/drv1440.bin, sx164/drv1440.bin, ruffian/drv1440.bin, takara/drv1440.bin, xl/drv1440.bin, xlt/drv1440.bin -- the Drivers Floppy images
These are the Drivers Floppy disk images. They contain the kernel modules, or drivers, for all kinds of hardware that are not necessary for initial booting. You will be prompted to choose the drivers you need during the installation process. If you used a special Rescue Floppy image, you need to use the corresponding Drivers Floppy image.

base2_1.tgz, or base14-1.bin, base14-2.bin, base14-3.bin, base14-4.bin, base14-5.bin, base14-6.bin, base14-7.bin -- the base system
These files contain the base system which will be installed on your Linux partition during the installation process. This is the bare minimum necessary for you to be able to install the rest of the packages. The base2_1.tgz file is for installation from non-floppy media, i.e., CD-ROM, harddisk, or NFS.

root1440.bin -- Root image
This file contains an image of a temporary filesystem that gets loaded into memory when you boot. This is used for installations from hard disk and from CD-ROM.

install.txt, install.html -- Installation Manual
This file you are now reading, in plain ASCII or HTML format.

fdisk.txt cfdisk.txt
Instructions for using your available partitioning programs.

basecont.txt
Listing of the contents of the base system.

md5sum.txt
List of MD5 checksums for the binary files. If you have the md5sum program, you can ensure that your files are not corrupt by running md5sum -v -c md5sum.txt.


5.3 Installing from a Hard Disk

In some cases, you may wish to boot from an existing operating system. You can also boot into the installation system using other means, but install the base system from disk.


5.3.1 Installing from a Linux Partition

You can install Debian from an ext2fs partition or from a Minix partition. This installation technique may be appropriate if you are completely removing your current Linux system with Debian, for instance.

Note that the partition you are installing from should not be the same as the partitions you are installing Debian to (i.e., /, /usr, /lib, and all that).

To install from an already existing Linux partition, follow these instructions.

  1. Get the following files and place them in a directory on your Linux partition. Use the largest possible files for your architecture:

  2. You can use any other functional boot method when installing from a partition. The following assumes you are booting with floppies; however, any boot installation can be used.

  3. Create the Rescue Floppy as discussed in Creating Floppies from Disk Images, section 5.8. Note that you won't need the Drivers Floppy.

  4. Insert the Rescue Floppy into your floppy drive, and reboot the computer.

  5. Skip down to Booting the Installation System, chapter 6.


5.4 Installing from a CD-ROM

If you have a CD which is bootable, and if you architecture and system supports booting from a CD-ROM, you don't need any floppies. Then put the CD-ROM into the drive, and reboot. Now you can skip down to Booting the Installation System, chapter 6.

However you decide to boot, you can install the base Debian system from the CD-ROM. Simply boot using one of the other installation techniques; when it is time to install the base system, and when you install the complete system, just point your installation system at the CD-ROM drive as described in ``Install the Base System'', section 7.13.


5.5 Installing from NFS

Due to the nature of this method of installation, only the base system can be installed via NFS. You will need to have the rescue disk and the driver disk available locally using one of the above methods. To install the base system via NFS, you'll have to go through the regular installation as explained in Using dbootstrap for Initial System Configuration, chapter 7. Do not forget to insert the module (driver) for your ethernet card, and the file system module for NFS.

When dbootstrap asks you where the base system is located (``Install the Base System'', section 7.13), you should choose NFS, and follow the instructions.


5.6 Booting from Floppies

Booting from floppies is a simple process. Simply download the Rescue Floppy image and the Drivers Floppy image. Copy these to floppies as described in Creating Floppies from Disk Images, section 5.8. If you need to, you can also modify the Rescue Floppy; see Replacing the Rescue Floppy Kernel, section 9.3.


5.7 Installing Base from Floppies

NOTE: This is not a recommended way of installing Debian, because the floppies are generally the least reliable type of media. This is only recommended if you have no extra, pre-existing filesystems on any of the hard drives on your system.

Complete these steps:

  1. Obtain these disk images (these files are described in greater detail in Description of Installation System Files, section 5.2):

  2. Locate sufficient floppies for all the images you need to write.

  3. Create the floppies, as discussed in Creating Floppies from Disk Images, section 5.8.

  4. Insert the Rescue Floppy into your floppy drive, and reboot the computer.

  5. Skip down to Booting the Installation System, chapter 6.


5.8 Creating Floppies from Disk Images

Disk images are files containing the complete contents of a floppy disk in raw form. Disk images, such as resc1440.bin, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in raw mode. This is required because these images are raw representations of the disk; it is required to do a sector copy of the data from the file onto the floppy.

There are different techniques for creating floppies from disk images, which depend on your platform. This section describes how to create floppies from disk images for different platforms.

No matter which method you use to create your floppies, you should remember to flip the tab on the floppies once you have written them, to ensure they are not damaged unintentionally.


5.8.1 Writing Disk Images From a Linux or Unix System

To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command

dd if=file of=/dev/fd0 bs=512 conv=sync ; sync
where file is one of the floppy disk image files. /dev/fd0 is a commonly used name of the floppy disk device, it may be different on your workstation (on Solaris, it is /dev/fd/0). The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive (on Solaris, use eject, see the manual page).

Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in raw mode. Unfortunately, how to accomplish this will vary based on your operating system. On Solaris, make sure vold isn't running. On other systems, ask your system administrator.


5.8.2 Floppy Disk Reliability

The biggest problem for people installing Debian for the first time seems to be floppy-disk reliability.

The Rescue Floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the Drivers Floppy and the base floppies, most of which indicate themselves with a flood of messages about disk I/O errors.

If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a different floppy. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system.

One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the third floppy.

Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers.


[back] [Abstract] [Copyright Notice] [Contents] [next]
Installing Debian GNU/Linux For Alpha
version 2.1.8.1, 25 February, 1999
Bruce Perens
Sven Rudolph
Igor Grobman
James Treacy
Adam Di Carlo