Red Hat Enterprise Linux 5.0.
Red Hat Enterprise Linux 5.0.0: Red Hat Enterprise Linux Installation Guide Copyright © 2007 Red Hat, Inc. This Installation Guide documents relevant information regarding the installation of Red Hat Enterprise Linux 5.0.0. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park, NC 27709 USA Documentation-Deployment Copyright © 2007 by Red Hat, Inc.
Table of Contents Introduction .............................................................................................................. xii 1. Architecture-specific Information .................................................................... xii 2. Document Conventions ................................................................................. xii 3. More to Come ............................................................................................... xv 3.1. Send in Your Feedback ....
Red Hat Enterprise Linux 5.0.0 14. Enter the Installation Number ...............................................................30 15. Disk Partitioning Setup ........................................................................31 16. Advanced Storage Options ..................................................................33 17. Create Default Layout ..........................................................................34 18. Partitioning Your System ................................................
Red Hat Enterprise Linux 5.0.0 4.5. Problems When You Try to Log In ...............................................69 4.6. Is Your RAM Not Being Recognized? ..........................................69 4.7. Your Printer Does Not Work ........................................................70 4.8. Problems with Sound Configuration .............................................70 4.9. Apache-based httpd service/Sendmail Hangs During Startup ........71 7. Driver Media for Intel and AMD Systems .................
Red Hat Enterprise Linux 5.0.0 5.1. Using the Keyboard to Navigate ................................................102 6. Beginning Installation ..........................................................................102 6.1. Installing from DVD/CD-ROM ....................................................102 7. Installing from a Hard Drive .................................................................103 8. Performing a Network Installation .........................................................104 9.
Red Hat Enterprise Linux 5.0.0 4.3. Problems with the X Window System (GUI) ................................139 4.4. Problems with the X Server Crashing and Non-Root Users .........139 4.5. Problems When You Try to Log In .............................................140 4.6. Your Printer Does Not Work ......................................................140 4.7. Apache-based httpd service/Sendmail Hangs During Startup ......140 15. Additional Boot Options for IBM Power Systems .............................
Red Hat Enterprise Linux 5.0.0 19.1. Preparing to Install .................................................................182 20. Installing Packages ...........................................................................183 21. Installation Complete .........................................................................183 18. Removing Red Hat Enterprise Linux ...........................................................185 19. Sample Parameter Files ...................................................
Red Hat Enterprise Linux 5.0.0 1.7. Disk Partitions and Mount Points ...............................................232 1.8. How Many Partitions? ...............................................................233 V. Basic System Recovery ......................................................................................234 26. Basic System Recovery .............................................................................235 1. Common Problems ..........................................................
Red Hat Enterprise Linux 5.0.0 11.2. Use an Interpreter ..................................................................296 12. Saving the File ..................................................................................296 30. Boot Process, Init, and Shutdown ...............................................................298 1. The Boot Process ...............................................................................298 2. A Detailed Look at the Boot Process ..................................
Introduction Welcome to the Red Hat Enterprise Linux Installation Guide . HTML and PDF versions of the guides are available online at http://www.redhat.com/docs/. Note Although this manual reflects the most current information possible, read the Red Hat Enterprise Linux Release Notes for information that may not have been available prior to the documentation being finalized. The Release Notes can be found on the Red Hat Enterprise Linux CD #1, online at http://www.redhat.
2. Document Conventions Use the cat testfile command to view the contents of a file, named testfile, in the current working directory. file name File names, directory names, paths, and RPM package names are represented this way. This style indicates that a particular file or directory exists with that name on your system. Examples: The .bashrc file in your home directory contains bash shell definitions and aliases for your own use.
2. Document Conventions button on a GUI screen or window This style indicates that the text can be found on a clickable button on a GUI screen. For example: Click on the Back button to return to the webpage you last viewed. computer output Text in this style indicates text displayed to a shell prompt such as error messages and responses to commands. For example: The ls command displays the contents of a directory. For example: Desktop about.html logs paulwesterberg.
3. More to Come Tip The directory /usr/share/doc/ contains additional documentation for packages installed on your system. Important If you modify the DHCP configuration file, the changes do not take effect until you restart the DHCP daemon. Caution Do not perform routine tasks as root — use a regular user account unless you need to use the root account for system administration tasks. Warning Be careful to remove only the necessary partitions.
4. Where to Find Other Manuals In addition to this manual, which covers installation, the Red Hat Enterprise Linux Deployment Guide contains further information on system administration and security. HTML and PDF versions of the guides are available online at http://www.redhat.com/docs/. Note Although this manual reflects the most current information possible, read the Red Hat Enterprise Linux Release Notes for information that may not have been available prior to the documentation being finalized.
Part I. x86, AMD64, Intel 64 and Itanium- Installation and Booting The Red Hat Enterprise Linux Installation Guide for Intel and AMD 32-bit and 64-bit systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Chapter 1. Itanium System Specific Information 1. Itanium System Installation Overview Installing Red Hat Enterprise Linux on an Itanium system is different from installing Red Hat Enterprise Linux on an x86-based system. In general, the sequence of steps to a successful installation are the following: 1. Boot into the Extensible Firmware Interface (EFI) Shell. 2. If you cannot boot from the CD-ROM, make an LS-120 diskette from the boot image file provided with Red Hat Enterprise Linux. 3.
2.2. Itanium Systems — EFI System Partition 4. SCSI hard drives on the SCSI interface 5. CD-ROM drives on the IDE interface 6. CD-ROM drives on the SCSI interface To view the results of this system poll, type the following command at the EFI Shell prompt: map The output is listed in the order the system was probed. So, all FAT16 file systems are listed first, then IDE hard drives, then SCSI hard drives, then IDE CD-ROM drives, and finally SCSI CD-ROM drives.
Chapter 2. Steps to Get You Started 1. Upgrade or Install? For information to help you determine whether to perform an upgrade or an installation refer to Chapter 23, Upgrading Your Current System. 2. Is Your Hardware Compatible? Hardware compatibility is particularly important if you have an older system or a system that you built yourself. Red Hat Enterprise Linux 5 should be compatible with most hardware in systems that were factory built within the last two years.
4.1. Alternative Boot Methods DVD? There are several methods that can be used to install Red Hat Enterprise Linux. Installing from a CD-ROM or DVD requires that you have purchased a Red Hat Enterprise Linux product, you have a Red Hat Enterprise Linux 5.0.0 CD-ROM or DVD, and you have a DVD/ CD-ROM drive on a system that supports booting from it. Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more information about changing your BIOS, refer to Section 3.
5. Preparing for a Network Installation 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 The above command was split into two lines for printing purposes only. When you execute this command, be sure to type it as a single command, all on the same line. Burn the resulting ISO image (named file.iso and located in ) to a CDROM as you normally would. 5.
5.1. Preparing for FTP and HTTP installation Note In the following examples, the directory on the installation staging server that will contain the installation files will be specified as /location/of/disk/space. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as /export/directory. For example, /location/of/disk/space may be a directory you create called /var/isos. /export/directory might be /var/www/html/rhel5, for an HTTP install.
6. Preparing for a Hard Drive Installation 5.2. Preparing for an NFS install For NFS installation it is not necessary to mount the iso image. It is sufficient to make the iso image itself available via NFS. You can do this by moving the iso image or images to the NFS exported directory: • For DVD: mv /location/of/disk/space/RHEL5.iso /export/directory/ • For CDROMs: mv /location/of/disk/space/disk*.
6. Preparing for a Hard Drive Installation 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.
Chapter 3. System Requirements Table The most recent list of supported hardware can be found at http://hardware.redhat.com/hcl/. This system requirements table will help you keep a record of your current system settings and requirements. Enter information about your system in the table provided as a handy reference to help make your Red Hat Enterprise Linux installation go more smoothly.
el, and manufacturer specifications; ex: Optiquest Q53, ViewSonic G773 video card: make, model number and size of VRAM; ex: Creative Labs Graphics Blaster 3D, 8MB sound card: make, chipset and model number; ex: 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; ex: example.
Chapter 4. Installing on Intel® and AMD Systems This chapter explains how to perform a Red Hat Enterprise Linux installation from the DVD/ CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed: • 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 1.
1.1. A Note about Virtual Consoles able during a text mode installation. Users who must use the text mode installation program can follow the GUI installation instructions and obtain all needed information. Note If you are using an Itanium system, and you do not wish to use the GUI installation program, the text mode installation program is also available. To start the text mode installation program, type the following command at the EFI Shell prompt: elilo linux text 1.1.
2. The Text Mode Installation Program User Interface 2. The Text Mode Installation Program User Interface The Red Hat Enterprise Linux text mode installation program uses a screen-based interface that includes most of the on-screen widgets commonly found on graphical user interfaces. Figure 4.1, “Installation Program Widgets as seen in Boot Loader Configuration”, and Figure 4.2, “Installation Program Widgets as seen in Disk Druid”, illustrate the screens that appear during the installation process.
2. The Text Mode Installation Program User Interface Figure 4.2. Installation Program Widgets as seen in Disk Druid Here is a list of the most important widgets shown in Figure 4.1, “Installation Program Widgets as seen in Boot Loader Configuration” and 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.
2.1. Using the Keyboard to Navigate • 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.
3.1. Booting the Installation Program on x86, AMD64, and Intel® 64 Systems Intel® 64 Systems You can boot the installation program using any one of the following media (depending upon what your system can support): • 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.
3.2. Booting the Installation Program on Itanium Systems keys. • If you press a help screen function key, there is a slight delay while the help screen is read from the boot media. Normally, you only need to press Enter to boot. Be sure to watch the boot messages to review if the Linux kernel detects your hardware. If your hardware is properly detected, continue to the next section.
3.3. Additional Boot Options If you are using the CD-ROM to load the installation program, follow the instructions contained in Chapter 4, Installing on Intel and AMD Systems. To boot from an LS-120 diskette follow these steps: 1. 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.
3.3. Additional Boot Options The installation program prompts you to insert a CD or select an ISO image to test, and select OK to 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.
4. Selecting an Installation Method For more information on kernel options refer to Chapter 8, Additional Boot Options for Intel and AMD Systems. 4. Selecting an Installation Method What type of installation method do you wish to use? The following installation methods are available: 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 5, “Installing from DVD/CD-ROM”, for DVD/CD-ROM installation instructions.
5.1. What If the IDE CD-ROM Was Not Found? the boot media. You can safely cancel the installation at any point before the About to Install screen. Refer to Section 24, “Preparing to Install” for more information. If your CD-ROM drive is not detected, and it is a SCSI CD-ROM, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter.
7. Performing a Network Installation Figure 4.3. Selecting Partition Dialog for Hard Drive Installation Enter the device name of the partition containing the Red Hat Enterprise Linux ISO images. This partition must be formatted with a ext2 or vfat filesystem, and cannot be a logical volume. There is also a field labeled Directory holding images. If the ISO images are in the root (top-level) directory of a partition, enter a /.
8. Installing via NFS Figure 4.4. TCP/IP Configuration 8. Installing via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected NFS Image in the Installation Method dialog). Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field. Next, enter the name of the exported directory.
9. Installing via FTP Figure 4.5. NFS Setup Dialog If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 9. Installing via FTP The FTP dialog applies only if you are installing from an FTP server (if you selected FTP in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux.
10. Installing via HTTP Figure 4.6. FTP Setup Dialog Enter the name or IP address of the FTP site you are installing from, and the name of the directory containing the variant/ directory for your architecture.
11. Welcome to Red Hat Enterprise Linux from which you are installing Red Hat Enterprise Linux. Enter the name or IP address of the HTTP site you are installing from, and the name of the directory containing the variant/ directory for your architecture.
12. Language Selection Release Notes for Red Hat Enterprise Linux 5.0.0 by clicking on the Release Notes button. Click on the Next button to continue. 12. Language Selection Using your mouse, select a language to use for the installation (refer to Figure 4.8, “Language Selection”). The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation.
13. Keyboard Configuration Figure 4.8. Language Selection Once you select the appropriate language, click Next to continue. 13. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below). Once you have made your selection, click Next to continue.
14. Enter the Installation Number Figure 4.9. Keyboard Configuration Tip To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool. Type the 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. 14. Enter the Installation Number Enter your Installation Number (refer to Figure 4.10, “Installation Number”).
15. Disk Partitioning Setup Figure 4.10. Installation Number 15. Disk Partitioning Setup Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not sure how you want your system to be partitioned, read Chapter 25, An Introduction to Disk Partitions for more information.
15. Disk Partitioning Setup Warning The Update Agent downloads updated packages to /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 If you choose to create a custom layout using Disk Druid, refer to Section 18, “Partitioning Your System”.
16. Advanced Storage Options gram. Users who have used programs such as EZ-BIOS have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began). No matter what type of installation you are performing, backups of the existing data on your systems should always be made. 16. Advanced Storage Options Figure 4.12.
17. Create Default Layout Figure 4.13. Configure ISCSI Parameters Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation. 17. Create Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
17. Create Default Layout • 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.14. Create Default Layout Using your mouse, choose the storage drive(s) on which you want Red Hat Enterprise Linux to be installed. If you have two or more drives, you can choose which drive(s) should contain this installation.
18. Partitioning Your System 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. An internal hard drive is necessary to use for partition creation with problematic RAID cards. A /boot/ partition is also necessary for software RAID setups. If you have chosen to automatically partition your system, you should select Review and manually edit your /boot/ partition.
18.1. Graphical Display of Hard Drive(s) type FAT (VFAT), a swap partition of at least 512 MB, and an appropriately-sized root (/) partition. Figure 4.15. Partitioning with Disk Druid on x86, AMD64, and Intel® 64 Systems The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation. 18.1.
18.3. Partition Fields These buttons control Disk Druid's actions. They are used to change the attributes of a partition (for example the file system type and mount point) and also to create RAID devices. Buttons on this screen are also used to accept the changes you have made, or to exit Disk Druid. For further explanation, take a look at each button in order: • New: Used to request a new partition.
18.4. Recommended Partitioning Scheme • 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 Edit button. • Type: This field shows the partition's file system type (for example, ext2, ext3, or vfat).
18.4. Recommended Partitioning Scheme Swap should equal 2x physical RAM for up to 2 GB of physical RAM, and then an additional 1x physical RAM for any amount above 2 GB, but never less than 32 MB. So, if: M = Amount of RAM in GB, and S = Amount of swap in GB, then If M < 2 S = M *2 Else S = M + 2 Using this formula, a system with 2 GB of physical RAM would have 4 GB of swap, while one with 3 GB of physical RAM would have 5 GB of swap.
18.5. Adding Partitions If M < 2 S = M *2 Else S = M + 2 Using this formula, a system with 2 GB of physical RAM would have 4 GB of swap, while one with 3 GB of physical RAM would have 5 GB of swap. Creating a large swap space partition can be especially helpful if you plan to upgrade your RAM at a later time. For systems with really large amounts of RAM (more than 32 GB) you can likely get away with a smaller swap partition (around 1x, or less, of physical RAM).
18.5. Adding Partitions For more information, refer to Chapter 25, An Introduction to Disk Partitions. Figure 4.16. 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.
18.6. Editing Partitions 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.
18.7. Deleting a Partition To edit a partition, select the Edit button or double-click on the existing partition. Note If the partition already exists on your disk, you can only change the partition's mount point. To make any other changes, you must delete the partition and recreate it. 18.7. Deleting a Partition To delete a partition, highlight it in the Partitions section and click the Delete button. Confirm the deletion when prompted.
19. x86, AMD64, and Intel® 64 Boot Loader Configuration Figure 4.17. Boot Loader Configuration If you do not want to install GRUB as your boot loader, click Change boot loader, where you can choose not to install a boot loader at all. If you already have a boot loader that can boot Red Hat Enterprise Linux and do not want to overwrite your current boot loader, choose Do not install a boot loader by clicking on the Change boot loader button.
19.1. Advanced Boot Loader Configuration not move forward in the installation unless you choose a default boot image. Note The Label column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system. Once you have loaded the GRUB boot screen, use the arrow keys to choose a boot label or type e for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
19.1. Advanced Boot Loader Configuration Figure 4.18. Boot Loader Installation Tip 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 loader should not be installed on the MBR of the RAID array. Rather, the boot loader should be installed on the MBR of the same drive as the /boot/ partition was created. If your system only uses Red Hat Enterprise Linux, you should choose the MBR.
19.2. Rescue Mode Tip While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the /boot Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024. In parted, 1024 cylinders equals 528MB. For more information, refer to: http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.
19.4. SMP Motherboards and GRUB and 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 Boot loaders such as LOADLIN and System Commander are considered to be third-party boot loaders and are not supported by Red Hat. 19.4.
20. Network Configuration Figure 4.19. Network Configuration The installation program automatically detects any network devices you have and displays them in the Network Devices list. Once you have selected a network device, click Edit. From the Edit Interface pop-up screen, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device via DHCP (or manually if DHCP is not selected) and you can choose to activate the device at boot time.
20. Network Configuration Figure 4.20. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
21. Time Zone Configuration Tip To change your network configuration after you have completed the installation, use the Network Administration Tool. Type the 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. 21. Time Zone Configuration Set your time zone by selecting the city closest to your computer's physical location.
22. Set Root Password Select System Clock uses UTC if you know that your system is set to UTC. Tip To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool. Type the 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. To run the Time and Date Properties Tool as a text-based application, use the command timeconfig. 22.
22. Set Root Password Figure 4.22. Root Password Use the root account only for system administration. Create a non-root account for your general use and 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. Tip To become root, type su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
23. Package Group Selection 123456, and anteater are all examples of bad passwords. Good passwords mix numerals with upper and lower case letters and do not contain dictionary words: Aard387vark or 420BMttNT, for example. Remember that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create. Note Do not use one of the example passwords offered in this manual.
23. Package Group Selection To select a component, click on the checkbox beside it (refer to Figure 4.23, “Package Group Selection”). Figure 4.23. Package Group Selection Select each component you wish to install. Once a package group has been selected, if optional components are available you can click on Optional packages to view which packages are installed by default, and to add or remove optional packages from that group. If there are no optional components this button will be disabled.
24. Preparing to Install Figure 4.24. Package Group Details 24. Preparing to Install 24.1. Prepare to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system. Warning If, for some reason, you would rather not continue with the installation process, this is your last opportunity to safely cancel the process and reboot your machine.
26. Installation Complete 25. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. 26. Installation Complete Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot.
27.1. Post-Installation Boot Loader Options After you type 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.) If you want to load a different kernel, type the label name of the kernel from the file / boot/efi/elilo.conf after the elilo command. For example, to load the kernel named linux, type: elilo linux If you do not know the names of the installed kernels, you can view the /boot/efi/elilo.
27.2. Booting Red Hat Enterprise Linux Automatically 5. At the Enter New Description: prompt, type Red Hat Enterprise you want to appear on the EFI Boot Manager menu. 6. At the Enter Boot Option Data Type: prompt, enter N for No Boot Option 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. 7.
Chapter 5. Removing Red Hat Enterprise Linux To uninstall Red Hat Enterprise Linux from your x86-based system, you must remove the Red Hat Enterprise Linux boot loader information from your master boot record (MBR). Note It is always a good idea to backup any data that you have on your system(s). Mistakes do happen and can result in the loss all of your data. In DOS and Windows, use the Windows fdisk utility to create a new MBR with the undocumented flag /mbr.
To remove partitions, use the partitioning utility parted. Start parted, where /dev/hda is the device on which to remove the partition: parted /dev/hda Using the print command, view the current partition table to determine the minor number of the partition to remove: print The 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. Remove the partition with the command rm.
Chapter 6. Troubleshooting Installation on an Intel® or AMD System This appendix discusses some common installation problems and their solutions. 1. You are Unable to Boot Red Hat Enterprise Linux 1.1. Are You Unable to Boot With Your RAID Card? If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently. Some BIOSes do not support booting from RAID cards.
2. Trouble Beginning the Installation Another option is to perform a media check on your installation CD-ROMs. The Red Hat Enterprise Linux installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods.
3.2. Saving Traceback Messages Without a Diskette Drive You can also refer to the Red Hat Hardware Compatibility List, available online at: http://hardware.redhat.com/hcl/ 3.2. Saving Traceback Messages Without a Diskette Drive If you receive a traceback error message during installation, you can usually save it to a diskette. If you do not have a diskette drive available in your system, you can scp the error message to a remote system.
3.6. Other Partitioning Problems for Itanium System Users • A partition of type swap Tip When defining a partition's type as swap, do not assign it a mount point. Disk Druid automatically assigns the mount point for you. 3.6. Other Partitioning Problems for Itanium System Users If you are using Disk Druid to create partitions, but cannot move to the next screen, you probably have not created all the partitions necessary for Disk Druid's dependencies to be satisfied.
4. Problems After Installation process, so the installation program cannot write information and fails. If you experience such an error, first try to download any available errata for anaconda. Errata can be found at: http://www.redhat.com/support/errata/ The anaconda website may also be a useful reference and can be found online at: http://rhlinux.redhat.com/anaconda/ You can also search for bug reports related to this problem. To search Red Hat's bug tracking system, go to: http://bugzilla.redhat.
4.3. Problems with the X Window System (GUI) /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. Open a shell prompt. If you are in your user account, become root by typing the su command. Now, type gedit /etc/inittab to edit the file with gedit. The file /etc/inittab opens.
4.5. Problems When You Try to Log In To verify that this is the problem you are experiencing, run the following command: df -h The 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. A key indicator is 100% full or a percentage above 90% or 95% on a partition.
4.7. Your Printer Does Not Work the cat /proc/meminfo command. Verify that the displayed quantity is the same as the known amount of RAM in your system. If they are not equal, add the following line to the /boot/grub/grub.conf: mem=xxM Replace xx with the amount of RAM you have in megabytes. In /boot/grub/grub.conf, the above example would look similar to the following: # NOTICE: You have a /boot partition.
4.9. Apache-based httpd service/Sendmail Hangs During Startup tion => Soundcard Detection in GNOME, or Main Menu => Administration => Soundcard Detection in KDE. A small text box pops up prompting you for your root password. You can also type the 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. Driver Media for Intel® and AMD Systems 1. Why Do I Need Driver Media? While the Red Hat Enterprise Linux installation program is loading, a screen may appear asking you for driver media.
3.1. Creating a Driver Diskette from an Image File (including images/drvnet.img — network card drivers and images/drvblock.img — drivers for SCSI controllers) containing many drivers (both common and obscure). Tip It is also possible to use a driver image via a network file. Instead of using the linux dd boot command, use the linux dd=url command, where url is replaced by an HTTP, FTP, or NFS address of the driver image to be used.
4. Using a Driver Image During Installation For example, to specifically load a driver diskette that you have created, begin the installation process by booting from the Red Hat Enterprise Linux CD #1 (or using boot media you have created). For x86-based systems, at the boot: prompt, enter linux dd if using an x86 or x86-64 system. Refer to Section 3.1, “Booting the Installation Program on x86, AMD64, and Intel 64 Systems” for details on booting the installation program.
Chapter 8. Additional Boot Options for Intel® and AMD Systems This appendix discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. To use any of the boot options presented here, type the command you wish to invoke at the installation 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.
the original display. Using the command xhost +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.
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.
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.
Chapter 9. The GRUB Boot Loader When a computer with Red Hat Enterprise Linux is turned on, the operating system is loaded into memory by a special program called a boot loader. A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory. 1.
2.2. Features of GRUB able of loading either the Stage 1.5 or Stage 2 boot loader. 2. 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. 3.
3. Installing GRUB 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.
4.2. File Names and Blocklists When referring to a specific device with GRUB, do so using the following format (note that the parentheses and comma are very important syntactically): (,) The specifies the type of device from which GRUB boots. The two most common options are 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.
4.3. The Root File System and GRUB The following illustrates the structure of such a command: (,) In this example, replace with hd, fd, or nd. Replace with the integer for the device. Replace with an absolute path relative to the top-level of the device.
5. GRUB Interfaces terfaces allows users to boot the Linux kernel or another operating system. The interfaces are as follows: Note The following GRUB interfaces can only be accessed by pressing any key within the three seconds of the GRUB menu bypass screen. 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.
5.1. Interfaces Load Order Refer to Section 6, “GRUB Commands” for a list of common commands. 5.1. Interfaces Load Order When GRUB loads its second stage boot loader, it first searches for its configuration file. Once found, the menu interface bypass screen is displayed. If a key is pressed within three seconds, GRUB builds a menu list and displays the menu interface. If no key is pressed, the default kernel entry in the GRUB menu is used.
7. GRUB Menu Configuration File • — Specifies the disk where the stage 1 boot loader should be installed, such as (hd0). • — Passes the stage 2 boot loader location to the stage 1 boot loader, such as (hd0,0)/grub/stage2. • p — This option tells the install command to look for the menu configuration file specified by , such as (hd0,0)/grub/grub.conf. Warning The install command overwrites any information already located on the MBR. • ...
7.2. Configuration File Directives 7.1. Configuration File Structure The GRUB menu interface configuration file is /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.
8. Changing Runlevels at Boot Time the menu interface times out. • fallback= — Replace with the entry title number to try if the first attempt fails. • hiddenmenu — Prevents the GRUB menu interface from being displayed, loading the default entry when the timeout period expires. The user can see the standard GRUB menu by pressing the Esc key.
9. Additional Resources • 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 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.
Chapter 10. Additional Resources about Itanium and Linux Other reference materials, related to running Red Hat Enterprise Linux on an Itanium system, are available on the Web. A few of the available resources are as follows: • http://www.intel.com/products/processor/itanium2/ — The Intel website on the Itanium 2 Processor • http://developer.intel.com/technology/efi/index.htm?iid=sr+efi — The Intel website for the Extensible Firmware Interface (EFI) • http://www.itanium.
Part II. IBM POWER Architecture Installation and Booting The Red Hat Enterprise Linux Installation Guide for IBM POWER systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Chapter 11. Steps to Get You Started 1. Upgrade or Install? For information to help you determine whether to perform an upgrade or an installation refer to Chapter 23, Upgrading Your Current System. 2. Preparation for IBM eServer System p and System i The IBM eServer System p and IBM eServer System i systems introduce many options for partitioning, virtual or native devices, and consoles.
4. Can You Install Using the CD-ROM or DVD? Linux is no exception. When you install Red Hat Enterprise Linux, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to Chapter 25, An Introduction to Disk Partitions before proceeding. The disk space used by Red Hat Enterprise Linux must be separate from the disk space used by other OSes you may have installed on your system.
5.1. Preparing for FTP and HTTP installation rity of the installation media. It works with the CD / DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs).
5.2. Preparing for an NFS install In this case /export/directory will be a directory that is shared via FTP or HTTP. • For CDROMs: mount -o loop /location/of/disk/space/diskX.iso /export/directory/diskX/ Do the above for each of the CDROM iso images, for example: mount -o loop /var/isos/disk1.iso /var/www/html/rhel5-install/disk1/ Next make sure that the /export/directory directory is shared via FTP or HTTP, and verify client access.
6. Preparing for a Hard Drive Installation a file system other than those listed here, such as reiserfs, you will not be able to perform a hard drive installation. Hard drive installations require the use of the ISO (or DVD/CD-ROM) images. An ISO image is a file containing an exact copy of a DVD/CD-ROM image. After placing the required ISO images (the binary Red Hat Enterprise Linux DVD/CD-ROMs) in a directory, choose to install from the hard drive.
Chapter 12. Installing on IBM System i and IBM System p systems This chapter explains how to perform a Red Hat Enterprise Linux installation from the DVD/ CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed: • 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.
2. Booting the IBM System i or IBM System p Installation Program overview of text mode installation instructions. It is highly recommended that installs be performed using the GUI installation program. The GUI installation program offers the full functionality of the Red Hat Enterprise Linux installation program, including LVM configuration which is not available during a text mode installation.
3. A Note about Linux Virtual Consoles Once in the SMS menu, select the option for Select Boot Options. In that menu, specify Select Install or Boot a Device. There, select CD/DVD, and then the bus type (in most cases SCSI). If you are uncertain, you can select to view all devices. This scans all available buses for boot devices, including network adapters and hard drives. Finally, select the device containing the installation CD. YABOOT is loaded from this device and you are presented with a boot: prompt.
5. The Text Mode Installation Program User Interface The HMC vterm is the console for any partitioned IBM System p or IBM System i system. This is opened by right clicking on the partition on the HMC, and then selecting Open Terminal Window. Only a single vterm can be connected to the console at one time and there is no console access for partitioned system besides the vterm.
5. The Text Mode Installation Program User Interface Figure 12.2. Installation Program Widgets as seen in Boot Loader Configuration Figure 12.3. Installation Program Widgets as seen in Disk Druid Here is a list of the most important widgets shown in Figure 12.2, “Installation Program Widgets as seen in Boot Loader Configuration” and Figure 12.
5.1. Using the Keyboard to Navigate • 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.
7. Installing from a Hard Drive SCSI adapter automatically. If the DVD/CD-ROM drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD/CD-ROM. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support.
8. Performing a Network Installation Figure 12.4. Selecting Partition Dialog for Hard Drive Installation Enter the device name of the partition containing the Red Hat Enterprise Linux ISO images. This partition must be formatted with a ext2 or vfat filesystem, and cannot be a logical volume. There is also a field labeled Directory holding images. If the ISO images are in the root (top-level) directory of a partition, enter a /.
9. Installing via NFS Figure 12.5. TCP/IP Configuration 9. Installing via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected NFS Image in the Installation Method dialog). Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field. Next, enter the name of the exported directory.
10. Installing via FTP Figure 12.6. NFS Setup Dialog If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 10. Installing via FTP The FTP dialog applies only if you are installing from an FTP server (if you selected FTP in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux.
11. Installing via HTTP Figure 12.7. FTP Setup Dialog Enter the name or IP address of the FTP site you are installing from, and the name of the directory containing the variant/ directory for your architecture.
12. Welcome to Red Hat Enterprise Linux from which you are installing Red Hat Enterprise Linux. Enter the name or IP address of the HTTP site you are installing from, and the name of the directory containing the variant/ directory for your architecture.
13. Language Selection Release Notes for Red Hat Enterprise Linux 5.0.0 by clicking on the Release Notes button. Click on the Next button to continue. 13. Language Selection Using your mouse, select a language to use for the installation (refer to Figure 12.9, “Language Selection”). The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation.
14. Keyboard Configuration Figure 12.9. Language Selection Once you select the appropriate language, click Next to continue. 14. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to Figure 12.10, “Keyboard Configuration”). Once you have made your selection, click Next to continue.
15. Enter the Installation Number Figure 12.10. Keyboard Configuration Tip To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool. Type the 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. 15. Enter the Installation Number Enter your Installation Number (refer to Figure 12.11, “Installation Number”).
16. Disk Partitioning Setup Figure 12.11. Installation Number 16. Disk Partitioning Setup Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not sure how you want your system to be partitioned, read Chapter 25, An Introduction to Disk Partitions for more information.
17. Advanced Storage Options Warning The Update Agent downloads updated packages to /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 If you choose to create a custom layout using Disk Druid, refer to Section 19, “Partitioning Your System”.
17. Advanced Storage Options 17. Advanced Storage Options Figure 12.13. Advanced Storage Options From this screen you can choose to disable a dmraid device, in which case the individual elements of the dmraid device will appear as separate hard drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target. To configure an ISCSI target invoke the 'Configure ISCSI Parameters' dialog by selecting 'Add ISCSI target' and clicking on the 'Add Drive' button.
18. Create Default Layout Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation. 18. Create Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
18. Create Default Layout Figure 12.15. Create Default Layout Using your mouse, choose the storage drive(s) on which you want Red Hat Enterprise Linux to be installed. If you have two or more drives, you can choose which drive(s) should contain this installation. Unselected drives, and any data on them, are not touched. Caution It is always a good idea to back up any data that you have on your systems.
19. Partitioning Your System hard drive is necessary to use for partition creation with problematic RAID cards. A /boot/ partition is also necessary for software RAID setups. If you have chosen to automatically partition your system, you should select Review and manually edit your /boot/ partition. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option.
19.1. Graphical Display of Hard Drive(s) Figure 12.16. Partitioning with Disk Druid on IBM System p and System i systems The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation. 19.1. Graphical Display of Hard Drive(s) Disk Druid offers a graphical representation of your hard drive(s).
19.3. Partition Fields • New: Used to request a new partition. When selected, a dialog box appears containing fields (such as the mount point and size fields) that must be filled in. • Edit: Used to modify attributes of the partition currently selected in the Partitions section. Selecting Edit 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.
19.4. Recommended Partitioning Scheme • 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.
19.5. Adding Partitions tition 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.
19.5. Adding Partitions Figure 12.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.
19.6. Editing Partitions 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 1.
20. Network Configuration ate it. 20. Network Configuration If you do not have a network device, physical LAN, or virtual LAN, this screen does not appear during your installation and you should advance to Section 21, “Time Zone Configuration”. Figure 12.18. Network Configuration The installation program automatically detects any network devices you have and displays them in the Network Devices list. Once you have selected a network device, click Edit.
21. Time Zone Configuration Figure 12.19. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
21. Time Zone Configuration 21. Time Zone Configuration Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world. From here there are two ways for you to select your time zone: • 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.
22. Set Root Password Date Properties Tool. If you are not root, it prompts you for the root password to continue. To run the Time and Date Properties Tool as a text-based application, use the command timeconfig. 22. Set Root Password Setting up a root account and password is one of the most important steps during your installation. Your root account is similar to the administrator account used on Windows NT machines.
23. Package Group Selection Use the root account only for system administration. Create a non-root account for your general use and 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. Tip To become root, type su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter. The installation program prompts you to set a root password7 for your system.
23. Package Group Selection 23. Package Group Selection Now that you have made most of the choices for your installation, you are ready to confirm the default package selection or customize packages for your system. The Package Installation Defaults screen appears and details the default package set for your Red Hat Enterprise Linux installation. This screen varies depending on the version of Red Hat Enterprise Linux you are installing.
24. Preparing to Install Figure 12.22. Package Group Selection Select each component you wish to install. Once a package group has been selected, if optional components are available you can click on Optional packages to view which packages are installed by default, and to add or remove optional packages from that group. If there are no optional components this button will be disabled. Figure 12.23. Package Group Details 24. Preparing to Install 24.1.
25. Installing Packages Warning If, for some reason, you would rather not continue with the installation process, this is your last opportunity to safely cancel the process and reboot your machine. Once you press the Next button, partitions are written and packages are installed. If you wish to abort the installation, you should reboot now before any existing information on any hard drive is rewritten.
26. Installation Complete 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, a login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
Chapter 13. Driver Media for IBM POWER Systems 1. Why Do I Need Driver Media? While the Red Hat Enterprise Linux installation program is loading, a screen may appear asking you for driver media.
1.3. Using a Driver Image During Installation Tip It is also possible to use a driver image via a network file. Instead of using the linux dd boot command, use the linux dd=url command, where url is replaced by an HTTP, FTP, or NFS address of the driver image to be used. Another option for finding specialized driver information is on Red Hat's website at http://www.redhat.com/support/errata/ under the section called Bug Fixes.
Chapter 14. Troubleshooting Installation on an IBM POWER System This appendix discusses some common installation problems and their solutions. You may also find the IBM Online Alert Section for System p and System i useful. It is located at: http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html Please note that the url above has been split across two lines for readability. It should be entered into a browser as one continuous line, with no linebreak. 1.
2. Trouble Beginning the Installation For more information concerning signal 11 errors, refer to: http://www.bitwizard.nl/sig11/ 2. Trouble Beginning the Installation 2.1. Problems with Booting into the Graphical Installation There are some video cards that have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it tries to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode.
3.3. Trouble with Partition Tables When the traceback dialog appears, the traceback error message is automatically written to a file named /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. 3.3.
4. Problems After Installation 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:
4.3. Problems with the X Window System (GUI) To set up your system so that you can log in at a graphical login screen, you must edit one file, /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. Open a shell prompt. If you are in your user account, become root by typing the su command. Now, type gedit /etc/inittab to edit the file with gedit. The file /etc/inittab opens.
4.5. Problems When You Try to Log In If you are having trouble with the X server crashing when anyone other than root logs in, you may have a full file system (or, a lack of available hard drive space). To verify that this is the problem you are experiencing, run the following command: df -h The df command should help you diagnose which partition is full.
Chapter 15. Additional Boot Options for IBM Power Systems This appendix discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. To use any of the boot options presented here, type the command you wish to invoke at the installation 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.
chine. 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. nopass this command disables the passing of keyboard and mouse information to stage 2 of the installation program.
Part III. IBM System z Architecture Installation and Booting The Red Hat Enterprise Linux Installation Guide for IBM System z Architecture systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Chapter 16. Steps to Get You Started 1. Pre-Installation The installation process assumes a basic familiarity with the IBM eServer System z platforms. For additional information on these platforms, refer to the IBM Redbooks available online at: http://www.redbooks.ibm.com/ [http://www.redbooks.ibm.com] This manual assumes you are familiar with the related Redbooks and can set up logical partitions (LPARs) and virtual machines (VMs) on an IBM eServer System z system.
3. Basic Overview of the Boot Method System z supports QDIO-enabled (Queued Direct I/O) and LCS (LAN channel station) devices. The CTC (channel-to-channel) and IUCV (inter-user communication vehicle) are deprecated and are not supported in Red Hat Enterprise Linux. For the purposes of this installation, it is recommended that at least 4 GB of disk space (such as two 2 GB DASD, direct access storage device, partitions or equivalent IBM System z SCSI LUNs) be allocated for the installation process.
4.1. Preparing for FTP and HTTP installation an HTTP install. To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps: • Create an iso image from the installation disk(s) using the following command: • For DVD: dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso where dvd refers to your DVD drive device. • For CD-ROMs: dd if=/dev/cdrom of=/location/of/disk/space/diskX.
5. Preparing for a Hard Drive Installation mv /location/of/disk/space/RHEL5.iso /export/directory/ • For CDROMs: mv /location/of/disk/space/disk*.iso /export/directory/ Ensure that the /export/directory directory is exported via NFS via an entry in /etc/exports. To export to a specific system: /export/directory client.ip.
6. Installing under z/VM lems. To verify the ISO images are intact prior to performing an installation, use an md5sum program (many md5sum programs are available for various operating systems). An md5sum 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 called updates.
6. Installing under z/VM You may now create the parameter file (for example, redhat.parm). Refer to Chapter 19, Sample Parameter Files for sample parm files. Below is an explanation of the parm file contents. There is a limit of 32 total parameters in the parameter file. In order to accommodate limitations with parameter files, a new configuration file on a CMS DASD should be used to configure the initial network setup and the DASD specification. A .
6. Installing under z/VM Where dasd-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 the DASD= 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.
6. Installing under z/VM 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::serverN Where server1:server2::serverN is a list of DNS servers, separated by colons. For example: DNS=10.0.0.1:10.0.0.
7. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD • 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 • FCP_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. refers to the storage logical unit identifier and is specified as a hex-value (such as 0x4010).
8. Installing in an LPAR without the Red Hat Enterprise Linux for System z CD-ROMs 7. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD The following steps must be taken when installing onto an LPAR. • 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 Images, then select the LPAR to which you wish to install.
9. Installing in an LPAR (Common Steps) pub/redhat/linux/rawhide/s390x) • Click Continue. • In the dialog that follows, keep the default selection of redhat.ins and click Continue. • Refer to Section 9, “Installing in an LPAR (Common Steps)” to continue. 9. Installing in an LPAR (Common Steps) Once the installation program has started (if the red field behind the LPAR icon is disappearing, the installation program has begun), select the LPAR and double-click on Operating System Messages.
Chapter 17. Installing on IBM System z Systems This chapter explains how to perform a Red Hat Enterprise Linux installation using the graphical, mouse-based installation program. The following topics are discussed: • 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 1.
2. The Text Mode Installation Program User Interface ure 17.1, “Installation Program Widgets as seen in Boot Loader Configuration”, and Figure 17.2, “Installation Program Widgets as seen in Disk Druid”, illustrate the screens that appear during the installation process. Note While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions.
2. The Text Mode Installation Program User Interface Figure 17.2. Installation Program Widgets as seen in Disk Druid Here is a list of the most important widgets shown in Figure 17.1, “Installation Program Widgets as seen in Boot Loader Configuration” and Figure 17.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.
2.1. Using the Keyboard to Navigate • 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.
3.1. Installation using X11 Forwarding lection details and other options not available in text-based installs. It is strongly recommended to use the graphical installation whenever possible. To run the graphical installation, use a workstation that has an X Window System server or VNC client installed. Use an SSH client that allows X11 forwarding or a Telnet client. SSH is strongly recommended for its security features as well as its ability to forward X and VNC sessions.
5. Installing via NFS This partition must be formatted with a ext2 or vfat filesystem, and cannot be a logical volume. There is also a field labeled Directory holding images. If the ISO images are in the root (top-level) directory of a partition, enter a /. 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.
6. Installing via FTP If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 6. Installing via FTP The FTP dialog applies only if you are installing from an FTP server (if you selected FTP in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. Figure 17.4.
7. Installing via HTTP without copying them into a single tree by loopback mounting them. For each ISO image: mkdir discX mount -o loop RHEL5-discX.iso discX 7. Installing via HTTP The HTTP dialog applies only if you are installing from an HTTP server (if you selected HTTP in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux.
8. Welcome to Red Hat Enterprise Linux Tip You can save disk space by using the ISO images you have already copied to the server. To accomplish this, install Red Hat Enterprise Linux using ISO images without copying them into a single tree by loopback mounting them. For each ISO image: mkdir discX mount -o loop RHEL5-discX.iso discX 8. Welcome to Red Hat Enterprise Linux The Welcome screen does not prompt you for any input. From this screen you can access the Release Notes for Red Hat Enterprise Linux 5.
10. Enter the Installation Number later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. Figure 17.6. Language Selection Once you select the appropriate language, click Next to continue. 10. Enter the Installation Number Enter your Installation Number (refer to Figure 17.7, “Installation Number”). This number will determine the package selection set that is available to the installer.
11. Disk Partitioning Setup Figure 17.7. Installation Number 11. Disk Partitioning Setup Partitioning allows you to divide your storage drive(s) into isolated sections, where each section behaves as its own drive. Partitioning is particularly useful if you run multiple operating systems, or wish to enforce a logical or functional distinction between your storage partitions (such as a / home partition that persistently contains user information).
11. Disk Partitioning Setup Warning The Update Agent downloads updated packages to /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.8. Disk Partitioning Setup If you choose to create a custom layout using Disk Druid, refer to Section 14, “Partitioning Your System”.
12. Advanced Storage Options gram. No matter what type of installation you are performing, backups of the existing data on your systems should always be made. 12. Advanced Storage Options 12.1. FCP Devices FCP (Fibre Channel protocol) devices enable IBM System z to use SCSI devices rather than DASD devices. FCP (Fibre Channel protocol) devices provide a switched fabric topology that enables zSeries systems to use SCSI LUNs as disk devices in addition to traditional DASD devices.
12.1. FCP Devices Figure 17.9. Advanced Storage Options To configure a Fiber Channel Protocol SCSI device invoke the 'Add FCP device' dialog by selecting 'Add ZFCP LUN' and clicking on the 'Add Drive' button. Fill in the details for the 16 bit device number, 64 bit World Wide Port Number (WWPN) and 64 bit FCP LUN. Click the 'Add' button to attempt connection to the FCP device using this information.
12.1. FCP Devices Figure 17.10. Configure FCP Device The newly added device should then be present and usable during the Disk installation.
13. Create Default Layout Figure 17.11. Configure FCP Device Note The installer requires that at least one ECKD DASD be defined. In the situation where a SCSI-only installation is desired a DASD= parameter should be entered into the CMS conf file with a non-existent device number. This will satisfy Anaconda's requirement for a defined ECKD DASD, while resulting in a SCSI-only environment. 13.
13. Create Default Layout Caution 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).
14. Partitioning Your System Caution It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your drive(s). Mistakes do happen and can result in the loss of all your data. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option.
14.1. Graphical Display of DASD Device(s) The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation. 14.1. Graphical Display of DASD Device(s) Disk Druid offers a graphical representation of your DASD device(s). Using your mouse, click once to highlight a particular field in the graphical display.
14.4. Recommended Partitioning Scheme point. Double-click on the partition or click the Edit 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.
14.5. Editing Partitions • 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 limitations, creating a native ext3 partition to hold these files is required. For most users, a 100 MB boot partition is sufficient. 14.5. Editing Partitions To edit a partition, select the Edit button or double-click on the existing partition.
15. Network Configuration The installation program automatically detects any network devices you have and displays them in the Network Devices list. Once you have selected a network device, click Edit. From the Edit Interface pop-up screen, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device via DHCP (or manually if DHCP is not selected) and you can choose to activate the device at boot time.
16. Time Zone Configuration Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance. If you have a hostname (fully qualified domain name) for the network device, you can choose to have DHCP (Dynamic Host Configuration Protocol) automatically detect it or you can manually enter the hostname in the field provided.
17. Set Root Password Figure 17.16. Configuring the Time Zone Select System Clock uses UTC if you know that your system is set to UTC. Tip To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool. Type the 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.
17. Set Root Password Note The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done only to perform system maintenance or administration. Figure 17.17. Root Password Use the root account only for system administration. Create a non-root account for your general use and su - to root when you need to fix something quickly.
18. Package Group Selection ceed to the next stage of the installation process without entering a root password. The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again. You should make the root password something you can remember, but not something that is easy for someone else to guess.
18. Package Group Selection Note Users of IBM System z who want support for developing or running legacy 31-bit applications are encouraged to select the Compatibility Arch Support and Compatibility Arch Development Support packages to install architecture specific support for their systems. To select a component, click on the checkbox beside it (refer to Figure 17.18, “Package Group Selection”). Figure 17.18. Package Group Selection Select each component you wish to install.
19. Preparing to Install Figure 17.19. Package Group Details 19. Preparing to Install 19.1. Preparing to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system. Warning If, for some reason, you would rather not continue with the installation process, this is your last opportunity to safely cancel the process and reboot your machine.
20. Installing Packages 3270 terminal emulator. 20. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. 21. Installation Complete Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot.
21. Installation Complete 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. The first time you start your Red Hat Enterprise Linux system in a graphical environment, the Setup Agent may be manually started, which guides you through the Red Hat Enterprise Linux configuration. Using this tool, you can set your system time and date, install software, register your machine with Red Hat Network, and more.
Chapter 18. Removing Red Hat Enterprise Linux To remove from the S/390 you can either remove the DASD allocation from the VM or you can start the installation program and re-format all of the DASD partitions. Instead of selecting OK you will select Cancel to exit the installation program.
Chapter 19. Sample Parameter Files The IBM System z architectures use a special parameter file to set up networking before the installation program (anaconda) can be started. This section describes the contents of the parameter file. The parameter file has a limit of 32 total parameters. To accommodate limitations of the parameter files, a new configuration file on a CMS DASD should be used to configure the initial network setup and the DASD specification. The .
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 The following parameters are optional: 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.
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_* (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). Use the following samples as a guide to formatting proper parameter files.
Chapter 20. Additional Boot Options This appendix discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. To use any of the boot options presented here, type the command you wish to invoke at the installation 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.
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.
Chapter 21. Troubleshooting Installation on an IBM System z System This appendix discusses some common installation problems and their solutions. 1. You are Unable to Boot Red Hat Enterprise Linux 1.1. Is Your System Displaying Signal 11 Errors? A signal 11 error, commonly know as a segmentation fault, means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
2.4. Are You Seeing Python Errors? 2.3. Other Partitioning Problems If you are using Disk Druid to create partitions, but cannot move to the next screen, you probably have not created all the partitions necessary for Disk Druid's dependencies to be satisfied. You must have the following partitions as a bare minimum: • A / (root) partition • A partition of type swap Tip When defining a partition's type as swap, do not assign it a mount point.
3. Problems After Installation system, go to: http://bugzilla.redhat.com/bugzilla/ Finally, if you are still facing problems related to this error, register your product and contact our support team. To register your product, go to: http://www.redhat.com/apps/activate/ 3. Problems After Installation 3.1.
3.3. Your Printer Does Not Work passwd root, down -r now which allows you to enter a new password for root. At this point you can type shutto reboot the system with the new root password. If you cannot remember your user account password, you must become root. To become root, type su - and enter your root password when prompted. Then, type passwd . This allows you to enter a new password for the specified user account.
Chapter 22. Additional Information for IBM System z Users 1. The sysfs File System The Linux 2.6 kernel introduced the 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.
2. Using the zFCP Driver This 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 use sysfs is the need to refer to devices by their sysfs name. On a 2.4 kernel image, the zFCP driver was passed as its device addresses. On the 2.6 Kernel image system the driver is passed as 0.0.1600. 2.
2. Using the zFCP Driver cmb_enable cutype detach_state devtype fc_topology hardware_version host2 in_recovery port_add port_remove scsi_host_no serial_number wwpn # 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.
3. Using mdadm to Configure RAID-Based and Multipath Storage ./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.
3.1. Creating a RAID Device With mdadm 3. Using to Configure RAID-Based and Multipath Storage mdadm Similar to other tools comprising the 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 3.1. Creating a RAID Device With mdadm To create a RAID device, edit the /etc/mdadm.
3.2. Creating a Multipath Device With mdadm Raid Level : raid0 Array Size : 15621632 (14.90 GiB 15.
4. Configuring IPL from a SCSI Device mdadm: array /dev/md0 started. Due to the length of the mdadm command line, it has been broken into two lines. In this example, the hardware consists of one SCSI LUN presented as four separate SCSI devices, each accessing the same storage by a different pathway.
5. Adding DASD To IPL the SCSI disk, we provide the WWPN and LUN to the machine loader using the 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 IPL the SCSI disk using the FCP device defined to the guest. q fcp 00: FCP 010A ON FCP 010ACHPID C1 SUBCHANNEL = 0000 00: 010A QDIO-ELIGIBLE QIOASSIST-ELIGIBLE Ready; T=0.01/0.
5. Adding DASD # cd /sys/bus/ccw/drivers/dasd-eckd/0.0.
5. Adding DASD 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.
5. Adding DASD Each line that ends with "(elf64-s390)" should be treated as one line with no spaces, such as / 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.
6. Adding a Network Device 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. 6.
6.1. Adding a qeth 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. In the following example, read_device_bus_id is 0.0.0600, write_device_bus_id is 0.0.0601, and data_device_bus_id is 0.0.0602. The device is a z/VM virtual NIC and the IP address to be assigned to this interface is 192.168.70.69. # echo 0.0.0600,0.0.0601,0.0.
6.1. Adding a qeth Device • add_hhlen • broadcast_mode • buffer_count • canonical_macaddr • card_type • checksumming • chpid • detach_state • fake_broadcast • fake_ll • ipa_takeover • portno • priority_queueing • recover • route4 • rxip • state • ungroup • vipa For information on how these features work, refer to http://www-128.ibm.com/developerworks/linux/linux390/october2005_documentation.html#3 (Device Drivers, Features, and Commands - SC33-8289-02).
6.1. Adding a qeth Device 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 Edit the new ifcfg-eth1 file. Remove the HWADDR line for now. Modify the DEVICE statement to reflect the contents of the if_name file from your ccwgroup. Modify the IPADDR statement to reflect the IP address of your new interface.
6.2. Quick Reference for Adding Network Devices collisions:0 txqueuelen:1000 RX bytes:644 (644.0 b) TX bytes:264 (264.0 b) Note that the 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 Now 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.
6.2. Quick Reference for Adding Network Devices The following sections provide basic information for each task of each IBM System z network device driver. 6.2.1. Working With the LCS Device Driver The LAN channel station (LCS) device driver supports OSA-2 Ethernet/Token Ring, OSAExpress Fast Ethernet in non-QDIO mode, and OSA-Express High Speed Token Ring in nonQDIO mode. For z990, the LCS driver also supports Gigabit Ethernet in non-QDIO mode (including 1000Base-T).
6.2. Quick Reference for Adding Network Devices 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=Ethernet Based on the type interface being added, the DEVICE parameter should be one of the following: DEVICE=ethn DEVICE=trn • Activate the device.
6.2. Quick Reference for Adding Network Devices /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.
7. Kernel-Related Information # ifup ethn # ifup trn 7. Kernel-Related Information Red Hat Enterprise Linux includes a modification to the way the Linux kernel timer interrupt is handled. Normally, a hardware timer is set to generate periodic interrupts at a fixed rate (100 times a second for most architectures). These periodic timer interrupts are used by the kernel to schedule various internal housekeeping tasks, such as process scheduling, accounting, and maintaining system uptime.
Part IV. Common Tasks Information that is common to all architectures related to registering your system with Red Hat Network, choosing whether to install or upgrade, and information on disk partitioning is contained in this section.
Chapter 23. Upgrading Your Current System This chapter explains the various methods available for upgrading your Red Hat Enterprise Linux system. 1. Determining Whether to Upgrade or ReInstall While upgrading from Red Hat Enterprise Linux version 4 Update 4 is supported, you are more likely to have a consistent experience by backing up your data and then installing this release of Red Hat Enterprise Linux 5.0.0 over your previous Red Hat Enterprise Linux installation.
2. Upgrading Your System carefully compare your original configuration files to the new files before integrating your changes. Note It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your hard drive(s). Mistakes do happen and can result in the loss of all of your data. Some upgraded packages may require the installation of other packages for proper operation.
2. Upgrading Your System To re-install your system, select Perform a new Red Hat Enterprise Linux installation and refer to http://www.redhat.com/docs/wp/ as well as Chapter 4, Installing on Intel and AMD Systems, Chapter 12, Installing on IBM System i and IBM System p systems, or Chapter 17, Installing on IBM System z Systems for further instructions.
Chapter 24. Activate Your Subscription 1. RHN Registration Before you can access service and software maintenance information, and the support documentation included in your subscription, you must activate your subscription by registering with Red Hat.
1.3. Connect Your System 1.3. Connect Your System The Red Hat Network Registration Client helps you connect your system so that you can begin to get updates and perform systems management. There are three ways to connect: 1. During the Setup Agent — Check the Send hardware information and Send system package list options when prompted. 2. After the Setup Agent has been completed — From Applications (the main menu on the panel), go to System Tools, then select Package Updater. 3.
Chapter 25. An Introduction to Disk Partitions Note This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply. This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply. If you are reasonably comfortable with disk partitions, you could skip ahead to Section 1.
1.1. It is Not What You Write, it is How You Write It Formatting (usually known as "making a file system") writes information to the drive, creating order out of the empty space in an unformatted drive. Figure 25.2. Disk Drive with a File System As Figure 25.2, “Disk Drive with a File System”, implies, the order imposed by a file system involves some trade-offs: • A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead.
1.2. Partitions: Turning One Drive Into Many Figure 25.4. Disk Drive with Data Written to It As Figure 25.4, “Disk Drive with Data Written to It”, shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one file or many, as all files use at least one block and some files use multiple blocks.
1.2. Partitions: Turning One Drive Into Many Figure 25.5. Disk Drive with Partition Table As Figure 25.5, “Disk Drive with Partition Table” shows, the partition table is divided into four sections or four primary partitions. A primary partition is a partition on a hard drive that can contain only one logical drive (or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions.
1.3. Partitions within Partitions — An Overview of Extended Partitions We have labeled this partition as being of the "DOS" type. Although it is only one of several possible partition types listed in Table 25.1, “Partition Types”, it is adequate for the purposes of this discussion. Table 25.1, “Partition Types”, contains a listing of some popular (and obscure) partition types, along with their hexadecimal numeric values.
1.4. Making Room For Red Hat Enterprise Linux Partitions Of course, over time it became obvious that four partitions would not be enough. As disk drives continued to grow, it became more and more likely that a person could configure four reasonably-sized partitions and still have disk space left over. There needed to be some way of creating more partitions. Enter the extended partition. As you may have noticed in Table 25.1, “Partition Types”, there is an "Extended" partition type.
1.4. Making Room For Red Hat Enterprise Linux Note Keep in mind that the following illustrations are simplified in the interest of clarity and do not reflect the exact partition layout that you encounter when actually installing Red Hat Enterprise Linux. 1.4.1. Using Unpartitioned Free Space In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. Figure 25.
1.4. Making Room For Red Hat Enterprise Linux Figure 25.9. Disk Drive With an Unused Partition In Figure 25.9, “Disk Drive With an Unused Partition”, 1 represents an unused partition and 2 represents reallocating an unused partition for Linux. If you find yourself in this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place.
1.4. Making Room For Red Hat Enterprise Linux Figure 25.10. Disk Drive Being Destructively Repartitioned In Figure 25.10, “Disk Drive Being Destructively Repartitioned”, 1 represents before and 2 represents after. Caution As Figure 25.
1.4. Making Room For Red Hat Enterprise Linux Figure 25.11. Disk Drive Being Compressed In Figure 25.11, “Disk Drive Being Compressed”, 1 represents before and 2 represents after. This step is crucial. Without it, the location of your data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved.
1.5. Partition Naming Scheme In Figure 25.13, “Disk Drive with Final Partition Configuration”, 1 represents before and 2 represents after. Note The following information is specific to x86-based computers only. As a convenience to our customers, we provide the parted utility. This is a freely available program that can resize partitions. If you decide to repartition your hard drive with parted, it is important that you be familiar with disk storage and that you perform a backup of your computer data.
1.6. Disk Partitions and Other Operating Systems 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) or sd (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 through 4. Logical partitions start at 5.
1.8. How Many Partitions? Continuing our example, it is also possible that one or more directories below /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. 1.8.
Part V. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This section describes how to boot into rescue mode, singleuser mode, and emergency mode, where you can use your own knowledge to repair the system..
Chapter 26. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, singleuser mode, and emergency mode, where you can use your own knowledge to repair the system. 1. Common Problems You might need to boot into one of these recovery modes for any of the following reasons: • You are unable to boot normally into Red Hat Enterprise Linux (runlevel 3 or 5).
2. Booting into Rescue Mode 2. Booting into Rescue Mode Rescue mode provides the ability to boot a small Red Hat Enterprise Linux environment entirely from CD-ROM, or some other boot method, instead of the system's hard drive. As the name implies, rescue mode is provided to rescue you from something. During normal operation, your Red Hat Enterprise Linux system uses files located on your system's hard drive to do everything — run programs, store your files, and more.
2. Booting into Rescue Mode If you select Continue, it attempts to mount your file system under the directory /mnt/sysimage/. If it fails to mount a partition, it notifies you. If you select Read-Only, it attempts to mount your file system under the directory /mnt/sysimage/, but in read-only mode. If you select Skip, your file system is not mounted. Choose Skip if you think your file system is corrupted.
2.1. Reinstalling the Boot Loader • rpm for installing or upgrading software • joe for editing configuration files Note If you try to start other popular editors such as emacs, pico, or vi, the joe editor is started. 2.1. Reinstalling the Boot Loader In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems.
4. Booting into Emergency Mode 2. Select Red Hat Enterprise Linux with the version of the kernel that you wish to boot and type a to append the line. 3. Go to the end of the line and type single as a separate word (press the Spacebar and then type single). Press Enter to exit edit mode. 4. Booting into Emergency Mode In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up.
Chapter 27. Rescue Mode on POWER Systems You can use the installation disks in rescue mode, in case your system does not boot. Rescue mode gives you access to the disk partitions on your system so you can make any changes necessary to rescue your installation.
1. Special Considerations for Accessing the SCSI Utilities from Rescue Mode 5. Make sure the installation disc is not in your CD-ROM drive. 6. IPL the Linux system. 7. Follow the prompts as decribed in Chapter 27, Rescue Mode on POWER Systems. An additonal prompt for the installation source appears. Select NFS or FTP (as appropriate) and complete the following network configuration screen. 8.
Part VI. Advanced Installation and Deployment The Red Hat Enterprise Linux Installation Guide discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. However, advanced installation options are also covered in this manual. This part provides instructions for kickstart (an automated installation technique)and all related tools.
Chapter 28. Kickstart Installations 1. What are Kickstart Installations? Many system administrators would prefer to use an automated installation method to install Red Hat Enterprise Linux on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
4. Kickstart Options • Command section — Refer to Section 4, “Kickstart Options” for a list of kickstart options. You must include the required options. • The %packages section — Refer to Section 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 6, “Pre-installation Script” and Section 7, “Post-installation Script” for details. • Items that are not required can be omitted.
4. Kickstart Options (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 the part directive. autopart (optional) Causes the installer to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored.
4. Kickstart Options about users (UIDs, home directories, shells, etc.) from an LDAP directory. To use this option, you must install the nss_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 the pam_ldap module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the nss_ldap package installed.
4. Kickstart Options --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. Tip To look up user information for "jim", the Hesiod library looks up jim.passwd, 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).
4. Kickstart Options --driveorder Specify which drive is first in the BIOS boot order. For example: bootloader --driveorder=sda,hda --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), or none (do not install the boot loader). --password= If using GRUB, sets the GRUB boot loader password to the one specified with this option.
4. Kickstart Options Do not remove any partitions. (optional) Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 console. cmdline (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.
4. Kickstart Options 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. --enabled or --disable Do not configure any iptables rules. --disabled --trust= Listing a device here, such as eth0, allows all traffic coming from that device to go through the firewall.
4. Kickstart Options fore rebooting. During a kickstart installation, if no completion method is specified, the reboot option is used as default. The halt option is roughly equivalent to the shutdown -h command. For other completion methods, refer to the poweroff, reboot, and shutdown kickstart options. (optional) Perform the kickstart installation in graphical mode. This is the default. graphical The halt option is roughly equivalent to the shutdown -h command.
4. Kickstart Options 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:/// or: url --url ftp://:@/ (optional) Used to specify disks that anaconda should not touch when partitioning, formatting, and clearing.
4. Kickstart Options (required) Sets system keyboard type.
4. Kickstart Options --fstype= Sets the file system type for the logical volume. Valid values are ext2, ext3, swap, and vfat. --fsoptions= Sets the file system type for the logical volume. Valid values are ext2, ext3, swap, and vfat. --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.
4. Kickstart Options (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. 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.
4. Kickstart Options start file. As the name implies, this information is static and are 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. For example: (the "\" indicates that this should be read as one continuous line): network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 \ --gateway=10.0.2.254 --nameserver=10.0.2.
4. Kickstart Options --onboot= Whether or not to enable the device at boot time. --class= The DHCP class. --mtu= The MTU of the device. --noipv4= Disable IPv4 on this device. --noipv6= Disable IPv6 on this device. (optional) multipath --name= --device= --rule= multipath or partition (required for installs, ignored for upgrades) Creates a partition on the system.
4. Kickstart Options • raid. The partition is used for software RAID (refer to raid). • pv. The partition is used for LVM (refer to logvol). --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. --maxsize= The maximum partition size in megabytes when the partition is set to grow.
4. Kickstart Options --recommended Determine the size of the partition automatically. --onbiosdisk Forces the partition to be created on a particular disk as discovered by the BIOS. Note If partitioning fails for any reason, diagnostic messages appear on virtual console 3. (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.
4. Kickstart Options md7, 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 are ext2, ext3, swap, and vfat.
4. Kickstart Options Note Use of the reboot option may result in an endless installation loop, depending on the installation media and method. The reboot option is the default completion method if no other methods are explicitly specified in the kickstart file. For other completion methods, refer to the halt, poweroff, and shutdown kickstart options. (optional) Configures additional yum repositories that may be used as sources for package installation. Multiple repo lines may be specified.
4. Kickstart Options Note If the selinux 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. For complete information regarding SELinux for Red Hat Enterprise Linux, refer to the Red Hat Enterprise Linux Deployment Guide.
4. Kickstart Options Tells the system to upgrade an existing system rather than install a fresh system. You must specify one of cdrom, harddrive, nfs, or url (for FTP and HTTP) as the location of the installation tree. Refer to install for details. (optional) Creates a new user on the system. user user --name= [--groups=] [--homedir=] [--password=] [--iscrypted] [- --name= Provides the name of the user. This option is required.
4. Kickstart Options volgroup 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.
4.1. Advanced Partitioning Example If zerombr is specified, and yes is its sole argument, any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables. This command should be in the following format: zerombr yes No other format is effective.
6. Pre-installation Script the asterisk. The installation program defines several groups that contain related packages. Refer to the 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.
6.1. Example 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 Note that the pre-install script is not run in the change root environment. --interpreter /usr/bin/python Allows you to specify a different scripting language, such as Python.
7. Post-installation Script Note The pre-installation script section of kickstart cannot manage multiple install trees or source media. This information must be included for each created ks.cfg file, as the pre-installation script occurs during the second stage of the installation process. 7. Post-installation Script You have the option of adding commands to run on the system once the installation is complete. This section must be at the end of the kickstart file and must start with the %post command.
8. Making the Kickstart File Available 7.1. Examples Register the system to a Red Hat Network Satellite: %post ( # Note that in this example we run the entire %post section as a subshell for logging. wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash /usr/sbin/rhnreg_ks --activationkey= # End the subshell and capture any output to a post-install log file. ) 1>/root/post_install.log 2>&1 Run a script named runme from an NFS share: mkdir /mnt/temp mount -o nolock 10.10.
8.2. Making the Kickstart File Available on the Network To perform a pen-based flash memory kickstart installation, the kickstart file must be named 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. For example, the following transfers a boot image to the pen drive (/dev/sda) using the dd command: dd if=diskboot.
9. Making the Installation Tree Available 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. Note that if you do not specify a server name, then the client system attempts to use the server that answered the BOOTP/DHCP request as its NFS server.
10. Starting a Kickstart Installation command at the boot: prompt (where ks.cfg is the name of the kickstart file): linux ks=cdrom:/ks.cfg Other options to start a kickstart installation are as follows: 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. debug Start up pdb immediately. dd Use a driver disk. dhcpclass= Sends a custom DHCP vendor class identifier.
10. Starting a Kickstart Installation . 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 be ks=nfs:server.example.com:/mydir/ks.cfg. ks=http:/// The installation program looks for the kickstart file on the HTTP server , as file . The installation program uses DHCP to configure the Ethernet card.
10. Starting a Kickstart Installation 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: "XRHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab". lang= Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command. loglevel= Set the minimum level required for messages to be logged.
10. Starting a Kickstart Installation fatal error occurs. 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.
10. Starting a Kickstart Installation updates=ftp:// Image containing updates over FTP. updates=http:// 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=[:] Once installation is up and running, connect to the vnc client named , and optionally use port .
Chapter 29. Kickstart Configurator Kickstart Configurator allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file. To use Kickstart Configurator, you must be running the X Window System. To start Kickstart Configurator, select Applications (the main menu on the panel) => System Tools => Kickstart, or type the command /usr/sbin/system-config-kickstart.
2. Installation Method mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select Encrypt root password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it.
3. Boot Loader Options are disabled. They are not supported for kickstart upgrades. Choose the type of kickstart installation or upgrade from the following options: • CD-ROM — Choose this option to install or upgrade from the Red Hat Enterprise Linux CDROMs. • NFS — Choose this option to install or upgrade from an NFS shared directory. In the text field for the the NFS server, enter a fully-qualified domain name or IP address.
3. Boot Loader Options Figure 29.3. Boot Loader Options Please note that this screen will be disabled if you have specified a target architecture other than x86 / x86_64. GRUB is the default boot loader for Red Hat Enterprise Linux on x86 / x86_64 architectures. If you do not want to install a boot loader, select Do not install a boot loader. If you choose not to install a boot loader, make sure you create a boot diskette or have another way to boot your system, such as a third-party boot loader.
4. Partition Information Note The Upgrade existing boot loader option does not function at the time of General Availability of Red Hat Enterprise Linux 5. This issue is being addressed, and the functionality will be made available in an errata release. 4. Partition Information Figure 29.4. Partition Information Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions.
4.1. Creating Partitions 4.1. Creating Partitions To create a partition, click the Add button. The Partition Options window shown in Figure 29.5, “Creating Partitions” appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following: • 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.
4.1. Creating Partitions Figure 29.5. Creating Partitions To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Figure 29.5, “Creating Partitions”, except it reflects the values for the selected partition. Modify the partition options and click OK. To delete an existing partition, select the partition from the list and click the Delete button. 4.1.1.
4.1. Creating Partitions 2. Select Create a software RAID partition. 3. 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 29.6. Creating a Software RAID Partition Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions.
5. Network Configuration 3. 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 29.7. Creating a Software RAID Device 4. Click OK to add the device to the list. 5.
6. Authentication Figure 29.8. Network Configuration If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the Network Configuration page. Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the Network Administration Tool (system-config-network). Refer to the Red Hat Enterprise Linux Deployment Guide for details.
7. Firewall Configuration Figure 29.9. Authentication In the Authentication section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default. The Authentication Configuration options allow you to configure the following methods of authentication: • NIS • LDAP • Kerberos 5 • Hesiod • SMB • Name Switch Cache These methods are not enabled by default.
7.1. SELinux Configuration Figure 29.10. Firewall Configuration If Disable firewall is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied. Selecting Enable firewall configures the system to 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 required, you can choose to allow specific services through the firewall.
8.1. General 8. Display Configuration If you are installing the X Window System, you can configure it during the kickstart installation by checking the Configure the X Window System option on the Display Configuration window as shown in Figure 29.11, “X Configuration - General”. If this option is not chosen, the X configuration options are disabled and the skipx option is written to the kickstart file. 8.1. General The first step in configuring X is to choose the default color depth and resolution.
8.3. Monitor 8.2. Video Card Probe for video card driver is selected by default. Accept this default to have the installation program probe for the video card during installation. Probing works for most modern video cards. If this option is selected and the installation program cannot successfully probe the video card, the installation program stops at the video card configuration screen. To continue the installation process, select the driver for your video card from the list and click Next.
9. Package Selection Figure 29.13. X Configuration - Monitor Probe for monitor is selected by default. Accept this default to have the installation program probe for the monitor during installation. Probing works for most modern monitors. If this option is selected and the installation program cannot successfully probe the monitor, the installation program stops at the monitor configuration screen. To continue the installation process, select your monitor from the list and click Next.
10. Pre-Installation Script Figure 29.14. Package Selection The Package Selection window allows you to choose which package groups to install. Package resolution is carried out automatically. Currently, Kickstart Configurator does not allow you to select individual packages. To install individual packages, modify the %packages section of the kickstart file after you save it. Refer to Section 5, “Package Selection” for details. 10.
10. Pre-Installation Script Figure 29.15. Pre-Installation Script You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area.
11. Post-Installation Script md5sum, mdev, mesg, mkdir, mke2fs, mkfifo, mkfs.ext2, mkfs.ext3, mkfs.
11.1. Chroot Environment Figure 29.16. Post-Installation Script You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area. Caution Do not include the %post command. It is added for you.
11.2. Use an Interpreter this option on the top of the Post-Installation window. This is equivalent to using the -nochroot option in the %post section. To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/.
12. Saving the File Figure 29.17. Preview To save the kickstart file, click the Save to File button in the preview window. To save the file without previewing it, select File => Save File or press Ctrl-S . A dialog box appears. Select where to save the file. After saving the file, refer to Section 10, “Starting a Kickstart Installation” for information on how to start the kickstart installation.
Chapter 30. Boot Process, Init, and Shutdown An important and powerful aspect of Red Hat Enterprise Linux is the open, user-configurable method it uses for starting the operating system. Users are free to configure many aspects of the boot process, including specifying the programs launched at boot-time. Similarly, system shutdown gracefully terminates processes in an organized and configurable way, although customization of this process is rarely required.
2.2. The Boot Loader reason it is written into read-only, permanent memory and is always available for use. Other platforms use different programs to perform low-level tasks roughly equivalent to those of the BIOS on an x86 system. For instance, Itanium-based computers use the Extensible Firmware Interface (EFI) Shell. Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system.
2.3. The Kernel For instructions on using the boot loader to supply command line arguments to the kernel, refer to Chapter 9, The GRUB Boot Loader. For information on changing the runlevel at the boot loader prompt, refer Section 8, “Changing Runlevels at Boot Time”. The boot loader then places one or more appropriate initramfs images into memory. Next, the kernel decompresses these images from memory to /sysroot/, a RAM-based virtual file system, via cpio.
2.4. The /sbin/init Program quired 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. The init command then runs the /etc/inittab script, which describes how the system should be set up in each SysV init runlevel.
3. Running Additional Programs at Boot Time Note One of the last things the init program executes is the /etc/rc.d/rc.local file. This file is useful for system customization. Refer to Section 3, “Running Additional Programs at Boot Time” for more information about using the rc.local file. After the 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.
4.1. Runlevels services. Each of the numbered directories represent the six runlevels configured by default under Red Hat Enterprise Linux. 4.1. Runlevels The idea behind SysV init runlevels revolves around the idea that different systems can be used in different ways. For example, a server runs more efficiently without the drag on system resources created by the X Window System.
4.2. Runlevel Utilities For more information on single-user and rescue mode, refer to the chapter titled Basic System Recovery in the Red Hat Enterprise Linux Deployment Guide. It is possible to change the default runlevel at boot time by modifying the arguments passed by the boot loader to the kernel. For information on changing the runlevel at boot time, refer to Section 8, “Changing Runlevels at Boot Time”. 4.2.
Chapter 31. PXE Network Installations Red Hat Enterprise Linux allows for installation over a network using the NFS, FTP, or HTTP protocols. A network installation can be started from a boot CD-ROM, a bootable flash memory drive, or by using the askmethod boot option with the Red Hat Enterprise Linux CD #1.
3. Adding PXE Hosts package, can be used to configure the tftp server files as described in Section 4, “TFTPD”: config-netboot pxeos -a -i "" -p -D 0 -s client.example.com \ -L -k -K The following list explains the options: • -a — Specifies that an OS instance is being added to the PXE configuration. • -i "" • -p • -D • -sclient.example.com — Replace "" with a description of the OS instance.
3.1. Command Line Configuration Figure 31.2. Add a Host Enter the following information: • 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. • 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.
5. Configuring the DHCP Server Note For more information on installing RPM packages, refer to the Package Management Section of the Red Hat Enterprise Linux Deployment Guide. tftp is an xinetd-based service; start it with the following commands: /sbin/chkconfig --level 345 xinetd on /sbin/chkconfig --level 345 tftp on These commands configure the tftp and xinetd services to immediately turn on and also configure them to start at boot time in runlevels 3, 4, and 5. 5.
