Auto Install for Mandrake Linux
Prev Next

Installation Methods

Overview

Installation of the Mandrake Linux distribution on a computer(s) depends on a number of things:

Environment:

is the computer connected to a network, are you trying to use the computer for more than one Operating System (Multi-Boot).

Equipment:

does the computer contain conventional hardware, or are there special considerations such as USB or PCMCIA devices.

Preferences:

what works best for you or your situation.

MandrakeSoft has gone to great lengths to simplify the installation process of their distribution on a large variety of computers, yet provide you a choice of approaches.

The Mandrake Linux distribution provides support for three primary installation methods (sources):

via CD-ROM

via Hard Disk with Linux, Windows or Reiser file systems

via Network based Services such as NFS, FTP or HTTP

In addition, there are a few variations that provide support for specific equipment:

via PCMCIA devices

via Other (Non-standard hardware)

And finally, if none of the above work with your hardware, there are a series of Alternatives which utilize different kernel versions for each of the above.

If you have time, read the file on the first Installation CD called INSTALL.htm and the one in the images directory called README for a bit more detail.



DVD-ROM and CD-ROM are synonymous within this document, except where noted.

Installation via Hard Disk has changed and now uses the Grub Boot Loader.

Installation via Network Services has changed due to the new 2.6 kernel and the number of network device drivers that need to be supported. Mandrake has split the Network Services boot image into two disk images, one to hold the kernel and message files and a second that contains the network device driver files.

Installation can also be performed for any of the available methods by using the new Bootable ISO image. This method allows the use of all three installation modes.


CD-ROM based installation is portable. With a floppy diskette and the CD-ROM set, you can install the distribution, anywhere, on any computer that has a CD-ROM drive and a floppy disk drive.

Hard Disk based installation is more for those of you that have multiple disk drives installed in the target computer, one to hold the distribution file set and a second which will contain the installed system. This would most likely be used in situations where the computer dual boots Linux and other OS's. It is not very portable, but it does afford one the ability to install Linux without disturbing the existing OS and it is very fast.

Network based installation is where the flexibility of the Automated Installation process really shines. One computer holds the distribution file set, all other computers only require network based access to the file set. Now I can just carry a single CD-ROM and a diskette to hold the configuration file or 2 diskettes, insert in the desired computer, push reset and go for coffee (almost - the 2 diskettes require that I hang around until the installer prompts me for the second diskette).

With the three options, NFS, FTP and HTTP, you can actually install files from one computer to another, anywhere in the world. However, there are performance and reliability issues which you will have to be prepared to deal with when accessing servers outside your own local world.

There are three installation modes that may be employed for each of the methods:

Manual

this mode is where you select every thing interactively. Most people use this method when they are installing the distribution on their personal workstation computer.

Fully Automated

this mode is where all selections are predetermined, the installation process is controlled, without manual intervention, by the contents of a simple configuration file and, progress is indicated by simple text messages. It is ideally suited for installations on identical computers. Creative individuals using the postInstall features can overcome most obstacles.

Replay

this mode is very similar to the fully automated mode, except that progress is indicated via a graphical presentation and, the configuration file provides you with the ability to manually intervene during certain steps. You will love this one for situations where the computers are virtually identical, but you would normally have created a custom install disk to deal with certain hardware peculiarities or, you have a need to perform customization with each installation.

As I indicated earlier, you are going to have to make some choices that fit your situation and environment. The beauty of all these Choices is that you are not stuck doing it one way....

Getting Started

Before getting started, you should review the descriptions of the various Installation Mediums (diskette, CD-ROM) in the sections following this one.

The simplest approach to get started is to perform a Manual Install, then generate the desired Auto Install diskette. However, before you get started, please check the Errata page on the Mandrake web site (www.linux-mandrake.com) since there may be information there that applies to your equipment. The following are a brief set of steps to get you started.

1.

decide if you are going to perform a CD-ROM, Hard Disk or Network based install. If you are going to do a CD-ROM install, then skip the next step.

2.

copy the contents of all three CD-ROMs (or single DVD), or obtain the file set via ftp and:

a)

For a Hard Disk, make sure that the Mandrake Linux file set is present on one of the computer's hard disks (partitions). Remember to retain the CD's directory hierarchy. Also, this method requires that you place the files on one of three types of file systems: Linux (ext2), Windows (vfat) or Reiser (a journaling file system).

b)

For network services, make sure the Mandrake Linux file set is accessible on the server you want to use. (see section Setting up a Simple NFS Server). Remember to retain the CD's directory hierarchy.

3.

Create a boot floppy disk(s) using the appropriate image file(s):

images/cdrom.img for a CD-ROM based install (only if your computer can not boot from CD-ROM).

images/hd_grub.img for a Hard Disk based install

images/network.img and images/network_drivers.img for a Network Services based install.

Or create a CD-ROM using the images/boot.iso for an install using any of the available methods.

See the INSTALL.txt and the images/README files for instructions on how to create the diskette(s). Also you will find additional / alternate images to use which may resolve situations for your particular equipment setup.

4.

