As you initially install Debian, there are several steps that you shall undergo, in order:
Booting the Debian installation system, the first step, is generally done with the Rescue Floppy or from the CD-ROM. Alternatively, you can boot Debian over the network. 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, are 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.
First, choose the media to use to boot the installation system. Next, choose the method you will use to install the base system.
To boot the installation system, you have the following choices: floppies, bootable CD-ROM, network boot (TFTP), 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.8.
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.5.
Booting from the network requires that you have a TFTP server, a RARP server, and a network connection supported by the boot floppies. This installation method is described in Booting from TFTP, section 5.6.
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.4.
The base system can be installed in the following ways: from floppies (Installing Base from Floppies, section 5.9), from a CD-ROM (Installing from a CD-ROM, section 5.5), from an NFS server (Installing from NFS, section 5.7), or from a local hard disk (Installing from a Hard Disk, section 5.4). You should choose whatever method matches the media you have, and whatever is the most convenient.
This section contains an annotated list of files you will find in the
disks-sparc 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 disks. 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. Otherwise, you can retrieve them from ftp://ftp.debian.org/debian/dists/slink/main/disks-sparc/current/, or a similar directory in any of the Debian mirror sites.
base2_1.tgz file is for installation
from non-floppy media, i.e., CD-ROM, harddisk, or NFS.
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.
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.
Get the following files and place them in a directory on your Linux partition. Use the largest possible files for your architecture:
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.
You need to setup two servers: a RARP server and a TFTP server. The Reverse Address Resolution Protocol (RARP) is how your client will figure out what IP address to use; the Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux.
To setup RARP, you need to know the ethernet address of the client (a.k.a. the MAC address). If you don't know this information, you can pick it off the initial OpenPROM boot messages, use the OpenBoot .enet-addr command, or boot into ``Rescue'' mode (i.e., from the Rescue Floppy) and use the command /sbin/ifconfig eth0.
In GNU/Linux you need to populate the kernel's RARP table. To do this execute
/sbin/rarp -s client-hostname client-enet-addr /sbin/arp -s client-ip client-enet-addrUnder SunOS, you need to ensure that the ethernet hardware address for the client is listed in the ``ethers'' database (either in the
/etc/ethers file, or via NIS/NIS+) and in the ``hosts''
database. Then you need to start the RARP daemon. In SunOS 4, issue
the command (as root): /usr/etc/rarpd -a; in SunOS 5, use
/usr/sbin/rarpd -a.
To get the TFTP server ready to go, you should first make sure that
tftpd is enabled. This is usually enabled by having the
following line in /etc/inetd.conf:
tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -s /bootLook in that file and remember the directory which is used for the ``-s'' argument of
in.tftpd; you'll need that below. If
you've had to change /etc/inetd.conf, you'll have to
notify the running inetd process that the file has
changed. On a Debian machine, run /etc/init.d/netbase
reload; on other machines, find out the process ID for
inetd, and run kill -1 inetd-pid.
Next, place the TFTP boot image, tftpboot.img, in the
tftpd boot image directory. Generally, this directory
will be /boot in Debian, and /tftpboot in
other operating systems. Then, you'll have to make a link from that
file to the file which tftpd will use for booting a
particular client. The form of the file that tftpd will
look for is
client-ip-in-hex.client-architecture.
To compute client-ip-in-hex, take each byte of the client
IP address and translate it into hexadecimal notation. You have you
have a machine handy with the bc program, you can use the
program. First issue the obase=16 command to set the output
to hex, then enter the individual components of the client IP one at a
time. As for client-architecture, try out some values. Sparc
architectures for instance use the sub-architecture names, such as
``SUN4M'' or ``SUN4C''. Once you've determined the name, make the
link like so: ln /boot/tftpboot.img
/boot/file-name.
Now you should be ready to actually boot your system. On machines with OpenBoot, simply enter the boot monitor on the machine you are installing to, and use the command boot net.
On some systems, the standard installation RAM-disk, combined with the memory requirements of the TFTP boot image, cannot fit in memory. In this case, you can still install using TFTP, you'll just have to go through the additional step of NFS mounting your root directory over the network as well. This type of setup is also appropriate for diskless or dataless clients.
First, follow all the steps above in Booting from TFTP, section 5.6.
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.
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.10. If you need to, you can also modify the Rescue Floppy; see Replacing the Rescue Floppy Kernel, section 9.3.
On your architecture, the Rescue Floppy couldn't fit the root filesystem image, so you'll need the root image to be written to a disk as well. You can create that floppy just as the other images are written to floppies. Once the kernel has been loaded from the Rescue Floppy, you'll be prompted for the root disk. Insert that floppy and continue. See also Booting with the Rescue Floppy, section 6.2.
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:
Obtain these disk images (these files are described in greater detail in Description of Installation System Files, section 5.3):
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.
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 ; syncwhere 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.
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.