Before you start, make sure to back up every file that is now on your system. The installation procedure can wipe out all of the data on a hard disk! The programs used in installation are quite reliable and most have seen years of use; still, a false move can cost you. Even after backing up be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work.
Even if you are installing a multi-boot system, make sure that you have on hand the distribution media of any other present operating systems. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in some cases (i.e., Macintosh), the whole operating system itself.
Since the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, you will need the original operating system in order to boot Linux.
Besides this document, you'll need the atari-fdisk manual page, the amiga-fdisk manual page, the mac-fdisk manual page, the pmac-fdisk manual page, the dselect Tutorial, and the Linux/m68k FAQ.
If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection -- not a PPP connection), you should ask your network's system administrator for this information:
If your computer's only network connection is via a serial line, using PPP or an equivalent dialup connection, you are probably not installing the base system over a network. You don't need to worry about getting your network setup until your system is already installed. See Setting up PPP, section 7.21 below for information on setting up PPP under Debian.
It is important to decide what type of machine you are creating. This will determine disk space requirements and affect your partitioning scheme.
There are a number of default ``Profiles'' which Debian offers for your convenience (see Select and Install Profiles, section 7.19. Profiles are simply sets of package selections which make it easier for you, in that a number of packages are automatically marked for installation.
Each given profile has a size of the resulting system after installation is complete. Even if you don't use these profiles, this discussion is important for planning, since it will give you a sense of how large your partition or partitions need to be.
The following are some of the available profiles (or made-up ones), and their sizes:
Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data.
There is sometimes some tweaking to your system that must be done prior to installation. The x86 platform is the most notorious of these; pre-installation hardware setup on other architectures is considerably simpler.
This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for you system. The ``firmware'' is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up).
Motorola 680x0 machines are generally self-configuring and do not require
firmware configuration. However, you should make sure that you have
the appropriate ROM and system patches. On the Macintosh, MacOS
version >= 7.1 is recommended because version 7.0.1 contains a bug in
the video drivers preventing the booter from deactivating the video
interrupts, resulting in a boot hang. The Amiga bootstrap requires
ixemul.library
, a version of which is distributed on the CD-ROM.
AmigaOS ROM version 3.1 is recommended, but it should really work with any
other recent version. The BVME4000 and 6000 machines require BVMBug
Revision G or later boot ROMs which are freely available from BVM Ltd.
<sales@bvmltd.co.uk>. For your convenience, we have included a
copy of the BVMBug ROM image in the bvme6000 directory on the CD-ROM,
see the accompanying bvmbug.txt.
Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It
sometimes works, but is sensitive to temperature and other factors and
can actually damage your system. One of the authors of this document
over-clocked his own system for a year, and then the system started
aborting the gcc
program with an unexpected signal while it
was compiling the operating system kernel. Turning the CPU speed back
down to its rated value solved the problem.
The gcc
compiler is often the first thing to die from bad
memory modules (or other hardware problems that change data
unpredictably) because it builds huge data structures that it
traverses repeatedly. An error in these data structures will cause it
to execute an illegal instruction or access a non-existent
address. The symptom of this will be gcc
dying from an
unexpected signal.
Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile, see the Linux/m68k FAQ for a description.