Steve's RHCE Study Guide: Installation

Next Previous Contents

3.1 Installation Types/Classes

Server
- Space Requirements
  1. Minimum (no GUI) -- 1 GB
  2. Everything (no GUI) -- 1.3 GB
  3. Everything, including GUI (KDE & GNOME) -- 2 GB
- File System Setup
  1. / = 384 MB
  2. /boot = 50 MB (Intel arch only)
  3. /dos = 16 MB (Alpha arch only)
  4. /var = 256 MB
  5. /home = 512 MB minimum
  6. /usr = 1400 MB minimum
  7. swap = 1 - 2x RAM depending on available disk space
- Removes all existing partitions/OSes
Workstation
- Space Requirements
  1. KDE or GNOME -- 1.5 GB
  2. KDE & GNOME -- 1.8 GB
- File System Setup
  1. / = 1100 MB minimum
  2. /boot = 50 MB (Intel arch only)
  3. /dos = 16 MB (Alpha arch only)
  4. swap = 1 - 2x RAM depending on available disk space
- xinetd no longer installed by default. Increases security.
- Previously installed OSes are left intact
- Deletes all existing ext2 and ext3 partitions
- Will be configured to dual boot if another OS is present
Laptop
- Space Requirements -- Same as Workstation
- File System Setup -- Same as Workstation
- xinetd no longer installed by default. Increases security.
- Previously installed OSes are left intact.
- Deletes all existing ext2 and ext3 partitions
- Will be configured to dual boot if another OS is present.
- Installs laptop related packages (card services, etc.)
Custom
- Space Requirements
  1. Minimum -- 350 MB
  2. Everything -- 3.4 GB
- File System Layout
  With automatic partitioning:
  1. / = 700 MB
  2. /boot = 50 MB (Intel arch only)
  3. /dos = 16 MB (Alpha arch only)
  4. swap = 1 - 2x RAM depending on available disk space
  If automatic partitioning is not chosen, then the user configures the layout.
- Most flexible installation method.
Upgrade
- Existing installation must be at least RH 3.0.3.
- Existing data is not lost.
- Upgrades the kernel and all currently installed software packages.

3.2 Installation Sources

CD-ROM
- Most convenient method.
- Can boot directly from CD-ROM, or create a boot floppy from boot.img/pcmcia.img.
NFS
- Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
- Allows for simultaneous installations on multiple machines.
FTP
- Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
- Allows for simultaneous installations on multiple machines.
- Handles more simultaneous installations than NFS.
HTTP
- Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
- Allows for simultaneous installations on multiple machines.
Samba
- Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
- Allows for simultaneous installations on multiple machines.
Local hard drive
- Create boot floppy from boot.img.

3.3 Installation Method

GUI
- Most user friendly.
- Only available for NFS or CD-ROM installations.
Text Mode
- Used for http, samba, and ftp installs.
- Can be used for other installs if chosen.
- Type "linux text" at boot prompt to enter text mode.
Expert Mode
- Permits manual setup of hardware devices.
- Type "linux expert" at boot prompt to enter expert mode.
Kickstart
- Automated installation.
- Must create a Kickstart configuration file(ks.cfg) describing the install.
- ks.cfg can be located locally, or on the network.
  1. Local - floppy, cd-rom, or hard drive.
  2. Network - Must be located on an NFS server. Requires DHCP to be configured and used.
- Installation source can be CD-ROM, http, ftp, or nfs.

3.4 Partition-less Installs

Partitionless installs allow the user to install on an existing FAT partition. In this case FAT refers to a regular FAT or a FAT32 partition. This installation method is not recommended!

Requirements
- Enough space on FAT partition for install.
- A boot disk is necessary since LILO will not be installed.
- FAT partition must be formatted prior to installation.
Setup
During the install, choose an existing FAT partition and assign your / partition to it.
Limitations
- System will be slower.
- Cannot have multiple partitions dedicated to Linux.
- Requires boot disk.

3.5 Creating Disk Images

The boot images are stored on the CD under /images. Images can be created from DOS or in Linux.

From DOS -- use RAWRITE.COM and follow the prompts.
From Linux -- dd if=image of=/dev/fd0 bs=1k
Available images:
- bootnet.img - Used for network based install.
- boot.img - Used for CD-ROM and hard drive based install.
- pcmcia.img - Used for installing on laptop machines.
- pcmciadd.img - PCMCIA Driver disk.
- drvblock.img - Additional block drivers.
- drvnet.img - Additional network drivers.
- oldcdrom.img - Additional CD-ROM drivers.

3.6 Starting the installation from DOS.

Execute the following on the CD-ROM: E:\DOSUTILS\AUTOBOOT.BAT

3.7 Partitioning

Manual
- Allows user to customize partitions.
- Can use either FDISK or Disk Druid:
  1. Disk Druid
    - Easier to use.
    - Only available at install time.
    - Allows easy configuration for RAID devices.
  2. FDISK
    - Always available.
    - Greater learning curve than Disk Druid.
    - Offers more features than Disk Druid.
Automatic
Partitions are automatically configured according to installation type as described above.
Partition Types
- Linux Native = 83
- Linux Swap = 82

3.8 Rescue Mode

RH 6.x - Requires boot.img and rescue.img
RH 7.x - Must be booted from CD-ROM
Existing filesystem will be mounted under /mnt/sysimage (7.x only)

3.9 Boot Disks

Use mkbootdisk to create a boot floppy. You must specify a device and a kernel to use.

mkbootdisk --device /dev/fd0 `uname -r`
mkbootdisk `uname -r`                     # Same as above.  Default device is /dev/fd0

(Note: `uname -r` returns the kernel version.)

Custom installations allow you to choose which package groups and/or packages you wish to install. Package groups are defined in /RedHat/base/comps. You can modify existing groups and define your own package groups.