Boot the computer and perform the installation manually.

5.

JUST before re-booting, select 'Advanced', then select 'Generate an auto install floppy', then pick either 'Replay' or 'Automated'. This will create the needed diskette(s) containing all the basic files you will need for the next installation.

6.

Review the contents of the diskette(s) and adjust as necessary before using. See the remainder of this document.

7.

Install any where, any time and as often as you like, or until the coffee runs out.

There are a number of different and innovative approaches that you could use rather than the simplistic one above, but then that your job, eh? However, for those of you who are a bit braver or, just want to do it your self then you should see the section Scratch Built Auto Install Diskette for a examples of various customized approaches.

For those of you who were so excited about installing and test driving the new Mandrake Linux release that you forgot to 'Generate an auto install floppy', no problem. Mandrake Linux has a tool available, as part of the drakconf program (Mandrake Control Center), that will allow you to generate an Auto Install disk at any time after the initial installation, see the section Replay Install for details. Or you can get a copy of the auto_inst.cfg.pl file located in the directory /root/drakx.

Installation Mediums

In addition to the standard CD-ROM and DVD installations that most users are familiar with, Auto Installation makes use of floppy diskettes and CD-ROMs to initiate and control the installation process. The next three sections describe the contents of the diskette(s) that you generated at the end of the manual installation process described in the previous section.

Contents of the Install Diskette

After completing the 'Generate an auto install floppy' step (using the cdrom, network or pcmcia images), you should have a diskette (two for Network Services based installs) containing the following files:

advanced.msg

This file contains some text that describes a number of advanced options. You could customize this.

auto_inst.cfg

This file contains your selections. See the section Anatomy of the 'auto_inst.cfg' File for details. For Network Services based installs, this file is on the second diskette. In case you were wondering, you will also find this file in the /root/drakx directory with the name auto_inst.cfg.pl.

boot.msg

This file contains a graphic image that appears as soon as you boot from the diskette. You could customize this.

help.msg

This file contains some text regarding the start up options and keys, which you can customize too. It is optional and may not be present on your generated diskette (space limitations).

ldlinux.sys

This is what booted (boot loader). Don't mess with it.

cdrom.rdz or hd.rdz or network.rdz

The file name is dependent on the Method you used to perform the manual install. It contains stage 1 of DrakX and other things which are needed for the automated install.

syslinux.cfg

This file contains information that controls the operation of the 'ldlinux' boot loader. You may have to modify this. See the section Anatomy of the Boot Loader Configuration Files for details.

vmlinuz

This is the compressed Linux kernel image file. Don't mess with this one either.

modules.mar

This file contains all the possible network device drivers supported by the Stage1 installer. It is only present on the second diskette of Network Services based install diskette set.

Contents of the HD_Grub Boot Diskette

After completing the 'Generate an auto install floppy' step (using the hd_grub image), you should have a diskette containing the following files:

auto_inst.cfg

This file contains your selections. See the section Anatomy of the 'auto_inst.cfg' File for details. In case you were wondering, you will also find this file in the /root/drakx directory with the name auto_inst.cfg.pl.

menu.lst

This file contains information that controls the operation of the 'grub' boot loader. You may have to modify this. See the section Anatomy of the Boot Loader Configuration Files for details. MandrakeSoft has a web page, http://qa.mandrakesoft.com/hd_grub.cgi, that you should use to help with setting specific parameters need to boot your computer's hardware.

stage1

This is used to load and run stage2. Do not mess with it

stage2

This is the actual Grub Boot Loader program. Do not mess with it either.



Contents of the Boot CD-ROM and Diskette

After completing the 'Generate an auto install floppy' step, the only file, on the diskette, that is important is:

auto_inst.cfg

This file contains your selections. See the section Anatomy of the 'auto_inst.cfg' File for details. In case you were wondering, you will also find this file in the /root/drakx directory with the name auto_inst.cfg.pl.

After creating a CD-ROM from the boot.iso file, you should have a CD-ROM containing the following files in the isolinux/ directory:

advanced.msg

This file contains some text that describes a number of advanced options. You could customize this.

boot.cat

This file contains information for the isolinux boot loader. Don't mess with it.

boot.msg

This file contains a graphic image that appears as soon as you boot from the diskette. You could customize this.

help.msg

This file contains some text regarding the start up options and keys, which you can customize too.

isolinux.bin

This is what booted (boot loader). Don't mess with it.

isolinux.cfg

This file contains information that controls the operation of the 'isolinux' boot loader. You may have to modify this. See the section Anatomy of the Boot Loader Configuration Files for details.

alt0 and alt1

Are directories containing the following files:

all.rdz

It contains stage 1 of DrakX and other things which are needed for the install.

vmlinuz

This is the compressed Linux kernel image file. Don't mess with this one either.

test

directory containing the memory test program (Press F2 on boot to access).



The contents of the files, syslinux.cfg, menu.lst, isolinux.cfg and auto_inst.cfg, are what the bulk of this document is about, so with out further a due....










PrevHome Next
Introduction   Anatomy of the Boot Loader Configuration Files