Ensurepass

3. Installation
3.1 Installation Types/Classes
1. Server
o Space Requirements
1. Minimum (no GUI) — 1 GB
2. Everything (no GUI) — 1.3 GB
3. Everything, including GUI (KDE & GNOME) — 2 GB
o 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
o Removes all existing partitions/OSes
2. Workstation
o Space Requirements
1. KDE or GNOME — 1.5 GB
2. KDE & GNOME — 1.8 GB
o 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
o xinetd no longer installed by default. Increases security.
o Previously installed OSes are left intact
o Deletes all existing ext2 and ext3 partitions
o Will be configured to dual boot if another OS is present
3. Laptop
o Space Requirements — Same as Workstation
o File System Setup — Same as Workstation
o xinetd no longer installed by default. Increases security.
o Previously installed OSes are left intact.
o Deletes all existing ext2 and ext3 partitions
o Will be configured to dual boot if another OS is present.
o Installs laptop related packages (card services, etc.)
4. Custom
o Space Requirements
1. Minimum — 350 MB
2. Everything — 3.4 GB
o 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.
o Most flexible installation method.
5. Upgrade
o Existing installation must be at least RH 3.0.3.
o Existing data is not lost.
o Upgrades the kernel and all currently installed software packages.
3.2 Installation Sources
1. CD-ROM
o Most convenient method.
o Can boot directly from CD-ROM, or create a boot floppy from boot.img/pcmcia.img.
2. NFS
o Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
o Allows for simultaneous installations on multiple machines.
3. FTP
o Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
o Allows for simultaneous installations on multiple machines.
o Handles more simultaneous installations than NFS.
4. HTTP
o Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
o Allows for simultaneous installations on multiple machines.
5. Samba
o Create network boot floppy from bootnet.img (or pcmcia.img for laptops).
o Allows for simultaneous installations on multiple machines.
6. Local hard drive
o Create boot floppy from boot.img.
3.3 Installation Method
1. GUI
o Most user friendly.
o Only available for NFS or CD-ROM installations.
2. Text Mode
o Used for http, samba, and ftp installs.
o Can be used for other installs if chosen.
o Type “linux text” at boot prompt to enter text mode.
3. Expert Mode
o Permits manual setup of hardware devices.
o Type “linux expert” at boot prompt to enter expert mode.
4. Kickstart
o Automated installation.
o Must create a Kickstart configuration file(ks.cfg) describing the install.
o 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.
o 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!
1. Requirements
o Enough space on FAT partition for install.
o A boot disk is necessary since LILO will not be installed.
o FAT partition must be formatted prior to installation.
2. Setup
During the install, choose an existing FAT partition and assign your / partition to it.
3. Limitations
o System will be slower.
o Cannot have multiple partitions dedicated to Linux.
o 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.
1. From DOS — use RAWRITE.COM and follow the prompts.
2. From Linux — dd if=image of=/dev/fd0 bs=1k
3. Available images:
o bootnet.img – Used for network based install.
o boot.img – Used for CD-ROM and hard drive based install.
o pcmcia.img – Used for installing on laptop machines.
o pcmciadd.img – PCMCIA Driver disk.
o drvblock.img – Additional block drivers.
o drvnet.img – Additional network drivers.
o oldcdrom.img – Additional CD-ROM drivers.
3.6 Starting the installation from DOS.
Execute the following on the CD-ROM: E:DOSUTILSAUTOBOOT.BAT
3.7 Partitioning
1. Manual
o Allows user to customize partitions.
o 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.
2. Automatic
Partitions are automatically configured according to installation type as described above.
3. Partition Types
o Linux Native = 83
o Linux Swap = 82
3.8 Rescue Mode
1. RH 6.x – Requires boot.img and rescue.img
2. RH 7.x – Must be booted from CD-ROM
3. 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.)
3.10 Package Selection
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.

Download the Ensurepass Latest 2013 RHCE EX300 Practise Test PDF to pass RHCE EX300 exam.

Comments are closed.