To find the nearest (and thus probably the fastest) mirror, see the list of Debian mirrors.
When downloading files from a Debian mirror, be sure to download the files in binary mode, not text or automatic mode. It's important to replicate the directory structure you find on the mirror to create a local `sub-mirror'. It isn't really necessary to do this if you place all the installation files on floppies; but it still makes it easier to find the files when you need them. You should start your local directory structure at the level under installer-powerpc, for example:
current/images/subarchitecture/netboot/initrd.gz |
You don't need to download every file under that level, just those that apply to you (you'll find out which ones apply as you read on). Just name the directories the same as the mirror's, and keep the files in their proper directories.
If your machine is set up to automatically decompress/decode files you download, you must turn that feature off when downloading the installation system files. They will be decompressed just-in-time by the installer. Decompressing in your current system will waste space and time, and if the original compressed archives are deleted by the decompression program, they won't be there later when the installer needs them.
This is particularly true on the Macintosh, where .bin files are interpreted to be MacBinary, and the decoder's attempts to convert them will fail noisily.
Also, many of the binary files such as yaboot will be automatically interpreted as text since they have no file extensions unless you specifically select binary transfer mode. These files will be unusable if they are transferred in text mode.
Files you may need fall into three categories:
Files needed to boot into the installation system (for example, boot.img and root.img, or vmlinuz and initrd.gz)
Files the installation system will need access to after it has been booted in order to install the operating system kernel and peripheral drivers (for example, net-drivers.img and cd-drivers.img)
Base system installation files
If you have a working Ethernet connection on the computer, and your Ethernet card is of one of the types compiled into the installation kernel, you may only need the install system boot files. The installer is capable of installing drivers and the rest of the system over the network for many common Ethernet cards.
If you have an Ethernet connection for which the installer doesn't have built-in support, you may need both the install system boot files and the peripheral driver installation files.
If you are installing on a system without a working network connection, or if your network connection is via PPP (using a modem) rather than Ethernet, you will need to obtain all three types of files before starting the installation. The base system installation files are available on the first Debian CD (or on its smaller variant called netinst, which is under 120MB). You can use this ISO image even if you don't have a CD-ROM drive.
If you're not sure which files you need, just start with the install system boot files. If your first attempt to configure the network within the installer fails, you can just quit, get the extra files you need, and re-start the installation.
Installation files include kernel images, which are available for various subarchitectures. Each subarchitecture supports a different set of hardware. The kernel config files for these subarchitectures can be found in their respective directories in a file named kernel-config. The subarchitectures available for PowerPC are:
This is the kernel to use for most Power Macintosh computers; it uses version 2.2 of the Linux kernel.
Use this kernel for very new Power Macintosh computers; it is based on version 2.4 of the Linux kernel. If you want to install the new-powermac version on an OldWorld machine, you are limited to using BootX to boot the installer; the kernel doesn't fit on a floppy and Debian CDs are not bootable on OldWorlds. You could also switch to the 2.4.25 kernel after you finish the powermac flavor install.
Use this kernel for Amiga Power-UP Systems (APUS); it is based on version 2.2 of the Linux kernel.
Use this kernel for embedded CHRP computers; it is based on version 2.2 of the Linux kernel.
Use this kernel for Motorola and IBM RS/6000 PReP computers; it is based on version 2.2 of the Linux kernel.
The kernel config files for these subarchitectures can be found in their respective directories in a file named config.gz.
Both the boot-floppy-hfs floppy image and the boot.img image contain a compressed Linux boot kernel. The boot-floppy-hfs floppy is used to boot the installation system, while boot.img serves as the source for the Linux kernel when the kernel is being installed on your machine. A boot.img floppy cannot be booted on PowerPC . A third uncompressed kernel image, simply named linux.bin, is used when booting the installer from the hard disk or CD-ROM. It is not needed for floppy installer booting.
There are two versions of the hfs boot floppy image. The standard one, boot-floppy-hfs.img, may work best on older machines such as the 7200 and 8500 with no added video cards. If the standard image gives a black screen when booting, try the image with video=ofonly added to the boot arguments: boot-video-ofonly.img.
Refer to Sección 4.3, “Creating Floppies from Disk Images” for important information on properly creating floppy disks from floppy images.
The root floppy image root.img contains a compressed RAMdisk filesystem which gets loaded into memory after you boot the installer.
The peripheral drivers may be downloaded as a series of floppy images or as a tarball (drivers.tgz). The installer system will need access to the drivers file during installation. If you have a hard drive partition or connected computer which will be accessible to the installer (see below), the tarball will be more convenient to handle. The floppy image files are needed only if you must install the drivers from floppies.
When downloading files, you should also pay attention to the type of file system you are downloading them to, unless you will use floppies for the kernel and drivers. The installer can read files from many kinds of file systems, including FAT, HFS, ext2fs, and Minix. When downloading files to a *nix file system, choose the largest possible files from the archive.
During the installation, you will erase the partition(s) on which you are installing Debian before beginning the installation. All downloaded files must be placed on partitions other than those on which you are planning to install the system.
For floppy-less installation on NewWorld Macs, it may be most convenient to obtain all the necessary files packaged into one Stuffit archive from http://debian-imac.sourceforge.net/ (separate instructions are included in the archive). Otherwise, obtain the normal installation files listed above. Retrieve the files to an HFS (not HFS+) partition on your system. You will also need the yaboot and yaboot.conf files from the new-powermac or powermac archive folder. However, the newest G4 PowerMacs, and those that work without MacOS 9, need the newest version of yaboot; the one in the archive will not work. Obtain the newest version from http://penguinppc.org/projects/yaboot/.