Installation Guide
Installing Red Hat Enterprise Linux 5 for all architectures
Abstract
Part I. x86, AMD64, Intel® 64 and Itanium - Installation and Booting
Chapter 1. Itanium System Specific Information
1.1. Itanium System Installation Overview
- Boot into the Extensible Firmware Interface (EFI) Shell.
- If you cannot boot from the CD-ROM, make an LS-120 diskette from the boot image file provided with Red Hat Enterprise Linux.
- Using the EFI Shell and the ELILO boot loader, load and run the kernel, and boot into the Red Hat Enterprise Linux installation program.
1.2. Itanium Systems — The EFI Shell
edit
, type
, cp
, rm
, and mkdir
. For a list of utilities and other commands, type help
at the EFI Shell prompt.
http://developer.intel.com/technology/efi/index.htm
1.2.1. Itanium Systems — EFI Device Names
map
command can be used to list all devices and file systems that EFI can recognize. When your Itanium system boots into the EFI shell, it probes your system in the following order:
- LS-120 drive (if it contains media)
- IDE hard drives on the primary IDE interface
- IDE hard drives on the secondary IDE interface
- SCSI hard drives on the SCSI interface
- CD-ROM drives on the IDE interface
- CD-ROM drives on the SCSI interface
map
map
command might look like the following:
Device mapping table fs0 : VenHw(Unknown Device:00)/HD(Part1,Sig00000000) fs1 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) fs2 : VenHw(Unknown Device:FF)/CDROM(Entry1)/HD(Part1,Sig00000000) blk0 : VenHw(Unknown Device:00) blk1 : VenHw(Unknown Device:00)/HD(Part1,Sig00000000) blk2 : VenHw(Unknown Device:80) blk3 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) blk4 : VenHw(Unknown Device:80)/HD(Part2,Sig00000000) blk5 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000) blk6 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000)/HD(Part1,Sig725F7772) blk7 : VenHw(Unknown Device:FF) blk8 : VenHw(Unknown Device:FF)/CDROM(Entry1) blk9 : VenHw(Unknown Device:FF)/CDROM(Entry1)/HD(Part1,Sig00000000)
fs
are FAT16 file systems that EFI can read. All the listings beginning with blk
are block devices that EFI recognizes. Both the file systems and block devices are listed in the order they are probed. Therefore, fs0
is the system partition on the LS-120, fs1
is the system partition on the hard drive, and fs2
is the system partition on the CD-ROM.
1.2.2. Itanium Systems — EFI System Partition
/boot/efi/
. This partition contains the installed Linux kernel(s) as well as the ELILO configuration file (elilo.conf
). The elilo.conf
file contains a list of kernels from which you can boot your system.
Chapter 2. Steps to Get You Started
2.1. Upgrade or Install?
2.2. Is Your Hardware Compatible?
http://hardware.redhat.com/hcl/
2.3. Do You Have Enough Disk Space?
/
and swap
) must be dedicated to Red Hat Enterprise Linux. For Itanium systems, at least three partitions (/
, /boot/efi/
, and swap
) must be dedicated to Red Hat Enterprise Linux.
- have enough unpartitioned[1] disk space for the installation of Red Hat Enterprise Linux, or
- have one or more partitions that may be deleted, thereby freeing up enough disk space to install Red Hat Enterprise Linux.
2.4. Can You Install Using the CD-ROM or DVD?
- Insert a blank, writeable CD into your computer's CD or DVD burner. On some computers, a window opens and displays various options when you insert the disc. If you see a window like this, look for an option to launch your chosen disc burning program. If you do not see an option like this, close the window and launch the program manually.
- Launch your disc burning program. On some computers, you can do this by right-clicking (or control-clicking) on the image file and selecting a menu option with a label like Copy image to CD, or Copy CD or DVD image. Other computers might provide you with a menu option to launch your chosen disc burning program, either directly or with an option like . If none of these options are available on your computer, launch the program from an icon on your desktop, in a menu of applications such as the menu on Windows operating systems, or in the Mac
Applications
folder. - In your disc burning program, select the option to burn a CD from an image file. For example, in Nero Burning ROM, this option is called and is located on the menu.Note that you can skip this step when using certain CD burning software; for example, Disk Utility on Mac OS X does not require it.
- Browse to the disc image file that you downloaded previously and select it for burning.
- Click the button that starts the burning process.
2.4.1. Alternative Boot Methods
- Boot DVD/CD-ROM
- If you can boot using the DVD/CD-ROM drive, you can create your own CD-ROM to boot the installation program. This may be useful, for example, if you are performing an installation over a network or from a hard drive. Refer to Section 2.4.2, “Making an Installation Boot CD-ROM” for further instructions.
- USB pen drive
- If you cannot boot from the DVD/CD-ROM drive, but you can boot using a USB device, such as a USB pen drive, the following alternative boot method is available.Your system firmware must support booting from a USB device in order for this boot method to work. Refer to the hardware vendor's documentation for details on specifying the device from which the system boots.
Important
When configuring partitions and file systems during installation, ensure you verify the USB device's size, name, and type. The order in which names are assigned to USB-attached storage devices can vary because certain devices may take longer to initialize than others. Consequently, a device may receive a different name than you expect, such assdc
instead ofsda
.- Make a copy of the Red Hat Enterprise Linux 5 installation files available. Either:
- Insert the Red Hat Enterprise Linux 5 installation DVD or CD-ROM#1.
- Mount an image of the Red Hat Enterprise Linux 5 installation DVD or CD-ROM#1.
- Ensure that the installation files are available on a network location accessible by your system, for example, on an NFS share that it can access.
- Attach a USB flash drive to your system. The following steps presume a system that runs Red Hat Enterprise Linux 5.
- Run
dmesg
to identify the device name for the drive. If you rundmesg
shortly after you attach the drive, the device name appears in the most recent lines of output. For example, the followingdmesg
output shows a flash drive that receives the device name/dev/sdb
:Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. Vendor: USB 2.0 Model: Flash Disk Rev: 5.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 2043904 512-byte hdwr sectors (1046 MB) sdb: Write Protect is off sdb: Mode Sense: 0b 00 00 08 sdb: assuming drive cache: write through SCSI device sdb: 2043904 512-byte hdwr sectors (1046 MB) sdb: Write Protect is off sdb: Mode Sense: 0b 00 00 08 sdb: assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: Attached scsi removable disk sdb sd 2:0:0:0: Attached scsi generic sg1 type 0 usb-storage: device scan complete
- Unmount any partitions on the flash drive that are currently mounted. It is likely that your system automatically mounted any available partitions when you attached the flash drive.
- Use the
mount
command to find any mounted partitions on the flash drive. For example, the following output shows a single partition on/dev/sdb
is mounted, the partition named/dev/sdb1
:$ mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sda1 on /boot type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/sdb1 on /media/BOOTUSB type vfat (rw,nosuid,nodev,uid=500,utf8,shortname=mixed,flush)
- Unmount partitions with the
umount
command. For example, to unmount/dev/sdb1
, run:umount /dev/sdb1
Runumount
for each partition on the flash drive that is mounted.
- Use
fdisk
to partition the flash drive to contain a single partition only, with the following parameters:- numbered
1
. - partition type is set to
b
(W95 FAT32). - flagged as bootable.
- Run
mkdosfs
to format the partition created in the previous step as FAT. For example:mkdosfs /dev/sdb1
- Mount the partition. For example:
mount /dev/sdb1 /mnt
- Copy the contents of the
isolinux/
directory of the installation DVD or CD-ROM#1 onto the flash drive. - Rename the configuration file from
isolinux.cfg
tosyslinux.cfg
. For example, if the flash drive is mounted on/mnt
, run:cd /mnt/; mv isolinux.cfg syslinux.cfg
- If necessary, edit
syslinux.cfg
for your particular environment. For example, to configure the installation to use a kickstart file shared over NFS, specify:linux ks=nfs:://ks.cfg
- Copy the
images/pxeboot/initrd.img
file from the installation DVD or CD-ROM#1 onto the flash drive. - Unmount the flash drive. For example:
umount /dev/sdb1
- Make the USB flash drive bootable. For example:
syslinux /dev/sdb1
- Mount the flash drive again. For example:
mount /dev/sdb1 /mnt
- Install the GRUB boot loader on the USB flash drive. For example:
grub-install --root-directory=/mnt /dev/sdb
- Verify that the USB flash drive has a /boot/grub directory. If it does not, create the directory manually; for example:
mkdir -p /mnt/boot/grub
- Create the
boot/grub/grub.conf
file on the flash drive as follows:default=0 timeout=5 root (hd1,0) title Red Hat Enterprise Linux installer kernel /vmlinuz initrd /initrd.img
- Unmount the flash drive. For example:
umount /dev/sdb1
- Detach the USB flash drive.
- Attach the USB disk to the system on which you wish to install Red Hat Enterprise Linux.
- Boot the target system from the USB flash drive.
2.4.2. Making an Installation Boot CD-ROM
isolinux
(not available for Itanium systems) is used for booting the Red Hat Enterprise Linux installation CD. To create your own CD-ROM to boot the installation program, use the following instructions:
isolinux/
directory from the Red Hat Enterprise Linux DVD or CD #1 into a temporary directory (referred to here as <path-to-workspace>
) using the following command:
cp -r <path-to-cd>/isolinux/
<path-to-workspace>
<path-to-workspace>
directory you have created:
cd <path-to-workspace>
chmod u+w isolinux/*
mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot \ -boot-load-size 4 -boot-info-table -R -J -v -T isolinux/
Note
file.iso
and located in <path-to-workspace>
) to a CD-ROM as you normally would.
2.5. Preparing for a Network Installation
Note
boot:
prompt (prepend with elilo
for Itanium systems):
linux mediacheck
Note
/location/of/disk/space
. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as /publicly/available/directory. For example, /location/of/disk/space
may be a directory you create called /var/isos
. /publicly/available/directory
might be /var/www/html/rhel5
, for an HTTP install.
- Create an iso image from the installation disk(s) using the following command (for DVDs):
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
where dvd refers to your DVD drive device.
2.5.1. Preparing for FTP and HTTP installation
RELEASE-NOTES
files and all files from the RedHat
directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD-ROM/ISO image):
- Insert CD-ROM or DVD-ROM.
mount /media/cdrom
- If you are installing the Server variant, run
cp -a /media/cdrom/Server <target-directory>
If you are installing the Client variant, runcp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory>
(Installation CD 1 or DVD only)cp /media/cdrom/images <target-directory>
(Installation CD 1 or DVD only)umount /media/cdrom
<target-directory>
represents the path to the directory to contain the installation tree.)
Note
/publicly/available/directory
directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
2.5.2. Preparing for an NFS install
- For DVD:
mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
- For CDROMs:
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory
directory is exported via NFS via an entry in /etc/exports
.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start
). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload
).
2.6. Preparing for a Hard Drive Installation
Note
- Using a set of CD-ROMs, or a DVD — Create ISO image files from each installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), execute the following command on a Linux system:
dd if=/dev/cdrom of=/tmp/file-name.iso
- Using ISO images — transfer these images to the system to be installed.Verifying that ISO images are intact before you attempt an installation, helps to avoid problems. To verify the ISO images are intact prior to performing an installation, use an
md5sum
program (manymd5sum
programs are available for various operating systems). Anmd5sum
program should be available on the same Linux machine as the ISO images.
Note
boot:
prompt (prepend with elilo
for Itanium systems):
linux mediacheck
updates.img
exists in the location from which you install, it is used for updates to anaconda
, the installation program. Refer to the file install-methods.txt
in the anaconda
RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
Chapter 3. System Specifications List
- hard drive(s): type, label, size; e.g. IDE hda=40 GB
- partitions: map of partitions and mount points; e.g.
/dev/hda1=/home
,/dev/hda2=/
(fill this in once you know where they will reside) - memory: amount of RAM installed on your system; e.g. 512 MB, 1 GB
- CD-ROM: interface type; e.g. SCSI, IDE (ATAPI)
- SCSI adapter: if present, make and model number; e.g. BusLogic SCSI Adapter, Adaptec 2940UW
- network card: if present, make and model number; e.g. Tulip, 3COM 3C590
- mouse: type, protocol, and number of buttons; e.g. generic 3 button PS/2 mouse, MouseMan 2 button serial mouse
- monitor: make, model, and manufacturer specifications; e.g. Optiquest Q53, ViewSonic G773
- video card: make, model number and size of VRAM; e.g. Creative Labs Graphics Blaster 3D, 8MB
- sound card: make, chipset and model number; e.g. S3 SonicVibes, Sound Blaster 32/64 AWE
- IP, DHCP, and BOOTP addresses
- netmask
- gateway IP address
- one or more name server IP addresses (DNS)
- domain name: the name given to your organization; e.g.
example.com
- hostname: the name of your computer; your personal choice of names; e.g.
cookie
,southpark
Chapter 4. Installing on Intel® and AMD Systems
- Becoming familiar with the installation program's user interface
- Starting the installation program
- Selecting an installation method
- Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
- Finishing the installation
4.1. The Graphical Installation Program User Interface
Note
boot:
prompt:
linux text
Note
elilo linux text
4.1.1. A Note about Virtual Consoles
console | keystrokes | contents |
---|---|---|
1 | ctrl+alt+f1 | installation dialog |
2 | ctrl+alt+f2 | shell prompt |
3 | ctrl+alt+f3 | install log (messages from installation program) |
4 | ctrl+alt+f4 | system-related messages |
5 | ctrl+alt+f5 | other messages |
6 | ctrl+alt+f6 | x graphical display |
4.2. Screenshots during installation
/root/anaconda-screenshots
.
autostep --autoscreenshot
option to generate a screenshot of each step of the installation automatically. Refer to Section 31.3, “Creating the Kickstart File” for details of configuring a Kickstart file.
4.3. The Text Mode Installation Program User Interface
Note
Figure 4.1. Installation Program Widgets as seen in Boot Loader Configuration
Figure 4.2. Installation Program Widgets as seen in Disk Druid
- Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath.
- Checkbox — Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press Space to select or deselect a feature.
- Text Input — Text input lines are regions where you can enter information required by the installation program. When the cursor rests on a text input line, you may enter and/or edit information on that line.
- Text Widget — Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the Up and Down arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a # character, which moves up and down the scroll bar as you scroll.
- Scroll Bar — Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file.
- Button Widget — Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the Tab and Enter keys. Buttons can be selected when they are highlighted.
- Cursor — Although not a widget, the cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or next to the widget.
4.3.1. Using the Keyboard to Navigate
Warning
4.4. Starting the Installation Program
Note
4.4.1. Booting the Installation Program on x86, AMD64, and Intel® 64 Systems
- Red Hat Enterprise Linux DVD/CD-ROM — Your machine supports a bootable DVD/CD-ROM drive and you have the Red Hat Enterprise Linux CD-ROM set or DVD.
- Boot CD-ROM — Your machine supports a bootable CD-ROM drive and you want to perform network or hard drive installation.
- USB pen drive — Your machine supports booting from a USB device.
- PXE boot via network — Your machine supports booting from the network. This is an advanced installation path. Refer to Chapter 34, PXE Network Installations for additional information on this method.
Note
boot:
prompt should appear. The screen contains information on a variety of boot options. Each boot option also has one or more help screens associated with it. To access a help screen, press the appropriate function key as listed in the line at the bottom of the screen.
- Once the
boot:
prompt appears, the installation program automatically begins if you take no action within the first minute. To disable this feature, press one of the help screen function keys. - If you press a help screen function key, there is a slight delay while the help screen is read from the boot media.
4.4.2. Booting the Installation Program on Itanium Systems
4.4.2.1. Booting the Installation Program from the DVD/CD-ROM
- Remove all media except Red Hat Enterprise Linux CD #1.
- From themenu choose .
- At the
Shell>
prompt, change to the file system on the CD-ROM. For example, in the above samplemap
output, the system partition on the CD-ROM isfs1
. To change to thefs1
file system, typefs1:
at the prompt. - Type
elilo linux
to boot into the installation program. - Go to Chapter 4, Installing on Intel® and AMD Systems to begin the installation.
4.4.2.2. Booting the Installation Program from an LS-120 Diskette
images/boot.img
. To create this diskette in Linux, insert a blank LS-120 diskette and type the following command at a shell prompt:
dd if=boot.img of=/dev/hda bs=180k
/dev/hda
with the correct device name for the LS-120 diskette drive.
- Insert the LS-120 diskette you made from the boot image file
boot.img
. If you are performing a local CD-ROM installation but booting off the LS-120 diskette, insert the Red Hat Enterprise Linux CD #1 also. If you are performing a hard drive, NFS, FTP, or HTTP installation, you do not need the CD-ROM. - From themenu choose .
- At the
Shell>
prompt, change the device to the LS-120 drive by typing the commandfs0:
, using the examplemap
output above. - Type
elilo linux
to boot into the installation program. - Go to Chapter 4, Installing on Intel® and AMD Systems to begin the installation.
4.4.3. Additional Boot Options
elilo linux option
Note
linux text
- ISO images have an md5sum embedded in them. To test the checksum integrity of an ISO image, at the installation boot prompt, type:
linux mediacheck
The installation program prompts you to insert a CD or select an ISO image to test, and selectto perform the checksum operation. This checksum operation can be performed on any Red Hat Enterprise Linux CD and does not have to be performed in a specific order (for example, CD #1 does not have to be the first CD you verify). It is strongly recommended to perform this operation on any Red Hat Enterprise Linux CD that was created from downloaded ISO images. This command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. - Also in the
images/
directory is theboot.iso
file. This file is an ISO image than can be used to boot the installation program. To use theboot.iso
, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. You must then burn theboot.iso
file onto a recordable/rewriteable CD-ROM. linux console=<device>
For text mode installations, use:linux text console=<device>
In the above command, <device> should be the device you are using (such as ttyS0 or ttyS1). For example,linux text console=ttyS0
.Text mode installations using a serial terminal work best when the terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, Kermit '95 works well. Non-UTF-8 capable terminals works as long as only English is used during the installation process. An enhanced serial display can be used by passing theutf8
command as a boot-time option to the installation program. For example:linux console=ttyS0 utf8
4.4.3.1. Kernel Options
linux updates
linux text updates
rhupdates/
on the server.
4.5. Selecting an Installation Method
- DVD/CD-ROM
- If you have a DVD/CD-ROM drive and the Red Hat Enterprise Linux CD-ROMs or DVD you can use this method. Refer to Section 4.6, “Installing from DVD/CD-ROM”, for DVD/CD-ROM installation instructions.
- Hard Drive
- If you have copied the Red Hat Enterprise Linux ISO images to a local hard drive, you can use this method. You need a boot CD-ROM (use the
linux askmethod
boot option). Refer to Section 4.7, “Installing from a Hard Drive”, for hard drive installation instructions. - NFS
- If you are installing from an NFS server using ISO images or a mirror image of Red Hat Enterprise Linux, you can use this method. You need a boot CD-ROM (use the
linux askmethod
boot option). Refer to Section 4.9, “Installing via NFS” for network installation instructions. Note that NFS installations may also be performed in GUI mode. - FTP
- If you are installing directly from an FTP server, use this method. You need a boot CD-ROM (use the
linux askmethod
boot option). Refer to Section 4.10, “Installing via FTP”, for FTP installation instructions. - HTTP
- If you are installing directly from an HTTP (Web) server, use this method. You need a boot CD-ROM (use the
linux askmethod
boot option). Refer to Section 4.11, “Installing via HTTP”, for HTTP installation instructions.
4.6. Installing from DVD/CD-ROM
Note
4.7. Installing from a Hard Drive
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd
boot option, you already specified a partition.
Figure 4.3. Selecting Partition Dialog for Hard Drive Installation
/
. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/
, and the images are in /home/new/
, you would enter /new/
.
4.8. Performing a Network Installation
askmethod
boot option, the Configure TCP/IP dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually. If manually, you have the option to enter IPv4 and/or IPv6 information. Enter the IP address you are using during installation and press Enter. Note that you need to supply IPv4 information if you wish to perform an NFS installation.
Figure 4.4. TCP/IP Configuration
4.9. Installing via NFS
eastcoast
in the domain example.com
, enter eastcoast.example.com
in the NFS Server field.
/export/directory/
.
Figure 4.5. NFS Setup Dialog
4.10. Installing via FTP
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp
boot option, you already specified a server and path.
Figure 4.6. FTP Setup Dialog
variant/
directory for your architecture. For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
4.11. Installing via HTTP
askmethod
boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http
boot option, you already specified a server and path.
variant/
directory for your architecture. For example, if the HTTP site contains the directory /mirrors/redhat/arch/variant/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Figure 4.7. HTTP Setup Dialog
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
4.12. Welcome to Red Hat Enterprise Linux
4.13. Language Selection
Figure 4.8. Language Selection
4.14. Keyboard Configuration
Figure 4.9. Keyboard Configuration
Note
system-config-keyboard
command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue.
4.15. Enter the Installation Number
Figure 4.10. Installation Number
4.16. Disk Partitioning Setup
Warning
/var/cache/yum/
by default. If you partition the system manually, and create a separate /var/
partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
Figure 4.11. Disk Partitioning Setup
Warning
Important
mapper/mpath
instead.
4.17. Advanced Storage Options
Figure 4.12. Advanced Storage Options
Figure 4.13. Enable network Interface
Figure 4.14. Configure ISCSI Parameters
4.18. Create Default Layout
- Remove all partitions on selected drives and create default layout — select this option to remove all partitions on your hard drive(s) (this includes partitions created by other operating systems such as Windows VFAT or NTFS partitions).
Warning
If you select this option, all data on the selected hard drive(s) is removed by the installation program. Do not select this option if you have information that you want to keep on the hard drive(s) where you are installing Red Hat Enterprise Linux. - Remove Linux partitions on selected drives and create default layout — select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your hard drive(s) (such as VFAT or FAT32 partitions).
- Use free space on selected drives and create default layout — select this option to retain your current data and partitions, assuming you have enough free space available on your hard drive(s).
Figure 4.15. Create Default Layout
Warning
Note
/boot/
partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/
partition is also necessary for software RAID setups.
/boot/
partition.
4.19. Partitioning Your System
Note
Note
/boot/efi/
partition of approximately 100 MB and of type FAT (VFAT), a swap partition of at least 512 MB, and an appropriately-sized root (/
) partition.
Figure 4.16. Partitioning with Disk Druid on x86, AMD64, and Intel® 64 Systems
4.19.1. Graphical Display of Hard Drive(s)
4.19.2. Disk Druid's Buttons
- Partitions section. Selecting opens a dialog box. Some or all of the fields can be edited, depending on whether the partition information has already been written to disk.: Used to modify attributes of the partition currently selected in theYou can also edit free space as represented in the graphical display to create a new partition within that space. Either highlight the free space and then select thebutton, or double-click on the free space to edit it.
- To make a RAID device, you must first create (or reuse existing) software RAID partitions. Once you have created two or more software RAID partitions, selectto join the software RAID partitions into a RAID device.
- Current Disk Partitions section. You will be asked to confirm the deletion of any partition.: Used to remove the partition currently highlighted in the
- Disk Druid to its original state. All changes made will be lost if you the partitions.: Used to restore
- It should only be used if you have experience using RAID. To read more about RAID, see the Red Hat Enterprise Linux Deployment Guide.: Used to provide redundancy to any or all disk partitions.To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, selectto join the software RAID partitions into a RAID device.
- It should only be used if you have experience using LVM. To read more about LVM, see the Red Hat Enterprise Linux Deployment Guide. Note, LVM is only available in the graphical installation program.: Allows you to create an LVM logical volume. The role of LVM (Logical Volume Manager) is to present a simple logical view of underlying physical storage space, such as a hard drive(s). LVM manages individual physical disks — or to be more precise, the individual partitions present on them.To create an LVM logical volume, you must first create partitions of type physical volume (LVM). Once you have created one or more physical volume (LVM) partitions, selectto create an LVM logical volume.
4.19.3. Partition Fields
- Device: This field displays the partition's device name.
- Mount Point/RAID/Volume: A mount point is the location within the directory hierarchy at which a volume exists; the volume is "mounted" at this location. This field indicates where the partition is mounted. If a partition exists, but is not set, then you need to define its mount point. Double-click on the partition or click the button.
- Type: This field shows the partition's file system type (for example, ext2, ext3, or vfat).
- Format: This field shows if the partition being created will be formatted.
- Size (MB): This field shows the partition's size (in MB).
- Start: This field shows the cylinder on your hard drive where the partition begins.
- End: This field shows the cylinder on your hard drive where the partition ends.
4.19.4. Recommended Partitioning Scheme
4.19.4.1. Itanium systems
- A
/boot/efi/
partition (100 MB minimum) — the partition mounted on/boot/efi/
contains all the installed kernels, the initrd images, and ELILO configuration files.Warning
You must create a/boot/efi/
partition of type VFAT and at least 100 MB in size as the first primary partition. - A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing.In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, we recommend determining system swap using the following table.
Table 4.2. Recommended System Swap Space Amount of RAM in the System Recommended Amount of Swap Space 4GB of RAM or less a minimum of 2GB of swap space 4GB to 16GB of RAM a minimum of 4GB of swap space 16GB to 64GB of RAM a minimum of 8GB of swap space 64GB to 256GB of RAM a minimum of 16GB of swap space 256GB to 512GB of RAM a minimum of 32GB of swap space Note that you can obtain better performance by distributing swap space over multiple storage devices, particularly on systems with fast drives, controllers, and interfaces. - A root partition (3.0 GB - 5.0 GB) — this is where "
/
" (the root directory) is located. In this setup, all files (except those stored in/boot/efi
) are on the root partition.A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.
4.19.4.2. x86, AMD64, and Intel® 64 systems
- A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing.In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, we recommend determining system swap using the following table.
Table 4.3. Recommended System Swap Space Amount of RAM in the System Recommended Amount of Swap Space 4GB of RAM or less a minimum of 2GB of swap space 4GB to 16GB of RAM a minimum of 4GB of swap space 16GB to 64GB of RAM a minimum of 8GB of swap space 64GB to 256GB of RAM a minimum of 16GB of swap space 256GB to 512GB of RAM a minimum of 32GB of swap space Note that you can obtain better performance by distributing swap space over multiple storage devices, particularly on systems with fast drives, controllers, and interfaces. - A
/boot/
partition (250 MB) — the partition mounted on/boot/
contains the operating system kernel (which allows your system to boot Red Hat Enterprise Linux), along with files used during the bootstrap process. Due to limitations, creating a native ext3 partition to hold these files is required. For most users, a 250 MB boot partition is sufficient.Note
If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a/boot/
partition if you want the/
(root) partition to use all of the remaining space on your hard drive.Note
If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the/boot/
partition must be created on a partition outside of the RAID array, such as on a separate hard drive. - A
root
partition (3.0 GB - 5.0 GB) — this is where "/
" (the root directory) is located. In this setup, all files (except those stored in/boot
) are on the root partition.A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups. - A
home
partition (at least 100 MB) — for storing user data separately from system data. This will be a dedicated partition within a volume group for the/home
directory. This will enable you to upgrade or reinstall Red Hat Enterprise Linux without erasing user data files.
Warning
/var
on a network filesystem (for example, NFS, iSCSI, or NBD) The /var
directory contains critical data that must be read from or written to during the boot process before establishing network services.
/var/spool
, /var/www
or other subdirectories on a separate network disk, just not the complete /var
filesystem.
4.19.5. Adding Partitions
Note
Figure 4.17. Creating a New Partition
- Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter
/
; enter/boot
for the/boot
partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set - setting the filesystem type to swap is sufficient. - File System Type: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to Section 4.19.5.1, “File System Types”.
- Allowable Drives: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is not checked, then the partition will never be created on that hard disk. By using different checkbox settings, you can have Disk Druid place partitions where you need them, or let Disk Druid decide where partitions should go.
- Size (MB): Enter the size (in megabytes) of the partition. Note, this field starts with 100 MB; unless changed, only a 100 MB partition will be created.
- Additional Size Options: Choose whether to keep this partition at a fixed size, to allow it to "grow" (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard drive space available.If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use.
- Force to be a primary partition: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to Section 26.1.3, “Partitions within Partitions — An Overview of Extended Partitions”, for more information.
- Encrypt: Choose whether to encrypt the partition so that the data stored on it cannot be accessed without a passphrase, even if the storage device is connected to another system. Refer to Chapter 29, Disk Encryption Guide for information on encryption of storage devices. If you select this option, the installer prompts you to provide a passphrase before it writes the partition to the disk.
4.19.5.1. File System Types
- ext3 — The ext3 file system is based on the ext2 file system and has one main advantage — journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to
fsck
[2] the file system. A maximum file system size of 16TB is supported for ext3. The ext3 file system is selected by default and is highly recommended. - ext2 — An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters.
- physical volume (LVM) — Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. For more information regarding LVM, see the Red Hat Enterprise Linux Deployment Guide.
- software RAID — Creating two or more software RAID partitions allows you to create a RAID device. For more information regarding RAID, see chapter RAID (Redundant Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide.
- swap — Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. See the Red Hat Enterprise Linux Deployment Guide for additional information.
- vfat — The VFAT file system is a Linux file system that is compatible with Microsoft Windows long filenames on the FAT file system. This file system must be used for the
/boot/efi/
partition on Itanium systems.
4.19.6. Editing Partitions
Note
4.19.7. Deleting a Partition
4.20. x86, AMD64, and Intel® 64 Boot Loader Configuration
Figure 4.18. Boot Loader Configuration
Warning
Red Hat Enterprise Linux
(for GRUB). Other partitions may also have boot labels. To add or change the boot label for other partitions that have been detected by the installation program, click once on the partition to select it. Once selected, you can change the boot label by clicking the button.
Note
Important
Important
4.20.1. Advanced Boot Loader Configuration
- The master boot record (MBR) — This is the recommended place to install a boot loader, unless the MBR already starts another operating system loader, such as System Commander. The MBR is a special area on your hard drive that is automatically loaded by your computer's BIOS, and is the earliest point at which the boot loader can take control of the boot process. If you install it in the MBR, when your machine boots, GRUB presents a boot prompt. You can then boot Red Hat Enterprise Linux or any other operating system that you have configured the boot loader to boot.
Figure 4.19. Boot Loader Installation
Note
/boot/
partition was created.
/boot/
partition. If you have a system which supports the LBA32 extension for booting operating systems above the 1024 cylinder limit, and you want to place your /boot/
partition above cylinder 1024, you should select this option.
Note
/boot
Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
parted
, 1024 cylinders equals 528MB. For more information, refer to:
http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html
Important
/dev/mapper/mpath0
.
4.20.2. Rescue Mode
- Using the CD-ROM to boot an x86, AMD64, or Intel® 64 system, type
linux rescue
at the installation boot prompt. Itanium users should typeelilo linux rescue
to enter rescue mode.
4.20.3. Alternative Boot Loaders
- LOADLIN
- You can load Linux from MS-DOS. Unfortunately, this requires a copy of the Linux kernel (and an initial RAM disk, if you have a SCSI adapter) to be available on an MS-DOS partition. The only way to accomplish this is to boot your Red Hat Enterprise Linux system using some other method (for example, from a boot CD-ROM) and then copy the kernel to an MS-DOS partition. LOADLIN is available fromand associated mirror sites.
- SYSLINUX
- SYSLINUX is an MS-DOS program very similar to LOADLIN. It is also available fromand associated mirror sites.
- Commercial boot loaders
- You can load Linux using commercial boot loaders. For example, System Commander and Partition Magic are able to boot Linux (but still require GRUB to be installed in your Linux root partition).
Note
4.20.4. SMP Motherboards and GRUB
4.21. Network Configuration
Figure 4.20. Network Configuration
Figure 4.21. Editing a Network Device
Note
Note
localhost
.
Note
system-config-network
command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue.
4.22. Time Zone Configuration
- Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection.
- You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
Note
system-config-date
command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig
.
4.23. Set Root Password
Note
Figure 4.22. Root Password
su -
to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
Note
su -
at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
Note
Note
system-config-rootpassword
command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
4.24. Package Group Selection
Note
Figure 4.23. Package Group Selection
Figure 4.24. Package Group Details
4.25. Preparing to Install
4.25.1. Prepare to Install
/root/install.log
once you reboot your system.
Warning
4.26. Installing Packages
4.27. Installation Complete
- Press Enter — causes the default boot entry to be booted.
- Select a boot label, followed by Enter — causes the boot loader to boot the operating system corresponding to the boot label.
- Do nothing — after the boot loader's timeout period, (by default, five seconds) the boot loader automatically boots the default boot entry.
login:
prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
4.28. Itanium Systems — Booting Your Machine and Post-Installation Setup
elilo
elilo
, the default kernel listed in the /boot/efi/elilo.conf
configuration file is loaded. (The first kernel listed in the file is the default.)
/boot/efi/elilo.conf
after the elilo
command. For example, to load the kernel named linux
, type:
elilo linux
/boot/efi/elilo.conf
file in EFI with the following instructions:
- At the
Shell>
prompt, change devices to the system partition (mounted as/boot/efi
in Linux). For example, iffs0
is the system boot partition, typefs0:
at the EFI Shell prompt. - Type
ls
at thefs0:\>
to make sure you are in the correct partition. - Then type:
Shell>
type elilo.conf
This command displays the contents of the configuration file. Each stanza contains a line beginning withlabel
followed by a label name for that kernel. The label name is what you type afterelilo
to boot the different kernels.
4.28.1. Post-Installation Boot Loader Options
single
for single user mode or mem=1024M
to force Red Hat Enterprise Linux to use 1024 MB of memory. To pass options to the boot loader, enter the following at the EFI Shell prompt (replace linux
with the label name of the kernel you want to boot and option
with the boot options you want to pass to the kernel):
elilo linux option
4.28.2. Booting Red Hat Enterprise Linux Automatically
elilo
and any boot options at the EFI Shell prompt each time you wish to boot your Itanium system. However, if you wish to configure your system to boot into Red Hat Enterprise Linux automatically, you need to configure the EFI Boot Manager.
- Boot the Itanium system and choose EFI Boot Manager menu.from the
- Choosefrom the Main Menu.
- Select the system partition that is mounted as
/boot/efi/
in Linux. - Select the
elilo.efi
file. - At the
Enter New Description:
prompt, typeRed Hat Enterprise Linux 5
, or any name that you want to appear on the EFI Boot Manager menu. - At the
Enter Boot Option Data Type:
prompt, enterN
for if you do not want to pass options to the ELILO boot loader. This option works for most cases. If you want to pass options to the boot loader, you can configure it in the/boot/efi/elilo.conf
configuration file instead. - Answer
Yes
to theSave changes to NVRAM
prompt. This returns you to the EFI Boot Maintenance Manager menu. - Next, you want to make themenu item the default. A list of boot options appears. Move the menu item up to the top of the list by selecting it with the arrow keys and pressing the u key to move it up the list. You can move items down the list by selecting it and pressing the d key. After changing the boot order, choose . Choose to return to the Main Menu.
- Optionally, you can change the boot timeout value by choosing=> from the Main Menu.
- Return to the EFI Boot Manager by selecting .
4.28.2.1. Using a Startup Script
startup.nsh
. The last command should be elilo
to boot into Linux.
startup.nsh
script should be in the /boot/efi
partition (/boot/efi/startup.nsh
) and contain the following text:
echo -off your set of commands elilo
elilo
.
Shell>
prompt, change devices to the system partition (mounted as /boot/efi
in Linux). For example, if fs0
is the system boot partition, type fs0:
at the EFI Shell prompt. Type ls
to make sure you are in the correct partition. Then type edit startup.nsh
. Type the contents of the file and save it.
startup.nsh
file and use it to boot the system. To stop EFI from loading the file, type Ctrl+c . This aborts the process, and returns you to the EFI shell prompt.
fsck
application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
Chapter 5. Removing Red Hat Enterprise Linux
Note
fdisk
utility to create a new MBR with the undocumented flag /mbr
. This ONLY rewrites the MBR to boot the primary DOS partition. The command should look like the following:
fdisk /mbr
fdisk
, you will experience the Partitions exist but they do not exist problem. The best way to remove non-DOS partitions is with a tool that understands partitions other than DOS.
linux rescue
. This starts the rescue mode program.
list-harddrives
. This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes.
Warning
parted
. Start parted
, where /dev/hda is the device on which to remove the partition:
parted /dev/hda
print
command, view the current partition table to determine the minor number of the partition to remove:
print
command also displays the partition's type (such as linux-swap, ext2, ext3, and so on). Knowing the type of the partition helps you in determining whether to remove the partition.
rm
. For example, to remove the partition with minor number 3:
rm 3
Important
print
command to confirm that it is removed from the partition table.
quit
to quit parted
.
parted
, type exit
at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If it does not, you can reboot your computer using Control+Alt+Delete .
Chapter 6. Troubleshooting Installation on an Intel® or AMD System
6.1. You are Unable to Boot Red Hat Enterprise Linux
6.1.1. Are You Unable to Boot With Your RAID Card?
GRUB:
) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
/boot
partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/
partition.
6.1.2. Is Your System Displaying Signal 11 Errors?
boot:
or yaboot:
prompt (prepend with elilo
for Itanium systems):
linux mediacheck
http://www.bitwizard.nl/sig11/
6.2. Trouble Beginning the Installation
6.2.1. Problems with Booting into the Graphical Installation
resolution=
boot option. This option may be most helpful for laptop users. Another solution to try is the driver=
option to specify the driver that should be loaded for your video card. If this works, it should be reported as a bug as the installer has failed to autodetect your videocard. Refer to Chapter 8, Additional Boot Options for Intel® and AMD Systems for more information on boot options.
Note
nofb
boot option. This command may be necessary for accessibility with some screen reading hardware.
6.3. Trouble During the Installation
6.3.1. No devices found to install Red Hat Enterprise Linux
Error Message
No devices found to install Red Hat Enterprise Linux
, there is probably a SCSI controller that is not being recognized by the installation program.
6.3.2. Saving Traceback Messages Without a Diskette Drive
scp
the error message to a remote system.
/tmp/anacdump.txt
. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys Ctrl+Alt+F2
and scp
the message written to /tmp/anacdump.txt
to a known working remote system.
6.3.3. Trouble with Partition Tables
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
6.3.4. Using Remaining Space
swap
and a /
(root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.
/boot
partition if you want the /
(root) partition to use all of the remaining space on your hard drive.
6.3.5. Other Partitioning Problems
- A
/
(root) partition - A <swap> partition of type swap
Note
6.3.6. Other Partitioning Problems for Itanium System Users
- A
/boot/efi/
partition of type VFAT - A
/
(root) partition - A <swap> partition of type swap
Note
6.3.7. Are You Seeing Python Errors?
/tmp/
directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/
are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
6.4. Problems After Installation
6.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?
/boot/grub/grub.conf
file.
grub.conf
file, comment out the line which begins with splashimage
by inserting the #
character at the beginning of the line.
b
to boot the system.
grub.conf
file is reread and any changes you have made take effect.
grub.conf
file.
6.4.2. Booting into a Graphical Environment
startx
.
/etc/inittab
, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
su
command.
gedit /etc/inittab
to edit the file with gedit. The file /etc/inittab
opens. Within the first screen, a section of the file which looks like the following appears:
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
# id:3:initdefault:
id:3:initdefault:
from a 3
to a 5
.
Warning
3
to 5
.
id:5:initdefault:
6.4.3. Problems with the X Window System (GUI)
6.4.4. Problems with the X Server Crashing and Non-Root Users
df -h
df
command should help you diagnose which partition is full. For additional information about df
and an explanation of the options available (such as the -h
option used in this example), refer to the df
man page by typing man df
at a shell prompt.
/home/
and /tmp/
partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
6.4.5. Problems When You Try to Log In
linux single
.
elilo
followed by the boot command.
e
for edit when the GRUB boot screen has loaded. You are presented with a list of items in the configuration file for the boot label you have selected.
kernel
and type e
to edit this boot entry.
kernel
line, add:
single
b
to boot the system.
#
prompt, you must type passwd root
, which allows you to enter a new password for root. At this point you can type shutdown -r now
to reboot the system with the new root password.
su -
and enter your root password when prompted. Then, type passwd <username>
. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/
6.4.6. Is Your RAM Not Being Recognized?
cat /proc/meminfo
command.
/boot/grub/grub.conf
:
mem=xxM
/boot/grub/grub.conf
, the above example would look similar to the following:
# NOTICE: You have a /boot partition. This means that # all kernel paths are relative to /boot/ default=0 timeout=30 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Enterprise Linux (2.6.9-5.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.EL ro root=/dev/hda3 mem=128M
grub.conf
are reflected on your system.
e
for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
kernel
and type e
to edit this boot entry.
kernel
line, add
mem=xxM
b
to boot the system.
elilo
followed by the boot command.
6.4.7. Your Printer Does Not Work
system-config-printer
command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
6.4.8. Problems with Sound Configuration
system-config-soundcard
) utility.
system-config-soundcard
command at a shell prompt to launch the Sound Card Configuration Tool. If you are not root, it prompts you for the root password to continue.
Chapter 7. Updating drivers during installation on Intel and AMD systems
- place the image file in a location accessible to the installer:
- on a local IDE hard drive
- a USB storage device such as a USB flash drive
- on a FTP, HTTP, or NFS server on your local network (or take note of a location on the Internet where someone else has placed the image file)
- create a driver update disk by unpacking the image file onto:
- a CD (if your computer has an IDE optical drive)
- a DVD (if your computer has an IDE optical drive)
- a floppy disk
- a USB storage device such as a USB flash drive
- create an initial ramdisk update from the image file and store it on a PXE server. This is an advanced procedure that you should consider only if you cannot perform a driver update with any other method.
7.1. Limitations of driver updates during installation
- Devices already in use
- You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation process, consider performing an initial RAM disk driver update — refer to Section 7.2.3, “Preparing an initial RAM disk update”.
- Devices with an equivalent device available
- Because all devices of the same type are initialized together, you cannot update drivers for a device if the installation program has loaded drivers for a similar device. For example, consider a system that has two different network adapters, one of which has a driver update available. The installation program will initialize both adapters at the same time, and therefore, you will not be able to use this driver update. Again, complete the installation with the drivers loaded by the installation program and update to the new drivers after installation, or use an initial RAM disk driver update.
7.2. Preparing for a driver update during installation
- Methods that use the image file itself
- local hard drive (IDE only)
- USB storage device (for example, USB flash drive)
- network (HTTP, FTP, NFS)
- Methods that use a driver update disk produced from an image file
- floppy disk
- CD (IDE only)
- DVD (IDE only)
- USB storage device (for example, USB flash drive)
- Methods that use an initial RAM disk update
- PXE
Important
7.2.1. Preparing to use a driver update image file
7.2.1.1. Preparing to use an image file on local storage
.iso
. In the following example, the file is named dd.iso
:
Figure 7.1. Content of a USB flash drive holding a driver update image file
OEMDRV
, the installation program will automatically examine it for driver updates and load any that it detects. This behavior is controlled by the dlabel=on
boot option, which is enabled by default. Refer to Section 7.3.1, “Let the installer automatically find a driver update disk”.
7.2.1.2. Preparing to use an image file available through a network
7.2.2. Preparing a driver update disk
7.2.2.1. Creating a driver update disk on CD or DVD
Important
- Use the desktop file manager to locate the driver update ISO image file supplied to you by Red Hat or your hardware vendor.
Figure 7.2. A typical .iso file displayed in a file manager window
- Right-click on this file and choose. You will see a window similar to the following:
Figure 7.3. CD/DVD Creator's Write to Disc dialog
- Click the CD/DVD Creator will prompt you to insert one.button. If a blank disc is not already in the drive,
Figure 7.4. Contents of a typical driver update disc on CD or DVD
.iso
, then you have not created the disk correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system.
7.2.2.2. Creating a driver update disk on floppy disk, or USB storage device
Important
Warning
- Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example,
/dev/fd0
for a floppy disk in the first floppy drive on your system.If you do not know the device name, become root and use the commandfdisk -l
on the command line. You will see a list of all storage devices available on your system. Compare the output offdisk -l
when the disk inserted or the storage device is attached with the output of this command when the disk is removed or the storage device is disconnected. - At the command line, change into the directory that contains the image file.
- At the command line, type:
dd if=image of=device
where image is the image file, and device is the device name. For example, to create a driver disk on floppy disk/dev/fd0
from driver update image filedd.iso
, you would use:dd if=dd.iso of=/dev/fd0
7.2.3. Preparing an initial RAM disk update
Important
- Place the driver update image file on your PXE server. Usually, you would do this by downloading it to the PXE server from a location on the Internet specified by Red Hat or your hardware vendor. Names of driver update image files end in
.iso
. - Copy the driver update image file into the
/tmp/initrd_update
directory. - Rename the driver update image file to
dd.img
. - At the command line, change into the
/tmp/initrd_update
directory, type the following command, and press Enter:find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img
- Copy the file
/tmp/initrd_update.img
into the directory the holds the target that you want to use for installation. This directory is placed under the/tftpboot/pxelinux/
directory. For example,/tftpboot/pxelinux/r5su3/
might hold the PXE target for Red Hat Enterprise Linux 5.3 Server. - Edit the
/tftpboot/pxelinux/pxelinux.cfg/default
file to include an entry that includes the initial RAM disk update that you just created, in the following format:label target-dd kernel target/vmlinuz append initrd=target/initrd.img,target/dd.img
Where target is the target that you want to use for installation.
Example 7.1. Preparing an initial RAM disk update from a driver update image file
driver_update.iso
is a driver update image file that you downloaded from the Internet to a directory on your PXE server. The target that you want to PXE boot from is located in /tftpboot/pxelinux/r5su3
$ cp driver_update.iso /tmp/initrd_update/dd.img $ cd /tmp/initrd_update $ find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img $ cp /tmp/initrd_update.img /tftpboot/pxelinux/r5su3/dd.img
/tftpboot/pxelinux/pxelinux.cfg/default
file and include the following entry:
label r5su3-dd kernel r5su3/vmlinuz append initrd=r5su3/initrd.img,r5su3/dd.img
7.3. Performing a driver update during installation
- let the installer automatically find a driver update disk.
- let the installer prompt you for a driver update.
- use a boot option to specify a driver update disk.
- use a boot option to specify a driver update image file on a network.
- select a PXE target that includes a driver update.
7.3.1. Let the installer automatically find a driver update disk
OEMDRV
before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 7.2.1.1, “Preparing to use an image file on local storage” to prepare a storage device for the installer to find.
7.3.2. Let the installer prompt you for a driver update
- Begin the installation normally for whatever method you have chosen. If the installer cannot load drivers for a piece of hardware that is essential for the installation process (for example, if it cannot detect any network or storage controllers), it prompts you to insert a driver update disk:
Figure 7.5. The no driver found dialog
- Select Use a driver disk and refer to Section 7.4, “Specifying the location of a driver update image file or driver update disk”.
7.3.3. Use a boot option to specify a driver update disk
Important
- Type
linux dd
at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk:Figure 7.6. The driver disk prompt
- Insert the driver update disk that you created on CD, DVD, floppy disk, or USB storage device and select. The installer examines the storage devices that it can detect. If there is only one possible location that could hold a driver disk (for example, the installer detects the presence of a floppy disk, but no other storage devices) it will automatically load any driver updates that it finds at this location.If the installer finds more than one location that could hold a driver update, it prompts you to specify the location of the update. Refer to to Section 7.4, “Specifying the location of a driver update image file or driver update disk” .
7.3.4. Use a boot option to specify a driver update image file on a network
Important
linux dd=URL
(where URL is the HTTP, FTP, or NFS address of a driver update image) at the boot prompt at the start of the installation process and press Enter. The installer will retrieve the driver update image from that address and use it during installation.
7.3.5. Select a PXE target that includes a driver update
- Select
network boot
in your computer's BIOS or boot menu. The procedure to specify this option varies widely among different computers. Consult your hardware documentation or the hardware vendor for specifics relevant to your computer. - In the preexecution boot environment (PXE), choose the boot target that you prepared on your PXE server. For example, if you labeled this environment
r5su3-dd
in the/tftpboot/pxelinux/pxelinux.cfg/default
file on your PXE server, typer5su3-dd
at the prompt and press Enter.
7.4. Specifying the location of a driver update image file or driver update disk
Figure 7.7. Selecting a driver disk source
Figure 7.8. Selecting a driver disk partition
Figure 7.9. Selecting an ISO image
Chapter 8. Additional Boot Options for Intel® and AMD Systems
boot:
prompt.
Boot Time Command Arguments
askmethod
- this command asks you to select the installation method you would like to use when booting from the Red Hat Enterprise Linux CD-ROM.
apic
- this x86 boot command works around a bug commonly encountered in the Intel 440GX chipset BIOS and should only be executed with the installation program kernel.
dd
- this argument causes the installation program to prompt you to use a driver diskette.
dd=url
- this argument causes the installation program to prompt you to use a driver image from a specified HTTP, FTP, or NFS network address.
display=ip:0
- this command allows remote display forwarding. In this command, ip should be replaced with the IP address of the system on which you want the display to appear.On the system you want the display to appear on, you must execute the command
xhost +remotehostname
, where remotehostname is the name of the host from which you are running the original display. Using the commandxhost +remotehostname
limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access. driverdisk
- this command performs the same function as the
dd
command and also prompts you to use a driver diskette during the installation of Red Hat Enterprise Linux. linux upgradeany
- this command relaxes some of the checks on your
/etc/redhat-release
file. If your/etc/redhat-release
file has been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5. Use this option only if your existing Red Hat Enterprise Linux installation was not detected. mediacheck
- this command gives you the option of testing the integrity of the install source (if an ISO-based method). this command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during an installation.
mem=xxxm
- this command allows you to override the amount of memory the kernel detects for the machine. This may be needed for some older systems where only 16 mb is detected and for some new machines where the video card shares the video memory with the main memory. When executing this command, xxx should be replaced with the amount of memory in megabytes.
mpath
- enables multipath support.
Important
If you install Red Hat Enterprise Linux 5.11 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. nmi_watchdog=1
- this command enables the built-in kernel deadlock detector. This command can be used to debug hard kernel lockups. by executing periodic NMI (Non Maskable Interrupt) interrupts, the kernel can monitor whether any CPU has locked up and print out debugging messages as needed.
noapic
- this x86 boot command tells the kernel not to use the APIC chip. It may be helpful for some motherboards with a bad APIC (such as the Abit BP6) or with a buggy bios. systems based on the nvidia nforce3 chipset (such as the Asus SK8N) have been known to hang during IDE detection at boot time, or display other interrupt-delivery issues.
noeject
- do not eject optical discs after installation. This option is useful in remote installations where it is difficult to close the tray afterwards.
nomce
- this x86 boot command disables self-diagnosis checks performed on the CPU. the kernel enables self-diagnosis on the CPU by default (called machine check exception). Early Compaq Pentium systems may need this option as they do not support processor error checking correctly. A few other laptops, notably those using the Radeon IGP chipset, may also need this option.
nonet
- this command disables network hardware probing.
nopass
- this command disables the passing of keyboard and mouse information to stage 2 of the installation program. It can be used to test keyboard and mouse configuration screens during stage 2 of the installation program when performing a network installation.
nopcmcia
- this command ignores any PCMCIA controllers in system.
noprobe
- this command disables hardware detection and instead prompts the user for hardware information.
noshell
- this command disables shell access on virtual console 2 during an installation.
nostorage
- this command disables probing for SCSI and RAID storage hardware.
nousb
- this command disables the loading of USB support during the installation. If the installation program tends to hang early in the process, this command may be helpful.
nousbstorage
- this command disables the loading of the usbstorage module in the installation program's loader. It may help with device ordering on SCSI systems.
numa=off
- Red Hat Enterprise Linux supports NUMA (non-uniform memory access) on the AMD64 architecture. while all cpus can access all memory even without numa support, the numa support present in the updated kernel causes memory allocations to favor the cpu on which they originate as much as possible, thereby minimizing inter-CPU memory traffic. This can provide significant performance improvements in certain applications. to revert to the original non-NUMA behavior, specify this boot option.
reboot=b
- this x86, AMD64, and Intel® EM64T boot command changes the way the kernel tries to reboot the machine. If a kernel hang is experienced while the system is shutting down, this command may cause the system to reboot successfully.
rescue
- this command runs rescue mode. Refer to Chapter 27, Basic System Recovery for more information about rescue mode.
resolution=
- tells the installation program which video mode to run. it accepts any standard resolution, such as
640x480
,800x600
,1024x768
, and so on. serial
- this command turns on serial console support.
text
- this command disables the graphical installation program and forces the installation program to run in text mode.
updates
- this command prompts you to insert a floppy diskette containing updates (bug fixes) for the anaconda installation program. It is not needed if you are performing a network installation and have already placed the updates image contents in
rhupdates/
on the server. updates=
- this command allows you to specify a URL to retrieve updates (bug fixes) for the anaconda installation program.
vnc
- this command allows you to install from a VNC server.
vncpassword=
- this command sets the password used to connect to the VNC server.
Important
Chapter 9. The GRUB Boot Loader
9.1. Boot Loaders and System Architecture
Architecture | Boot Loaders |
---|---|
AMD® AMD64 | GRUB |
IBM® eServer™ System i™ | OS/400® |
IBM® eServer™ System p™ | YABOOT |
IBM® System z® | z/IPL |
IBM® System z® | z/IPL |
Intel® Itanium™ | ELILO |
x86 | GRUB |
9.2. GRUB
9.2.1. GRUB and the x86 Boot Process
- The Stage 1 or primary boot loader is read into memory by the BIOS from the MBR[4]. The primary boot loader exists on less than 512 bytes of disk space within the MBR and is capable of loading either the Stage 1.5 or Stage 2 boot loader.
- The Stage 1.5 boot loader is read into memory by the Stage 1 boot loader, if necessary. Some hardware requires an intermediate step to get to the Stage 2 boot loader. This is sometimes true when the
/boot/
partition is above the 1024 cylinder head of the hard drive or when using LBA mode. The Stage 1.5 boot loader is found either on the/boot/
partition or on a small part of the MBR and the/boot/
partition. - The Stage 2 or secondary boot loader is read into memory. The secondary boot loader displays the GRUB menu and command environment. This interface allows the user to select which kernel or operating system to boot, pass arguments to the kernel, or look at system parameters.
- The secondary boot loader reads the operating system or kernel as well as the contents of
/boot/sysroot/
into memory. Once GRUB determines which operating system or kernel to start, it loads it into memory and transfers control of the machine to that operating system.
Warning
9.2.2. Features of GRUB
- GRUB provides a true command-based, pre-OS environment on x86 machines. This feature affords the user maximum flexibility in loading operating systems with specified options or gathering information about the system. For years, many non-x86 architectures have employed pre-OS environments that allow system booting from a command line.
- GRUB supports Logical Block Addressing (LBA) mode. LBA places the addressing conversion used to find files in the hard drive's firmware, and is used on many IDE and all SCSI hard devices. Before LBA, boot loaders could encounter the 1024-cylinder BIOS limitation, where the BIOS could not find a file after the 1024 cylinder head of the disk. LBA support allows GRUB to boot operating systems from partitions beyond the 1024-cylinder limit, so long as the system BIOS supports LBA mode. Most modern BIOS revisions support LBA mode.
- GRUB can read ext2 partitions. This functionality allows GRUB to access its configuration file,
/boot/grub/grub.conf
, every time the system boots, eliminating the need for the user to write a new version of the first stage boot loader to the MBR when configuration changes are made. The only time a user needs to reinstall GRUB on the MBR is if the physical location of the/boot/
partition is moved on the disk. For details on installing GRUB to the MBR, refer to Section 9.3, “Installing GRUB”.
9.3. Installing GRUB
/sbin/grub-install <location>
, where <location> is the location that the GRUB Stage 1 boot loader should be installed. For example, the following command installs GRUB to the MBR of the master IDE device on the primary IDE bus:
/sbin/grub-install /dev/hda
Important
/boot
directory must reside on a single, specific disk partition. The /boot
directory cannot be striped across multiple disks, as in a level 0 RAID. To use a level 0 RAID on your system, place /boot on a separate partition outside the RAID.
/boot
directory must reside on a single, specific disk partition, GRUB cannot boot the system if the disk holding that partition fails or is removed from the system. This is true even if the disk is mirrored in a level 1 RAID. The following Red Hat Knowledgebase article describes how to make the system bootable from another disk in the mirrored set: http://kbase.redhat.com/faq/docs/DOC-7095
9.4. GRUB Terminology
9.4.1. Device Names
(<type-of-device><bios-device-number>,<partition-number>)
hd
for a hard disk or fd
for a 3.5 diskette. A lesser used device type is also available called nd
for a network disk. Instructions on configuring GRUB to boot over the network are available online at http://www.gnu.org/software/grub/manual/.
0
and a secondary IDE hard drive is numbered 1
. This syntax is roughly equivalent to that used for devices by the kernel. For example, the a
in hda
for the kernel is analogous to the 0
in hd0
for GRUB, the b
in hdb
is analogous to the 1
in hd1
, and so on.
0
. However, BSD partitions are specified using letters, with a
corresponding to 0
, b
corresponding to 1
, and so on.
Note
0
, not 1
. Failing to make this distinction is one of the most common mistakes made by new users.
(hd0)
and the second as (hd1)
. Likewise, GRUB refers to the first partition on the first drive as (hd0,0)
and the third partition on the second hard drive as (hd1,2)
.
- It does not matter if system hard drives are IDE or SCSI, all hard drives begin with the letters
hd
. The lettersfd
are used to specify 3.5 diskettes. - To specify an entire device without respect to partitions, leave off the comma and the partition number. This is important when telling GRUB to configure the MBR for a particular disk. For example,
(hd0)
specifies the MBR on the first device and(hd3)
specifies the MBR on the fourth device. - If a system has multiple drive devices, it is very important to know how the drive boot order is set in the BIOS. This is a simple task if a system has only IDE or SCSI drives, but if there is a mix of devices, it becomes critical that the type of drive with the boot partition be accessed first.
9.4.2. File Names and Blocklists
(<device-type><device-number>,<partition-number>)</path/to/file>
hd
, fd
, or nd
. Replace <device-number> with the integer for the device. Replace </path/to/file> with an absolute path relative to the top-level of the device.
0+50,100+25,200+1
(hd0,0)+1
chainloader
command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:
chainloader +1
9.4.3. The Root File System and GRUB
(hd0,0)/grub/splash.xpm.gz
is located within the /grub/
directory at the top-level (or root) of the (hd0,0)
partition (which is actually the /boot/
partition for the system).
kernel
command is executed with the location of the kernel file as an option. Once the Linux kernel boots, it sets up the root file system that Linux users are familiar with. The original GRUB root file system and its mounts are forgotten; they only existed to boot the kernel file.
9.5. GRUB Interfaces
Note
- Menu Interface
- This is the default interface shown when GRUB is configured by the installation program. A menu of operating systems or preconfigured kernels are displayed as a list, ordered by name. Use the arrow keys to select an operating system or kernel version and press the Enter key to boot it. If you do nothing on this screen, then after the time out period expires GRUB will load the default option.Press the e key to enter the entry editor interface or the c key to load a command line interface.Refer to Section 9.7, “GRUB Menu Configuration File” for more information on configuring this interface.
- Menu Entry Editor Interface
- To access the menu entry editor, press the e key from the boot loader menu. The GRUB commands for that entry are displayed here, and users may alter these command lines before booting the operating system by adding a command line (o inserts a new line after the current line and O inserts a new line before it), editing one (e), or deleting one (d).After all changes are made, the b key executes the commands and boots the operating system. The Esc key discards any changes and reloads the standard menu interface. The c key loads the command line interface.
Note
For information about changing runlevels using the GRUB menu entry editor, refer to Section 9.8, “Changing Runlevels at Boot Time”. - Command Line Interface
- The command line interface is the most basic GRUB interface, but it is also the one that grants the most control. The command line makes it possible to type any relevant GRUB commands followed by the Enter key to execute them. This interface features some advanced shell-like features, including Tab key completion based on context, and Ctrl key combinations when typing commands, such as Ctrl+a to move to the beginning of a line and Ctrl+e to move to the end of a line. In addition, the arrow, Home, End, and Delete keys work as they do in the
bash
shell.Refer to Section 9.6, “GRUB Commands” for a list of common commands.
9.5.1. Interfaces Load Order
9.6. GRUB Commands
boot
— Boots the operating system or chain loader that was last loaded.chainloader </path/to/file>
— Loads the specified file as a chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation,+1
, instead of the file name.The following is an examplechainloader
command:chainloader +1
displaymem
— Displays the current use of memory, based on information from the BIOS. This is useful to determine how much RAM a system has prior to booting it.initrd </path/to/initrd>
— Enables users to specify an initial RAM disk to use when booting. Aninitrd
is necessary when the kernel needs certain modules in order to boot properly, such as when the root partition is formatted with the ext3 file system.The following is an exampleinitrd
command:initrd /initrd-2.6.8-1.523.img
install <stage-1> <install-disk> <stage-2>
— Installs GRUB to the system MBR.p
config-file<stage-1>
— Signifies a device, partition, and file where the first boot loader image can be found, such as(hd0,0)/grub/stage1
.<install-disk>
— Specifies the disk where the stage 1 boot loader should be installed, such as(hd0)
.<stage-2>
— Passes the stage 2 boot loader location to the stage 1 boot loader, such as(hd0,0)/grub/stage2
.p
<config-file>
— This option tells theinstall
command to look for the menu configuration file specified by<config-file>
, such as(hd0,0)/grub/grub.conf
.
Warning
Theinstall
command overwrites any information already located on the MBR.kernel </path/to/kernel> <option-1> <option-N>
... — Specifies the kernel file to load when booting the operating system. Replace </path/to/kernel> with an absolute path from the partition specified by the root command. Replace <option-1> with options for the Linux kernel, such asroot=/dev/VolGroup00/LogVol00
to specify the device on which the root partition for the system is located. Multiple options can be passed to the kernel in a space separated list.The following is an examplekernel
command:kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00
The option in the previous example specifies that the root file system for Linux is located on thehda5
partition.root (<device-type><device-number>,<partition>)
— Configures the root partition for GRUB, such as(hd0,0)
, and mounts the partition.The following is an exampleroot
command:root (hd0,0)
rootnoverify (<device-type><device-number>,<partition>)
— Configures the root partition for GRUB, just like theroot
command, but does not mount the partition.
help --all
for a full list of commands. For a description of all GRUB commands, refer to the documentation available online at http://www.gnu.org/software/grub/manual/.
9.7. GRUB Menu Configuration File
/boot/grub/grub.conf
), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The commands given in Section 9.6, “GRUB Commands” can be used, as well as some special commands that are only available in the configuration file.
9.7.1. Configuration File Structure
/boot/grub/grub.conf
. The commands to set the global preferences for the menu interface are placed at the top of the file, followed by stanzas for each operating kernel or operating system listed in the menu.
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux Server (2.6.18-2.el5PAE) root (hd0,0) kernel /boot/vmlinuz-2.6.18-2.el5PAE ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.18-2.el5PAE.img # section to load Windows title Windows rootnoverify (hd0,0) chainloader +1
Note
title
line in the GRUB configuration file. For the Windows
section to be set as the default in the previous example, change the default=0
to default=1
.
9.7.2. Configuration File Directives
chainloader </path/to/file>
— Loads the specified file as a chain loader. Replace </path/to/file> with the absolute path to the chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation,+1
.color <normal-color> <selected-color>
— Allows specific colors to be used in the menu, where two colors are configured as the foreground and background. Use simple color names such asred/black
. For example:color red/black green/blue
default=<integer>
— Replace <integer> with the default entry title number to be loaded if the menu interface times out.fallback=<integer>
— Replace <integer> with the entry title number to try if the first attempt fails.hiddenmenu
— Prevents the GRUB menu interface from being displayed, loading thedefault
entry when thetimeout
period expires. The user can see the standard GRUB menu by pressing the Esc key.initrd </path/to/initrd>
— Enables users to specify an initial RAM disk to use when booting. Replace </path/to/initrd> with the absolute path to the initial RAM disk.kernel </path/to/kernel> <option-1> <option-N>
— Specifies the kernel file to load when booting the operating system. Replace </path/to/kernel> with an absolute path from the partition specified by the root directive. Multiple options can be passed to the kernel when it is loaded.password=<password>
— Prevents a user who does not know the password from editing the entries for this menu option.Optionally, it is possible to specify an alternate menu configuration file after thepassword=<password>
directive. In this case, GRUB restarts the second stage boot loader and uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file.For more information about securing GRUB, see the chapter titled Workstation Security in the Red Hat Enterprise Linux Deployment Guide.root (<device-type><device-number>,<partition>)
— Configures the root partition for GRUB, such as(hd0,0)
, and mounts the partition.rootnoverify (<device-type><device-number>,<partition>)
— Configures the root partition for GRUB, just like theroot
command, but does not mount the partition.timeout=<integer>
— Specifies the interval, in seconds, that GRUB waits before loading the entry designated in thedefault
command.splashimage=<path-to-image>
— Specifies the location of the splash screen image to be used when GRUB boots.title group-title
— Specifies a title to be used with a particular group of commands used to load a kernel or operating system.
#
).
9.8. Changing Runlevels at Boot Time
- When the GRUB menu bypass screen appears at boot time, press any key to enter the GRUB menu (within the first three seconds).
- Press the a key to append to the
kernel
command. - Add
<space><runlevel>
at the end of the boot options line to boot to the desired runlevel. For example, the following entry would initiate a boot process into runlevel 3:grub append> ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
9.9. Additional Resources
9.9.1. Installed Documentation
/usr/share/doc/grub-<version-number>/
— This directory contains good information about using and configuring GRUB, where <version-number> corresponds to the version of the GRUB package installed.info grub
— The GRUB info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB and its usage.
9.9.2. Useful Websites
- http://www.gnu.org/software/grub/ — The home page of the GNU GRUB project. This site contains information concerning the state of GRUB development and an FAQ.
- http://kbase.redhat.com/faq/FAQ_43_4053.shtm — Details booting operating systems other than Linux.
- http://www.linuxgazette.com/issue64/kohli.html — An introductory article discussing the configuration of GRUB on a system from scratch, including an overview of GRUB command line options.
Chapter 10. Additional Resources about Itanium and Linux
- / — The Intel website on the Itanium Processor
- http://developer.intel.com/technology/efi/index.htm?iid=sr+efi — The Intel website for the Extensible Firmware Interface (EFI)
- http://www.itanium.com/business/bss/products/server/itanium2/index.htm — The Intel website on the Itanium 2 processor
Part II. IBM POWER Architecture - Installation and Booting
Chapter 11. Steps to Get You Started
11.1. Upgrade or Install?
11.2. Preparation for IBM eServer System p and System i
11.3. Do You Have Enough Disk Space?
- have enough unpartitioned[5] disk space for the installation of Red Hat Enterprise Linux, or
- have one or more partitions that may be deleted, thereby freeing up enough disk space to install Red Hat Enterprise Linux.
11.4. Can You Install Using the CD-ROM or DVD?
11.5. Preparing for a Network Installation
Note
yaboot:
prompt:
linux mediacheck
Note
/location/of/disk/space
. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as /publicly/available/directory. For example, /location/of/disk/space
may be a directory you create called /var/isos
. /publicly/available/directory
might be /var/www/html/rhel5
, for an HTTP install.
- Create an iso image from the installation disk(s) using the following command (for DVDs):
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
where dvd refers to your DVD drive device.
11.5.1. Preparing for FTP and HTTP installation
RELEASE-NOTES
files and all files from the RedHat
directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD-ROM/ISO image):
- Insert CD-ROM or DVD-ROM.
mount /media/cdrom
- If you are installing the Server variant, run
cp -a /media/cdrom/Server <target-directory>
If you are installing the Client variant, runcp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory>
(Installation CD 1 or DVD only)cp /media/cdrom/images <target-directory>
(Installation CD 1 or DVD only)umount /media/cdrom
<target-directory>
represents the path to the directory to contain the installation tree.)
Note
/publicly/available/directory
directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
11.5.2. Preparing for an NFS install
- For DVD:
mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
- For CDROMs:
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory
directory is exported via NFS via an entry in /etc/exports
.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start
). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload
).
11.6. Preparing for a Hard Drive Installation
Note
- Using a set of CD-ROMs, or a DVD — Create ISO image files from each installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), execute the following command on a Linux system:
dd if=/dev/cdrom of=/tmp/file-name.iso
- Using ISO images — transfer these images to the system to be installed.Verifying that ISO images are intact before you attempt an installation, helps to avoid problems. To verify the ISO images are intact prior to performing an installation, use an
md5sum
program (manymd5sum
programs are available for various operating systems). Anmd5sum
program should be available on the same Linux machine as the ISO images.
updates.img
exists in the location from which you install, it is used for updates to anaconda
, the installation program. Refer to the file install-methods.txt
in the anaconda
RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
Chapter 12. Installing on IBM System i and IBM System p systems
- Becoming familiar with the installation program's user interface
- Starting the installation program
- Selecting an installation method
- Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
- Finishing the installation
12.1. The Graphical Installation Program User Interface
Note
yaboot:
prompt:
linux text
12.2. Booting the IBM System i or IBM System p Installation Program
Figure 12.1. SMS console
boot:
prompt. Press Enter or wait for the timeout to expire for the installation to begin.
images/netboot/ppc64.img
file on CD #1.
12.3. A Note about Linux Virtual Consoles
console | keystrokes | contents |
---|---|---|
1 | ctrl+alt+f1 | installation dialog |
2 | ctrl+alt+f2 | shell prompt |
3 | ctrl+alt+f3 | install log (messages from installation program) |
4 | ctrl+alt+f4 | system-related messages |
5 | ctrl+alt+f5 | other messages |
6 | ctrl+alt+f6 | x graphical display |
12.4. Using the HMC vterm
12.5. The Text Mode Installation Program User Interface
Note
Figure 12.2. Installation Program Widgets as seen in Boot Loader Configuration
Figure 12.3. Installation Program Widgets as seen in Disk Druid
- Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath.
- Checkbox — Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press Space to select or deselect a feature.
- Text Input — Text input lines are regions where you can enter information required by the installation program. When the cursor rests on a text input line, you may enter and/or edit information on that line.
- Text Widget — Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the Up and Down arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a # character, which moves up and down the scroll bar as you scroll.
- Scroll Bar — Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file.
- Button Widget — Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the Tab and Enter keys. Buttons can be selected when they are highlighted.
- Cursor — Although not a widget, the cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or next to the widget. In Figure 12.2, “Installation Program Widgets as seen in Boot Loader Configuration”, the cursor is positioned on the button. Figure 12.3, “Installation Program Widgets as seen in Disk Druid”, shows the cursor on the button.
12.5.1. Using the Keyboard to Navigate
Warning
12.6. Beginning Installation
12.6.1. Installing from DVD/CD-ROM
12.7. Installing from a Hard Drive
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd
boot option, you already specified a partition.
Figure 12.4. Selecting Partition Dialog for Hard Drive Installation
/
. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/
, and the images are in /home/new/
, you would enter /new/
.
12.8. Performing a Network Installation
askmethod
boot option, the Configure TCP/IP dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually. If manually, you have the option to enter IPv4 and/or IPv6 information. Enter the IP address you are using during installation and press Enter. Note that you need to supply IPv4 information if you wish to perform an NFS installation.
Figure 12.5. TCP/IP Configuration
12.9. Installing via NFS
eastcoast
in the domain example.com
, enter eastcoast.example.com
in the NFS Server field.
/export/directory/
which contains the variant/
directory.
Figure 12.6. NFS Setup Dialog
12.10. Installing via FTP
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp
boot option, you already specified a server and path.
Figure 12.7. FTP Setup Dialog
variant/
directory for your architecture. For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
12.11. Installing via HTTP
askmethod
boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http
boot option, you already specified a server and path.
variant/
directory for your architecture. For example, if the HTTP site contains the directory /mirrors/redhat/arch/variant/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Figure 12.8. HTTP Setup Dialog
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
12.12. Welcome to Red Hat Enterprise Linux
12.13. Language Selection
Figure 12.9. Language Selection
12.14. Keyboard Configuration
Figure 12.10. Keyboard Configuration
Note
system-config-keyboard
command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue.
12.15. Enter the Installation Number
Figure 12.11. Installation Number
12.16. Disk Partitioning Setup
Warning
/var/cache/yum/
by default. If you partition the system manually, and create a separate /var/
partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
Figure 12.12. Disk Partitioning Setup
Warning
Important
mapper/mpath
instead.
12.17. Advanced Storage Options
Figure 12.13. Advanced Storage Options
Figure 12.14. Enable network Interface
Figure 12.15. Configure ISCSI Parameters
12.18. Create Default Layout
- Remove all partitions on selected drives and create default layout — select this option to remove all partitions on your hard drive(s) (this includes partitions created by other operating systems such as Windows VFAT or NTFS partitions).
Warning
If you select this option, all data on the selected hard drive(s) is removed by the installation program. Do not select this option if you have information that you want to keep on the hard drive(s) where you are installing Red Hat Enterprise Linux. - Remove Linux partitions on selected drives and create default layout — select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your hard drive(s) (such as VFAT or FAT32 partitions).
- Use free space on selected drives and create default layout — select this option to retain your current data and partitions, assuming you have enough free space available on your hard drive(s).
Figure 12.16. Create Default Layout
Warning
Note
/boot/
partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/
partition is also necessary for software RAID setups.
/boot/
partition.
12.19. Partitioning Your System
Note
Note
/
) partition, a /boot/
partition, PPC PReP boot partition, and a swap partition equal to twice the amount of RAM you have on the system.
Figure 12.17. Partitioning with Disk Druid on IBM System p and System i systems
12.19.1. Graphical Display of Hard Drive(s)
12.19.2. Disk Druid's Buttons
- Partitions section. Selecting opens a dialog box. Some or all of the fields can be edited, depending on whether the partition information has already been written to disk.: Used to modify attributes of the partition currently selected in theYou can also edit free space as represented in the graphical display to create a new partition within that space. Either highlight the free space and then select thebutton, or double-click on the free space to edit it.
- To make a RAID device, you must first create (or reuse existing) software RAID partitions. Once you have created two or more software RAID partitions, selectto join the software RAID partitions into a RAID device.
- Current Disk Partitions section. You will be asked to confirm the deletion of any partition.: Used to remove the partition currently highlighted in the
- Disk Druid to its original state. All changes made will be lost if you the partitions.: Used to restore
- It should only be used if you have experience using RAID. To read more about RAID, see the Red Hat Enterprise Linux Deployment Guide.: Used to provide redundancy to any or all disk partitions.To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, selectto join the software RAID partitions into a RAID device.
- It should only be used if you have experience using LVM. To read more about LVM, see the Red Hat Enterprise Linux Deployment Guide. Note, LVM is only available in the graphical installation program.: Allows you to create an LVM logical volume. The role of LVM (Logical Volume Manager) is to present a simple logical view of underlying physical storage space, such as a hard drive(s). LVM manages individual physical disks — or to be more precise, the individual partitions present on them.To create an LVM logical volume, you must first create partitions of type physical volume (LVM). Once you have created one or more physical volume (LVM) partitions, selectto create an LVM logical volume.
12.19.3. Partition Fields
- Device: This field displays the partition's device name.
- Mount Point/RAID/Volume: A mount point is the location within the directory hierarchy at which a volume exists; the volume is "mounted" at this location. This field indicates where the partition is mounted. If a partition exists, but is not set, then you need to define its mount point. Double-click on the partition or click the button.
- Type: This field shows the partition's file system type (for example, ext2, ext3, or vfat).
- Format: This field shows if the partition being created will be formatted.
- Size (MB): This field shows the partition's size (in MB).
- Start: This field shows the cylinder on your hard drive where the partition begins.
- End: This field shows the cylinder on your hard drive where the partition ends.
12.19.4. Recommended Partitioning Scheme
- A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing.In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, we recommend determining system swap using the following table.
Table 12.2. Recommended System Swap Space Amount of RAM in the System Recommended Amount of Swap Space 4GB of RAM or less a minimum of 2GB of swap space 4GB to 16GB of RAM a minimum of 4GB of swap space 16GB to 64GB of RAM a minimum of 8GB of swap space 64GB to 256GB of RAM a minimum of 16GB of swap space 256GB to 512GB of RAM a minimum of 32GB of swap space Note that you can obtain better performance by distributing swap space over multiple storage devices, particularly on systems with fast drives, controllers, and interfaces. - A PPC PReP boot partition on the first partition of the hard drive — the PPC PReP boot partition contains the YABOOT boot loader (which allows other POWER systems to boot Red Hat Enterprise Linux). Unless you plan to boot from a floppy or network source, you must have a PPC PReP boot partition to boot Red Hat Enterprise Linux.For IBM System i and IBM System p users: The PPC PReP boot partition should be between 4-8 MB, not to exceed 10 MB.
- A
/boot/
partition (100 MB) — the partition mounted on/boot/
contains the operating system kernel (which allows your system to boot Red Hat Enterprise Linux), along with files used during the bootstrap process. Due to the limitations of most PC firmware, creating a small partition to hold these is a good idea. For most users, a 100 MB boot partition is sufficient.Warning
If you have a RAID card, be aware that Red Hat Enterprise Linux 5.11 does not support setting up hardware RAID on an IPR card. You can boot the standalone diagnostics CD prior to installation to create a RAID array and then install to that RAID array. - A
root
partition (3.0 GB - 5.0 GB) — this is where "/
" (the root directory) is located. In this setup, all files (except those stored in/boot
) are on the root partition.A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.
Warning
/var
on a network filesystem (for example, NFS, iSCSI, or NBD) The /var
directory contains critical data that must be read from or written to during the boot process before establishing network services.
/var/spool
, /var/www
or other subdirectories on a separate network disk, just not the complete /var
filesystem.
12.19.5. Adding Partitions
Note
Figure 12.18. Creating a New Partition
- Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter
/
; enter/boot
for the/boot
partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set - setting the filesystem type to swap is sufficient. - File System Type: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to Section 12.19.5.1, “File System Types”.
- Allowable Drives: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is not checked, then the partition will never be created on that hard disk. By using different checkbox settings, you can have Disk Druid place partitions where you need them, or let Disk Druid decide where partitions should go.
- Size (MB): Enter the size (in megabytes) of the partition. Note, this field starts with 100 MB; unless changed, only a 100 MB partition will be created.
- Additional Size Options: Choose whether to keep this partition at a fixed size, to allow it to "grow" (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard drive space available.If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use.
- Force to be a primary partition: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to Section 26.1.3, “Partitions within Partitions — An Overview of Extended Partitions”, for more information.
- Encrypt: Choose whether to encrypt the partition so that the data stored on it cannot be accessed without a passphrase, even if the storage device is connected to another system. Refer to Chapter 29, Disk Encryption Guide for information on encryption of storage devices. If you select this option, the installer prompts you to provide a passphrase before it writes the partition to the disk.
12.19.5.1. File System Types
- ext3 — The ext3 file system is based on the ext2 file system and has one main advantage — journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to
fsck
[6] the file system. A maximum file system size of 16TB is supported for ext3. The ext3 file system is selected by default and is highly recommended. - ext2 — An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters.
- physical volume (LVM) — Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. For more information regarding LVM, see the Red Hat Enterprise Linux Deployment Guide.
- software RAID — Creating two or more software RAID partitions allows you to create a RAID device. For more information regarding RAID, see chapter RAID (Redundant Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide.
- swap — Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. See the Red Hat Enterprise Linux Deployment Guide for additional information.
12.20. Network Configuration
Figure 12.19. Network Configuration
Figure 12.20. Editing a Network Device
Note
Note
system-config-network
command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue.
12.21. Time Zone Configuration
- Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection.
- You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
Note
system-config-date
command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig
.
12.22. Set Root Password
Note
Figure 12.21. Root Password
su -
to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
Note
su -
at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
Note
Note
system-config-rootpassword
command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
12.23. Package Group Selection
Note
Figure 12.22. Package Group Selection
Figure 12.23. Package Group Details
12.24. Preparing to Install
12.24.1. Prepare to Install
/root/install.log
once you reboot your system.
Warning
12.25. Installing Packages
12.26. Installation Complete
- IBM eServer System p and System i — Completing the Installation
- Do not forget to remove any boot media.After rebooting, you must set the open firmware boot device to the disk containing your Red Hat Enterprise Linux PReP and / partitions. To accomplish this, wait until the LED indicator or HMC SRC says
E1F1
, then press 1 to enter the System Management Services GUI. Click on . Select . Select . Select the disk containing Red Hat Enterprise Linux. Set the other devices as you wish. Then exit the SMS menus to boot your new system.Note
Steps in the SMS menu may be different depending on the machine model.After your computer's normal power-up sequence has completed, YABOOT's prompt appears, at which you can do any of the following things:- Press Enter — causes YABOOT's default boot entry to be booted.
- Select a boot label, followed by Enter — causes YABOOT to boot the operating system corresponding to the boot label. (Press Tab for non-System i systems at the
boot:
prompt for a list of valid boot labels.) - Do nothing — after YABOOT's timeout period, (by default, five seconds) YABOOT automatically boots the default boot entry.
Once Red Hat Enterprise Linux has booted, one or more screens of messages should scroll by. Eventually, alogin:
prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
fsck
application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
Chapter 13. Updating drivers during installation on IBM POWER systems
- place the image file in a location accessible to the installer:
- on a local IDE hard drive
- a USB storage device such as a USB flash drive
- on a FTP, HTTP, or NFS server on your local network (or take note of a location on the Internet where someone else has placed the image file)
- create a driver update disk by unpacking the image file onto:
- a CD (if your computer has an IDE optical drive)
- a DVD (if your computer has an IDE optical drive)
- a floppy disk
- a USB storage device such as a USB flash drive
- create an initial ramdisk update from the image file and store it on a PXE server. This is an advanced procedure that you should consider only if you cannot perform a driver update with any other method.
13.1. Limitations of driver updates during installation
- Devices already in use
- You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation process, consider performing an initial RAM disk driver update — refer to Section 13.2.3, “Preparing an initial RAM disk update”.
- Devices with an equivalent device available
- Because all devices of the same type are initialized together, you cannot update drivers for a device if the installation program has loaded drivers for a similar device. For example, consider a system that has two different network adapters, one of which has a driver update available. The installation program will initialize both adapters at the same time, and therefore, you will not be able to use this driver update. Again, complete the installation with the drivers loaded by the installation program and update to the new drivers after installation, or use an initial RAM disk driver update.
13.2. Preparing for a driver update during installation
- Methods that use the image file itself
- local hard drive (IDE only)
- USB storage device (for example, USB flash drive)
- network (HTTP, FTP, NFS)
- Methods that use a driver update disk produced from an image file
- floppy disk
- CD (IDE only)
- DVD (IDE only)
- USB storage device (for example, USB flash drive)
- Methods that use an initial RAM disk update
- PXE
Important
13.2.1. Preparing to use a driver update image file
13.2.1.1. Preparing to use an image file on local storage
.iso
. In the following example, the file is named dd.iso
:
Figure 13.1. Content of a USB flash drive holding a driver update image file
OEMDRV
, the installation program will automatically examine it for driver updates and load any that it detects. This behavior is controlled by the dlabel=on
boot option, which is enabled by default. Refer to Section 13.3.1, “Let the installer automatically find a driver update disk”.
13.2.1.2. Preparing to use an image file available through a network
13.2.2. Preparing a driver update disk
13.2.2.1. Creating a driver update disk on CD or DVD
Important
- Use the desktop file manager to locate the driver update ISO image file supplied to you by Red Hat or your hardware vendor.
Figure 13.2. A typical .iso file displayed in a file manager window
- Right-click on this file and choose. You will see a window similar to the following:
Figure 13.3. CD/DVD Creator's Write to Disc dialog
- Click the CD/DVD Creator will prompt you to insert one.button. If a blank disc is not already in the drive,
Figure 13.4. Contents of a typical driver update disc on CD or DVD
.iso
, then you have not created the disk correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system.
13.2.2.2. Creating a driver update disk on floppy disk, or USB storage device
Important
Warning
- Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example,
/dev/fd0
for a floppy disk in the first floppy drive on your system.If you do not know the device name, become root and use the commandfdisk -l
on the command line. You will see a list of all storage devices available on your system. Compare the output offdisk -l
when the disk inserted or the storage device is attached with the output of this command when the disk is removed or the storage device is disconnected. - At the command line, change into the directory that contains the image file.
- At the command line, type:
dd if=image of=device
where image is the image file, and device is the device name. For example, to create a driver disk on floppy disk/dev/fd0
from driver update image filedd.iso
, you would use:dd if=dd.iso of=/dev/fd0
13.2.3. Preparing an initial RAM disk update
Important
- Place the driver update image file on your PXE server. Usually, you would do this by downloading it to the PXE server from a location on the Internet specified by Red Hat or your hardware vendor. Names of driver update image files end in
.iso
. - Copy the driver update image file into the
/tmp/initrd_update
directory. - Rename the driver update image file to
dd.img
. - At the command line, change into the
/tmp/initrd_update
directory, type the following command, and press Enter:find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img
- Copy the file
/tmp/initrd_update.img
into the directory the holds the target that you want to use for installation. This directory is placed under the/tftpboot/pxelinux/
directory. For example,/tftpboot/pxelinux/r5su3/
might hold the PXE target for Red Hat Enterprise Linux 5.3 Server. - Edit the
/tftpboot/pxelinux/pxelinux.cfg/default
file to include an entry that includes the initial RAM disk update that you just created, in the following format:label target-dd kernel target/vmlinuz append initrd=target/initrd.img,target/dd.img
Where target is the target that you want to use for installation.
Example 13.1. Preparing an initial RAM disk update from a driver update image file
driver_update.iso
is a driver update image file that you downloaded from the Internet to a directory on your PXE server. The target that you want to PXE boot from is located in /tftpboot/pxelinux/r5su3
$ cp driver_update.iso /tmp/initrd_update/dd.img $ cd /tmp/initrd_update $ find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img $ cp /tmp/initrd_update.img /tftpboot/pxelinux/r5su3/dd.img
/tftpboot/pxelinux/pxelinux.cfg/default
file and include the following entry:
label r5su3-dd kernel r5su3/vmlinuz append initrd=r5su3/initrd.img,r5su3/dd.img
13.3. Performing a driver update during installation
- let the installer automatically find a driver update disk.
- let the installer prompt you for a driver update.
- use a boot option to specify a driver update disk.
- use a boot option to specify a driver update image file on a network.
- select a PXE target that includes a driver update.
13.3.1. Let the installer automatically find a driver update disk
OEMDRV
before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 13.2.1.1, “Preparing to use an image file on local storage” to prepare a storage device for the installer to find.
13.3.2. Let the installer prompt you for a driver update
- Begin the installation normally for whatever method you have chosen. If the installer cannot load drivers for a piece of hardware that is essential for the installation process (for example, if it cannot detect any network or storage controllers), it prompts you to insert a driver update disk:
Figure 13.5. The no driver found dialog
- Select Use a driver disk and refer to Section 13.4, “Specifying the location of a driver update image file or driver update disk”.
13.3.3. Use a boot option to specify a driver update disk
Important
- Type
linux dd
at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk:Figure 13.6. The driver disk prompt
- Insert the driver update disk that you created on CD, DVD, floppy disk, or USB storage device and select. The installer examines the storage devices that it can detect. If there is only one possible location that could hold a driver disk (for example, the installer detects the presence of a floppy disk, but no other storage devices) it will automatically load any driver updates that it finds at this location.If the installer finds more than one location that could hold a driver update, it prompts you to specify the location of the update. Refer to to Section 13.4, “Specifying the location of a driver update image file or driver update disk” .
13.3.4. Use a boot option to specify a driver update image file on a network
Important
linux dd=URL
(where URL is the HTTP, FTP, or NFS address of a driver update image) at the boot prompt at the start of the installation process and press Enter. The installer will retrieve the driver update image from that address and use it during installation.
13.3.5. Select a PXE target that includes a driver update
- Select
network boot
in your computer's BIOS or boot menu. The procedure to specify this option varies widely among different computers. Consult your hardware documentation or the hardware vendor for specifics relevant to your computer. - In the preexecution boot environment (PXE), choose the boot target that you prepared on your PXE server. For example, if you labeled this environment
r5su3-dd
in the/tftpboot/pxelinux/pxelinux.cfg/default
file on your PXE server, typer5su3-dd
at the prompt and press Enter.
13.4. Specifying the location of a driver update image file or driver update disk
Figure 13.7. Selecting a driver disk source
Figure 13.8. Selecting a driver disk partition
Figure 13.9. Selecting an ISO image
Chapter 14. Troubleshooting Installation on an IBM POWER System
http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html
14.1. You are Unable to Boot Red Hat Enterprise Linux
14.1.1. Is Your System Displaying Signal 11 Errors?
boot:
or yaboot:
prompt (prepend with elilo
for Itanium systems):
linux mediacheck
http://www.bitwizard.nl/sig11/
14.2. Trouble Beginning the Installation
14.2.1. Problems with Booting into the Graphical Installation
resolution=
boot option. Refer to Chapter 15, Additional Boot Options for IBM Power Systems for more information.
Note
nofb
boot option. This command may be necessary for accessibility with some screen reading hardware.
14.3. Trouble During the Installation
14.3.1. No devices found to install Red Hat Enterprise Linux
Error Message
No devices found to install Red Hat Enterprise Linux
, there is probably a SCSI controller that is not being recognized by the installation program.
14.3.2. Saving Traceback Messages Without a Diskette Drive
scp
the error message to a remote system.
/tmp/anacdump.txt
. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys Ctrl+Alt+F2
and scp
the message written to /tmp/anacdump.txt
to a known working remote system.
14.3.3. Trouble with Partition Tables
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
14.3.4. Other Partitioning Problems for IBM™ POWER System Users
- A
/
(root) partition - A <swap> partition of type swap
- A PPC PReP Boot partition.
- A /boot/ partition.
Note
14.3.5. Are You Seeing Python Errors?
/tmp/
directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/
are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
14.4. Problems After Installation
14.4.1. Unable to IPL from *NWSSTG
14.4.2. Booting into a Graphical Environment
startx
.
/etc/inittab
, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
su
command.
gedit /etc/inittab
to edit the file with gedit. The file /etc/inittab
opens. Within the first screen, a section of the file which looks like the following appears:
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
# id:3:initdefault:
id:3:initdefault:
from a 3
to a 5
.
Warning
3
to 5
.
id:5:initdefault:
14.4.3. Problems with the X Window System (GUI)
14.4.4. Problems with the X Server Crashing and Non-Root Users
df -h
df
command should help you diagnose which partition is full. For additional information about df
and an explanation of the options available (such as the -h
option used in this example), refer to the df
man page by typing man df
at a shell prompt.
/home/
and /tmp/
partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
14.4.5. Problems When You Try to Log In
linux single
.
#
prompt, you must type passwd root
, which allows you to enter a new password for root. At this point you can type shutdown -r now
to reboot the system with the new root password.
su -
and enter your root password when prompted. Then, type passwd <username>
. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/
14.4.6. Your Printer Does Not Work
system-config-printer
command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
Chapter 15. Additional Boot Options for IBM Power Systems
boot:
prompt.
Boot Time Command Arguments
askmethod
- this command asks you to select the installation method you would like to use when booting from the Red Hat Enterprise Linux CD-ROM.
dd
- this argument causes the installation program to prompt you to use a driver diskette.
dd=url
- this argument causes the installation program to prompt you to use a driver image from a specified HTTP, FTP, or NFS network address.
display=ip:0
- this command allows remote display forwarding. In this command, ip should be replaced with the IP address of the system on which you want the display to appear.On the system you want the display to appear on, you must execute the command
xhost +remotehostname
, where remotehostname is the name of the host from which you are running the original display. Using the commandxhost +remotehostname
limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access. driverdisk
- this command performs the same function as the
dd
command and also prompts you to use a driver diskette during the installation of Red Hat Enterprise Linux. ide=nodma
- this command disables DMA on all IDE devices and may be useful when having IDE-related problems.
mediacheck
- this command gives you the option of testing the integrity of the install source (if an ISO-based method). this command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during an installation.
mem=xxxm
- this command allows you to override the amount of memory the kernel detects for the machine. This may be needed for some older systems where only 16 mb is detected and for some new machines where the video card shares the video memory with the main memory. When executing this command, xxx should be replaced with the amount of memory in megabytes.
mpath
- enables multipath support.
Important
If you install Red Hat Enterprise Linux 5.11 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. noeject
- do not eject optical discs after installation. This option is useful in remote installations where it is difficult to close the tray afterwards.
nopass
- this command disables the passing of keyboard and mouse information to stage 2 of the installation program. It can be used to test keyboard and mouse configuration screens during stage 2 of the installation program when performing a network installation.
nopcmcia
- this command ignores any PCMCIA controllers in system.
noprobe
- this command disables hardware detection and instead prompts the user for hardware information.
noshell
- this command disables shell access on virtual console 2 during an installation.
nostorage
- this command disables probing for SCSI and RAID storage hardware.
nousb
- this command disables the loading of USB support during the installation. If the installation program tends to hang early in the process, this command may be helpful.
nousbstorage
- this command disables the loading of the usbstorage module in the installation program's loader. It may help with device ordering on SCSI systems.
rescue
- this command runs rescue mode. Refer to Chapter 27, Basic System Recovery for more information about rescue mode.
resolution=
- tells the installation program which video mode to run. it accepts any standard resolution, such as
640x480
,800x600
,1024x768
, and so on. serial
- this command turns on serial console support.
text
- this command disables the graphical installation program and forces the installation program to run in text mode.
updates
- this command prompts you to insert a floppy diskette containing updates (bug fixes) for the anaconda installation program. It is not needed if you are performing a network installation and have already placed the updates image contents in
rhupdates/
on the server. vnc
- this command allows you to install from a VNC server.
vncpassword=
- this command sets the password used to connect to the VNC server.
Part III. IBM System z Architecture - Installation and Booting
Chapter 16. Steps to Get You Started
16.1. Pre-Installation
http://www.redbooks.ibm.com/
Note
- Allocate sufficient Disk Storage Space using DASDs [8] or SCSI[9] partitions to provide suitable disk space (for example, 2 GB is sufficient for server installations, while 5 GB is minimally required to install all packages).
Important
Red Hat Enterprise Linux 5 cannot use unformatted DASDs when installing with kickstart and the cmdline user interface. Refer to theclearpart
documentation in Section 31.4, “Kickstart Options” for a method to ensure that DASDs are formatted during installation. - Acquire a minimum of 512 MB RAM (1 GB is strongly recommended) to designate for the Linux virtual machine.
- Determine if you need swap space and if so how much. While it is possible (and recommended) to assign enough memory to z/VM and let z/VM do the necessary swapping, there may be cases where the amount of required RAM is not predictable. Such instances should be examined on a case-by-case basis.
- Decide on the environment under which to run the operating system (on an LPAR or as a guest operating system on one or more virtual machines).
- Finally, it is important to review sections 3.3 through 3.8, and Chapters 5 and 6 of the IBM Linux for System z Redbook, as it explains the different configurations and install scenarios available on the zSeries platform as well as how to setup an initial LPAR or Linux virtual machine (z/VM).
16.2. Additional Hardware Preparation for System z
16.3. Basic Overview of the Boot Method
kernel.img
), the ram disk (initrd.img
), and if using z/VM, an optional CMS configuration file (redhat.conf
) and a parameter file. Sample parameter and CMS configuration files are provided (redhat.parm
and redhat.conf
). You should edit the CMS configuration file and add information about your DASD. You may also want to add some information about your network configuration. Once this is started on the IBM System z, the networking is configured. You can then use ssh on another computer to log into your installation image. Now you can start an installation script to install Red Hat Enterprise Linux.
16.4. Preparing for a Network Installation
Note
/location/of/disk/space
. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as /publicly/available/directory. For example, /location/of/disk/space
may be a directory you create called /var/isos
. /publicly/available/directory
might be /var/www/html/rhel5
, for an HTTP install.
- Create an iso image from the installation disk(s) using the following command (for DVDs):
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
where dvd refers to your DVD drive device.
16.4.1. Preparing for FTP and HTTP installation
RELEASE-NOTES
files and all files from the RedHat
directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD-ROM/ISO image):
- Insert CD-ROM or DVD-ROM.
mount /media/cdrom
- If you are installing the Server variant, run
cp -a /media/cdrom/Server <target-directory>
If you are installing the Client variant, runcp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory>
(Installation CD 1 or DVD only)cp /media/cdrom/images <target-directory>
(Installation CD 1 or DVD only)umount /media/cdrom
<target-directory>
represents the path to the directory to contain the installation tree.)
Note
/publicly/available/directory
directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
16.4.2. Preparing for an NFS install
- For DVD:
mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
- For CDROMs:
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory
directory is exported via NFS via an entry in /etc/exports
.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start
). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload
).
16.5. Preparing for a Hard Drive Installation
Note
- Using a set of CD-ROMs, or a DVD — Create ISO image files from each installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), execute the following command on a Linux system:
dd if=/dev/cdrom of=/tmp/file-name.iso
This command may raise an error message when the data at the end of the CD-ROM is reached which can be ignored. The ISO images created can now be used for installation, once copied to the correct DASD. - Using ISO images - transfer these to the system to be installed (or to the correct DASD or SCSI devices).Verifying that ISO images are intact before you attempt an installation, helps to avoid problems. To verify the ISO images are intact prior to performing an installation, use an
md5sum
program (manymd5sum
programs are available for various operating systems). Anmd5sum
program should be available on the same Linux machine as the ISO images.Make the correct DASDs or SCSI LUNs accessible to the new VM or LPAR, and then proceed with installation.Additionally, if a file calledupdates.img
exists in the location from which you install, it is used for updates toanaconda
, the installation program. Refer to the fileinstall-methods.txt
in theanaconda
RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
16.6. Installing under z/VM
i cms
vmlink tcpmaint 592 592
set qioassist off
kernel.img
and initrd.img
), log in, and execute the following commands. Use the (repl
option if you are overwriting existing kernel.img
, initrd.img
, generic.prm
, or redhat.exec
files:
cd /location/of/boot/images//images/
locsite fix 80
bin
get kernel.img (repl
get initrd.img (repl
ascii
get generic.prm (repl
get redhat.exec (repl
quit
redhat.parm
). Refer to Chapter 19, Sample Parameter Files for sample parm
files. Below is an explanation of the parm
file contents.
.parm
file is still required for the real kernel parameters, such as root=/dev/ram0 ro ip=off ramdisk_size=40000
, and single parameters which are not assigned to variables, such as vnc
. Two parameters which are used in z/VM installs to point the installation program at the new CMS configuration file need to be added to the .parm
file:
CMSDASD=191 CMSCONFFILE=redhat.conf
variable="value"
pairs, one on each line.
redhat.parm
file:
root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc
redhat.exec
file shipped by Red Hat is:
/* */ 'cl rdr' 'purge rdr all' 'spool punch * rdr' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'ch rdr all keep nohold' 'i 00c'
redhat.conf
file:
HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096"
DASD=dasd-list
Wheredasd-list
represents the list of DASD devices to be used by Red Hat Enterprise Linux.Although autoprobing for DASDs is done if this parameter is omitted, it is highly recommended to include theDASD=
parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in an unusable system.Additionally, in SAN-based environments, autoprobing in an LPAR-based install may have unintended side effects, as the number of DASD and SCSI volumes visible may be unexpectedly large and include volumes currently in use by other users. In particular, autoprobing during a kickstart install (which may have enabled autopartitioning to clear all partitions) is highly discouraged.root=file-system
wherefile-system
represents the device on which the root file system can be found. For installation purposes, it should be set to/dev/ram0
, which is the ramdisk containing the Red Hat Enterprise Linux installation program.
SUBCHANNELS=
Provides required device bus IDs for the various network interfaces.qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id, data_device_bus_id" lcs: SUBCHANNELS="read_device_bus_id,write_device_bus_id"
For example (a sample qeth SUBCHANNEL statement):SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
HOSTNAME=string
Wherestring
is the hostname of the newly-installed Linux guest.NETTYPE=type
Wheretype
must be one of the following:lcs
, orqeth
.Chooselcs
for:- OSA-2 Ethernet/Token Ring
- OSA-Express Fast Ethernet in non-QDIO mode
- OSA-Express High Speed Token Ring in non-QDIO mode
- Gigabit Ethernet in non-QDIO mode
Chooseqeth
for:- OSA-Express Fast Ethernet
- Gigabit Ethernet (including 1000Base-T)
- High Speed Token Ring
- HiperSockets
- ATM (running Ethernet LAN emulation)
IPADDR=IP
WhereIP
is the IP address of the new Linux guest.NETWORK=network
Wherenetwork
is the address of your network.NETMASK=netmask
Wherenetmask
is the netmask.BROADCAST=broadcast
Wherebroadcast
is the broadcast address.GATEWAY=gw
Wheregw
is the gateway-IP for youreth
device.MTU=mtu
Wheremtu
is the Maximum Transmission Unit (MTU) for this connection.DNS=server1:server2::serverN
Whereserver1:server2::serverN
is a list of DNS servers, separated by colons. For example:DNS=10.0.0.1:10.0.0.2
SEARCHDNS=domain1:domain2::domainN
Wheredomain1:domain2::domainN
is a list of the search domains, separated by colons. For example:SEARCHDNS=example.com:example.org
PORTNAME=osa_portname
|lcs_portnumber
This variable supports OSA devices operating in qdio mode or non-qdio mode.When using qdio mode: osa_portname is the portname specified on the OSA device when operating in qeth mode. PORTNAME is only required for z/VM 4.3 or older without APARs VM63308 and PQ73878.When using non-qdio mode: lcs_portnumber is used to pass the relative port number as integer in the range of 0 through 15.FCP_n="device_number SCSI_ID WWPN SCSI_LUN FCP_LUN"
The variables can be used on systems with FCP devices to preconfigure the FCP setup and can be subsequently edited in anaconda during the installation. An example value may look similar to:FCP_1="0.0.5000 0x01 0x5105074308c212e9 0x0 4010"
- n is an integer value (e.g.
FCP_1
,FCP_2
, ...). - device_number is used to specify the address of the FCP device (
0.0.5000
for device 5000, for example). - SCSI_ID is specified in hex-value, typically sequential values (e.g.
0x01
,0x02
... ) are used over multiple FCP_ variables. - WWPN is the world wide port name used for routing (often in conjunction with multipathing) and is as a 16-digit hex value (e.g.
0x5105074308c212e9
). - SCSI_LUN refers to the local SCSI logical unit value and is specified as a hex-value, typically sequential values (e.g. 0x00, 0x01, ...) are used over multiple FCP_ variables.
- FCP_LUN refers to the storage logical unit identifier and is specified as a hex-value (such as
0x4010
).
Note
Each of the values used in the FCP parameters (FCP_1, FCP_2, ...) are site-specific and are normally supplied by the FCP storage administrator.
Important
Important
RUNKS=value
Wherevalue
is defined as1
if you want to run the installation program in noninteractive (kickstart) mode in the 3270 terminal, or0
otherwise.cmdline
Whencmdline
is specified, 3270 terminal output becomes much more readable, as the installer disables most escape terminal sequences that are applicable to unix-like consoles, but not supported on the 3270 console.- Make sure that your kickstart file contains all required parameters before you use either of the RUNKS of cmdline options.
parm
file, a prompt appears during the installation boot process.
i cms
redhat.exec
that contains the commands necessary to IPL the kernel image and start the installation. After having IPLed CMS, enter redhat
on the 3270 console and press the Enter key to execute this script.
parm
file.
16.7. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD
- Log in on the Hardware Master Console (HMC) or the Support Element Workplace (SEW) as a user with sufficient privileges to install a new OS to an LPAR. The SYSPROG user is recommended.
- Select, then select the LPAR to which you wish to install. Use the arrows in the frame on the right side to navigate to the menu.
- Double-click on.
- In the dialog box that follows, select Local CD-ROM then click Continue.
- In the dialog that follows, keep the default selection of
generic.ins
then click Continue. - Skip to Section 16.9, “Installing in an LPAR (Common Steps)” to continue.
16.8. Installing in an LPAR without the Red Hat Enterprise Linux for System z CD-ROMs
- Log in on the Support Element Workplace as a user with sufficient privileges to install a new OS to an LPAR.
- Select, then select the LPAR you wish to install to.
- Use the arrows in the frame on the right side to navigate to themenu.
- Double-click on Load from CD-ROM or Server.
- In the dialog box that follows, select FTP Source, and enter the following information:
- Host Computer:
- Hostname or IP address of the FTP server you wish to install from (for example,
ftp.redhat.com
) - User ID:
- Your user name on the FTP server (or anonymous)
- Password:
- Your password (use your email address if you are logging in as anonymous)
- Account:
- Leave this field empty
- File location (can be left blank):
- Directory on the FTP server holding Red Hat Enterprise Linux for System z (for example,
/pub/redhat/linux/rawhide/s390x
)
- Click
- In the dialog that follows, keep the default selection of
redhat.ins
and click . - Refer to Section 16.9, “Installing in an LPAR (Common Steps)” to continue.
16.9. Installing in an LPAR (Common Steps)
Note
16.10. Do You Have Enough Disk Space?
dasda
has dasda[123]
.
Chapter 17. Installing on IBM System z Systems
- Becoming familiar with the installation program's user interface
- Starting the installation program
- Selecting an installation method
- Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
- Finishing the installation
17.1. The Graphical Installation Program User Interface
Note
17.2. The Text Mode Installation Program User Interface
Note
Figure 17.1. Installation Program Widgets as seen in Disk Druid
- Text Widget — Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the Up and Down arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a # character, which moves up and down the scroll bar as you scroll.
- Scroll Bar — Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file.
- Button Widget — Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the Tab and Enter keys. Buttons can be selected when they are highlighted.
- Cursor — Although not a widget, the cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or next to the widget. Figure 17.1, “Installation Program Widgets as seen in Disk Druid”, shows the cursor on the button.
17.2.1. Using the Keyboard to Navigate
Warning
17.3. Running the Installation Program
ssh
to the configured Linux install system on the IBM System z.
Note
DISPLAY=
variable in the parm
file. The text-based installation is similar to the graphical installation; however, the graphical installation offers more package selection details and other options not available in text-based installs. It is strongly recommended to use the graphical installation whenever possible.
17.3.1. Installation using X11 Forwarding
ssh -X linuxvm.example.com
-X
option enables X11 forwarding.
DISPLAY=
variable. Add the parameter DISPLAY=workstationname:0.0
in the parameter file, replacing workstationname with the hostname of the client workstation connecting to the Linux Image. Allow the Linux image to connect to the workstation using the command xhost +linuxvm
on the local workstation.
DISPLAY=
variable settings in the parm
file. If performing a VM installation, rerun the installation to load the new parm
file on the reader. Additionally, make sure when performing an X11 forwarded display that the X server is started on the workstation machine. Finally, make sure either the NFS, FTP or HTTP protocols are selected, as all 3 methods support graphical installations.
17.3.2. Installation using VNC
loader
will start the installation program.
loader
starts, several screens appear for selecting the installation method.
17.4. Installing from a Hard Drive (DASD)
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd
boot option, you already specified a partition.
/
. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/
, and the images are in /home/new/
, you would enter /new/
.
17.5. Installing via NFS
eastcoast
in the domain example.com
, enter eastcoast.example.com
in the NFS Server field.
/export/directory/
.
Figure 17.2. NFS Setup Dialog
17.6. Installing via FTP
askmethod
boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp
boot option, you already specified a server and path.
Figure 17.3. FTP Setup Dialog
variant/
directory for your architecture. For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
17.7. Installing via HTTP
askmethod
boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http
boot option, you already specified a server and path.
variant/
directory for your architecture. For example, if the HTTP site contains the directory /mirrors/redhat/arch/variant/
, enter /mirrors/redhat/arch/
(where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Figure 17.4. HTTP Setup Dialog
Note
mkdir discX
mount -o loop RHEL5-discX.iso discX
X
with the corresponding disc number.
17.8. Welcome to Red Hat Enterprise Linux
17.9. Language Selection
Figure 17.5. Language Selection
17.10. Enter the Installation Number
Figure 17.6. Installation Number
17.11. Disk Partitioning Setup
/home
partition that persistently contains user information).
Warning
Warning
/var/cache/yum/
by default. If you partition the system manually, and create a separate /var/
partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
Figure 17.7. Disk Partitioning Setup
Warning
Important
mapper/mpath
instead.
17.12. Advanced Storage Options
17.12.1. FCP Devices
Note
Figure 17.8. Advanced Storage Options
Figure 17.9. Configure FCP Device
Figure 17.10. Configure FCP Device
Note
17.13. Create Default Layout
- Remove all partitions on selected drives and create default layout — select this option to remove all partitions on your hard drive(s) (this includes partitions created by other operating systems such as z/VM or z/OS).
Warning
If you select this option, all data on the selected DASD and SCSI storage drive(s) is removed by the installation program. Do not select this option if you have information that you want to keep on the storage drive(s) where you are installing Red Hat Enterprise Linux. - Remove Linux partitions on selected drives and create default layout — select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your storage drive(s) (such as z/VM or z/OS partitions).
- Use free space on selected drives and create default layout — select this option to retain your current data and partitions, assuming you have enough free space available on your storage drive(s).
Figure 17.11. Create Default Layout
Warning
17.14. Partitioning Your System
Figure 17.12. Partitioning with Disk Druid
17.14.1. Graphical Display of DASD Device(s)
/boot
. The kernel files and bootloader sector will be associated with this device. For most common cases, the first DASD or SCSI LUN will be used, but for some unusual cases, this may not be the case. The device number will be used when re-ipling the post-installed system.
17.14.2. Disk Druid's Buttons
- Partitions section. Selecting opens a dialog box. Some or all of the fields can be edited, depending on whether the partition information has already been written to disk.: Used to modify attributes of the partition currently selected in the
- It should only be used if you have experience using RAID. To read more about RAID, see the Red Hat Enterprise Linux Deployment Guide.: Used to provide redundancy to any or all disk partitions.To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, selectto join the software RAID partitions into a RAID device.
17.14.3. Partition Fields
- Device: This field displays the partition's device name.
- Mount Point/RAID/Volume: A mount point is the location within the directory hierarchy at which a volume exists; the volume is "mounted" at this location. This field indicates where the partition is mounted. If a partition exists, but is not set, then you need to define its mount point. Double-click on the partition or click the button.
- Type: This field shows the partition's file system type (for example, ext2, ext3, or vfat).
- Format: This field shows if the partition being created will be formatted.
- Size (MB): This field shows the partition's size (in MB).
- Start: This field shows the cylinder on your hard drive where the partition begins.
- End: This field shows the cylinder on your hard drive where the partition ends.
17.14.4. Recommended Partitioning Scheme
- 'Chapter 7. Linux Swapping' in the IBM Redbook Linux on IBM System z: Performance Measurement and Tuning [IBM Form Number SG24-6926-01], [ISBN 0738485586], available from http://www.redbooks.ibm.com/abstracts/sg246926.html
- Linux on System z performance in the IBM Systems Information Center at http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/liaag/lcon_Linux_on_System_z_performance.htm
- Linux Performance when running under VM, available from http://www.vm.ibm.com/perf/tips/linuxper.html
17.15. Network Configuration
Figure 17.13. Network Configuration
Note
qdio/qeth
devices that are configured with OSA layer 3 support. Layer 3 does not provide MAC address or Address Resolution Protocol (ARP) abilities and so can not be used with network services that require them.
Figure 17.14. Editing a Network Device
Note
17.16. Time Zone Configuration
- Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection.
- You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
Note
system-config-date
command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig
.
17.17. Set Root Password
Note
Figure 17.15. Root Password
su -
to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
Note
su -
at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
Note
Note
system-config-rootpassword
command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
17.18. Package Group Selection
Note
Figure 17.16. Package Group Selection
Figure 17.17. Package Group Details
17.19. Preparing to Install
17.19.1. Preparing to Install
/root/install.log
once you reboot your system.
Warning
17.20. Installing Packages
17.21. Installation Complete
/boot
partition for Red Hat Enterprise Linux has been installed.
200
on the 3270 console you may issue the command #cp i 200
. Often, especially in DASD only environments where automatic partitioning (clearing data from all partitions) was chosen, the first dasd (dasda
) is where the /boot
partition is located.
/boot
on a SCSI LUN in a z/VM guest account, it may be necessary to provide WWPN and LUN information through which a zFCP device can ipl. As an example,
#CP SET LOADDEV PORTNAME 50050763 FCCD9689 LUN 83030000 00000000
0x50050763FCCD9689
is the example WWPN, and 8303
is the SCSI LUN). Then the zFCP device information can be queried and used to start the IPL:
#cp q v fcp
4322
in this example) could be ipl-ed with a command like:
#cp ipl 4322
/boot
partition is located.
Note
#cp disc
instead of #cp logout
or #cp log
. This allows for the virtual system running Red Hat Enterprise Linux for IBM System z to continue even when not connected to the 3270 console.
ssh
. It is important to note that the only place you can log in as root is from the 3270 or from other devices as listed in /etc/securetty
.
Chapter 18. Removing Red Hat Enterprise Linux
Chapter 19. Sample Parameter Files
.parm
file should contain the real kernel parameters, such as root=/dev/ram0 ro ip=off ramdisk_size=40000
, and single parameters which are not assigned to variables, such as vnc
. Two new parameters which point the installation program at the new configuration file need to be added to the .parm
file. They are CMSDASD
and CMSCONF
.
CMSDASD=cmsdasd_address
- Where cmsdasd_address represents the list of the device ID of the CMS DASD device which contains the configuration file. This is usually the CMS user's 'A' disk. This option is applicable only for users who have a CMS formatted disk (z/VM) available.For example:
CMSDASD=191
CMSCONFFILE=configuration_file
- Where configuration_file represents the name of the configuration file. This value must be specified in lower case. It is specified in a Linux style file name format. The CMS file
REDHAT CONF
is specified asredhat.conf
. This option is applicable only for users who have a CMS formatted disk (z/VM) available.For example:CMSCONFFILE=redhat.conf
DASD=dasd-list
- Where dasd-list represents the list of DASD devices to be used by Red Hat Enterprise Linux.Although automatic probing for DASDs is done if this parameter is omitted, it is highly recommended to include the
DASD=
parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the guest. This can result in an unusable system.For example:DASD=0.0.0100,0.0201-0.0.0204
SUBCHANNELS=
- Provides required device bus IDs for the various network interfaces.
qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id, data_device_bus_id" lcs: SUBCHANNELS="read_device_bus_id,write_device_bus_id"
Due to the length of the qeth command line, it has been broken into two lines.Note
The CTC, and NETIUCV drivers have been deprecated and are no longer supported in Red Hat Enterprise Linux.For example (a sample qeth SUBCHANNEL statement):SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
HOSTNAME=string
- Where string is the hostname of the newly-installed Linux guest.
NETTYPE=type
- Where type must be one of the following: qeth or lcs.
IPADDR=IP
- Where IP is the IP address of the new Linux guest.
NETWORK=network
- Where network is the address of your network.
NETMASK=netmask
- Where netmask is the netmask.
BROADCAST=broadcast
- Where broadcast is the broadcast address.
GATEWAY=gw
- Where gw is the gateway-IP for your eth device.
MTU=mtu
- Where mtu is the Maximum Transmission Unit (MTU) for this connection.
DNS=server1:server2:additional_server_terms:serverN
- Where server1:server2:additional_server_terms:serverN is a list of DNS servers, separated by colons. For example:
DNS=10.0.0.1:10.0.0.2
SEARCHDNS=domain1:domain2:additional_dns_terms:domainN
- Where domain1:domain2:additional_dns_terms:domainN is a list of the search domains, separated by colons. For example:
SEARCHDNS=example.com:example.org
PORTNAME=osa_portname | lcs_portnumber
- This variable supports OSA devices operating in qdio mode or in non-qdio mode.When using qdio mode: osa_portname is the portname specified on the OSA device when operating in qeth mode. PORTNAME is only required for z/VM 4.3 or older without APARs VM63308 and PQ73878.When using non-qdio mode: lcs_portnumber is used to pass the relative port number as integer in the range of 0 through 15.
PORTNO=portnumber
- When installing under z/VM, you can add either
PORTNO=0
(to use port 0) orPORTNO=1
(to use port 1) to the CMS configuration file to avoid being prompted for the mode.ThePORTNO=
setting also works on LPAR, but you must place it directly in the parmfile rather than the CMS configuration file. LAYER2=
- Add either
LAYER2=0
orLAYER2=1
to the CMS configuration file to make the mode persistent when installing on a System z guest.UseLAYER2=0
when the OSA is in layer 3 mode, andLAYER2=1
when the OSA is in layer 2 mode. VSWITCH=
- When specifying
LAYER2=1
, you can also specifyVSWITCH=1
when connecting to a VSWITCH, orVSWITCH=0
when connecting directly to the OSA. MACADDR=MAC_address
- When specifying
LAYER2=1
and a VSWITCH is not in use, you can use this parameter to specify the MAC address in the CMS configuration file. - FCP_* (FCP_1, FCP_2, ...)
- These variables can be used on systems with FCP devices to preconfigure the FCP setup (these can be changed during the installation).
root=/dev/ram0 DASD=200
Note
redhat.parm
file:
root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc
redhat.conf
file (pointed to by CMSCONFFILE in redhat.parm
)
DASD=200 HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096"
Chapter 20. Additional Boot Options
boot:
prompt.
zipl.conf
file, either by editing the file manually or using the zipl tool.
Important
parameters="vmhalt='LOGOFF'"
is correct, while parameters='vmhalt="LOGOFF"'
is not correct and may lead to unexpected behavior.
boot time command arguments
askmethod
- this command asks you to select the installation method you would like to use when booting from the Red Hat Enterprise Linux CD-ROM.
dd=url
- this argument causes the installation program to prompt you to use a driver image from a specified HTTP, FTP, or NFS network address.
display=ip:0
- this command allows remote display forwarding. In this command, ip should be replaced with the IP address of the system on which you want the display to appear.On the system you want the display to appear on, you must execute the command
xhost +remotehostname
, where remotehostname is the name of the host from which you are running the original display. Using the commandxhost +remotehostname
limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access. mediacheck
- this command gives you the option of testing the integrity of the install source (if an ISO-based method). this command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during an installation.
mpath
- enables multipath support.
Important
If you install Red Hat Enterprise Linux 5.11 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. noeject
- do not eject optical discs after installation. This option is useful in remote installations where it is difficult to close the tray afterwards.
noprobe
- this command disables hardware detection and instead prompts the user for hardware information.
rescue
- this command runs rescue mode. Refer to Chapter 27, Basic System Recovery for more information about rescue mode.
text
- this command disables the graphical installation program and forces the installation program to run in text mode.
vnc
- this command allows you to install from a VNC server.
vncpassword=
- this command sets the password used to connect to the VNC server.
noipv6
- this command disables the default selection of ipv6 options during the installer stage 1 processing. Ipv6 settings may still be made manually if this option is specified, but the default behavior will be that Ipv6 settings are not enabled.
cmdline
- The 3270 console (most often used during installation on IBM System z) does not recognize terminal formatting entries common to most unix-style terminals. Specifying this option changes the behavior of anaconda during kickstart installations so that console output on the 3270 is much better. This option should not be used for regular, interactive installations.
RUNKS=1
- This option is used to specify (usually in conjunction with the
cmdline
option) kickstart installation for IBM System z.
Chapter 21. Troubleshooting Installation on an IBM System z System
21.1. You are Unable to Boot Red Hat Enterprise Linux
21.1.1. Is Your System Displaying Signal 11 Errors?
21.2. Trouble During the Installation
21.2.1. No devices found to install Red Hat Enterprise Linux
Error Message
No devices found to install Red Hat Enterprise Linux
, then there may be an issue with your DASD devices. If you encounter this error, add the DASD=<disks>
parameter to your parm
file (where disks is the DASD range reserved for installation) and start the install again.
dasdfmt
command within a Linux root shell, instead of formatting the DASDs using CMS.
21.2.2. Trouble with Partition Tables
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
21.2.3. Other Partitioning Problems
- A
/
(root) partition - A <swap> partition of type swap
Note
21.2.4. Are You Seeing Python Errors?
/tmp/
directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/
are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
21.3. Problems After Installation
21.3.1. Remote Graphical Desktops and XDMCP
/etc/gdm/custom.conf
file on the Red Hat Enterprise Linux system with a text editor such as vi
or nano
:
Enable=true
, save the file, and exit the text editor. Switch to runlevel 5 to start the X server:
/sbin/init 5
X
. For example:
X :1 -query s390vm.example.com
:1
of the client system (usually accessible by using the Ctrl-Alt-F8 key combination).
Xnest
allows users to open a remote desktop nested within their local X session. For example, run Xnest
using the following command, replacing s390vm.example.com with the hostname of the remote X server:
Xnest :1 -query s390vm.example.com
21.3.2. Problems When You Try to Log In
linux single
.
#
prompt, you must type passwd root
, which allows you to enter a new password for root. At this point you can type shutdown -r now
to reboot the system with the new root password.
su -
and enter your root password when prompted. Then, type passwd <username>
. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/
21.3.3. Your Printer Does Not Work
system-config-printer
command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
Chapter 22. Additional Information for IBM System z Users
22.1. The sysfs
File System
sysfs
file system. The sysfs
file system is described as a union of the proc
, devfs
, and devpty
file systems. The sysfs
file system enumerates the devices and busses attached to the system into a file system hierarchy that can be accessed from user space. It is designed to handle the device and driver specific options that have previously resided in /proc/
, and encompass the dynamic device addition previously offered by devfs
.
sysfs
file system is mounted at /sys/
and contains directories that organize the devices attached to the system in several different ways. The /sysfs/
subdirectories include:
- The
/devices/
directoryThis directory contains the/css0/
directory. Its subdirectories represent all the subchannels detected by the Linux kernel. Subchannel directories are named in the form0.0.nnnn
where nnnn is the subchannel number in hex between 0000 and ffff. Subchannel directories in turn contain status files and another subdirectory which represents the actual device. The device directory is named0.0.xxxx
where xxxx is the unit address for the device. The/devices/
directory also contains status information as well as configuration options for the device. - The
/bus/
directoryThis contains a/ccw/
subdirectory and a/ccwgroup/
subdirectory. CCW devices are accessed using channel command words. Devices in the/ccw/
directory only use one subchannel on the mainframe channel subsystem. CCW group devices are also accessed with channel command words, but they use more than one subchannel per device. For example, a 3390-3 DASD device uses one subchannel, while a QDIO network connection for an OSA adapter uses three subchannels. The/ccw/
and the/ccwgroup/
directories both contain directories called devices and drivers:The/devices/
directory contains a symbolic link to the device directories in the/sys/devices/css0/
directory.The/drivers/
directory contains directories for each device driver currently loaded on the system. Drivers associated with devices such asdasd
,console
,qeth
, andzfcp
have directory entries here. The/driver/
directory contains settings for the device driver, as well as symbolic links to the devices it is using (in the/sys/devices/css0/
directory). - The
/class/
directoryThis contains directories that group together similar devices such as ttys, SCSI tape drives, network devices, and other miscellaneous devices. - The
/block/
directoryThis directory contains directories for each of the block devices on the system. These are mostly disk type devices such as real DASD, loopback devices, and software raid block devices. The noticeable difference between older Linux systems and ones that usesysfs
is the need to refer to devices by theirsysfs
name. On a 2.4 kernel image, thezFCP
driver was passed as its device addresses. On the 2.6 Kernel image system the driver is passed as0.0.1600
.
22.2. Using the zFCP
Driver
/etc/zfcp.conf
file which contains your SCSI configuration. It also adds the line alias scsi_hostadapter zFCP
to /etc/modprobe.conf
. This loads the required zFCP
modules.
# cat /etc/zfcp.conf 0.0.010a 0x01 0x5005076300c18154 0x00 0x5719000000000000 # cat /etc/modprobe.conf alias eth0 qeth options dasd_mod dasd=201,4b2e alias scsi_hostadapter zfcp
# cd /lib/modules/2.6.7-1.451.2.3/kernel/drivers/s390/scsi # modprobe zfcp # lsmod Module Size Used by zfcp 221460 0 [permanent] autofs4 39944 0 qeth 166288 0 qdio 60240 3 zfcp,qeth ccwgroup 25344 1 qeth ipt_REJECT 23552 1 ipt_state 18944 5 ip_conntrack 57904 1 ipt_state iptable_filter 19712 1 ip_tables 37888 3 ipt_REJECT,ipt_state,iptable_filter sd_mod 39688 0 scsi_mod 182904 2 zfcp,sd_mod dm_mod 86408 0 ext3 179056 2 jbd 92720 1 ext3 dasd_fba_mod 25344 0 dasd_eckd_mod 77056 4 dasd_mod 85328 6 dasd_fba_mod,dasd_eckd_mod # cd /sys/bus/ccw/drivers/zfcp/0.0.010a # echo 1 > online # cat online 1 # echo 0x5005076300c18154 > /sys/bus/ccw/drivers/zfcp/0.0.010a/port_add # ls 0x5005076300c18154 failed lic_version s_id availability fc_link_speed nameserver status card_version fc_service_class online wwnn cmb_enable fc_topology port_add wwpn cutype hardware_version port_remove detach_state host2 scsi_host_no devtype in_recovery serial_number # cd /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154 # echo 0x5719000000000000 > unit_add # ls 0x5719000000000000 d_id in_recovery status unit_remove detach_state failed scsi_id unit_add wwnn # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/scsi_host_no 0x0 # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id 0x1 # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun 0x0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.010a # cat /sys/bus/scsi/devices/0\:0\:1\:0/wwpn 0x5005076300c18154 # cat /sys/bus/scsi/devices/0\:0\:1\:0/fcp_lun 0x5719000000000000 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/dev 8:0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/sda1/dev 8:1 # cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: 2105F20 Rev: .123 Type: Direct-Access ANSI SCSI revision: 03 # fdisk /dev/sda # mke2fs -j /dev/sda1 # mount /dev/sda1 /mnt # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2344224 1427948 797196 65% / none 511652 0 511652 0% /dev/shm /dev/dasdb1 2365444 32828 2212456 2% /opt /dev/sda1 3844088 32828 3615988 1% /mnt # cd /boot # mv initrd-2.6.7-1.451.2.3.img initrd-2.6.7-1.451.2.3.img.orig # mkinitrd -v --with=scsi_mod --with=zfcp --with=sd_mod initrd-2.6.7-1.451.2.3.img 2.6.7-1.451.2.3 Looking for deps of module ide-disk Looking for deps of module dasd_mod Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Looking for deps of module scsi_mod Looking for deps of module zfcp qdio scsi_mod Looking for deps of module qdio Looking for deps of module scsi_mod Looking for deps of module sd_mod scsi_mod Looking for deps of module scsi_mod Using modules: ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/s390/cio/qdio.ko ./kernel/drivers/s390/scsi/zfcp.ko ./kernel/drivers/scsi/sd_mod.ko Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.cT1534/bin/nash /sbin/insmod.static -> /tmp/initrd.cT1534/bin/insmod `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko'-> `/tmp/initrd.cT1534/lib/dasd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_eckd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_fba_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko' -> `/tmp/initrd.cT1534/lib/jbd.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko' -> `/tmp/initrd.cT1534/lib/ext3.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/scsi_mod.ko' -> `/tmp/initrd.cT1534/lib/scsi_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/cio/qdio.ko' -> `/tmp/initrd.cT1534/lib/qdio.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/scsi/zfcp.ko' -> `/tmp/initrd.cT1534/lib/zfcp.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/sd_mod.ko' -> `/tmp/initrd.cT1534/lib/sd_mod.ko' ... Loading module dasd_mod with options dasd=201,4b2e Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3 Loading module scsi_mod Loading module qdio Loading module zfcp Loading module sd_mod # zipl -V Using config file '/etc/zipl.conf' Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: 0201 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 3308 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 595416 Building bootmap '/boot//bootmap' Building menu 'rh-automatic-menu' Adding #1: IPL section 'linux' (default) kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000 kernel parmline...: 'root=LABEL=/' at 0x1000 initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000 Preparing boot device: dasda (0201). Preparing boot menu Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: 'linux' Syncing disks... Done.
22.3. Using mdadm
to Configure RAID-Based and Multipath Storage
raidtools
package set, the mdadm
command can be used to perform all the necessary functions related to administering multiple-device sets. This section explains how mdadm
can be used to:
- Create a RAID device
- Create a multipath device
22.3.1. Creating a RAID Device With mdadm
/etc/mdadm.conf
file to define appropriate DEVICE
and ARRAY
values:
DEVICE /dev/sd[abcd]1 ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
DEVICE
line is using traditional file name globbing (refer to the glob
(7) man page for more information) to define the following SCSI devices:
/dev/sda1
/dev/sdb1
/dev/sdc1
/dev/sdd1
ARRAY
line defines a RAID device (/dev/md0
) that is comprised of the SCSI devices defined by the DEVICE
line.
/proc/mdstat
file shows no active RAID devices:
Personalities : read_ahead not set Event: 0 unused devices: none
mdadm
command to create a RAID 0 array:
mdadm -C /dev/md0 --level=raid0 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 \ /dev/sdd1 Continue creating array? yes mdadm: array /dev/md0 started.
mdadm --detail /dev/md0
:
/dev/md0: Version : 00.90.00 Creation Time : Mon Mar 1 13:49:10 2004 Raid Level : raid0 Array Size : 15621632 (14.90 GiB 15.100 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Mar 1 13:49:10 2004 State : dirty, no-errors Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Chunk Size : 64K Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 2 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1 UUID : 25c0f2a1:e882dfc0:c0fe135e:6940d932 Events : 0.1
22.3.2. Creating a Multipath Device With mdadm
mdadm
can also be used to take advantage of hardware supporting more than one I/O path to individual SCSI LUNs (disk drives). The goal of multipath storage is continued data availability in the event of hardware failure or individual path saturation. Because this configuration contains multiple paths (each acting as an independent virtual controller) accessing a common SCSI LUN (disk drive), the Linux kernel detects each shared drive once "through" each path. In other words, the SCSI LUN (disk drive) known as /dev/sda
may also be accessible as /dev/sdb
, /dev/sdc
, and so on, depending on the specific configuration.
mdadm
includes an additional parameter to its level
option. This parameter multipath
directs the md layer in the Linux kernel to re-route I/O requests from one pathway to another in the event of an I/O path failure.
/etc/mdadm.conf
file to define values for the DEVICE
and ARRAY
lines that reflect your hardware configuration.
Note
/etc/mdadm.conf
must represent different physical disk drives), each device in this file refers to the same shared disk drive.
multipath
parameter:
mdadm -C /dev/md0 --level=multipath --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 Continue creating array? yes mdadm: array /dev/md0 started.
/dev/md0
is created, all I/O operations referencing /dev/md0
are directed to /dev/sda1
, /dev/sdb1
, /dev/sdc1
, or /dev/sdd1
(depending on which path is currently active and operational).
/dev/md0
can be examined more closely using the command mdadm --detail /dev/md0
to verify that it is, in fact, a multipath device:
/dev/md0: Version : 00.90.00 Creation Time : Tue Mar 2 10:56:37 2004 Raid Level : multipath Array Size : 3905408 (3.72 GiB 3.100 GB) Raid Devices : 1 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue Mar 2 10:56:37 2004 State : dirty, no-errors Active Devices : 1 Working Devices : 4 Failed Devices : 0 Spare Devices : 3 Number Major Minor RaidDevice State 0 8 49 0 active sync /dev/sdd1 1 8 17 1 spare /dev/sdb1 2 8 33 2 spare /dev/sdc1 3 8 1 3 spare /dev/sda1 UUID : 4b564608:fa01c716:550bd8ff:735d92dc Events : 0.1
mdadm
is the ability to force a device (be it a member of a RAID array or a path in a multipath configuration) to be removed from an operating configuration. In the following example, /dev/sda1
is flagged as being faulty, is then removed, and finally is added back into the configuration. For a multipath configuration, these actions would not affect any I/O activity taking place at the time:
# mdadm /dev/md0 -f /dev/sda1 mdadm: set /dev/sda1 faulty in /dev/md0 # mdadm /dev/md0 -r /dev/sda1 mdadm: hot removed /dev/sda1 # mdadm /dev/md0 -a /dev/sda1 mdadm: hot added /dev/sda1 #
22.4. Configuring IPL from a SCSI Device
22.4.1. IPL the SCSI Disk
SET LOADDEV
command.
#cp set loaddev portname 50050763 00c18154 lun 57190000 00000000 Ready; T=0.01/0.01 15:47:53 q loaddev PORTNAME 50050763 00C18154 LUN 57190000 00000000 BOOTPROG 0 BR_LBA 00000000 00000000 Ready; T=0.01/0.01 15:47:56
q fcp 00: FCP 010A ON FCP 010ACHPID C1 SUBCHANNEL = 0000 00: 010A QDIO-ELIGIBLE QIOASSIST-ELIGIBLE Ready; T=0.01/0.01 15:51:29 i 010a 00: I 010A 00: HCPLDI2816I Acquiring the machine loader from the processor controller. 00: HCPLDI2817I Load completed from the processor controller. 00: HCPLDI2817I Now starting machine loader version 0001. 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 00. 00: MLOEVL012I: Machine loader up and running (version 0.13). 00: MLOPDM003I: Machine loader finished, moving data to final storage location. Linux version 2.6.7-1.451.2.3 (bhcompile@example.z900.redhat.com) (gcc version 3.4 .1 20040702 (Red Hat Linux 3.4.1-2)) #1 SMP Wed Jul 14 17:52:22 EDT 2004 We are running under VM (64 bit mode)
Note
22.5. Adding DASD
Note
CP LINK RHEL4X 4B2E 4B2E MR DASD 4B2E LINKED R/W
Procedure 22.1. Bringing a disk online
- Use the
cd
command to change to the/sys/
directory that represents that volume:# cd /sys/bus/ccw/drivers/dasd-eckd/0.0.4b2e/ # ls -l total 0 -r--r--r-- 1 root root 4096 Aug 25 17:04 availability -rw-r--r-- 1 root root 4096 Aug 25 17:04 cmb_enable -r--r--r-- 1 root root 4096 Aug 25 17:04 cutype -rw-r--r-- 1 root root 4096 Aug 25 17:04 detach_state -r--r--r-- 1 root root 4096 Aug 25 17:04 devtype -r--r--r-- 1 root root 4096 Aug 25 17:04 discipline -rw-r--r-- 1 root root 4096 Aug 25 17:04 online -rw-r--r-- 1 root root 4096 Aug 25 17:04 readonly -rw-r--r-- 1 root root 4096 Aug 25 17:04 use_diag
- Next, check to see if it is already online:
# cat online 0
- If it is not online, run the following command to bring it online:
# echo 1 > online # cat online 1
- Verify which block devnode it is being accessed as:
# ls -l total 0 -r--r--r-- 1 root root 4096 Aug 25 17:04 availability lrwxrwxrwx 1 root root 0 Aug 25 17:07 block -> ../../../../block/dasdb -rw-r--r-- 1 root root 4096 Aug 25 17:04 cmb_enable -r--r--r-- 1 root root 4096 Aug 25 17:04 cutype -rw-r--r-- 1 root root 4096 Aug 25 17:04 detach_state -r--r--r-- 1 root root 4096 Aug 25 17:04 devtype -r--r--r-- 1 root root 4096 Aug 25 17:04 discipline -rw-r--r-- 1 root root 0 Aug 25 17:04 online -rw-r--r-- 1 root root 4096 Aug 25 17:04 readonly -rw-r--r-- 1 root root 4096 Aug 25 17:04 use_diag
As shown in this example, device 4B2E is being accessed as/dev/dasdb
.
# chccwdev -e 4b2e
/root
directory and format the device:
# cd # dasdfmt -b 4096 -d cdl -f /dev/dasdb -l LX4B2E -p -y cyl 97 of 3338 |#----------------------------------------------| 2%
fdasd
to partition the device:
# fdasd -a /dev/dasdb auto-creating one partition for the whole disk... writing volume label... writing VTOC... checking ! wrote NATIVE! rereading partition table...
# mke2fs -j /dev/dasdb1 mke2fs 1.35 (28-Feb-2004) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 300960 inodes, 600816 blocks 30040 blocks (5.00%) reserved for the super user First data block=0 19 block groups 32768 blocks per group, 32768 fragments per group 15840 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 39 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
# mount /dev/dasdb1 /opt # mount /dev/dasda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /dev/shm type tmpfs (rw) /dev/dasdb1 on /opt type ext3 (rw)
/etc/fstab
so that the file system is mounted at IPL time:
# vi /etc/fstab # cat /etc/fstab LABEL=/ / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/dasdb1 /opt ext3 defaults 1 2
/etc/modprobe.conf
Make sure to add the new device at the end of the list, otherwise it changes the device number : devnode mapping and file systems are not on the devices they used to be on.
# vi /etc/modprobe.conf # cat /etc/modprobe.conf alias eth0 qeth options dasd_mod dasd=201,4B2E
mkinitrd
to pick up the changes to modprobe.conf
so that the device can be online and mountable after the next IPL:
/tmp/initrd.AR1182/lib/dasd_mod.ko(elf64-s390)
.
# cd /boot # mv initrd-2.6.7-1.451.2.3.img initrd-2.6.7-1.451.2.3.img.old # mkinitrd -v initrd-2.6.7-1.451.2.3.img 2.6.7-1.451.2.3 Looking for deps of module ide-disk Looking for deps of module dasd_mod Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Using modules: ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.AR1182/bin/nash /sbin/insmod.static -> /tmp/initrd.AR1182/bin/insmod copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_mod.ko(elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_eckd_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_fba_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko(elf64-s390) to /tmp/initrd.AR1182/lib/jbd.ko(elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko(elf64-s390) to /tmp/initrd.AR1182/lib/ext3.ko(elf64-s390) Loading module dasd_mod with options dasd=201,4B2E Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3
zipl
to save the changes to initrd
for the next IPL:
# zipl -V Using config file '/etc/zipl.conf' Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: 0201 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 3308 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 595416 Building bootmap '/boot//bootmap' Building menu 'rh-automatic-menu' Adding #1: IPL section 'linux' (default) kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000 kernel parmline...: 'root=LABEL=/' at 0x1000 initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000 Preparing boot device: dasda (0201). Preparing boot menu Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: 'linux' Syncing disks... Done.
22.6. Adding a Network Device
- The
proc
file system is no longer used to control or obtain status on network devices. - The new
sys
file system now provides facilities for controlling devices. /sys/class/net/interface_name/device
now provides status on active devices.interface_name
is a name such aseth0
oreth2
that is given to a network interface by the device driver when the device is configured./etc/chandev.conf
no longer exists.Thesys
file system now contains the information that was placed in/etc/chandev.conf
./etc/modules.conf
no longer exists.Network interface alias specifications are now placed in/etc/modprobe.conf
.
qeth
Device” describes in detail how to add a qeth device to an existing instance of Red Hat Enterprise Linux. Section 22.6.2, “Quick Reference for Adding Network Devices” is a quick reference for installing other IBM System z network interfaces.
22.6.1. Adding a qeth
Device
qeth
device driver modules are loaded.
# lsmod | grep qeth qeth 135240 0 qdio 45360 2 qeth ipv6 303984 13 qeth ccwgroup 15104 1 qeth
lsmod
command shows that the modules are not loaded, you must run the modprobe
command to load them:
# modprobe qeth
qeth
group device.
# echo read_device_bus_id,write_device_bus_id, data_device_bus_id > /sys/bus/ccwgroup/drivers/qeth/group
# echo 0.0.0600,0.0.0601,0.0.0602 > /sys/bus/ccwgroup/drivers/qeth/group
qeth
group device was created properly:
# ls /sys/bus/ccwgroup/drivers/qeth 0.0.0600 0.0.09a0 group notifier_register
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/portname no portname required
Note
# echo portname > /sys/bus/ccwgroup/drivers/qeth/0.0.0600/portname
# echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0600/online
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/online 1
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/if_name eth1
add_hhlen
broadcast_mode
buffer_count
canonical_macaddr
checksumming
detach_state
fake_broadcast
fake_ll
ipa_takeover
portno
priority_queueing
recover
route4
rxip
ungroup
vipa
/etc/sysconfig/network-scripts/
.
if_name
file in the qeth group device that was created earlier. In this example it is eth1
.
# cd /etc/sysconfig/network-scripts # cp ifcfg-eth0 ifcfg-eth1
ifcfg-eth0
as a template.
/etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 BOOTPROTO=static HWADDR=00:06:29:FB:5F:F1 IPADDR=9.12.20.136 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.09a0,0.0.09a1,0.0.09a2 TYPE=Ethernet
ifcfg-eth1
file.
if_name
file from your ccwgroup.
yes
.
qeth
device.
/etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.70.87 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet
qeth
device requires an alias definition in /etc/modprobe.conf
. Edit this file and add an alias for your interface.
/etc/modprobe.conf alias eth0 qeth alias eth1 qeth options dasd_mod dasd=0.0.0100,0.0.4b19
# ifup eth1
# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:01 inet addr:192.168.70.87 Bcast:192.168.70.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:1/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:644 (644.0 b) TX bytes:264 (264.0 b)
HWaddr
field in the first line of the ifconfig
command output. The value after that must be added to the ifcfg-eth1
file. Add a line like the following to that file:
HWADDR=02:00:00:00:00:01
ifcfg-eth1
looks similar to the following:
# IBM QETH DEVICE=eth1 HWADDR=02:00:00:00:00:01 BOOTPROTO=static IPADDR=192.168.70.69 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet
# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.70.0 * 255.255.255.0 U 0 0 0 eth1 9.12.20.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 default pdlrouter-if5.p 0.0.0.0 UG 0 0 0 eth0
ping
command to ping the gateway:
# ping -c 1 192.168.70.8 PING 192.168.70.8 (192.168.70.8) 56(84) bytes of data. 64 bytes from 192.168.70.8: icmp_seq=0 ttl=63 time=8.07 ms
/etc/sysconfig/network
accordingly.
22.6.2. Quick Reference for Adding Network Devices
- Load the device driver.
- Create the group device.
- Configure the device.
- Set the device online.
- Define the alias (if needed).
- Create a configuration script.
- Activate the device.
22.6.2.1. Working With the LCS Device Driver
- Load the device driver:
# modprobe lcs
- Create the group device:
# echo read_device_bus_id,write_device_bus_id > /sys/bus/ccwgroup/drivers/lcs/group
Due to the length of this command, it has been broken into two lines. - Configure the device.OSA cards can provide up to 16 ports for a single CHPID. By default, the LCS group device uses port 0. To use a different port, issue a command similar to the following:
# echo portno > /sys/bus/ccwgroup/drivers/lcs/device_bus_id/portno
For more information about configuration of the LCS driver, refer to the following:http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC33-8289-02 (Linux for IBM System z and S/390 Device Drivers, Features, and Commands) - Set the device online:
# echo 1 > /sys/bus/ccwgroup/drivers/lcs/read_device_bus_id/online
- Define the alias.Based on the type interface being added, add a line to
/etc/modprobe.conf
that is similar to one of the following:ethn alias lcs trn alias lcs
- Create a configuration script.Create a file in
/etc/sysconfig/network-scripts/
with a name like one of the following:ifcfg-ethn ifcfg-trn
The file should look similar to the following:/etc/sysconfig/network-scripts/ifcfg-eth0
# IBM LCS DEVICE=eth0 BOOTPROTO=static HWADDR=00:06:29:FB:5F:F1 IPADDR=9.12.20.136 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=lcs SUBCHANNELS=0.0.09a0,0.0.09a1 PORTNAME=0 TYPE=EthernetBased on the type interface being added, the DEVICE parameter should be one of the following:DEVICE=ethn DEVICE=trn
- Activate the device.Based on the type interface being added, issue an
ifup
command:# ifup ethn # ifup trn
22.6.2.2. Working With the QETH Device Driver
- hsin for HiperSocket devices
- ethn for OSA-Express Fast Ethernet and Gigabit Ethernet
- trn for Token Ring
- Load the device driver:
# modprobe qeth
- Create the group device:
# echo read_device_bus_id,write_device_bus_id,data_device_bus_id > /sys/bus/ccwgroup/drivers/qeth/group
Due to the length of this command, it has been broken into two lines. - Configure the device.For more information about configuration of the QETH driver, refer to the following:http://oss.software.ibm.com/developerworks/opensource/linux390/docu/lx26apr04dd01.pdf (Linux for IBM System z and S/390 Device Drivers, Features, and Commands)
- Set the device online:
# echo 1 > /sys/bus/ccwgroup/drivers/qeth/read_device_bus_id/online
- Define the alias.Based on the type interface being added, add a line to
/etc/modprobe.conf
that is like one of the following:hsin alias qeth ethn alias qeth trn alias qeth
- Create a configuration script.Create a file in
/etc/sysconfig/network-scripts/
with a name like one of the following:ifcfg-hsin ifcfg-ethn ifcfg-trn
The file should look like this:/etc/sysconfig/network-scripts/ifcfg-eth0
# IBM QETH DEVICE=eth0 BOOTPROTO=static HWADDR=00:06:29:FB:5F:F1 IPADDR=9.12.20.136 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.09a0,0.0.09a1,0.0.09a2 TYPE=EthernetBased on the type interface being added, the DEVICE parameter should be like one of the following:DEVICE=hsin DEVICE=ethn DEVICE=trn
- Activate the device.Based on the type interface being added, issue an
ifup
command:# ifup hsin # ifup ethn # ifup trn
22.7. Kernel-Related Information
/proc/
file system. To disable periodic timer interrupts, issue the following command:
echo 0 > /proc/sys/kernel/hz_timer
echo 1 > /proc/sys/kernel/hz_timer
/etc/sysctl.conf
to disable periodic timer interrupts:
kernel.hz_timer = 0
Note
Part IV. Common Tasks
Chapter 23. Updating Your System
23.1. Driver update rpm packages
kmod-
(notice the final -
) and click .
Figure 23.1. Listing installed Driver Update RPM packages
$ rpm -qa | egrep ^kmod-Note the
-
on the end of kmod
. This will list all installed packages that begin with kmod-
, which should include all driver updates that are currently installed on your system. Additional drivers provided by third-party update software are not listed in this output. Contact the third-party vendor for details.
- Download the driver update rpm package from the location specified by Red Hat or your hardware vendor. The package file name will begin with
kmod
(short for kernel module) and have a form similar to this example:kmod-ipw3945-1.2.04.17.el5.i686.rpm
In the example, the driver update rpm package supplies an Intel IPW3945 WiFi driver update with version number 1.2.0-4.17 for Red Hat Enterprise Linux 5, on i686 systems. A version of this driver package for systems running a Xen kernel will be similar, but includexen
in the package name:kmod-ipw3945-xen-1.2.04.17.el5.i686.rpm
Driver update rpm packages are signed packages, and like all other software packages, they are automatically validated at install time. To perform this step manually, type the following at a command line:$ rpm --checksig -v filename.rpm
where filename.rpm is the driver update rpm package file name. This verifies the package against using the standard Red Hat GPG package signing key that is already installed on any Red Hat Enterprise Linux 5.11 system. If you need this key for verification purposes on another system, you can can obtain it from: https://www.redhat.com/security/team/key/ - Locate and double-click the file that you downloaded. The system might prompt you for the root password, after which it will present the following Installing Packages box:
Figure 23.2. The installing packages box
Clickto complete the package installation.Alternatively, you can install a driver update manually on the command line:$ rpm -ivh kmod-ipw3945-1.2.04.17.el5.i686
- Whether you used a graphical install, or a command line install, reboot your system to ensure your system is using the new driver.
Chapter 24. Upgrading Your Current System
24.1. Determining Whether to Upgrade or Re-Install
Important
- Individual package configuration files may or may not work after performing an upgrade due to changes in various configuration file formats or layouts.
- Third party or ISV applications may not work correctly following the upgrade.
- If you have one of Red Hat's layered products (such as the Cluster Suite) installed, it may need to be manually upgraded after the Red Hat Enterprise Linux upgrade has been completed.
- If you have package repositories from providers other than Red Hat enabled, note that software installed from those repositories may not function properly after a system upgrade. Red Hat cannot guarantee that such repositories are up-to-date.
.rpmsave
extension (for example, sendmail.cf.rpmsave
). The upgrade process also creates a log of its actions in /root/upgrade.log
.
Warning
Note
24.2. Upgrading Your System
Note
/etc/redhat-release
file have been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5.11.
linux upgradeany
linux upgradeany
command if your Red Hat Enterprise Linux installation was not given as an option to upgrade.
Chapter 25. Register Your System and Apply Subscriptions
25.1. Registering the System
- Software updates, errata, and maintenance
- Red Hat technical support resources and Knowledgebase articles
25.1.1. Registering at Firstboot
- Customer Portal Subscription Management, hosted services from Red Hat (the default)
- Subscription Asset Manager, an on-premise subscription server which proxies content delivery back to the Customer Portal's services
- CloudForms System Engine, an on-premise service which handles both subscription services and content delivery
- To identify which subscription server to use for registration, enter the hostname of the service. The default service is Customer Portal Subscription Management, with the hostname subscription.rhn.redhat.com. To use a different subscription service, such as Subscription Asset Manager, enter the hostname of the local server.
- Click.
- Enter the user credentials for the given subscription service to log in.
Important
The user credentials to use depend on the subscription service. When registering with the Customer Portal, use the Red Hat Network credentials for the administrator or company account.However, for Subscription Asset Manager or CloudForms System engine, the user account to use is created within the on-premise service and probably is not the same as the Customer Portal user account.If you have lost your login or password for the Customer Portal, recover them from https://www.redhat.com/wapps/sso/rhn/lostPassword.html. For lost login or password information for Subscription Asset Manager or CloudForms System Engine, contact your local administrator. - Set the system name for the host. This is anything which uniquely and clearly identifies the system within the subscription service inventory. This is usually the hostname or fully-qualified domain name of the machine, but it can be any string.
- Optional. Set whether subscriptions should be set manually after registration. By default, this checkbox is unchecked so that the best-matched subscriptions are automatically applied to the system. Selecting this checkbox means that subscriptions must be added to the system manually after firstboot registration is complete. (Even if subscriptions are auto-attached, additional subscriptions can be added to the system later using the local Subscription Manager tools.)
- When registration begins, firstboot scans for organizations and environments (sub-domains within the organization) to which to register the system.IT environments that use Customer Portal Subscription Management have only a single organization, so no further configuration is necessary. IT infrastructures that use a local subscription service like Subscription Asset Manager might have multiple organizations configured, and those organizations may have multiple environments configured within them.If multiple organizations are detected, Subscription Manager prompts to select the one to join.
- If you decided to let Subscription Manager automatically attach subscriptions to the system (the default), then the system scans for the subscriptions to attach as part of the registration process.When registration is complete, the Subscription Manager reports the applied service level for the system based on the information in the selected subscription and the specific subscription that has been attached to the new system. This subscription selection must be confirmed to complete the registration process.If you selected to apply subscriptions later, then that part of the registration process is skipped, and the Subscription Manager screen in firstboot simply instructs you to attach subscriptions later.
- Clickto move to the next configuration area for firstboot, user setup.
25.1.2. Registering After Firstboot
Note
register
command with the --autosubscribe
option so that the best-matched subscriptions are automatically attached. For example:
[root@server ~]# subscription-manager register --autosubscribe Username: admin@example.com Password: The system has been registered with id: 30a3dc1b-db07-4ee7-bfb0-e09504b4033c Installed Product Current Status: Product Name: Red Hat Enterprise Linux Server Status: Subscribed
- Launch Subscription Manager. For example:
[root@server ~]# subscription-manager-gui
- In the System menu of the Subscription Manager window, select the item.
- Enter the hostname of the subscription server to which to register the system. This server, by default, is Customer Portal Subscription Management (the hosted service), at
subscription.rhn.redhat.com
. To register with a Subscription Asset Manager server or a CloudForms System Engine server, enter the appropriate hostname. - Enter the username and password of the user account on the subscription service.
Important
The user credentials to use depend on the subscription service. When registering with the Customer Portal, use the Red Hat Network credentials for the administrator or company account.However, for Subscription Asset Manager or CloudForms System engine, the user account to use is created within the on-premise service and probably is not the same as the Customer Portal user account. - Optionally, select the Skip automatic subscription selection... checkbox.By default, the registration process automatically subscribes the system to the best matched subscription. This can be turned off so that the subscriptions can be selected manually.
25.1.3. Unregistering the System
unregister
command:
[root@server1 ~]# subscription-manager unregister
- Launch Subscription Manager. For example:
[root@server ~]# subscription-manager-gui
- In the System menu of the Subscription Manager window, select the item.
Chapter 26. An Introduction to Disk Partitions
Note
26.1. Hard Disk Basic Concepts
Figure 26.1. An Unused Disk Drive
26.1.1. It is Not What You Write, it is How You Write It
Figure 26.2. Disk Drive with a File System
- A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead.
- A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as blocks. [11]
Figure 26.3. Disk Drive with a Different File System
Figure 26.4. Disk Drive with Data Written to It
26.1.2. Partitions: Turning One Drive Into Many
Note
Figure 26.5. Disk Drive with Partition Table
- The points on the disk where the partition starts and ends
- Whether the partition is "active"
- The partition's type
Figure 26.6. Disk Drive With Single Partition
Partition Type | Value | Partition Type | Value |
---|---|---|---|
Empty | 00 | Novell Netware 386 | 65 |
DOS 12-bit FAT | 01 | PIC/IX | 75 |
XENIX root | 02 | Old MINIX | 80 |
XENIX usr | 03 | Linux/MINUX | 81 |
DOS 16-bit <=32M | 04 | Linux swap | 82 |
Extended | 05 | Linux native | 83 |
DOS 16-bit >=32 | 06 | Linux extended | 85 |
OS/2 HPFS | 07 | Amoeba | 93 |
AIX | 08 | Amoeba BBT | 94 |
AIX bootable | 09 | BSD/386 | a5 |
OS/2 Boot Manager | 0a | OpenBSD | a6 |
Win95 FAT32 | 0b | NEXTSTEP | a7 |
Win95 FAT32 (LBA) | 0c | BSDI fs | b7 |
Win95 FAT16 (LBA) | 0e | BSDI swap | b8 |
Win95 Extended (LBA) | 0f | Syrinx | c7 |
Venix 80286 | 40 | CP/M | db |
Novell | 51 | DOS access | e1 |
PPC PReP Boot | 41 | DOS R/O | e3 |
GNU HURD | 63 | DOS secondary | f2 |
Novell Netware 286 | 64 | BBT | ff |
26.1.3. Partitions within Partitions — An Overview of Extended Partitions
Figure 26.7. Disk Drive With Extended Partition
26.1.4. Making Room For Red Hat Enterprise Linux
- Unpartitioned free space is available
- An unused partition is available
- Free space in an actively used partition is available
Note
26.1.4.1. Using Unpartitioned Free Space
Figure 26.8. Disk Drive with Unpartitioned Free Space
26.1.4.2. Using Space from an Unused Partition
Figure 26.9. Disk Drive With an Unused Partition
26.1.4.3. Using Free Space from an Active Partition
- Destructive Repartitioning
- Basically, you delete the single large partition and create several smaller ones. As you might imagine, any data you had in the original partition is destroyed. This means that making a complete backup is necessary. For your own sake, make two backups, use verification (if available in your backup software), and try to read data from your backup before you delete the partition.
Warning
If there was an operating system of some type installed on that partition, it needs to be reinstalled as well. Be aware that some computers sold with pre-installed operating systems may not include the CD-ROM media to reinstall the original operating system. The best time to notice if this applies to your system is before you destroy your original partition and its operating system installation.After creating a smaller partition for your existing operating system, you can reinstall any software, restore your data, and start your Red Hat Enterprise Linux installation. Figure 26.10, “Disk Drive Being Destructively Repartitioned” shows this being done.Figure 26.10. Disk Drive Being Destructively Repartitioned
In Figure 26.10, “Disk Drive Being Destructively Repartitioned”, 1 represents before and 2 represents after.Warning
As Figure 26.10, “Disk Drive Being Destructively Repartitioned”, shows, any data present in the original partition is lost without proper backup! - Non-Destructive Repartitioning
- Here, you run a program that does the seemingly impossible: it makes a big partition smaller without losing any of the files stored in that partition. Many people have found this method to be reliable and trouble-free. What software should you use to perform this feat? There are several disk management software products on the market. Do some research to find the one that is best for your situation.While the process of non-destructive repartitioning is rather straightforward, there are a number of steps involved:
- Compress and backup existing data
- Resize the existing partition
- Create new partition(s)
26.1.4.3.1. Compress existing data
Figure 26.11. Disk Drive Being Compressed
26.1.4.3.2. Resize the existing partition
Figure 26.12. Disk Drive with Partition Resized
26.1.4.3.3. Create new partition(s)
Figure 26.13. Disk Drive with Final Partition Configuration
Note
parted
utility. This is a freely available program that can resize partitions.
parted
, it is important that you be familiar with disk storage and that you perform a backup of your computer data. You should make two copies of all the important data on your computer. These copies should be to removable media (such as tape, CD-ROM, or diskettes), and you should make sure they are readable before proceeding.
parted
, be aware that after parted
runs you are left with two partitions: the one you resized, and the one parted
created out of the newly freed space. If your goal is to use that space to install Red Hat Enterprise Linux, you should delete the newly created partition, either by using the partitioning utility under your current operating system or while setting up partitions during installation.
26.1.5. Partition Naming Scheme
- Each partition's type is checked to determine if it can be read by DOS/Windows.
- If the partition's type is compatible, it is assigned a "drive letter." The drive letters start with a "C" and move on to the following letters, depending on the number of partitions to be labeled.
- The drive letter can then be used to refer to that partition as well as the file system contained on that partition.
/dev/xxyN
.
/dev/
- This is the name of the directory in which all device files reside. Since partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in
/dev/
. xx
- The first two letters of the partition name indicate the type of device on which the partition resides, usually either
hd
(for IDE disks) orsd
(for SCSI disks). y
- This letter indicates which device the partition is on. For example,
/dev/hda
(the first IDE hard disk) or/dev/sdb
(the second SCSI disk). N
- The final number denotes the partition. The first four (primary or extended) partitions are numbered
1
through4
. Logical partitions start at5
. So, for example,/dev/hda3
is the third primary or extended partition on the first IDE hard disk, and/dev/sdb6
is the second logical partition on the second SCSI hard disk.
Note
26.1.6. Disk Partitions and Other Operating Systems
26.1.7. Disk Partitions and Mount Points
/dev/hda5
is mounted on /usr/
, that would mean that all files and directories under /usr/
physically reside on /dev/hda5
. So the file /usr/share/doc/FAQ/txt/Linux-FAQ
would be stored on /dev/hda5
, while the file /etc/gdm/custom.conf
would not.
/usr/
would be mount points for other partitions. For instance, a partition (say, /dev/hda7
) could be mounted on /usr/local/
, meaning that /usr/local/man/whatis
would then reside on /dev/hda7
rather than /dev/hda5
.
26.1.8. How Many Partitions?
swap
, /boot/
(or a /boot/efi/
partition for Itanium systems), a /var/
partition for Itanium systems, and /
(root).
Part V. Basic System Recovery
Chapter 27. Basic System Recovery
27.1. Common Problems
- You are unable to boot normally into Red Hat Enterprise Linux (runlevel 3 or 5).
- You are having hardware or software problems, and you want to get a few important files off of your system's hard drive.
- You forgot the root password.
27.1.1. Unable to Boot into Red Hat Enterprise Linux
/
partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the /boot/grub/grub.conf
file.
27.1.2. Hardware/Software Problems
27.2. Booting into Rescue Mode
- By booting the system from an installation boot CD-ROM.
- By booting the system from other installation boot media, such as USB flash devices.
- By booting the system from the Red Hat Enterprise Linux CD-ROM #1.
rescue
as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt:
linux rescue
The rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage. You can then make any changes required to your system. If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'. If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.
/mnt/sysimage/
. If it fails to mount a partition, it notifies you. If you select , it attempts to mount your file system under the directory /mnt/sysimage/
, but in read-only mode. If you select , your file system is not mounted. Choose if you think your file system is corrupted.
sh-3.00b#
chroot /mnt/sysimage
rpm
that require your root partition to be mounted as /
. To exit the chroot
environment, type exit
to return to the prompt.
/foo
, and typing the following command:
mount -t ext3 /dev/mapper/VolGroup00-LogVol02 /foo
/foo
is a directory that you have created and /dev/mapper/VolGroup00-LogVol02
is the LVM2 logical volume you want to mount. If the partition is of type ext2
, replace ext3
with ext2
.
fdisk -l
pvdisplay
vgdisplay
lvdisplay
ssh
,scp
, andping
if the network is starteddump
andrestore
for users with tape drivesparted
andfdisk
for managing partitionsrpm
for installing or upgrading softwarejoe
for editing configuration filesNote
If you try to start other popular editors such asemacs
,pico
, orvi
, thejoe
editor is started.
27.2.1. Reinstalling the Boot Loader
- Boot the system from an installation boot medium.
- Type
linux rescue
at the installation boot prompt to enter the rescue environment. - Type
chroot /mnt/sysimage
to mount the root partition. - Type
/usr/sbin/grub-install bootpart
to reinstall the GRUB boot loader, where bootpart is the boot partition (typically, /dev/sda). - Review the
/boot/grub/grub.conf
file, as additional entries may be needed for GRUB to control additional operating systems. - Reboot the system.
27.3. Booting into Single-User Mode
- At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
- Select Red Hat Enterprise Linux with the version of the kernel that you wish to boot and type
a
to append the line. - Go to the end of the line and type
single
as a separate word (press the Spacebar and then typesingle
). Press Enter to exit edit mode.
27.4. Booting into Emergency Mode
init
files are not loaded. If init
is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation.
single
with the keyword emergency
.
Chapter 28. Rescue Mode on POWER Systems
'rescue'
(including the quotes), or to 'dd rescue'
if you need to load the SCSI driver. On other systems, specify the rescue
or dd rescue
(without quotes) after the default kernel name at the YABOOT prompt.
exit 0
. This causes a reboot from the C side. To reboot from the A or B side or from *NWSSTG, you should vary off the system instead of exiting the shell.
28.1. Special Considerations for Accessing the SCSI Utilities from Rescue Mode
- Boot from the CD-ROM with the
linux rescue askmethod
command. This allows you to manually select NFS as the source of your rescue media instead of defaulting to the CD-ROM drive. - Copy the first installation disc onto a file system of another Linux system.
- Make this copy of the installation disc available through NFS or FTP.
- Vary off or power down the system you need to rescue. Set its IPL parameters as instructed for booting the Installation discs in rescue mode, except that the IPL source should point to the copy of
boot.img
on your IFS (from step 1, above). - Make sure the installation disc is not in your CD-ROM drive.
- IPL the Linux system.
- Follow the prompts as described in Chapter 28, Rescue Mode on POWER Systems. An additional prompt for the installation source appears. Select NFS or FTP (as appropriate) and complete the following network configuration screen.
- When the Linux system has booted into rescue mode, the CD-ROM drive is available for use and you can mount the driver media to access the SCSI utilities.
Part VI. Advanced Installation and Deployment
Chapter 29. Disk Encryption Guide
Note
29.1. What is block device encryption?
29.2. Encrypting block devices using dm-crypt/LUKS
dm-crypt
module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the cryptsetup
utility.
29.2.1. Overview of LUKS
- What LUKS does:
- LUKS encrypts entire block devices
- LUKS is thereby well-suited for protecting the contents of mobile devices such as:
- Removable storage media
- Laptop disk drives
- The underlying contents of the encrypted block device are arbitrary.
- This makes it useful for encrypting
swap
devices. - This can also be useful with certain databases that use specially formatted block devices for data storage.
- LUKS uses the existing device mapper kernel subsystem.
- This is the same subsystem used by LVM, so it is well tested.
- LUKS provides passphrase strengthening.
- This protects against dictionary attacks.
- LUKS devices contain multiple key slots.
- This allows users to add backup keys/passphrases.
- What LUKS does not do:
- LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device.
- LUKS is not well-suited for applications requiring file-level encryption.
29.2.2. How will I access the encrypted devices after installation? (System Startup)
Note
29.2.3. Choosing a Good Passphrase
29.3. Creating Encrypted Block Devices in Anaconda
Important
Note
Note
kickstart
to set a separate passphrase for each new encrypted block device.
29.3.1. What Kinds of Block Devices Can Be Encrypted?
29.4. Creating Encrypted Block Devices on the Installed System After Installation
29.4.1. Create the block devices
parted
, pvcreate
, lvcreate
and mdadm
.
29.4.2. Optional: Fill the device with random data
/dev/sda3
) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time.
Warning
- The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems):
dd if=/dev/urandom of=<device>
- Fastest way, which provides lower quality random data:
badblocks -c 10240 -s -w -t random -v <device>
29.4.3. Format the device as a dm-crypt/LUKS encrypted device
Warning
cryptsetup luksFormat <device>
Note
cryptsetup(8)
man page.
cryptsetup isLuks <device> && echo Success
cryptsetup luksDump <device>
29.4.4. Create a mapping to allow access to the device's decrypted contents
device-mapper
.
/dev/sda3
), is guaranteed to remain constant as long as the LUKS header remains intact. To find a LUKS device's UUID, run the following command:
cryptsetup luksUUID <device>
luks-<uuid>
, where <uuid> is replaced with the device's LUKS UUID (eg: luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8
). This naming convention might seem unwieldy but is it not necessary to type it often.
cryptsetup luksOpen <device> <name>
/dev/mapper/<name>
, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device.
dmsetup info <name>
Note
dmsetup(8)
man page.
29.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device
/dev/mapper/<name>
) as any other block device. To create an ext2
filesystem on the mapped device, use the following command:
mke2fs /dev/mapper/<name>
/mnt/test
, use the following command:
Important
/mnt/test
must exist before executing this command.
mount /dev/mapper/<name> /mnt/test
29.4.6. Add the mapping information to /etc/crypttab
/etc/crypttab
file. If the file doesn't exist, create it and change the owner and group to root (root:root
) and change the mode to 0744
. Add a line to the file with the following format:
<name> <device> none
cryptsetup luksUUID <device>
. This ensures the correct device will be identified and used even if the device node (eg: /dev/sda5
) changes.
Note
/etc/crypttab
file, read the crypttab(5)
man page.
29.4.7. Add an entry to /etc/fstab
/dev/mapper/<name>
in the /etc/fstab
file.
/etc/fstab
by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: /dev/sda4
) changes. LUKS device names in the form of /dev/mapper/luks-<luks_uuid>
are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in /etc/fstab
.
Note
/etc/fstab
file, read the fstab(5)
man page.
29.5. Common Post-Installation Tasks
29.5.1. Set a randomly generated key as an additional way to access an encrypted block device
29.5.1.1. Generate a key
$HOME/keyfile
.
dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1 chmod 600 $HOME/keyfile
29.5.1.2. Add the key to an available keyslot on the encrypted device
cryptsetup luksAddKey <device> ~/keyfile
29.5.2. Add a new passphrase to an existing device
cryptsetup luksAddKey <device>
29.5.3. Remove a passphrase or key from a device
cryptsetup luksRemoveKey <device>
Chapter 30. Installing Through VNC
- Less screen real estate for creating user interfaces similar to those found in the graphical mode.
- Difficult internationalization support.
- Desire to maintain a single interactive installation code path.
30.1. VNC Viewer
- Your workstation
- Laptop on a datacenter crash cart
- vncviewer is available on Red Hat Enterprise Linux by installing the vnc package:
#
yum install vnc
- TightVNC is available for Windows at http://www.tightvnc.com/
- MacOS X includes built-in VNC support as of version 10.5. In the Finder, click the Go menu and choose Connect to Server. In the server address field, you can type
vnc://SERVER:DISPLAY
, where SERVER is the IP address or DNS host name of the VNC server you wish to connect to and DISPLAY is the VNC display number (usually 1), and click Connect.
30.2. VNC Modes in Anaconda
30.2.1. Direct Mode
- Specify
vnc
as a boot argument. - Specify the
vnc
command in the kickstart file used for installation.
Running anaconda VERSION, the PRODUCT system installer - please wait...
- Requires visual access to the system console to see the IP address and port to connect the VNC viewer to.
- Requires interactive access to the system console to complete the first stage of the installer.
30.2.2. Connect Mode
vncconnect
boot parameter:
boot: linux vncconnect=HOST
30.3. Installation Using VNC
30.3.1. Installation Example
- Connect the laptop or other workstation to the target system using a crossover cable. If you are using regular patch cables, make sure you connect the two systems using a small hub or switch. Most recent Ethernet interfaces will automatically detect if they need to be crossover or not, so it may be possible to connect the two systems directly using a regular patch cable.
- Configure the VNC viewer system to use a RFC 1918 address with no gateway. This private network connection will only be used for the purpose of installation. Configure the VNC viewer system to be 192.168.100.1/24. If that address is in use, just pick something else in the RFC 1918 address space that is available to you.
- Start the RHEL installation on the target system.
- Booting the installation DVD or CD.If booting the installation media (CD or DVD), make sure
vnc
is passed as a boot parameter. To add thevnc
parameter, you will need a console attached to the target system that allows you to interact with the boot process. Enter the following at the prompt:boot:
linux vnc
- Boot over the network.If the target system is configured with a static IP address, add the
vnc
command to the kickstart file. If the target system is using DHCP, addvncconnect=HOST
to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Enter the following at the prompt:boot:
linux vncconnect=HOST
- When prompted for the network configuration on the target system, assign it an available RFC 1918 address in the same network you used for the VNC viewer system. For example, 192.168.100.2/24.
Note
This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer. - Once the installer indicates it is starting anaconda, you will be instructed to connect to the system using the VNC viewer. Connect to the viewer and follow the graphical installation mode instructions found in the product documentation.
30.3.2. Kickstart Considerations
vnc
command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file.
vncconnect
method may work better for you. Rather than adding the vnc
boot parameter to the kickstart file, add the vncconnect=HOST
parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. See the next section for more details on using the vncconnect mode.
30.3.3. Firewall Considerations
vnc
boot parameter, you may also want to pass the vncpassword
parameter in these scenarios. While the password is sent in plain text over the network, it does provide an extra step before a viewer can connect to a system. Once the viewer connects to the target system over VNC, no other connections are permitted. These limitations are usually sufficient for installation purposes.
Important
vncpassword
option. It should not be a password you use on any systems, especially a real root password.
vncconnect
parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass vncconnect=HOST
at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address).
30.4. References
- VNC description at Wikipedia: http://en.wikipedia.org/wiki/Vnc
- TightVNC: http://www.tightvnc.com/
- RFC 1918 - Address Allocation for Private Networks: http://www.ietf.org/rfc/rfc1918.txt
- Anaconda boot options: http://fedoraproject.org/wiki/Anaconda/Options
- Kickstart documentation: http://fedoraproject.org/wiki/Anaconda/Kickstart
Chapter 31. Kickstart Installations
31.1. What are Kickstart Installations?
31.2. How Do You Perform a Kickstart Installation?
- Create a kickstart file.
- Create a boot media with the kickstart file or make the kickstart file available on the network.
- Make the installation tree available.
- Start the kickstart installation.
31.3. Creating the Kickstart File
/root/anaconda-ks.cfg
. You should be able to edit it with any text editor or word processor that can save files as ASCII text.
- Sections must be specified in order. Items within the sections do not have to be in a specific order unless otherwise specified. The section order is:
- Command section — Refer to Section 31.4, “Kickstart Options” for a list of kickstart options. You must include the required options.
- The
%packages
section — Refer to Section 31.5, “Package Selection” for details. - The
%pre
and%post
sections — These two sections can be in any order and are not required. Refer to Section 31.6, “Pre-installation Script” and Section 31.7, “Post-installation Script” for details.
- Items that are not required can be omitted.
- Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item).
- Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.
- For kickstart upgrades, the following items are required:
- Language
- Installation method
- Device specification (if device is needed to perform the installation)
- Keyboard setup
- The
upgrade
keyword - Boot loader configuration
If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).
31.4. Kickstart Options
Note
autopart
(optional)- Automatically create partitions — 1 GB or more root (
/
) partition, a swap partition, and an appropriate boot partition for the architecture. One or more of the default partition sizes can be redefined with thepart
directive.--encrypted
— Should all devices with support be encrypted by default? This is equivalent to checking the Encrypt checkbox on the initial partitioning screen.--passphrase=
— Provide a default system-wide passphrase for all encrypted devices.
ignoredisk
(optional)- Causes the installer to ignore the specified disks. If the target system contains read-only devices, they must be specified with
ignoredisk
or the installation will stop and prompt for whether it should ignore the device.ignoredisk
is useful if you use autopartition and want to be sure that some disks are ignored. For example, withoutignoredisk
, attempting to deploy on a SAN-cluster the kickstart would fail, as the installer detects passive paths to the SAN that return no partition table. The--only-use
option specifies that only the disks listed will be used during installation.Theignoredisk
option is also useful if you have multiple paths to your disks.The syntax is:ignoredisk --drives=drive1,drive2,...
where driveN is one ofsda
,sdb
,...,hda
,... etc.--only-use
— specifies a list of disks for the installer to use. All other disks are ignored. For example, to use disksda
during installation and ignore all other disks:ignoredisk --only-use=sda
autostep
(optional)- Similar to
interactive
except it goes to the next screen for you. It is used mostly for debugging and should not be used when deploying a system because it may disrupt package installation.--autoscreenshot
— Take a screenshot at every step during installation and copy the images over to/root/anaconda-screenshots
after installation is complete. This is most useful for documentation.
auth
orauthconfig
(required)- Sets up the authentication options for the system. It is similar to the
authconfig
command, which can be run after the install. By default, passwords are normally encrypted and are not shadowed.--enablemd5
— Use md5 encryption for user passwords.--enablenis
— Turns on NIS support. By default,--enablenis
uses whatever domain it finds on the network. A domain should almost always be set by hand with the--nisdomain=
option.--nisdomain=
— NIS domain name to use for NIS services.--nisserver=
— Server to use for NIS services (broadcasts by default).--useshadow
or--enableshadow
— Use shadow passwords.--enableldap
— Turns on LDAP support in/etc/nsswitch.conf
, allowing your system to retrieve information about users (UIDs, home directories, shells, etc.) from an LDAP directory. To use this option, you must install thenss_ldap
package. You must also specify a server and a base DN (distinguished name) with--ldapserver=
and--ldapbasedn=
.--enableldapauth
— Use LDAP as an authentication method. This enables thepam_ldap
module for authentication and changing passwords, using an LDAP directory. To use this option, you must have thenss_ldap
package installed. You must also specify a server and a base DN with--ldapserver=
and--ldapbasedn=
.--ldapserver=
— If you specified either--enableldap
or--enableldapauth
, use this option to specify the name of the LDAP server to use. This option is set in the/etc/ldap.conf
file.--ldapbasedn=
— If you specified either--enableldap
or--enableldapauth
, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is set in the/etc/ldap.conf
file.--enableldaptls
— Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.--enablekrb5
— Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the/usr/sbin/useradd
command. If you use this option, you must have thepam_krb5
package installed.--krb5realm=
— The Kerberos 5 realm to which your workstation belongs.--krb5kdc=
— The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, separate their names with commas (,).--krb5adminserver=
— The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.--enablehesiod
— Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in/usr/share/doc/glibc-2.x.x/README.hesiod
, which is included in theglibc
package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.--hesiodlhs
— The Hesiod LHS ("left-hand side") option, set in/etc/hesiod.conf
. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.--hesiodrhs
— The Hesiod RHS ("right-hand side") option, set in/etc/hesiod.conf
. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.Note
To look up user information for "jim", the Hesiod library looks up jim.passwd<LHS><RHS>, which should resolve to a TXT record that looks like what his passwd entry would look like (jim:*:501:501:Jungle Jim:/home/jim:/bin/bash
). For groups, the situation is identical, except jim.group<LHS><RHS> would be used.Looking up users and groups by number is handled by making "501.uid" a CNAME for "jim.passwd", and "501.gid" a CNAME for "jim.group". Note that the library does not place a period . in front of the LHS and RHS values when performing a search. Therefore the LHS and RHS values need to have a period placed in front of them in order if they require this.--enablesmbauth
— Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LDAP, NIS, or Hesiod or by using the/usr/sbin/useradd
command to make their accounts known to the workstation. To use this option, you must have thepam_smb
package installed.--smbservers=
— The name of the server(s) to use for SMB authentication. To specify more than one server, separate the names with commas (,).--smbworkgroup=
— The name of the workgroup for the SMB servers.--enablecache
— Enables thenscd
service. Thenscd
service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using NIS, LDAP, or hesiod.--passalgo
— Enables SHA256 or SHA512 hashing for passphrases. Use--passalgo=sha256
or--passalgo=sha512
and remove the--enablemd5
if present.
bootloader
(required)- Specifies how the boot loader should be installed. This option is required for both installations and upgrades.
--append=
— Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"
--driveorder
— Specify which drive is first in the BIOS boot order. For example:bootloader --driveorder=sda,hda
--hvargs
— If using GRUB, specifies Xen hypervisor arguments. To specify multiple parameters, separate them with spaces. For example:bootloader --hvargs="dom0_mem=2G dom0_max_vcpus=4"
--location=
— Specifies where the boot record is written. Valid values are the following:mbr
(the default),partition
(installs the boot loader on the first sector of the partition containing the kernel), ornone
(do not install the boot loader).--password=
— If using GRUB, sets the GRUB boot loader password to the one specified with this option. This should be used to restrict access to the GRUB shell, where arbitrary kernel options can be passed.--md5pass=
— If using GRUB, similar to--password=
except the password should already be encrypted.--upgrade
— Upgrade the existing boot loader configuration, preserving the old entries. This option is only available for upgrades.
clearpart
(optional)- Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
Note
If theclearpart
command is used, then the--onpart
command cannot be used on a logical partition.Important
Red Hat Enterprise Linux 5 cannot use unformatted DASDs when installing with kickstart and the cmdline user interface. Use the following command in your kickstart file and explicitly list all DASDs that you want to be low-level formatted with dasdfmt automatically in case they are not yet low-level formatted:clearpart --initlabel --drives=names_of_DASDs
For example:clearpart --initlabel --drives=dasda,dasdb,dasdc
--all
— Erases all partitions from the system.--drives=
— Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:clearpart --drives=hda,hdb --all
--initlabel
— Initializes the disk label to the default for your architecture (for examplemsdos
for x86 andgpt
for Itanium). It is useful so that the installation program does not ask if it should initialize the disk label if installing to a brand new hard drive.--linux
— Erases all Linux partitions.--none
(default) — Do not remove any partitions.
cmdline
(optional)device
(optional)- On most PCI systems, the installation program autoprobes for Ethernet and SCSI cards properly. On older systems and some PCI systems, however, kickstart needs a hint to find the proper devices. The
device
command, which tells the installation program to install extra modules, is in this format:device <type> <moduleName> --opts=<options>
- <type> — Replace with either
scsi
oreth
. - <moduleName> — Replace with the name of the kernel module which should be installed.
--opts=
— Mount options to use for mounting the NFS export. Any options that can be specified in/etc/fstab
for an NFS mount are allowed. The options are listed in thenfs(5)
man page. Multiple options are separated with a comma.
driverdisk
(optional)- Driver diskettes can be used during kickstart installations. You must copy the driver diskettes's contents to the root directory of a partition on the system's hard drive. Then you must use the
driverdisk
command to tell the installation program where to look for the driver disk.driverdisk <partition> [--type=<fstype>]
Alternatively, a network location can be specified for the driver diskette:driverdisk --source=ftp://path/to/dd.img driverdisk --source=http://path/to/dd.img driverdisk --source=nfs:host:/path/to/img
- <partition> — Partition containing the driver disk.
--type=
— File system type (for example, vfat or ext2).
firewall
(optional)firewall --enabled|--disabled [--trust=] <device> [--port=]
--enabled
or--enable
— Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.--disabled
or--disable
— Do not configure any iptables rules.--trust=
— Listing a device here, such as eth0, allows all traffic coming to and from that device to go through the firewall. To list more than one device, use--trust eth0 --trust eth1
. Do NOT use a comma-separated format such as--trust eth0, eth1
.- <incoming> — Replace with one or more of the following to allow the specified services through the firewall.
--ssh
--telnet
--smtp
--http
--ftp
--port=
— You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specifyimap:tcp
. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify1234:udp
. To specify multiple ports, separate them by commas.
firstboot
(optional)- Determine whether the Setup Agent starts the first time the system is booted. If enabled, the
firstboot
package must be installed. If not specified, this option is disabled by default.--enable
or--enabled
— The Setup Agent is started the first time the system boots.--disable
or--disabled
— The Setup Agent is not started the first time the system boots.--reconfig
— Enable the Setup Agent to start at boot time in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
halt
(optional)- Halt the system after the installation has successfully completed. This is similar to a manual installation, where anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, this option is used as the default.The
halt
option is roughly equivalent to theshutdown -h
command.For other completion methods, refer to thepoweroff
,reboot
, andshutdown
kickstart options. graphical
(optional)install
(optional)- Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from
cdrom
,harddrive
,nfs
, orurl
(for FTP or HTTP installations). Theinstall
command and the installation method command must be on separate lines.cdrom
— Install from the first CD-ROM drive on the system.harddrive
— Install from a Red Hat installation tree on a local drive, which must be either vfat or ext2.--biospart=
BIOS partition to install from (such as 82).--partition=
Partition to install from (such as sdb2).--dir=
Directory containing thevariant
directory of the installation tree.
For example:harddrive --partition=hdb2 --dir=/tmp/install-tree
nfs
— Install from the NFS server specified.--server=
Server from which to install (hostname or IP).--dir=
Directory containing thevariant
directory of the installation tree.--opts=
Mount options to use for mounting the NFS export. (optional)
For example:nfs --server=nfsserver.example.com --dir=/tmp/install-tree
url
— Install from an installation tree on a remote server via FTP or HTTP.For example:url --url http://<server>/<dir>
or:url --url ftp://<username>:<password>@<server>/<dir>
interactive
(optional)- Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You are presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking or change the values and click to continue. Refer to the
autostep
command. iscsi
(optional)- Specifies additional iSCSI storage to be attached during installation. If you use the
iscsi
parameter, you must also assign a name to the iSCSI node, using theiscsiname
parameter. Theiscsiname
parameter must appear before theiscsi
parameter in the kickstart file.We recommend that wherever possible you configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use theiscsi
parameter. Anaconda automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the kickstart file.If you must use theiscsi
parameter, ensure that networking is activated at the beginning of the installation, and that theiscsi
parameter appears in the kickstart file before you refer to iSCSI disks with parameters such asclearpart
orignoredisk
.--port=
(mandatory) — the port number (typically,--port=3260
)--user=
— the username required to authenticate with the target--password=
— the password that corresponds with the username specified for the target--reverse-user=
— the username required to authenticate with the initiator from a target that uses reverse CHAP authentication--reverse-password=
— the password that corresponds with the username specified for the initiator
iscsiname
(optional)key
(optional)- Specify an installation key, which is needed to aid in package selection and identify your system for support purposes.
--skip
— Skip entering a key. Usually if the key command is not given, anaconda will pause at this step to prompt for a key. This option allows automated installation to continue if you do not have a key or do not want to provide one.
keyboard
(required)- Sets system keyboard type. Here is the list of available keyboards on i386, Itanium, and Alpha machines:
be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2, ru_win, se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup, speakup-lt, sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua, uk, us, us-acentos
The file/usr/lib/python2.2/site-packages/rhpl/keyboard_models.py
also contains this list and is part of therhpl
package. lang
(required)- Sets the language to use during installation and the default language to use on the installed system. For example, to set the language to English, the kickstart file should contain the following line:
lang en_US
The file/usr/share/system-config-language/locale-list
provides a list of the valid language codes in the first column of each line and is part of thesystem-config-language
package.Certain languages (mainly Chinese, Japanese, Korean, and Indic languages) are not supported during text mode installation. If one of these languages is specified using the lang command, installation will continue in English though the running system will have the specified language by default. langsupport
(deprecated)- The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the
%packages
section of your kickstart file. For instance, adding support for French means you should add the following to%packages
:@french-support
logvol
(optional)- Create a logical volume for Logical Volume Management (LVM) with the syntax:
logvol <mntpoint> --vgname=<name> --size=<size> --name=<name> <options>
The options are as follows:--noformat
— Use an existing logical volume and do not format it.--useexisting
— Use an existing logical volume and reformat it.--fstype=
— Sets the file system type for the logical volume. Valid values arexfs
,ext2
,ext3
,ext4
,swap
,vfat
, andhfs
.--fsoptions=
— Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the/etc/fstab
file of the installed system and should be enclosed in quotes.--bytes-per-inode=
— Specifies the size of inodes on the filesystem to be made on the logical volume. Not all filesystems support this option, so it is silently ignored for those cases.--size=
— The minimum size of the logical volume in megabytes. Specify an integer value here, and do not append the number with MB. If the logical volume is set to grow, the minimum size must be provided.--grow=
— Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting, while conforming to other limitations.--maxsize=
— The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here, and do not append the number with MB.--recommended=
— Determine the size of the logical volume automatically.--percent=
— Specify the size of the logical volume as a percentage of available space in the volume group.
Create the partition first, create the logical volume group, and then create the logical volume. For example:part pv.01 --size 3000 volgroup myvg pv.01 logvol / --vgname=myvg --size=2000 --name=rootvol
logging
(optional)- This command controls the error logging of anaconda during installation. It has no effect on the installed system.
--host=
— Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.--port=
— If the remote syslogd process uses a port other than the default, it may be specified with this option.--level=
— One of debug, info, warning, error, or critical.Specify the minimum level of messages that appear on tty3. All messages will still be sent to the log file regardless of this level, however.
mediacheck
(optional)- If given, this will force anaconda to run mediacheck on the installation media. This command requires that installs be attended, so it is disabled by default.
monitor
(optional)- If the monitor command is not given, anaconda will use X to automatically detect your monitor settings. Please try this before manually configuring your monitor.
--hsync=
— Specifies the horizontal sync frequency of the monitor.--monitor=
— Use specified monitor; monitor name should be from the list of monitors in /usr/share/hwdata/MonitorsDB from the hwdata package. The list of monitors can also be found on the X Configuration screen of the Kickstart Configurator. This is ignored if --hsync or --vsync is provided. If no monitor information is provided, the installation program tries to probe for it automatically.--noprobe=
— Do not try to probe the monitor.--vsync=
— Specifies the vertical sync frequency of the monitor.
mouse
(deprecated)- The mouse keyword is deprecated.
multipath
(optional)- Specifies a multipath device in the format:
multipath --name=mpathX --device=device_name --rule=policy
For example:multipath --name=mpath0 --device=/dev/sdc --rule=failover
The available options are:--name=
— the name for the multipath device, in the formatmpathX
, where X is an integer.--device=
— the block device connected as a multipath device.--rule=
— a multipath policy:failover
,multibus
,group_by_serial
,group_by_prio
, orgroup_by_node_name
. Refer to the multipath manpage for a description of these policies.
network
(optional)- Configures network information for the system. If the kickstart installation requires networking (when the Kickstart file is accessed over
HTTP
,FTP
orNFS
), the device specified in the first network command is activated with configuration specified by the command. If the--device=
option is not specified and multiple network devices are available, the device used to access the Kickstart file over the network is selected, or the user is asked to choose the device.Note that if network configuration is not specified in the firstnetwork
command (for example, if the--bootproto=
option is missing), the device will be activated with configuration set by boot options. On the installed system, this device will be configured using the default value, which is--bootproto=
dhcp
.--bootproto=
— One ofdhcp
,bootp
,static
orquery
.The default option isdhcp
.bootp
anddhcp
are treated the same.The DHCP method uses a DHCP server system to obtain its networking configuration. As you might guess, the BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. To direct a system to use DHCP:network --bootproto=dhcp
To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the kickstart file:network --bootproto=bootp
The static method requires that you enter all the required networking information in the kickstart file. As the name implies, this information is static and is used during and after the installation. The line for static networking is more complex, as you must include all network configuration information on one line. You must specify the IP address, netmask, gateway, and nameserver.Note that although the presentation of this example on this page has broken the line, in a real kickstart file, you must include all this information on a single line with no break.network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=10.0.2.1
If you use the static method, be aware of the following two restrictions:- All static networking configuration information must be specified on one line; you cannot wrap lines using a backslash, for example.
- You can also configure multiple nameservers here. To do so, specify them as a comma-delimited list in the command line.Note that although the presentation of this example on this page has broken the line, in a real kickstart file, you must include all this information on a single line with no break.
network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
If you set this option toquery
, you will be prompted to manually configure the network options during the actual installation process.network --bootproto=query
--device=
— Used to specify the network device being configured. For example:network --bootproto=dhcp --device=eth0
The above example configures deviceeth0
for DHCP.--ip=
— IP address for the machine to be installed.--gateway=
— Default gateway as an IP address.--nameserver=
— Primary nameserver, as an IP address.--nodns
— Do not configure any DNS server.--netmask=
— Netmask for the installed system.--hostname=
— Hostname for the installed system.--ethtool=
— Specifies additional low-level settings for the network device which will be passed to the ethtool program. Whenautoneg
is not specified,autoneg off
is inserted automatically.--essid=
— The network ID for wireless networks.--wepkey=
— The encryption key for wireless networks.--onboot=
— Whether or not to enable the device at boot time.--dhcpclass=
— The DHCP class.--mtu=
— The MTU of the device.--noipv4
— Disable IPv4 on this device.--noipv6
— Disable IPv6 on this device.
-
part
orpartition
(required for installs, ignored for upgrades) - Creates a partition on the system.If more than one Red Hat Enterprise Linux installation exists on the system on different partitions, the installation program prompts the user and asks which installation to upgrade.
Warning
All partitions created are formatted as part of the installation process unless--noformat
and--onpart
are used.For a detailed example ofpart
in action, refer to Section 31.4.1, “Advanced Partitioning Example”.- <mntpoint> — The <mntpoint> is where the partition is mounted and must be of one of the following forms:
/<path>
For example,/
,/usr
,/home
swap
The partition is used as swap space.To determine the size of the swap partition automatically, use the--recommended
option:swap --recommended
The recommended maximum swap size for machines with less than 2GB of RAM is twice the amount of RAM. For machines with 2GB or more, this recommendation changes to 2GB plus the amount of RAM.raid.<id>
The partition is used for software RAID (refer toraid
).pv.<id>
The partition is used for LVM (refer tologvol
).Note
You can assign any value to the<id>
field, but ensure these values are consistent across volumes and volume groups. The default value for the first volume is 01.
--size=
— The minimum partition size in megabytes. Specify an integer value here such as 500. Do not append the number with MB.--grow
— Tells the partition to grow to fill available space (if any), or up to the maximum size setting.Note
If you use--grow=
without setting--maxsize=
on a swap partition, Anaconda will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.--maxsize=
— The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here, and do not append the number with MB.--noformat
— Tells the installation program not to format the partition, for use with the--onpart
command.--onpart=
or--usepart=
— Put the partition on the already existing device. For example:partition /home --onpart=hda1
puts/home
on/dev/hda1
, which must already exist.--ondisk=
or--ondrive=
— Forces the partition to be created on a particular disk. For example,--ondisk=sdb
puts the partition on the second SCSI disk on the system.--asprimary
— Forces automatic allocation of the partition as a primary partition, or the partitioning fails.--type=
(replaced byfstype
) — This option is no longer available. Usefstype
.--fstype=
— Sets the file system type for the partition. Valid values arexfs
,ext2
,ext3
,ext4
,swap
,vfat
, andhfs
.--start=
— Specifies the starting cylinder for the partition. It requires that a drive be specified with--ondisk=
orondrive=
. It also requires that the ending cylinder be specified with--end=
or the partition size be specified with--size=
.--end=
— Specifies the ending cylinder for the partition. It requires that the starting cylinder be specified with--start=
.--bytes-per-inode=
— Specifies the size of inodes on the filesystem to be made on the partition. Not all filesystems support this option, so it is silently ignored for those cases.--recommended
— Determine the size of the partition automatically.--onbiosdisk
— Forces the partition to be created on a particular disk as discovered by the BIOS.--encrypted
— Specifies that this partition should be encrypted.--passphrase=
— Specifies the passphrase to use when encrypting this partition. Without the above--encrypted
option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.--fsoptions=
— Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the/etc/fstab
file of the installed system and should be enclosed in quotes.--label=
— assign a label to an individual partition.
Note
If partitioning fails for any reason, diagnostic messages appear on virtual console 3. -
poweroff
(optional) - Shut down and power off the system after the installation has successfully completed. Normally during a manual installation, anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, the
halt
option is used as default.Thepoweroff
option is roughly equivalent to theshutdown -p
command.Note
Thepoweroff
option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.For other completion methods, refer to thehalt
,reboot
, andshutdown
kickstart options. -
raid
(optional) - Assembles a software RAID device. This command is of the form:
raid <mntpoint> --level=<level> --device=<mddevice> <partitions*>
- <mntpoint> — Location where the RAID file system is mounted. If it is
/
, the RAID level must be 1 unless a boot partition (/boot
) is present. If a boot partition is present, the/boot
partition must be level 1 and the root (/
) partition can be any of the available types. The <partitions*> (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array. --level=
— RAID level to use (0, 1, 4, 5, 6, or 10).--device=
— Name of the RAID device to use (such as md0 or md1). RAID devices range from md0 to md15, and each may only be used once.--bytes-per-inode=
— Specifies the size of inodes on the filesystem to be made on the RAID device. Not all filesystems support this option, so it is silently ignored for those cases.--spares=
— Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.--fstype=
— Sets the file system type for the RAID array. Valid values arexfs
,ext2
,ext3
,ext4
,swap
,vfat
, andhfs
.--fsoptions=
— Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.--noformat
— Use an existing RAID device and do not format the RAID array.--useexisting
— Use an existing RAID device and reformat it.--encrypted
— Specifies that this RAID device should be encrypted.--passphrase=
— Specifies the passphrase to use when encrypting this RAID device. Without the above--encrypted
option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
The following example shows how to create a RAID level 1 partition for/
, and a RAID level 5 for/usr
, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive.part raid.01 --size=60 --ondisk=sda part raid.02 --size=60 --ondisk=sdb part raid.03 --size=60 --ondisk=sdc
part swap --size=128 --ondisk=sda part swap --size=128 --ondisk=sdb part swap --size=128 --ondisk=sdc
part raid.11 --size=1 --grow --ondisk=sda part raid.12 --size=1 --grow --ondisk=sdb part raid.13 --size=1 --grow --ondisk=sdc
raid / --level=1 --device=md0 raid.01 raid.02 raid.03 raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
For a detailed example ofraid
in action, refer to Section 31.4.1, “Advanced Partitioning Example”. -
reboot
(optional) - Reboot after the installation is successfully completed (no arguments). Normally, kickstart displays a message and waits for the user to press a key before rebooting.The
reboot
option is roughly equivalent to theshutdown -r
command.Specifyreboot
to automate installation fully when installing in cmdline mode on System z.For other completion methods, refer to thehalt
,poweroff
, andshutdown
kickstart options.Thehalt
option is the default completion method if no other methods are explicitly specified in the kickstart file.Note
Use of thereboot
option may result in an endless installation loop, depending on the installation media and method. repo
(optional)- Configures additional yum repositories that may be used as sources for package installation. Multiple repo lines may be specified.
repo --name=<repoid> [--baseurl=<url>| --mirrorlist=<url>]
--name=
— The repo id. This option is required.--baseurl=
— The URL for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --mirrorlist, not both.--mirrorlist=
— The URL pointing at a list of mirrors for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --baseurl, not both.
rootpw
(required)rootpw [--iscrypted] <password>
--iscrypted
— If this is present, the password argument is assumed to already be encrypted.
selinux
(optional)selinux [--disabled|--enforcing|--permissive]
--enforcing
— Enables SELinux with the default targeted policy being enforced.Note
If theselinux
option is not present in the kickstart file, SELinux is enabled and set to--enforcing
by default.--permissive
— Outputs warnings based on the SELinux policy, but does not actually enforce the policy.--disabled
— Disables SELinux completely on the system.
services
(optional)- Modifies the default set of services that will run under the default runlevel. The services listed in the disabled list will be disabled before the services listed in the enabled list are enabled.
--disabled
— Disable the services given in the comma separated list.--enabled
— Enable the services given in the comma separated list.
Important
If you include spaces in the comma-separated list, kickstart will enable or disable only the services up to the first space. For example:services --disabled auditd, cups,smartd, nfslock
will disable only the auditd service. To disable all four services, this entry should include no spaces between services:services --disabled auditd,cups,smartd,nfslock
shutdown
(optional)- Shut down the system after the installation has successfully completed. During a kickstart installation, if no completion method is specified, the
halt
option is used as default.Theshutdown
option is roughly equivalent to theshutdown
command.For other completion methods, refer to thehalt
,poweroff
, andreboot
kickstart options. skipx
(optional)text
(optional)timezone
(required)timezone [--utc] <timezone>
--utc
— If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
upgrade
(optional)user
(optional)user --name=<username> [--groups=<list>] [--homedir=<homedir>] [--password=<password>] [--iscrypted] [--shell=<shell>] [--uid=<uid>]
--name=
— Provides the name of the user. This option is required.--groups=
— In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created.--homedir=
— The home directory for the user. If not provided, this defaults to /home/<username>.--password=
— The new user's password. If not provided, the account will be locked by default.--iscrypted=
— Is the password provided by --password already encrypted or not?--shell=
— The user's login shell. If not provided, this defaults to the system default.--uid=
— The user's UID. If not provided, this defaults to the next available non-system UID.
vnc
(optional)- Allows the graphical installation to be viewed remotely via VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installs. With no options, this command will start a VNC server on the machine with no password and will print out the command that needs to be run to connect a remote machine.
vnc [--host=<hostname>] [--port=<port>] [--password=<password>]
--host=
— Instead of starting a VNC server on the install machine, connect to the VNC viewer process listening on the given hostname.--port=
— Provide a port that the remote VNC viewer process is listening on. If not provided, anaconda will use the VNC default.--password=
— Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
volgroup
(optional)volgroup <name> <partition> <options>
The partition is described in the formpv.<id>
. Any value can be assigned for <id> fields, as long as these values are consistent across volumes and volume groups. The default and lowest value is 01.The options are as follows:--noformat
— Use an existing volume group and do not format it.--useexisting
— Use an existing volume group and reformat it.--pesize=
— Set the size of the physical extents.
Create the partition first, create the logical volume group, and then create the logical volume. For example:part pv.01 --size 3000 volgroup myvg pv.01 logvol / --vgname=myvg --size=2000 --name=rootvol
For a detailed example ofvolgroup
in action, refer to Section 31.4.1, “Advanced Partitioning Example”.xconfig
(optional)- Configures the X Window System. If this option is not given, the user must configure X manually during the installation, if X was installed; this option should not be used if X is not installed on the final system.
--driver
— Specify the X driver to use for the video hardware.--videoram=
— Specifies the amount of video RAM the video card has.--defaultdesktop=
— Specify either GNOME or KDE to set the default desktop (assumes that GNOME Desktop Environment and/or KDE Desktop Environment has been installed through%packages
).--startxonboot
— Use a graphical login on the installed system.--resolution=
— Specify the default resolution for the X Window System on the installed system. Valid values are 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be sure to specify a resolution that is compatible with the video card and monitor.--depth=
— Specify the default color depth for the X Window System on the installed system. Valid values are 8, 16, 24, and 32. Be sure to specify a color depth that is compatible with the video card and monitor.
zerombr
(optional)- If
zerombr
is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables.Note that this command was previously specified aszerombr yes
. This form is now deprecated; you should now simply specifyzerombr
in your kickstart file instead. zfcp
(optional)zfcp [--devnum=<devnum>] [--fcplun=<fcplun>] [--scsiid=<scsiid>] [--scsilun=<scsilun>] [--wwpn=<wwpn>]
%include
(optional)
31.4.1. Advanced Partitioning Example
clearpart
, raid
, part
, volgroup
, and logvol
kickstart options in action:
clearpart --drives=hda,hdc --initlabel # Raid 1 IDE config part raid.11 --size 1000 --asprimary --ondrive=hda part raid.12 --size 1000 --asprimary --ondrive=hda part raid.13 --size 2000 --asprimary --ondrive=hda part raid.14 --size 8000 --ondrive=hda part raid.15 --size 1 --grow --ondrive=hda part raid.21 --size 1000 --asprimary --ondrive=hdc part raid.22 --size 1000 --asprimary --ondrive=hdc part raid.23 --size 2000 --asprimary --ondrive=hdc part raid.24 --size 8000 --ondrive=hdc part raid.25 --size 1 --grow --ondrive=hdc # You can add --spares=x raid / --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21 raid /safe --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22 raid swap --fstype swap --device md2 --level=RAID1 raid.13 raid.23 raid /usr --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24 raid pv.01 --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25 # LVM configuration so that we can resize /var and /usr/local later volgroup sysvg pv.01 logvol /var --vgname=sysvg --size=8000 --name=var logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal
31.5. Package Selection
Warning
@Everything
or simply *
in the %packages
section. Red Hat does not support this type of installation.
@Conflicts
group. If you specify @Everything
in a kickstart file, be sure to exclude @Conflicts
or the installation will fail:
@Everything -@Conflicts
@Everything
in a kickstart file, even if you exclude @Conflicts
.
%packages
command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
variant/repodata/comps-*.xml
file on the first Red Hat Enterprise Linux CD-ROM for a list of groups. Each group has an id, user visibility value, name, description, and package list. In the package list, the packages marked as mandatory are always installed if the group is selected, the packages marked default are selected by default if the group is selected, and the packages marked optional must be specifically selected even if the group is selected to be installed.
- Administration Tools
- Authoring and Publishing
- Development Libraries
- Development Tools
- DNS Name Server
- Eclipse
- Editors
- Engineering and Scientific
- FTP Server
- GNOME Desktop Environment
- GNOME Software Development
- Games and Entertainment
- Graphical Internet
- Graphics
- Java Development
- KDE (K Desktop Environment)
- KDE Software Development
- Legacy Network Server
- Legacy Software Development
- Legacy Software Support
- Mail Server
- Misc
- Multimedia
- MySQL Database
- Network Servers
- News Server
- Office/Productivity
- OpenFabrics Enterprise Distribution
- PostgreSQL Database
- Printing Support
- Server Configuration Tools
- Sound and Video
- System Tools
- Text-based Internet
- Web Server
- Windows File Server
- Windows PV Drivers
- X Software Development
- X Window System
Core
and Base
groups are always selected by default, so it is not necessary to specify them in the %packages
section.
%packages
selection:
%packages @ X Window System @ GNOME Desktop Environment @ Graphical Internet @ Sound and Video dhcp
@
symbol, a space, and then the full group name as given in the comps.xml
file. Groups can also be specified using the id for the group, such as gnome-desktop
. Specify individual packages with no additional characters (the dhcp
line in the example above is an individual package).
-autofs
%packages
option:
--nobase
- Do not install the @Base group. Use this option if you are trying to create a very small system.
--resolvedeps
- The --resolvedeps option has been deprecated. Dependencies are resolved automatically every time now.
--ignoredeps
- The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
--ignoremissing
- Ignore the missing packages and groups instead of halting the installation to ask if the installation should be aborted or continued. For example:
%packages --ignoremissing
31.6. Pre-installation Script
ks.cfg
has been parsed. This section must be at the end of the kickstart file (after the commands) and must start with the %pre
command. You can access the network in the %pre
section; however, name service has not been configured at this point, so only IP addresses work.
Note
--interpreter /usr/bin/python
- Allows you to specify a different scripting language, such as Python. Replace /usr/bin/python with the scripting language of your choice.
31.6.1. Example
%pre
section:
%pre #!/bin/sh hds="" mymedia="" for file in /proc/ide/h* do mymedia=`cat $file/media` if [ $mymedia == "disk" ] ; then hds="$hds `basename $file`" fi done set $hds numhd=`echo $#` drive1=`echo $hds | cut -d' ' -f1` drive2=`echo $hds | cut -d' ' -f2` #Write out partition scheme based on whether there are 1 or 2 hard drives if [ $numhd == "2" ] ; then #2 drives echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include echo "clearpart --all" >> /tmp/part-include echo "part /boot --fstype ext3 --size 75 --ondisk hda" >> /tmp/part-include echo "part / --fstype ext3 --size 1 --grow --ondisk hda" >> /tmp/part-include echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" >> /tmp/part-include else #1 drive echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include echo "clearpart --all" >> /tmp/part-include echo "part /boot --fstype ext3 --size 75" >> /tmp/part-include echo "part swap --recommended" >> /tmp/part-include echo "part / --fstype ext3 --size 2048" >> /tmp/part-include echo "part /home --fstype ext3 --size 2048 --grow" >> /tmp/part-include fi
%include /tmp/part-include
Note
31.7. Post-installation Script
%post
command. This section is useful for functions such as installing additional software and configuring an additional nameserver.
Note
%post
section. If you configured the network for DHCP, the /etc/resolv.conf
file has not been completed when the installation executes the %post
section. You can access the network, but you can not resolve IP addresses. Thus, if you are using DHCP, you must specify IP addresses in the %post
section.
Note
--nochroot
- Allows you to specify commands that you would like to run outside of the chroot environment.The following example copies the file
/etc/resolv.conf
to the file system that was just installed.%post --nochroot cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
--interpreter /usr/bin/python
- Allows you to specify a different scripting language, such as Python. Replace /usr/bin/python with the scripting language of your choice.
--log /path/to/logfile
- Logs the output of the post-install script. Note that the path of the log file must take into account whether or not you use the
--nochroot
option. For example, without--nochroot
:This command is available in Red Hat Enterprise Linux 5.5 and later.%post --log=/root/ks-post.log
with--nochroot
:%post --nochroot --log=/mnt/sysimage/root/ks-post.log
31.7.1. Examples
--log
option to log the result (in Red Hat Enterprise Linux 5.5 and later):
%post --log=/root/ks-post.log /usr/sbin/subscription-manager register --username=admin@example.com --password=secret --serverurl=sam-server.example.com --org="Admin Group" --environment="Dev" --servicelevel=standard
runme
from an NFS share:
mkdir /mnt/temp mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w -- /mnt/temp/runme umount /mnt/temp
Note
-o nolock
is required when mounting an NFS mount.
31.8. Making the Kickstart File Available
- On a boot diskette
- On a boot CD-ROM
- On a network
31.8.1. Creating Kickstart Boot Media
ks.cfg
.
ks.cfg
and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to Section 2.4.1, “Alternative Boot Methods” for instructions on creating boot media; however, before making the file.iso
image file, copy the ks.cfg
kickstart file to the isolinux/
directory.
ks.cfg
and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the ks.cfg
file.
Note
31.8.2. Making the Kickstart File Available on the Network
dhcpd.conf
file for the DHCP server:
filename
"/usr/new-machine/kickstart/"; next-server blarg.redhat.com;
filename
with the name of the kickstart file (or the directory in which the kickstart file resides) and the value after next-server
with the NFS server name.
<ip-addr>-kickstart
<ip-addr>
section of the file name should be replaced with the client's IP address in dotted decimal notation. For example, the file name for a computer with an IP address of 10.10.0.1 would be 10.10.0.1-kickstart
.
/kickstart
from the BOOTP/DHCP server and tries to find the kickstart file using the same <ip-addr>-kickstart
file name as described above.
31.9. Making the Installation Tree Available
31.10. Starting a Kickstart Installation
ks
command line argument is passed to the kernel.
- CD-ROM #1 and Diskette
- The
linux ks=floppy
command also works if theks.cfg
file is located on a vfat or ext2 file system on a diskette and you boot from the Red Hat Enterprise Linux CD-ROM #1.An alternate boot command is to boot off the Red Hat Enterprise Linux CD-ROM #1 and have the kickstart file on a vfat or ext2 file system on a diskette. To do so, enter the following command at theboot:
prompt:linux ks=hd:fd0:/ks.cfg
- With Driver Disk
- If you need to use a driver disk with kickstart, specify the
dd
option as well. For example, to boot off a boot diskette and use a driver disk, enter the following command at theboot:
prompt:linux ks=floppy dd
- Boot CD-ROM
- If the kickstart file is on a boot CD-ROM as described in Section 31.8.1, “Creating Kickstart Boot Media”, insert the CD-ROM into the system, boot the system, and enter the following command at the
boot:
prompt (whereks.cfg
is the name of the kickstart file):linux ks=cdrom:/ks.cfg
askmethod
- Do not automatically use the CD-ROM as the install source if we detect a Red Hat Enterprise Linux CD in your CD-ROM drive.
autostep
- Make kickstart non-interactive. Used for debugging and to generate screenshots. This option should not be used when deploying a system because it may disrupt package installation.
debug
- Start up pdb immediately.
dd
- Use a driver disk.
dhcpclass=<class>
- Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier".
dns=<dns>
- Comma separated list of nameservers to use for a network installation.
driverdisk
- Same as 'dd'.
expert
- Turns on special features:
- allows partitioning of removable media
- prompts for a driver disk
gateway=<gw>
- Gateway to use for a network installation.
graphical
- Force graphical install. Required to have ftp/http use GUI.
isa
- Prompt user for ISA devices configuration.
ip=<ip>
- IP to use for a network installation, use 'dhcp' for DHCP.
keymap=<keymap>
- Keyboard layout to use. Valid values are those which can be used for the 'keyboard' kickstart command.
ks=nfs:<server>:/<path>
- The installation program looks for the kickstart file on the NFS server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share
/mydir/ks.cfg
, the correct boot command would beks=nfs:server.example.com:/mydir/ks.cfg
. ks=http://<server>/<path>
- The installation program looks for the kickstart file on the HTTP server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory
/mydir/ks.cfg
, the correct boot command would beks=http://server.example.com/mydir/ks.cfg
. ks=floppy
- The installation program looks for the file
ks.cfg
on a vfat or ext2 file system on the diskette in/dev/fd0
. ks=floppy:/<path>
- The installation program looks for the kickstart file on the diskette in
/dev/fd0
, as file <path>. ks=hd:<device>:/<file>
- The installation program mounts the file system on <device> (which must be vfat or ext2), and look for the kickstart configuration file as <file> in that file system (for example,
ks=hd:sda3:/mydir/ks.cfg
). ks=file:/<file>
- The installation program tries to read the file <file> from the file system; no mounts are done. This is normally used if the kickstart file is already on the
initrd
image. ks=cdrom:/<path>
- The installation program looks for the kickstart file on CD-ROM, as file <path>.
ks
- If
ks
is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from the "bootServer" from the DHCP response as if it is an NFS server sharing the kickstart file. By default, the bootServer is the same as the DHCP server. The name of the kickstart file is one of the following:- If DHCP is specified and the boot file begins with a
/
, the boot file provided by DHCP is looked for on the NFS server. - If DHCP is specified and the boot file begins with something other than a
/
, the boot file provided by DHCP is looked for in the/kickstart
directory on the NFS server. - If DHCP did not specify a boot file, then the installation program tries to read the file
/kickstart/1.2.3.4-kickstart
, where 1.2.3.4 is the numeric IP address of the machine being installed.
ksdevice=<device>
- The installation program uses this network device to connect to the network. For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command
ks=nfs:<server>:/<path> ksdevice=eth1
at theboot:
prompt. kssendmac
- Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems. Includes MAC address of all nics in CGI environment variables of the form: "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".
lang=<lang>
- Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command.
loglevel=<level>
- Set the minimum level required for messages to be logged. Values for <level> are debug, info, warning, error, and critical. The default value is info.
lowres
- Force GUI installer to run at 640x480.
mediacheck
- Activates loader code to give user option of testing integrity of install source (if an ISO-based method).
method=cdrom://
- Do a CDROM based installation.
method=ftp://<path>
- Use <path> for an FTP installation.
method=hd:<dev>:<path>
- Use <path> on <dev> for a hard drive installation.
method=http://<path>
- Use <path> for an HTTP installation.
method=nfs:<path>
- Use <path> for an NFS installation.
netmask=<nm>
- Netmask to use for a network installation.
nofallback
- If GUI fails exit.
nofb
- Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
nofirewire
- Do not load support for firewire devices.
noipv6
- Disable IPv6 networking during installation.
Important
During installations from a PXE server, IPv6 networking might become active before anaconda processes the Kickstart file. If so, this option will have no effect during installation. nomount
- Don't automatically mount any installed Linux partitions in rescue mode.
nonet
- Do not auto-probe network devices.
noparport
- Do not attempt to load support for parallel ports.
nopass
- Don't pass keyboard/mouse info to stage 2 installer, good for testing keyboard and mouse config screens in stage2 installer during network installs.
nopcmcia
- Ignore PCMCIA controller in system.
noprobe
- Do not attempt to detect hw, prompts user instead.
noshell
- Do not put a shell on tty2 during install.
nostorage
- Do not auto-probe storage devices (SCSI, IDE, RAID).
nousb
- Do not load USB support (helps if install hangs early sometimes).
nousbstorage
- Do not load usbstorage module in loader. May help with device ordering on SCSI systems.
rescue
- Run rescue environment.
resolution=<mode>
- Run installer in mode specified, '1024x768' for example.
serial
- Turns on serial console support.
skipddc
- Skips DDC probe of monitor, may help if it's hanging system.
syslog=<host>[:<port>]
- Once installation is up and running, send log messages to the syslog process on <host>, and optionally, on port <port>. Requires the remote syslog process to accept connections (the -r option).
text
- Force text mode install.
updates
- Prompt for floppy containing updates (bug fixes).
updates=ftp://<path>
- Image containing updates over FTP.
updates=http://<path>
- Image containing updates over HTTP.
upgradeany
- Don't require an /etc/redhat-release that matches the expected syntax to upgrade.
vnc
- Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
vncconnect=<host>[:<port>]
- Once installation is up and running, connect to the vnc client named <host>, and optionally use port <port>.Requires 'vnc' option to be specified as well.
vncpassword=<password>
- Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.Requires 'vnc' option to be specified as well.
Chapter 32. Kickstart Configurator
/usr/sbin/system-config-kickstart
.
32.1. Basic Configuration
Figure 32.1. Basic Configuration
32.2. Installation Method
Figure 32.2. Installation Method
- CD-ROM — Choose this option to install or upgrade from the Red Hat Enterprise Linux CD-ROMs.
- NFS — Choose this option to install or upgrade from an NFS shared directory. In the text field for the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the
variant
directory of the installation tree. For example, if the NFS server contains the directory/mirrors/redhat/i386/Server/
, enter/mirrors/redhat/i386/
for the NFS directory. - FTP — Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the
variant
directory. For example, if the FTP server contains the directory/mirrors/redhat/i386/Server/
, enter/mirrors/redhat/i386/Server/
for the FTP directory. If the FTP server requires a username and password, specify them as well. - HTTP — Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the
variant
directory. For example, if the HTTP server contains the directory/mirrors/redhat/i386/Server/
, enter/mirrors/redhat/i386/Server/
for the HTTP directory. - Hard Drive — Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO (or CD-ROM) images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an
md5sum
program as well as thelinux mediacheck
boot option as discussed in the Red Hat Enterprise Linux Installation Guide. Enter the hard drive partition that contains the ISO images (for example,/dev/hda1
) in the Hard Drive Partition text box. Enter the directory that contains the ISO images in the Hard Drive Directory text box.
32.3. Boot Loader Options
/boot
partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
cdrecord
by configuring hdd=ide-scsi
as a kernel parameter (where hdd
is the CD-ROM device).
32.4. Partition Information
Figure 32.4. Partition Information
msdos
for x86 and gpt
for Itanium), select Initialize the disk label if you are installing on a brand new hard drive.
Note
anaconda
and kickstart
support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the Kickstart Configurator.
32.4.1. Creating Partitions
- In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
- Force the partition to be created as a primary partition.
- Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk (
/dev/hda
), specifyhda
as the drive. Do not include/dev
in the drive name. - Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk (
/dev/hda1
), specifyhda1
as the partition. Do not include/dev
in the partition name. - Format the partition as the chosen file system type.
Figure 32.5. Creating Partitions
32.4.1.1. Creating Software RAID Partitions
- Click thebutton.
- Select Create a software RAID partition.
- Configure the partitions as previously described, except select Software RAID as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use.
Figure 32.6. Creating a Software RAID Partition
- Click thebutton.
- Select Create a RAID device.
- Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device.
Figure 32.7. Creating a Software RAID Device
- Clickto add the device to the list.
32.5. Network Configuration
Figure 32.8. Network Configuration
system-config-network
). Refer to the Red Hat Enterprise Linux Deployment Guide for details.
32.6. Authentication
Figure 32.9. Authentication
- NIS
- LDAP
- Kerberos 5
- Hesiod
- SMB
- Name Switch Cache
32.7. Firewall Configuration
Figure 32.10. Firewall Configuration
port:protocol
. For example, to allow IMAP access through the firewall, specify imap:tcp
. Numeric ports can also be specified explicitly; to allow UDP packets on port 1234 through the firewall, enter 1234:udp
. To specify multiple ports, separate them with commas.
32.8. Display Configuration
skipx
option is written to the kickstart file.
32.8.1. General
Figure 32.11. X Configuration - General
/etc/inittab
configuration file.
32.8.2. Video Card
Figure 32.12. X Configuration - Video Card
32.8.3. Monitor
Figure 32.13. X Configuration - Monitor
32.9. Package Selection
Figure 32.14. Package Selection
%packages
section of the kickstart file after you save it. Refer to Section 31.5, “Package Selection” for details.
32.10. Pre-Installation Script
Figure 32.15. Pre-Installation Script
/usr/bin/python2.4
can be specified for a Python script. This option corresponds to using %pre --interpreter /usr/bin/python2.4
in your kickstart file.
addgroup
, adduser
, adjtimex
, ar
, arping
, ash
, awk
, basename
, bbconfig
, bunzip2
, busybox
, bzcat
, cal
, cat
, catv
, chattr
, chgrp
, chmod
, chown
, chroot
, chvt
, cksum
, clear
, cmp
, comm
, cp
, cpio
, crond
, crontab
, cut
, date
, dc
, dd
, deallocvt
, delgroup
, deluser
, devfsd
, df
, diff
, dirname
, dmesg
, dnsd
, dos2unix
, dpkg
, dpkg-deb
, du
, dumpkmap
, dumpleases
, e2fsck
, e2label
, echo
, ed
, egrep
, eject
, env
, ether-wake
, expr
, fakeidentd
, false
, fbset
, fdflush
, fdformat
, fdisk
, fgrep
, find
, findfs
, fold
, free
, freeramdisk
, fsck
, fsck.ext2
, fsck.ext3
, fsck.minix
, ftpget
, ftpput
, fuser
, getopt
, getty
, grep
, gunzip
, gzip
, hdparm
, head
, hexdump
, hostid
, hostname
, httpd
, hush
, hwclock
, id
, ifconfig
, ifdown
, ifup
, inetd
, insmod
, install
, ip
, ipaddr
, ipcalc
, ipcrm
, ipcs
, iplink
, iproute
, iptunnel
, kill
, killall
, lash
, last
, length
, less
, linux32
, linux64
, ln
, load_policy
, loadfont
, loadkmap
, login
, logname
, losetup
, ls
, lsattr
, lsmod
, lzmacat
, makedevs
, md5sum
, mdev
, mesg
, mkdir
, mke2fs
, mkfifo
, mkfs.ext2
, mkfs.ext3
, mkfs.minix
, mknod
, mkswap
, mktemp
, modprobe
, more
, mount
, mountpoint
, msh
, mt
, mv
, nameif
, nc
, netstat
, nice
, nohup
, nslookup
, od
, openvt
, passwd
, patch
, pidof
, ping
, ping6
, pipe_progress
, pivot_root
, printenv
, printf
, ps
, pwd
, rdate
, readlink
, readprofile
, realpath
, renice
, reset
, rm
, rmdir
, rmmod
, route
, rpm
, rpm2cpio
, run-parts
, runlevel
, rx
, sed
, seq
, setarch
, setconsole
, setkeycodes
, setlogcons
, setsid
, sh
, sha1sum
, sleep
, sort
, start-stop-daemon
, stat
, strings
, stty
, su
, sulogin
, sum
, swapoff
, swapon
, switch_root
, sync
, sysctl
, tail
, tar
, tee
, telnet
, telnetd
, test
, tftp
, time
, top
, touch
, tr
, traceroute
, true
, tty
, tune2fs
, udhcpc
, udhcpd
, umount
, uname
, uncompress
, uniq
, unix2dos
, unlzma
, unzip
, uptime
, usleep
, uudecode
, uuencode
, vconfig
, vi
, vlock
, watch
, watchdog
, wc
, wget
, which
, who
, whoami
, xargs
, yes
, zcat
, zcip
busybox command --help
anaconda
, bash
, bzip2
, jmacs
, ftp
, head
, joe
, kudzu-probe
, list-harddrives
, loadkeys
, mtools
, mbchk
, mtools
, mini-wm
, mtools
, jpico
, pump
, python
, python2.4
, raidstart
, raidstop
, rcp
, rlogin
, rsync
, setxkbmap
, sftp
, shred
, ssh
, syslinux
, syslogd
, tac
, termidx
, vncconfig
, vncpasswd
, xkbcomp
, Xorg
, Xvnc
, zcat
Warning
%pre
command. It is added for you.
Note
32.11. Post-Installation Script
Figure 32.16. Post-Installation Script
Warning
%post
command. It is added for you.
%post
section:
echo "Hackers will be punished" > /etc/motd
Note
32.11.1. Chroot Environment
--nochroot
option in the %post
section.
/mnt/sysimage/
.
echo "Hackers will be punished" > /mnt/sysimage/etc/motd
32.11.2. Use an Interpreter
/usr/bin/python2.2
can be specified for a Python script. This option corresponds to using %post --interpreter /usr/bin/python2.2
in your kickstart file.
32.12. Saving the File
Figure 32.17. Preview
Chapter 33. Boot Process, Init, and Shutdown
Important
/var/log/boot.log
. This functionality is not available in Red Hat Enterprise Linux 5.
33.1. The Boot Process
- The system BIOS checks the system and launches the first stage boot loader on the MBR of the primary hard disk.
- The first stage boot loader loads itself into memory and launches the second stage boot loader from the
/boot/
partition. - The second stage boot loader loads the kernel into memory, which in turn loads any necessary modules and mounts the root partition read-only.
- The kernel transfers control of the boot process to the
/sbin/init
program. - The
/sbin/init
program loads all services and user-space tools, and mounts all partitions listed in/etc/fstab
. - The user is presented with a login screen for the freshly booted Linux system.
33.2. A Detailed Look at the Boot Process
33.2.1. The BIOS
33.2.2. The Boot Loader
/boot/grub/grub.conf
— at boot time. Refer to Section 9.7, “GRUB Menu Configuration File” for information on how to edit this file.
Note
/boot/
directory. The kernel binary is named using the following format — /boot/vmlinuz-<kernel-version>
file (where <kernel-version>
corresponds to the kernel version specified in the boot loader's settings).
/sysroot/
, a RAM-based virtual file system, via cpio
. The initramfs
is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 file system.
initramfs
image(s) are loaded into memory, the boot loader hands control of the boot process to the kernel.
33.2.2.1. Boot Loaders for Other Architectures
init
command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel.
33.2.3. The Kernel
initramfs
image(s) in a predetermined location in memory, decompresses it directly to /sysroot/
, and loads all necessary drivers. Next, it initializes virtual devices related to the file system, such as LVM or software RAID, before completing the initramfs
processes and freeing up all the memory the disk image once occupied.
/sbin/init
program.
33.2.4. The /sbin/init
Program
/sbin/init
program (also called init
) coordinates the rest of the boot process and configures the environment for the user.
init
command starts, it becomes the parent or grandparent of all of the processes that start up automatically on the system. First, it runs the /etc/rc.d/rc.sysinit
script, which sets the environment path, starts swap, checks the file systems, and executes all other steps required for system initialization. For example, most systems use a clock, so rc.sysinit
reads the /etc/sysconfig/clock
configuration file to initialize the hardware clock. Another example is if there are special serial port processes which must be initialized, rc.sysinit
executes the /etc/rc.serial
file.
init
command then runs the /etc/inittab
script, which describes how the system should be set up in each SysV init runlevel. Runlevels are a state, or mode, defined by the services listed in the SysV /etc/rc.d/rc<x>.d/
directory, where <x> is the number of the runlevel. For more information on SysV init runlevels, refer to Section 33.4, “SysV Init Runlevels”.
init
command sets the source function library, /etc/rc.d/init.d/functions
, for the system, which configures how to start, kill, and determine the PID of a program.
init
program starts all of the background processes by looking in the appropriate rc
directory for the runlevel specified as the default in /etc/inittab
. The rc
directories are numbered to correspond to the runlevel they represent. For instance, /etc/rc.d/rc5.d/
is the directory for runlevel 5.
init
program looks in the /etc/rc.d/rc5.d/
directory to determine which processes to start and stop.
/etc/rc.d/rc5.d/
directory:
K05innd -> ../init.d/innd K05saslauthd -> ../init.d/saslauthd K10dc_server -> ../init.d/dc_server K10psacct -> ../init.d/psacct K10radiusd -> ../init.d/radiusd K12dc_client -> ../init.d/dc_client K12FreeWnn -> ../init.d/FreeWnn K12mailman -> ../init.d/mailman K12mysqld -> ../init.d/mysqld K15httpd -> ../init.d/httpd K20netdump-server -> ../init.d/netdump-server K20rstatd -> ../init.d/rstatd K20rusersd -> ../init.d/rusersd K20rwhod -> ../init.d/rwhod K24irda -> ../init.d/irda K25squid -> ../init.d/squid K28amd -> ../init.d/amd K30spamassassin -> ../init.d/spamassassin K34dhcrelay -> ../init.d/dhcrelay K34yppasswdd -> ../init.d/yppasswdd K35dhcpd -> ../init.d/dhcpd K35smb -> ../init.d/smb K35vncserver -> ../init.d/vncserver K36lisa -> ../init.d/lisa K45arpwatch -> ../init.d/arpwatch K45named -> ../init.d/named K46radvd -> ../init.d/radvd K50netdump -> ../init.d/netdump K50snmpd -> ../init.d/snmpd K50snmptrapd -> ../init.d/snmptrapd K50tux -> ../init.d/tux K50vsftpd -> ../init.d/vsftpd K54dovecot -> ../init.d/dovecot K61ldap -> ../init.d/ldap K65kadmin -> ../init.d/kadmin K65kprop -> ../init.d/kprop K65krb524 -> ../init.d/krb524 K65krb5kdc -> ../init.d/krb5kdc K70aep1000 -> ../init.d/aep1000 K70bcm5820 -> ../init.d/bcm5820 K74ypserv -> ../init.d/ypserv K74ypxfrd -> ../init.d/ypxfrd K85mdmpd -> ../init.d/mdmpd K89netplugd -> ../init.d/netplugd K99microcode_ctl -> ../init.d/microcode_ctl S04readahead_early -> ../init.d/readahead_early S05kudzu -> ../init.d/kudzu S06cpuspeed -> ../init.d/cpuspeed S08ip6tables -> ../init.d/ip6tables S08iptables -> ../init.d/iptables S09isdn -> ../init.d/isdn S10network -> ../init.d/network S12syslog -> ../init.d/syslog S13irqbalance -> ../init.d/irqbalance S13portmap -> ../init.d/portmap S15mdmonitor -> ../init.d/mdmonitor S15zebra -> ../init.d/zebra S16bgpd -> ../init.d/bgpd S16ospf6d -> ../init.d/ospf6d S16ospfd -> ../init.d/ospfd S16ripd -> ../init.d/ripd S16ripngd -> ../init.d/ripngd S20random -> ../init.d/random S24pcmcia -> ../init.d/pcmcia S25netfs -> ../init.d/netfs S26apmd -> ../init.d/apmd S27ypbind -> ../init.d/ypbind S28autofs -> ../init.d/autofs S40smartd -> ../init.d/smartd S44acpid -> ../init.d/acpid S54hpoj -> ../init.d/hpoj S55cups -> ../init.d/cups S55sshd -> ../init.d/sshd S56rawdevices -> ../init.d/rawdevices S56xinetd -> ../init.d/xinetd S58ntpd -> ../init.d/ntpd S75postgresql -> ../init.d/postgresql S80sendmail -> ../init.d/sendmail S85gpm -> ../init.d/gpm S87iiim -> ../init.d/iiim S90canna -> ../init.d/canna S90crond -> ../init.d/crond S90xfs -> ../init.d/xfs S95atd -> ../init.d/atd S96readahead -> ../init.d/readahead S97messagebus -> ../init.d/messagebus S97rhnsd -> ../init.d/rhnsd S99local -> ../rc.local
/etc/rc.d/rc5.d/
directory. Rather, all of the files in /etc/rc.d/rc5.d/
are symbolic links pointing to scripts located in the /etc/rc.d/init.d/
directory. Symbolic links are used in each of the rc
directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
K
or an S
. The K
links are processes that are killed on that runlevel, while those beginning with an S
are started.
init
command first stops all of the K
symbolic links in the directory by issuing the /etc/rc.d/init.d/<command> stop
command, where <command> is the process to be killed. It then starts all of the S
symbolic links by issuing /etc/rc.d/init.d/<command> start
.
Note
/etc/rc.d/init.d/httpd stop
stops the Apache HTTP Server.
Note
init
program executes is the /etc/rc.d/rc.local
file. This file is useful for system customization. Refer to Section 33.3, “Running Additional Programs at Boot Time” for more information about using the rc.local
file.
init
command has progressed through the appropriate rc
directory for the runlevel, the /etc/inittab
script forks an /sbin/mingetty
process for each virtual console (login prompt) allocated to the runlevel. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The /sbin/mingetty
process opens communication pathways to tty devices[14], sets their modes, prints the login prompt, accepts the user's username and password, and initiates the login process.
/etc/inittab
runs a script called /etc/X11/prefdm
. The prefdm
script executes the preferred X display manager[15] — gdm
, kdm
, or xdm
, depending on the contents of the /etc/sysconfig/desktop
file.
33.3. Running Additional Programs at Boot Time
/etc/rc.d/rc.local
script is executed by the init
command at boot time or when changing runlevels. Adding commands to the bottom of this script is an easy way to perform necessary tasks like starting special services or initialize devices without writing complex initialization scripts in the /etc/rc.d/init.d/
directory and creating symbolic links.
/etc/rc.serial
script is used if serial ports must be setup at boot time. This script runs setserial
commands to configure the system's serial ports. Refer to the setserial
man page for more information.
33.4. SysV Init Runlevels
init
launches or halts when initializing a runlevel. SysV init was chosen because it is easier to use and more flexible than the traditional BSD-style init process.
/etc/rc.d/
directory. Within this directory, are the rc
, rc.local
, rc.sysinit
, and, optionally, the rc.serial
scripts as well as the following directories:
init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/
init.d/
directory contains the scripts used by the /sbin/init
command when controlling services. Each of the numbered directories represent the six runlevels configured by default under Red Hat Enterprise Linux.
33.4.1. Runlevels
init
. For instance, runlevel 1 (single user mode) halts any network services, while runlevel 3 starts these services. By assigning specific services to be halted or started on a given runlevel, init
can quickly change the mode of the machine without the user manually stopping and starting services.
0
— Halt1
— Single-user text mode2
— Not used (user-definable)3
— Full multi-user text mode4
— Not used (user-definable)5
— Full multi-user graphical mode (with an X-based login screen)6
— Reboot
/etc/inittab
. To find out the default runlevel for a system, look for the line similar to the following near the top of /etc/inittab
:
id:5:initdefault:
/etc/inittab
as root.
Warning
/etc/inittab
. Simple typos can cause the system to become unbootable. If this happens, either use a boot diskette, enter single-user mode, or enter rescue mode to boot the computer and repair the file.
33.4.2. Runlevel Utilities
/etc/rc.d/
.
/sbin/chkconfig
— The/sbin/chkconfig
utility is a simple command line tool for maintaining the/etc/rc.d/init.d/
directory hierarchy.- /usr/sbin/ntsysv — The ncurses-based /sbin/ntsysv utility provides an interactive text-based interface, which some find easier to use than
chkconfig
. - Services Configuration Tool — The graphical Services Configuration Tool (
system-config-services
) program is a flexible utility for configuring runlevels.
33.5. Shutting Down
/sbin/shutdown
command. The shutdown
man page has a complete list of options, but the two most common uses are:
/sbin/shutdown -h now
/sbin/shutdown -r now
-h
option halts the machine, and the -r
option reboots.
reboot
and halt
commands to shut down the system while in runlevels 1 through 5. For more information about PAM console users, refer to the Red Hat Enterprise Linux Deployment Guide.
tty
devices.
Chapter 34. PXE Network Installations
askmethod
boot option with the Red Hat Enterprise Linux CD #1. Alternatively, if the system to be installed contains a network interface card (NIC) with Pre-Execution Environment (PXE) support, it can be configured to boot from files on another networked system rather than local media such as a CD-ROM.
tftp
server (which provides the files necessary to start the installation program), and the location of the files on the tftp
server. This is possible because of PXELINUX, which is part of the syslinux
package.
- Configure the network (NFS, FTP, HTTP) server to export the installation tree.
- Configure the files on the
tftp
server necessary for PXE booting. - Configure which hosts are allowed to boot from the PXE configuration.
- Start the
tftp
service. - Configure DHCP.
- Boot the client, and start the installation.
34.1. Setting up the Network Server
34.2. PXE Boot Configuration
tftp
server so they can be found when the client requests them. The tftp
server is usually the same server as the network server exporting the installation tree.
34.2.1. Command Line Configuration
pxeos
command line utility, which is part of the system-config-netboot-cmd
package, can be used to configure the tftp
server files as described in Section 34.4, “TFTPD”:
pxeos -a -i "<description>" -p <NFS|HTTP|FTP> -D 0 -s installer.example.com \ -L <location> -k <kernel> -K <kickstart> <os-identifer>
-a
— Specifies that an OS instance is being added to the PXE configuration.-i
"<description>" — Replace "<description>" with a description of the OS instance.-p
<NFS|HTTP|FTP> — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified.-D
<0|1> — Specify "0
" which indicates that it is not a diskless configuration sincepxeos
can be used to configure a diskless environment as well.-s
installer.example.com — Provide the name of the NFS, FTP, or HTTP server after the-s
option.-L
<location> — Provide the location of the installation tree on that server after the-L
option.For example, if the installation tree is exported as/install/rhel5
on an NFS share, specify-L /install/rhel5
.-k
<kernel> — Provide the specific kernel for booting. Installation trees can contain multiple kernels.For example, if the installation tree contain a patched kernel namedvmlinuz-du
alongside the standard kernel namedvmlinuz
, use-k vmlinuz-du
to specify the patched kernel.-K
<kickstart> — Provide the location of the kickstart file, if available. Specify this location as a full path, including the protocol; for example:-K nfs:192.168.0.1:/install/rhel5/ks.cfg
- <os-identifer> — Specify the OS identifier, which is used as the directory name in the
/tftpboot/linux-install/
directory.
-A 0 -u <username> -p <password>
/tftpboot/linux-install/pxelinux.cfg/pxeos.xml
file.
pxeos
command, refer to the pxeos
man page.
/tftpboot/linux-install/pxelinux.cfg/pxeos.xml
file and uses similar options to pxeos. Refer to the pxeboot man page for more detail.
34.3. Adding PXE Hosts
Figure 34.1. Add Hosts
Figure 34.2. Add a Host
- Hostname or IP Address/Subnet — The IP address, fully qualified hostname, or a subnet of systems that should be allowed to connect to the PXE server for installations.
Important
Only enter a single IP address. anaconda will not use multiple addresses. - Operating System — The operating system identifier to install on this client. The list is populated from the network install instances created from the Network Installation Dialog.
- Serial Console — This option allows use of a serial console.
- Kickstart File — The location of a kickstart file to use, such as
http://server.example.com/kickstart/ks.cfg
. This file can be created with the Kickstart Configurator. Refer to Chapter 32, Kickstart Configurator for details.
34.3.1. Command Line Configuration
pxeboot
utility, a part of the system-config-netboot
package, can be used to add hosts which are allowed to connect to the PXE server:
pxeboot -a -K <kickstart> -O <os-identifier> -r <value> <host>
-a
— Specifies that a host is to be added.-K
<kickstart> — The location of the kickstart file, if available.-O
<os-identifier> — Specifies the operating system identifier as defined in Section 34.2, “PXE Boot Configuration”.-r
<value> — Specifies the ram disk size.- <host> — Specifies the IP address or hostname of the host to add.
pxeboot
command, refer to the pxeboot
man page.
34.4. TFTPD
34.4.1. Starting the tftp
Server
tftp-server
package is installed with the command rpm -q tftp-server
. If it is not installed, install it via Red Hat Network or the Red Hat Enterprise Linux CD-ROMs. Note
tftp
is an xinetd-based service; start it with the following commands:
/sbin/chkconfig --level 345 xinetd on
/sbin/chkconfig --level 345 tftp on
tftp
and xinetd
services to immediately turn on and also configure them to start at boot time in runlevels 3, 4, and 5.
34.5. Configuring the DHCP Server
allow booting; allow bootp; class "pxeclients" { match if substring(option vendor-class-identifier, 0, 9) = "PXEClient"; next-server <server-ip>; filename "linux-install/pxelinux.0"; }
tftp
server.
Appendix A. Revision History
Revision History | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Revision 3.1-46 | Thu Sep 11 2014 | ||||||||||||
| |||||||||||||
Revision 3.1-45 | Mon Jun 30 2014 | ||||||||||||
| |||||||||||||
Revision 3.1-44 | Mon Jun 30 2014 | ||||||||||||
| |||||||||||||
Revision 3.1-43 | Thu Jul 11 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-42 | Thu Jul 11 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-39 | Tue Apr 23 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-38 | Tue Apr 23 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-37 | Mon Jan 7 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-36 | Mon Jan 7 2013 | ||||||||||||
| |||||||||||||
Revision 3.1-35 | Wed Oct 31 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-34 | Wed Oct 31 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-33 | Wed Sep 12 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-32 | Thu Sep 06 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-30 | Tue Aug 14 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-26 | Fri Feb 02 2012 | ||||||||||||
| |||||||||||||
Revision 3.1-24 | Fri Nov 18 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-22 | Wed Nov 9 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-21 | Fri Nov 4 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-20 | Thu Oct 13 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-19 | Thu Sep 29 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-18 | Fri Sep 23 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-17 | Mon Sep 19 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-16 | Thu Jul 21 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-15 | Fri Jun 10 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-14 | Mon Apr 11 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-13 | Thu Jan 6 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-12 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-11 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-10 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
Revision 3.1-9 | Tue Dec 21 2010 | ||||||||||||
| |||||||||||||
Revision 3.1-5 | Thu Oct 7 2010 | ||||||||||||
| |||||||||||||
Revision 3.1-2 | Mon Apr 19 2010 | ||||||||||||
| |||||||||||||
Revision 3.1-1 | Mon Apr 19 2010 | ||||||||||||
| |||||||||||||
Revision 3.1-0 | Tue Apr 6 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-23 | Tue Apr 6 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-22 | Wed Mar 31 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-21 | Tue Jan 12 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-20 | Tue Jan 12 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-19 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-18 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-17 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-16 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-15 | Fri Jan 8 2010 | ||||||||||||
| |||||||||||||
Revision 3.0-14 | Tue Dec 22 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-13 | Mon Dec 21 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-12 | Thu Dec 17 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-11 | Wed Dec 16 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-10 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-9 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-8 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
Revision 3.0-1 | Tue Aug 04 2009 | , | |||||||||||
| |||||||||||||
Revision 2.0-1 | Mon Jan 05 2009 | ||||||||||||
| |||||||||||||
Revision 1.0-1 | Fri Oct 03 2008 | ||||||||||||
|
Index
Symbols
- /boot/ partition
- recommended partitioning, Recommended Partitioning Scheme, Recommended Partitioning Scheme
- /boot/efi/ , Itanium systems
- /root/install.log
- install log file location, Prepare to Install , Prepare to Install , Preparing to Install
- /var/ partition
- recommended partitioning, Recommended Partitioning Scheme, Recommended Partitioning Scheme
A
- aboot , Boot Loaders for Other Architectures
- activating your subscription, Registering the System
- adding partitions, Adding Partitions, Adding Partitions
- file system type, File System Types, File System Types
- autoboot
- automatic partitioning, Disk Partitioning Setup, Create Default Layout, Disk Partitioning Setup, Create Default Layout, Disk Partitioning Setup, Create Default Layout
B
- Basic Input/Output System (see BIOS)
- BIOS
- definition of, The BIOS
- (see also boot process)
- boot CD-ROM, Alternative Boot Methods
- creating, Making an Installation Boot CD-ROM
- boot loader, x86, AMD64, and Intel® 64 Boot Loader Configuration
- alternatives to, Alternative Boot Loaders
- commercial products, Alternative Boot Loaders
- LOADLIN, Alternative Boot Loaders
- SYSLINUX, Alternative Boot Loaders
- configuration, x86, AMD64, and Intel® 64 Boot Loader Configuration
- GRUB, x86, AMD64, and Intel® 64 Boot Loader Configuration
- installing on boot partition, Advanced Boot Loader Configuration
- MBR, Advanced Boot Loader Configuration
- password, x86, AMD64, and Intel® 64 Boot Loader Configuration
- boot loader password, x86, AMD64, and Intel® 64 Boot Loader Configuration
- boot loaders, GRUB
- (see also GRUB)
- definition of, The GRUB Boot Loader
- types of
- boot method
- overview, Basic Overview of the Boot Method
- boot methods
- boot CD-ROM, Alternative Boot Methods
- USB pen drive, Alternative Boot Methods
- boot options, Additional Boot Options
- additional, Additional Boot Options for Intel® and AMD Systems, Additional Boot Options for IBM Power Systems, Additional Boot Options
- boot.iso , Additional Boot Options
- linux mediacheck , Preparing for a Hard Drive Installation, Preparing for a Hard Drive Installation
- mediacheck, Additional Boot Options
- serial mode, Additional Boot Options
- UTF-8, Additional Boot Options
- text mode, Additional Boot Options
- boot process, Boot Process, Init, and Shutdown, A Detailed Look at the Boot Process
- (see also boot loaders)
- chain loading, GRUB and the x86 Boot Process
- direct loading, GRUB and the x86 Boot Process
- for x86, A Detailed Look at the Boot Process
- stages of, The Boot Process, A Detailed Look at the Boot Process
- /sbin/init command, The /sbin/init Program
- BIOS, The BIOS
- boot loader, The Boot Loader
- EFI shell, The BIOS
- kernel, The Kernel
- boot.iso , Additional Boot Options
- booting
- emergency mode, Booting into Emergency Mode
- installation program
- from a CD-ROM, Booting the Installation Program from the DVD/CD-ROM
- from an LS-120 diskette, Booting the Installation Program from an LS-120 Diskette
- Itanium, Booting the Installation Program on Itanium Systems
- x86, AMD64 and Intel 64, Booting the Installation Program on x86, AMD64, and Intel® 64 Systems
- rescue mode, Booting into Rescue Mode
- single-user mode, Booting into Single-User Mode
- booting the installation program
- IBM System i and IBM System p , Booting the IBM System i or IBM System p Installation Program
C
- canceling the installation, Installing from DVD/CD-ROM
- CD-ROM
- ATAPI, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- boot CD-ROM, creating, Making an Installation Boot CD-ROM
- IDE, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- installation from, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- SCSI, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- chkconfig , Runlevel Utilities
- (see also services)
- clock, Time Zone Configuration, Time Zone Configuration, Time Zone Configuration
- configuration
- clock, Time Zone Configuration, Time Zone Configuration, Time Zone Configuration
- GRUB, x86, AMD64, and Intel® 64 Boot Loader Configuration
- hardware, System Specifications List
- network, Network Configuration, Network Configuration, Network Configuration
- time, Time Zone Configuration, Time Zone Configuration, Time Zone Configuration
- time zone, Time Zone Configuration, Time Zone Configuration, Time Zone Configuration
- consoles, virtual, A Note about Virtual Consoles, A Note about Linux Virtual Consoles
D
- DASD
- adding, Adding DASD
- DASD installation, Installing from a Hard Drive (DASD)
- DHCP
- diskless environment, Configuring the DHCP Server
- PXE installations, Configuring the DHCP Server
- Disk Druid
- adding partitions
- file system type, File System Types, File System Types
- buttons, Disk Druid's Buttons, Disk Druid's Buttons, Disk Druid's Buttons
- deleting partitions, Deleting a Partition
- editing partitions, Editing Partitions, Editing Partitions, Editing Partitions
- partitions, Partitioning Your System, Partitioning Your System, Partitioning Your System
- Disk Partitioner
- adding partitions, Adding Partitions, Adding Partitions
- disk partitioning, Disk Partitioning Setup, Disk Partitioning Setup, Disk Partitioning Setup
- disk space, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?
- diskless environment
- DHCP configuration, Configuring the DHCP Server
- dmraid
- installation, Advanced Storage Options , Advanced Storage Options , Advanced Storage Options
- driver diskette, Starting the Installation Program
E
- EFI
- system partition, Itanium Systems — EFI System Partition
- EFI Shell, Itanium Systems — The EFI Shell
- EFI shell
- definition of, The BIOS
- (see also boot process)
- ELILO, Boot Loaders and System Architecture, Boot Loaders for Other Architectures
- (see also boot loaders)
- autoboot, Booting Red Hat Enterprise Linux Automatically
- post-installation boot setup, Itanium Systems — Booting Your Machine and Post-Installation Setup
- emergency mode, Booting into Emergency Mode
- extended partitions, Partitions within Partitions — An Overview of Extended Partitions
- Extensible Firmware Interface shell (see EFI shell)
F
- FCP devices, FCP Devices
- file system
- formats, overview of, It is Not What You Write, it is How You Write It
- file system types, File System Types, File System Types
- FTP
G
- graphical installation program
- running from NFS, Running the Installation Program
- VNC, Installation using VNC
- x11 forwarding, Installation using X11 Forwarding
- GRUB, x86, AMD64, and Intel® 64 Boot Loader Configuration, Boot Loaders and System Architecture, The Boot Loader
- (see also boot loaders)
- additional resources, Additional Resources
- installed documentation, Installed Documentation
- related books, Related Books
- useful websites, Useful Websites
- alternatives to, Alternative Boot Loaders
- commercial products, Alternative Boot Loaders
- LOADLIN, Alternative Boot Loaders
- SYSLINUX, Alternative Boot Loaders
- boot process, GRUB and the x86 Boot Process
- Changing Runlevels at Boot Time, Changing Runlevels at Boot Time
- changing runlevels with, GRUB Interfaces
- commands, GRUB Commands
- configuration, x86, AMD64, and Intel® 64 Boot Loader Configuration
- configuration file
- /boot/grub/grub.conf , Configuration File Structure
- structure, Configuration File Structure
- definition of, GRUB
- features, Features of GRUB
- installing, Installing GRUB
- interfaces, GRUB Interfaces
- command line, GRUB Interfaces
- menu, GRUB Interfaces
- menu entry editor, GRUB Interfaces
- order of, Interfaces Load Order
- menu configuration file, GRUB Menu Configuration File
- directives, Configuration File Directives
- role in boot process, The Boot Loader
- SMP motherboards, SMP Motherboards and GRUB
- terminology, GRUB Terminology
- devices, Device Names
- files, File Names and Blocklists
- root file system, The Root File System and GRUB
- grub.conf , Configuration File Structure
- (see also GRUB)
H
- halt, Shutting Down
- (see also shutdown)
- hard disk
- basic concepts, Hard Disk Basic Concepts
- extended partitions, Partitions within Partitions — An Overview of Extended Partitions
- file system formats, It is Not What You Write, it is How You Write It
- partition introduction, Partitions: Turning One Drive Into Many
- partition types, Partitions: Turning One Drive Into Many
- partitioning of, An Introduction to Disk Partitions
- hard drive installation, Installing from a Hard Drive, Installing from a Hard Drive
- hardware
- compatibility, Is Your Hardware Compatible?
- configuration, System Specifications List
- preparation, Additional Hardware Preparation for System z
- hardware preparation, eServer System i, Preparation for IBM eServer System p and System i
- hardware preparation, eServer System p, Preparation for IBM eServer System p and System i
- HMC vterm, Using the HMC vterm
- hostname configuration, Network Configuration, Network Configuration, Network Configuration
- HTTP
I
- ia64 (see Itanium)
- init command, The /sbin/init Program
- (see also boot process)
- configuration files
- /etc/inittab , SysV Init Runlevels
- role in boot process, The /sbin/init Program
- (see also boot process)
- runlevels
- directories for, SysV Init Runlevels
- runlevels accessed by, Runlevels
- SysV init
- definition of, SysV Init Runlevels
- install log file
- /root/install.log , Prepare to Install , Prepare to Install , Preparing to Install
- installation
- aborting, Installing from DVD/CD-ROM
- can you install with a CD-ROM or DVD, Can You Install Using the CD-ROM or DVD?, Can You Install Using the CD-ROM or DVD?
- CD-ROM, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- disk space, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?
- FTP, Preparing for a Network Installation, Installing via FTP, Preparing for a Network Installation, Installing via FTP, Preparing for a Network Installation, Installing via FTP
- GUI
- hard drive, Preparing for a Hard Drive Installation, Installing from a Hard Drive, Preparing for a Hard Drive Installation, Installing from a Hard Drive, Preparing for a Hard Drive Installation
- HTTP, Preparing for a Network Installation, Installing via HTTP, Preparing for a Network Installation, Installing via HTTP, Preparing for a Network Installation, Installing via HTTP
- Itanium overview, Itanium System Installation Overview
- keyboard navigation, Using the Keyboard to Navigate, Using the Keyboard to Navigate, Using the Keyboard to Navigate
- kickstart (see kickstart installations)
- mediacheck, Additional Boot Options
- method
- CD-ROM, Selecting an Installation Method
- FTP, Selecting an Installation Method
- hard drive, Selecting an Installation Method
- HTTP, Selecting an Installation Method
- NFS image, Selecting an Installation Method
- selecting, Selecting an Installation Method
- network, Preparing for a Network Installation, Preparing for a Network Installation, Preparing for a Network Installation
- NFS, Preparing for a Network Installation, Installing via NFS, Preparing for a Network Installation, Installing via NFS, Preparing for a Network Installation, Installing via NFS
- server information, Installing via NFS, Installing via NFS, Installing via NFS
- partitioning, Partitioning Your System, Partitioning Your System, Partitioning Your System
- program
- graphical user interface, The Graphical Installation Program User Interface, The Graphical Installation Program User Interface, The Graphical Installation Program User Interface
- starting, Starting the Installation Program
- text mode user interface, The Text Mode Installation Program User Interface, The Text Mode Installation Program User Interface, The Text Mode Installation Program User Interface
- virtual consoles, A Note about Virtual Consoles, A Note about Linux Virtual Consoles
- PXE (see PXE installations)
- serial mode, Additional Boot Options
- UTF-8, Additional Boot Options
- starting, Installing from DVD/CD-ROM, Installing from DVD/CD-ROM
- text mode, Additional Boot Options
- installation media
- Installation Number , Enter the Installation Number, Enter the Installation Number, Enter the Installation Number
- installation overview, Itanium System Installation Overview
- installation program
- Itanium
- starting, Running the Installation Program
- x86, AMD64 and Intel 64
- installing
- without the LPAR CD
- using a recent SEW, Installing in an LPAR without the Red Hat Enterprise Linux for System z CD-ROMs
- without the Red Hat Enterprise Linux for IBM System z CD-ROMs, Installing in an LPAR without the Red Hat Enterprise Linux for System z CD-ROMs
- installing packages, Package Group Selection, Package Group Selection, Package Group Selection
- IPL configuration from a SCSI device, Configuring IPL from a SCSI Device
- IPL NWSSTG, Unable to IPL from *NWSSTG
- iscsi
- installation, Advanced Storage Options , Advanced Storage Options , Advanced Storage Options
K
- kernel
- boot options, Additional Boot Options for Intel® and AMD Systems, Additional Boot Options for IBM Power Systems, Additional Boot Options
- role in boot process, The Kernel
- kernel options, Kernel Options
- Kernel Related Information, Kernel-Related Information
- keyboard
- configuration, Keyboard Configuration, Keyboard Configuration
- navigating the installation program using, Using the Keyboard to Navigate, Using the Keyboard to Navigate, Using the Keyboard to Navigate
- keymap
- selecting type of keyboard, Keyboard Configuration, Keyboard Configuration
- kickstart
- how the file is found, Starting a Kickstart Installation
- Kickstart Configurator , Kickstart Configurator
- %post script, Post-Installation Script
- %pre script, Pre-Installation Script
- authentication options, Authentication
- basic options, Basic Configuration
- boot loader, Boot Loader Options
- boot loader options, Boot Loader Options
- Display configuration, Display Configuration
- firewall configuration, Firewall Configuration
- installation key, Basic Configuration
- installation method selection, Installation Method
- interactive, Basic Configuration
- keyboard, Basic Configuration
- language, Basic Configuration
- network configuration, Network Configuration
- package selection, Package Selection
- partitioning, Partition Information
- software RAID, Creating Software RAID Partitions
- preview, Kickstart Configurator
- reboot, Basic Configuration
- root password, Basic Configuration
- encrypt, Basic Configuration
- saving, Saving the File
- SELinux configuration, SELinux Configuration
- text mode installation, Basic Configuration
- time zone, Basic Configuration
- kickstart file
- %include , Kickstart Options
- %post, Post-installation Script
- %pre, Pre-installation Script
- auth , Kickstart Options
- authconfig , Kickstart Options
- autopart , Kickstart Options
- autostep , Kickstart Options
- bootloader , Kickstart Options
- CD-ROM-based, Creating Kickstart Boot Media
- clearpart , Kickstart Options
- cmdline , Kickstart Options
- creating, Kickstart Options
- device , Kickstart Options
- diskette-based, Creating Kickstart Boot Media
- driverdisk , Kickstart Options
- firewall , Kickstart Options
- firstboot , Kickstart Options
- flash-based, Creating Kickstart Boot Media
- format of, Creating the Kickstart File
- graphical , Kickstart Options
- halt , Kickstart Options
- ignoredisk , Kickstart Options
- include contents of another file, Kickstart Options
- install , Kickstart Options
- installation methods, Kickstart Options
- interactive , Kickstart Options
- iscsi , Kickstart Options
- iscsiname , Kickstart Options
- key , Kickstart Options
- keyboard , Kickstart Options
- lang , Kickstart Options
- langsupport , Kickstart Options
- logging , Kickstart Options
- logvol , Kickstart Options
- mediacheck , Kickstart Options
- mouse , Kickstart Options
- multipath , Kickstart Options
- network , Kickstart Options
- network-based, Making the Kickstart File Available on the Network, Making the Installation Tree Available
- options, Kickstart Options
- partitioning examples, Advanced Partitioning Example
- package selection specification, Package Selection
- part , Kickstart Options
- partition , Kickstart Options
- post-installation configuration, Post-installation Script
- poweroff , Kickstart Options
- pre-installation configuration, Pre-installation Script
- raid , Kickstart Options
- reboot , Kickstart Options
- rootpw , Kickstart Options
- selinux , Kickstart Options
- services , Kickstart Options
- shutdown , Kickstart Options
- skipx , Kickstart Options
- text , Kickstart Options
- timezone , Kickstart Options
- upgrade , Kickstart Options
- user , Kickstart Options
- vnc , Kickstart Options
- volgroup , Kickstart Options
- what it looks like, Creating the Kickstart File
- xconfig , Kickstart Options
- zerombr , Kickstart Options
- zfcp , Kickstart Options
- kickstart installations, Kickstart Installations
- CD-ROM-based, Creating Kickstart Boot Media
- diskette-based, Creating Kickstart Boot Media
- file format, Creating the Kickstart File
- file locations, Making the Kickstart File Available
- flash-based, Creating Kickstart Boot Media
- installation tree, Making the Installation Tree Available
- LVM, Kickstart Options
- network-based, Making the Kickstart File Available on the Network, Making the Installation Tree Available
- starting, Starting a Kickstart Installation
- from a boot CD-ROM, Starting a Kickstart Installation
- from CD-ROM #1 with a diskette, Starting a Kickstart Installation
L
- language
- selecting, Language Selection, Language Selection, Language Selection
- LILO, The Boot Loader
- (see also boot loaders)
- role in boot process, The Boot Loader
- LOADLIN, Alternative Boot Loaders
- LPAR
- installing
- common steps, Installing in an LPAR (Common Steps)
- using the LPAR CD, Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD
- without the Red Hat Enterprise Linux for IBM System z CD-ROMs, Installing in an LPAR without the Red Hat Enterprise Linux for System z CD-ROMs
- LS-120 boot diskette
- creating from boot image file, Booting the Installation Program from an LS-120 Diskette
- LS-120 boot.img , Booting the Installation Program from an LS-120 Diskette
- LVM
- with kickstart, Kickstart Options
M
- Master Boot Record, Unable to Boot into Red Hat Enterprise Linux (see MBR)
- reinstalling, Reinstalling the Boot Loader
- MBR
- definition of, A Detailed Look at the Boot Process, The BIOS
- (see also boot loaders)
- (see also boot process)
- installing boot loader on, Advanced Boot Loader Configuration
- mdadm
- RAID-based and multipath storage configuration, Using mdadm to Configure RAID-Based and Multipath Storage
- mount points
- partitions and, Disk Partitions and Mount Points
N
- network
- configuration, Network Configuration, Network Configuration, Network Configuration
- installations
- Network Booting Tool
- pxeboot , Command Line Configuration
- pxeos , Command Line Configuration
- network device (IBM System z)
- adding, Adding a Network Device
- network devices
- adding, quick reference, Quick Reference for Adding Network Devices
- LCS device driver, Working With the LCS Device Driver
- QETH device driver, Working With the QETH Device Driver
- network installation
- NFS
- ntsysv , Runlevel Utilities
- (see also services)
O
- OS/2 boot manager, Advanced Boot Loader Configuration
- OS/400, Boot Loaders and System Architecture
- (see also boot loaders)
P
- packages
- parameter files
- ctc sample, Sample Parameter Files
- minimal configuration, Sample Parameter Files
- optional parameters, Sample Parameter Files
- required parameters, Sample Parameter Files
- required parameters for networking, Sample Parameter Files
- samples, Sample Parameter Files
- parted partitioning utility, Create new partition(s)
- partition
- Partition Magic, Alternative Boot Loaders
- partitioning, Partitioning Your System, Partitioning Your System, Partitioning Your System
- automatic, Create Default Layout, Create Default Layout, Create Default Layout
- basic concepts, An Introduction to Disk Partitions
- creating new, Adding Partitions, Adding Partitions
- file system type, File System Types, File System Types
- deleting, Deleting a Partition
- destructive, Using Free Space from an Active Partition
- editing, Editing Partitions, Editing Partitions, Editing Partitions
- extended partitions, Partitions within Partitions — An Overview of Extended Partitions
- how many partitions, Partitions: Turning One Drive Into Many, How Many Partitions?
- introduction to, Partitions: Turning One Drive Into Many
- making room for partitions, Making Room For Red Hat Enterprise Linux
- mount points and, Disk Partitions and Mount Points
- naming partitions, Partition Naming Scheme
- non-destructive, Using Free Space from an Active Partition
- numbering partitions, Partition Naming Scheme
- other operating systems, Disk Partitions and Other Operating Systems
- primary partitions, Partitions: Turning One Drive Into Many
- recommended, Recommended Partitioning Scheme, Recommended Partitioning Scheme
- types of partitions, Partitions: Turning One Drive Into Many
- using free space, Using Unpartitioned Free Space
- using in-use partition, Using Free Space from an Active Partition
- using unused partition, Using Space from an Unused Partition
- password
- boot loader, x86, AMD64, and Intel® 64 Boot Loader Configuration
- setting root, Set Root Password, Set Root Password, Set Root Password
- post-installation setup, Itanium Systems — Booting Your Machine and Post-Installation Setup
- POWER systems rescue mode, Rescue Mode on POWER Systems
- accessing SCSI utilities, Special Considerations for Accessing the SCSI Utilities from Rescue Mode
- Pre-Execution Environment, PXE Network Installations
- programs
- running at boot time, Running Additional Programs at Boot Time
- PXE, PXE Network Installations
- PXE installations, PXE Network Installations
- adding hosts, Adding PXE Hosts
- boot message, custom, Adding a Custom Boot Message
- configuration, PXE Boot Configuration
- DHCP configuration, Configuring the DHCP Server
- overview, PXE Network Installations
- performing, Performing the PXE Installation
- setting up the network server, Setting up the Network Server
- pxeboot , Command Line Configuration
- pxeos , Command Line Configuration
R
- RAID
- kickstart installations, Kickstart Options
- system unbootable after disk failure, Installing GRUB
- RAID-based and multipath storage configuration, Using mdadm to Configure RAID-Based and Multipath Storage
- rc.local
- modifying, Running Additional Programs at Boot Time
- rc.serial , Running Additional Programs at Boot Time
- (see also setserial command)
- re-installation, Determining Whether to Upgrade or Re-Install
- registering your subscription, Registering the System
- removing
- Red Hat Enterprise Linux, Removing Red Hat Enterprise Linux
- rescue mode, Rescue Mode
- definition of, Booting into Rescue Mode
- utilities available, Booting into Rescue Mode
- rescue mode, POWER systems, Rescue Mode on POWER Systems
- accessing SCSI utilities, Special Considerations for Accessing the SCSI Utilities from Rescue Mode
- root / partition
- recommended partitioning, Recommended Partitioning Scheme, Recommended Partitioning Scheme
- root password, Set Root Password, Set Root Password, Set Root Password
- runlevel 1, Booting into Single-User Mode
- runlevels (see init command)
- changing with GRUB, GRUB Interfaces
- configuration of, Runlevel Utilities
- (see also services)
S
- screenshots
- during installation, Screenshots during installation
- SCSI-over-fiber driver (zFCP), Using the zFCP Driver
- selecting
- serial ports (see setserial command)
- services
- configuring with chkconfig , Runlevel Utilities
- configuring with ntsysv , Runlevel Utilities
- configuring with Services Configuration Tool , Runlevel Utilities
- Services Configuration Tool , Runlevel Utilities
- (see also services)
- setserial command
- configuring, Running Additional Programs at Boot Time
- Setup Agent
- via Kickstart, Kickstart Options
- shutdown, Shutting Down
- (see also halt)
- single-user mode, Booting into Single-User Mode
- SMP motherboards
- starting
- startup.nsh , Using a Startup Script
- steps
- disk space, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?, Do You Have Enough Disk Space?
- eServer System i hardware preparation, Preparation for IBM eServer System p and System i
- eServer System p hardware preparation, Preparation for IBM eServer System p and System i
- hardware compatibility, Is Your Hardware Compatible?
- installing with CD-ROM or DVD, Can You Install Using the CD-ROM or DVD?, Can You Install Using the CD-ROM or DVD?
- steps to get you started, Pre-Installation
- subscription registration, Registering the System
- subscription service, Registering the System
- swap file
- swap partition
- recommended partitioning, Recommended Partitioning Scheme, Recommended Partitioning Scheme
- sysfs file system, The sysfs File System
- SYSLINUX, Alternative Boot Loaders
- System Commander, Alternative Boot Loaders
- System Partition, Itanium Systems — EFI System Partition
- system recovery, Basic System Recovery
- common problems, Common Problems
- forgetting the root password, Root Password
- hardware/software problems, Hardware/Software Problems
- reinstalling the boot loader, Reinstalling the Boot Loader
- unable to boot into Red Hat Enterprise Linux, Unable to Boot into Red Hat Enterprise Linux
- system-config-kickstart (see Kickstart Configurator )
- SysV init (see init command)
T
- tables
- reference, System Specifications List
- TCP/IP configuration, Performing a Network Installation, Performing a Network Installation
- tftp , PXE Network Installations, Starting the tftp Server
- time zone
- configuration, Time Zone Configuration, Time Zone Configuration, Time Zone Configuration
- traceback messages
- saving traceback messages without a floppy drive, Saving Traceback Messages Without a Diskette Drive, Saving Traceback Messages Without a Diskette Drive
- troubleshooting, Troubleshooting Installation on an Intel® or AMD System, Troubleshooting Installation on an IBM POWER System, Troubleshooting Installation on an IBM System z System
- after the installation, Problems After Installation, Problems After Installation, Problems After Installation
- Apache-based httpd service hangs during startup, Apache-based httpd service/Sendmail Hangs During Startup, Apache-based httpd service/Sendmail Hangs During Startup, Apache-based httpd service/Sendmail Hangs During Startup
- booting into a graphical environment, Booting into a Graphical Environment, Booting into a Graphical Environment
- booting into GNOME or KDE, Booting into a Graphical Environment, Booting into a Graphical Environment
- booting into the X Window System, Booting into a Graphical Environment, Booting into a Graphical Environment
- graphical GRUB screen, Trouble With the Graphical GRUB Screen on an x86-based System?
- graphical login, Remote Graphical Desktops and XDMCP
- logging in, Problems When You Try to Log In, Problems When You Try to Log In, Problems When You Try to Log In
- printers, Your Printer Does Not Work, Your Printer Does Not Work, Your Printer Does Not Work
- RAM not recognized, Is Your RAM Not Being Recognized?
- Sendmail hangs during startup, Apache-based httpd service/Sendmail Hangs During Startup, Apache-based httpd service/Sendmail Hangs During Startup, Apache-based httpd service/Sendmail Hangs During Startup
- sound configuration, Problems with Sound Configuration
- X (X Window System), Problems with the X Window System (GUI), Problems with the X Window System (GUI)
- X server crashes, Problems with the X Server Crashing and Non-Root Users, Problems with the X Server Crashing and Non-Root Users
- beginning the installation, Trouble Beginning the Installation, Trouble Beginning the Installation
- frame buffer, disabling, Problems with Booting into the Graphical Installation, Problems with Booting into the Graphical Installation
- GUI installation method unavailable, Problems with Booting into the Graphical Installation, Problems with Booting into the Graphical Installation
- booting, You are Unable to Boot Red Hat Enterprise Linux, You are Unable to Boot Red Hat Enterprise Linux, You are Unable to Boot Red Hat Enterprise Linux
- CD-ROM failure
- during the installation, Trouble During the Installation, Trouble During the Installation, Trouble During the Installation
- completing partitions, Other Partitioning Problems, Other Partitioning Problems for Itanium System Users, Other Partitioning Problems for IBM™ POWER System Users , Other Partitioning Problems
- No devices found to install Red Hat Enterprise Linux error message, No devices found to install Red Hat Enterprise Linux Error Message, No devices found to install Red Hat Enterprise Linux Error Message, No devices found to install Red Hat Enterprise Linux Error Message
- partition tables, Trouble with Partition Tables, Trouble with Partition Tables, Trouble with Partition Tables
- Python errors, Are You Seeing Python Errors?, Are You Seeing Python Errors?, Are You Seeing Python Errors?
- saving traceback messages without a diskette drive, Saving Traceback Messages Without a Diskette Drive, Saving Traceback Messages Without a Diskette Drive
- using remaining hard drive space, Using Remaining Space
U
- uninstalling, Removing Red Hat Enterprise Linux, Removing Red Hat Enterprise Linux
- unregister, Registering the System
- upgrade, Determining Whether to Upgrade or Re-Install
- adding a swap file, Determining Whether to Upgrade or Re-Install
- USB pen drive
- boot methods, Alternative Boot Methods
- user interface, graphical
- user interface, text mode
V
- virtual consoles, A Note about Virtual Consoles, A Note about Linux Virtual Consoles
- VM (see z/VM)
- VNC, Installation using VNC
X
- x11 forwarding, Installation using X11 Forwarding
- XDMCP, Remote Graphical Desktops and XDMCP
Y
- YABOOT, Boot Loaders and System Architecture
- (see also boot loaders)
Z
- z/IPL, Boot Loaders and System Architecture
- (see also boot loaders)
- z/VM
- installing, Installing under z/VM
- zFCP driver, Using the zFCP Driver