Red Hat Enterprise Linux 5 Installation Guide Installing Red Hat Enterprise Linux 5 for all architectures Red Hat Engineering Content ServicesRüdiger Landmann Jack Reed Petr Bokoč David Cantrell Hans De Goede Jon Masters
Red Hat Enterprise Linux 5 Installation Guide Installing Red Hat Enterprise Linux 5 for all architectures Rüdiger Landmann Red Hat Engineering Co ntent Services r.landmann@redhat.co m Jack Reed Red Hat Engineering Co ntent Services jreed@redhat.co m Petr Bo ko č Red Hat Engineering Co ntent Services pbo ko c@redhat.co m David Cantrell dcantrell@redhat.co m VNC installatio n Hans De Go ede hdgo ede@redhat.co m iSCSI Jo n Masters jcm@redhat.
Legal Notice Co pyright © 20 14 Red Hat, Inc.. This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0 Unpo rted License. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red Hat trademarks must be remo ved.
T able of Cont ent s T able of Contents . .art P . . .I.. x8 . . 6. ,. AMD6 . . . . . .4., .Int . . el® . . . .6.4. .and . . . It . .anium . . . . . .- .Inst . . . allat . . . . ion . . . .and . . . Boot . . . . .ing . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. . . . . . . . . . . .hapt C . . . .er . .1. .. It. anium . . . . . . Syst . . . . em . . . Specific . . . . . . . .Informat . . . . . . . ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Red Hat Ent erprise Linux 5 Inst allat ion G uide . .hapt C . . . .er . .7. .. Updat . . . . . .ing . . .drivers . . . . . . during . . . . . . .inst . . . allat . . . . ion . . . on . . . Int . . .el. .and . . . .AMD . . . . syst . . . .ems . . . . . . . . . . . . . . . . . . . . . .7. 8. . . . . . . . . . 7 .1. Limitatio ns o f d river up d ates d uring ins tallatio n 78 7 .2. Prep aring fo r a d river up d ate d uring ins tallatio n 79 7 .3.
T able of Cont ent s 12.23. Pac kag e G ro up Selec tio n 12.24. Prep aring to Ins tall 145 147 12.25. Ins talling Pac kag es 147 12.26 . Ins tallatio n Co mp lete 148 . .hapt C . . . .er . .1. 3. . . Updat . . . . . .ing . . .drivers . . . . . . during . . . . . . .inst . . . allat . . . . ion . . . on . . . IBM . . . . PO . . .WER . . . . syst . . . . ems . . . . . . . . . . . . . . . . . . . . . .1. 50 ........... 13.1. Limitatio ns o f d river up d ates d uring ins tallatio n 150 13.2.
Red Hat Ent erprise Linux 5 Inst allat ion G uide . .hapt C . . . .er . .1. 8. .. Removing . . . . . . . . . .Red . . . .Hat . . . Ent . . . erprise . . . . . . .Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1. 2. . . . . . . . . . . .hapt C . . . .er . .1. 9. .. Sample . . . . . . . Paramet . . . . . . . er . . Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. 1. 3. . . . . . . . . .
T able of Cont ent s 3 0 .2. VNC Mo d es in Anac o nd a 28 0 3 0 .3. Ins tallatio n Us ing VNC 28 0 3 0 .4. Referenc es 28 2 . .hapt C . . . .er . .31 . . .. Kickst . . . . . art . . . Inst . . . .allat . . . .ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. 8. 3. . . . . . . . . . 3 1.1. What are Kic ks tart Ins tallatio ns ? 3 1.2. Ho w Do Yo u Perfo rm a Kic ks tart Ins tallatio n? 28 3 28 3 3 1.3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 1 . It anium Syst em Specific Informat ion Chapter 1. Itanium System Specific Information 1.1. It anium Syst em Inst allat ion 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The output is listed in the order the system was probed. So, all FAT16 file systems are listed first, then ID E hard drives, then SCSI hard drives, then ID E CD -ROM drives, and finally SCSI CD -ROM drives.
Chapt er 2 . St eps t o G et You St art ed Chapter 2. Steps to Get You Started 2.1. Upgrade or Inst all? For information to help you determine whether to perform an upgrade or an installation refer to Chapter 24, Upgrading Your Current System. 2.2. Is Your Hardware Compat ible? Hardware compatibility is particularly important if you have an older system or a system that you built yourself.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If you do not already have a Red Hat Enterprise Linux 5.11 CD set or D VD , you can download one as an ISO image file from the Red Hat Customer Portal. Visit https://access.redhat.com/home and enter your Login and Password. Click on the Downloads link to obtain a list of all currently supported Red Hat Enterprise Linux products. If you do not already have a Login and Password for the Red Hat Customer Portal, visit https://access.redhat.
Chapt er 2 . St eps t o G et You St art ed B o o t D VD /C D - R O M If you can boot using the D VD /CD -ROM drive, you can create your own CD -ROM to boot the installation program. This may be useful, for example, if you are performing an installation over a network or from a hard drive. Refer to Section 2.4.2, “ Making an Installation Boot CD -ROM” for further instructions.
Red Hat Ent erprise Linux 5 Inst allat ion G uide sdb: sdb1 sd 2:0:0:0: Attached scsi removable disk sdb sd 2:0:0:0: Attached scsi generic sg1 type 0 usb-storage: device scan complete 4. Unmount any partitions on the flash drive that are currently mounted. It is likely that your system automatically mounted any available partitions when you attached the flash drive. a. Use the mount command to find any mounted partitions on the flash drive.
Chapt er 2 . St eps t o G et You St art ed a. If necessary, edit syslinux.cfg for your particular environment. For example, to configure the installation to use a kickstart file shared over NFS, specify: linux ks=nfs:://ks.cfg 10. Copy the images/pxeboot/initrd.img file from the installation D VD or CD ROM#1 onto the flash drive. 11. Unmount the flash drive. For example: umount /dev/sdb1 12. Make the USB flash drive bootable. For example: syslinux /dev/sdb1 13. Mount the flash drive again.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Copy the isolinux/ directory from the Red Hat Enterprise Linux D VD or CD #1 into a temporary directory (referred to here as ) using the following command: cp -r /isolinux/ Change directories to the directory you have created: cd Make sure the files you have copied have appropriate permissions: chmod u+w isolinux/* Finally, issue the following command to create the
Chapt er 2 . St eps t o G et You St art ed 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 /publicly/available/directory. For example, /location/of/disk/space may be a directory you create called /var/isos. /publicly/available/directory might be /var/www/html/rhel5, for an HTTP install.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Next make sure that the /publicly/available/directory directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to. 2.5.2. Preparing for an NFS inst all For NFS installation it is not necessary to mount the iso image. It is sufficient to make the iso image itself available via NFS.
Chapt er 2 . St eps t o G et You St art ed Using a set of CD -ROMs, or a D VD — Create ISO image files from each installation CD -ROM, or from the D VD . For each CD -ROM (once for the D VD ), 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 3. System Specifications List The most recent list of supported hardware can be found at http://hardware.redhat.com/hcl/. This system specifications list will help you keep a record of your current system settings and requirements. Enter the corresponding information about your system in the list provided below as a handy reference to help make your Red Hat Enterprise Linux installation goes smoothly. hard drive(s): type, label, size; e.g.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Chapter 4. Installing on Intel® and AMD Systems This chapter explains how to perform a Red Hat Enterprise Linux installation from the D VD /CD -ROM, using the graphical, mouse-based installation program.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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 4 .1.1. A Not e about Virt ual Consoles The Red Hat Enterprise Linux installation program offers more than the dialog boxes of the installation process.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 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 D isk D ruid” , illustrate the screens that appear during the installation process.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .2. In st allat io n Pro g ram Wid g et s as seen in D isk D ru id 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 D isk D ruid” : Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Cursor — Although not a widget, the cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or next to the widget. 4 .3.1. Using t he Keyboard t o Navigat e Navigation through the installation dialogs is performed through a simple set of keystrokes.
Red Hat Ent erprise Linux 5 Inst allat ion G uide USB pen drive — Your machine supports booting from a USB device. PXE boot via network — Your machine supports booting from the network. This is an advanced installation path. Refer to Chapter 34, PXE Network Installations for additional information on this method. To create a boot CD -ROM or to prepare your USB pen drive for installation, refer to Section 2.4.1, “ Alternative Boot Methods” . Insert the boot media and reboot the system.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 4 .4 .2 .1 . Bo o t ing t he Inst allat io n Pro gram fro m t he DVD/CD-ROM To boot from the Red Hat Enterprise Linux CD #1 follow these steps: 1. Remove all media except Red Hat Enterprise Linux CD #1. 2. From the B o o t O p t io n menu choose EFI Sh ell. 3. At the Shell> prompt, change to the file system on the CD -ROM. For example, in the above sample map output, the system partition on the CD -ROM is fs1.
Red Hat Ent erprise Linux 5 Inst allat ion G uide For Itanium users: To pass options to the boot loader on an Itanium system, enter the following at the EFI Shell prompt: elilo linux option For x86, AMD64, and Intel® 64 users: To pass options to the boot loader on an x86, AMD 64, or Intel® 64 system, use the instructions as provided in the boot loader option samples below. Note Refer to Chapter 8, Additional Boot Options for Intel® and AMD Systems for additional boot options not covered in this section.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems linux console=ttyS0 utf8 4 .4 .3.1 . Ke rne l Opt io ns Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a floppy disk enter: linux updates For text mode installations, use: linux text updates This command will prompt you to insert a floppy diskette containing updates for anaconda.
Red Hat Ent erprise Linux 5 Inst allat ion G uide HTTP If you are installing directly from an HTTP (Web) server, use this method. You need a boot CD -ROM (use the linux askmethod boot option). Refer to Section 4.11, “ Installing via HTTP” , for HTTP installation instructions. 4 .6. Inst alling from DVD/CD-ROM To install Red Hat Enterprise Linux from a D VD /CD -ROM, place the D VD or CD #1 in your D VD /CD ROM drive and boot your system from the D VD /CD -ROM.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .3. Select in g Part it io n D ialo g f o r H ard D rive In st allat io n 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 /.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .4 . T C P/IP C o n f ig u rat io n 4 .9. Inst alling via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected N FS Imag e 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .5. N FS Set u p D ialo g 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. 4 .10. Inst alling via FT P The FTP dialog applies only if you are installing from an FTP server (that is, if you used the askmethod boot options and selected FT P in the Installation Method dialog).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .6 . FT P Set u p D ialo g 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems The HTTP dialog applies only if you are installing from an HTTP server (that is, if you used the askmethod boot option and selected H T T P in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 4 .12. Welcome t o Red Hat Ent erprise 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.11 by clicking on the Release Notes button. Click on the Next button to continue. 4 .13. Language Select ion Using your mouse, select a language to use for the installation (refer to Figure 4.8, “ Language Selection” ).
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .8. Lan g u ag e Select io n Once you select the appropriate language, click Next to continue. 4 .14 . Keyboard Configurat ion 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .9 . K eyb o ard C o n f ig u rat io n Note To change your keyboard layout type after you have completed the installation, use the K eyb o ard C o n f ig u rat io n T o o l. Type the system-config-keyboard command in a shell prompt to launch the K eyb o ard C o n f ig u rat io n T o o l. If you are not root, it prompts you for the root password to continue. 4 .15.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .10. In st allat io n N u mb er 4 .16. Disk Part it ioning Set up 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 26, An Introduction to Disk Partitions for more information.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning The U p d at e Ag en t 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. Fig u re 4 .11. D isk Part it io n in g Set u p If you choose to create a custom layout using D isk D ru id , refer to Section 4.19, “ Partitioning Your System” .
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: " The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL D ATA on this drive." you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .14 . C o n f ig u re ISC SI Paramet ers 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. 4 .18. Creat e Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .15. C reat e D ef au lt Layo u t 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. Warning It is always a good idea to back up any data that you have on your systems.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Note If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the /boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive. 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .16 . Part it io n in g wit h D isk D ru id o n x86 , AMD 6 4 , an d In t el® 6 4 Syst ems The partitioning tool used by the installation program is D isk D ru id . With the exception of certain esoteric situations, D isk D ru id can handle the partitioning requirements for a typical installation. 4 .19.1. Graphical Display of Hard Drive(s) D isk D ru id offers a graphical representation of your hard drive(s).
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 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. You can also edit free space as represented in the graphical display to create a new partition within that space.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Hide RAID device/LVM Volume Group members: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created. 4 .19.4 . Recommended Part it ioning Scheme 4 .1 9 .4 .1 .
Chapt er 4 . Inst alling on Int el® and AMD Syst ems A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning — do not place /var on network storage Red Hat Enterprise Linux 5.11 does not support having a separate /var on a network filesystem (for example, NFS, iSCSI, or NBD ) The /var directory contains critical data that must be read from or written to during the boot process before establishing network services. However, you may have /var/spool, /var/www or other subdirectories on a separate network disk, just not the complete /var filesystem. 4 .19.5.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .17. C reat in g a N ew Part it io n 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. Force to be a primary partition: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to Section 26.1.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 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. 4 .19.7. Delet ing a Part it ion To delete a partition, highlight it in the Partitions section and click the Delete button. Confirm the deletion when prompted. For further installation instructions for x86, AMD 64, and Intel® 64 systems, skip to Section 4.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .18. B o o t Lo ad er C o n f ig u rat io n 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide the earliest point at which the boot loader can take control of the boot process. If you install it in the MBR, when your machine boots, GRUB presents a boot prompt. You can then boot Red Hat Enterprise Linux or any other operating system that you have configured the boot loader to boot. The first sector of your boot partition — This is recommended if you are already using another boot loader on your system.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems The Force LBA32 (not normally required) option allows you to exceed the 1024 cylinder limit for the /boot/ partition. If you have a system which supports the LBA32 extension for booting operating systems above the 1024 cylinder limit, and you want to place your /boot/ partition above cylinder 1024, you should select this option.
Red Hat Ent erprise Linux 5 Inst allat ion G uide and associated mirror sites. SYSLIN U X SYSLINUX is an MS-D OS program very similar to LOAD LIN. It is also available from ftp://metalab.unc.edu/pub/Linux/system/boot/loaders/ and associated mirror sites. C o mmercial b o o t lo ad ers 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).
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .20. N et wo rk C o n f ig u rat io n The installation program automatically detects any network devices you have and displays them in the Network Devices list. When you have selected a network device, click Edit. From the Edit Interface dialog, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device to use D HCP or to use static settings.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .21. Ed it in g a N et wo rk D evice Note D o 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Note To change your network configuration after you have completed the installation, use the N et wo rk Ad min ist rat io n T o o l. Type the system-config-network command in a shell prompt to launch the N et wo rk Ad min ist rat io n T o o l. If you are not root, it prompts you for the root password to continue. 4 .22. T ime Zone Configurat ion Set your time zone by selecting the city closest to your computer's physical location.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Select System Clock uses UTC if you know that your system is set to UTC. Note To change your time zone configuration after you have completed the installation, use the T ime an d D at e Pro p ert ies T o o l. Type the system-config-date command in a shell prompt to launch the T ime an d D at e Pro p ert ies T o o l. If you are not root, it prompts you for the root password to continue.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .23. R o o t Passwo rd 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. Note 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Note D o not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk. Note To change your root password after you have completed the installation, use the R o o t Passwo rd T o o l. Type the system-config-rootpassword command in a shell prompt to launch the R o o t Passwo rd T o o l. If you are not root, it prompts you for the root password to continue. 4 .24 .
Chapt er 4 . Inst alling on Int el® and AMD Syst ems Fig u re 4 .24 . Packag e G ro u p Select io n 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 4 .25. Packag e G ro u p D et ails 4 .25. Preparing t o Inst all 4 .25.1. Prepare t o Inst all 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.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems 4 .26. Inst alling 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. 4 .27. Inst allat ion Complet e Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If you do not know the names of the installed kernels, you can view the /boot/efi/elilo.conf file in EFI with the following instructions: 1. At the Shell> prompt, change devices to the system partition (mounted as /boot/efi in Linux). For example, if fs0 is the system boot partition, type fs0: at the EFI Shell prompt. 2. Type ls at the fs0:\> to make sure you are in the correct partition. 3. Then type: Shell> type elilo.
Chapt er 4 . Inst alling on Int el® and AMD Syst ems options appears. Move the R ed H at En t erp rise Lin u x 5 menu item up to the top of the list by selecting it with the arrow keys and pressing the u key to move it up the list. You can move items down the list by selecting it and pressing the d key. After changing the boot order, choose Save ch an g es t o N VR AM. Choose Exit to return to the Main Menu. 9.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 5. Removing Red Hat Ent erprise Linux 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. For example, to remove the partition with minor number 3: rm 3 Important The changes start taking place as soon as you press [Enter], so review the command before committing to it.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 6. Troubleshooting Installation on an Intel® or AMD System This appendix discusses some common installation problems and their solutions. 6.1. You are Unable t o Boot Red Hat Ent erprise Linux 6.1.1. Are You Unable t o Boot Wit h 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.
Chapt er 6 . T roubleshoot ing Inst allat ion on an Int el® or AMD Syst em For more information concerning signal 11 errors, refer to: http://www.bitwizard.nl/sig11/ 6.2. T rouble Beginning t he Inst allat ion 6.2.1. Problems wit h Boot ing int o t he Graphical Inst allat ion 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 6.3.3. T rouble wit h Part it ion T ables If you receive an error after the Disk Partitioning Setup (Section 4.16, “ D isk Partitioning Setup” ) phase of the installation saying something similar to The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL D ATA on this drive.
Chapt er 6 . T roubleshoot ing Inst allat ion on an Int el® or AMD Syst em Note When defining a partition's type as swap, you do not have to assign it a mount point. D isk D ru id automatically assigns the mount point for you. 6.3.7. Are You Seeing Pyt hon Errors? D uring some upgrades or installations of Red Hat Enterprise Linux, the installation program (also known as an aco n d a) may fail with a Python or traceback error.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If you are experiencing problems with GRUB, you may need to disable the graphical boot screen. To do this, become the root user and edit the /boot/grub/grub.conf file. Within the grub.conf file, comment out the line which begins with splashimage by inserting the # character at the beginning of the line. Press Enter to exit the editing mode. Once the boot loader screen has returned, type b to boot the system. Once you reboot, the grub.
Chapt er 6 . T roubleshoot ing Inst allat ion on an Int el® or AMD Syst em When you are satisfied with your change, save and exit the file using the Ctrl+Q keys. A window appears and asks if you would like to save the changes. Click Save. The next time you log in after rebooting your system, you are presented with a graphical login prompt. 6.4 .3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Once the boot loader screen has returned, type b to boot the system. Once you have booted into single user mode and have access to the # prompt, you must type passwd root, which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password. If you cannot remember your user account password, you must become root. To become root, type su - and enter your root password when prompted.
Chapt er 6 . T roubleshoot ing Inst allat ion on an Int el® or AMD Syst em Remember to replace xx with the amount of RAM in your system. Press Enter to boot. 6.4 .7. Your Print er Does Not Work If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the Prin t er C o n f ig u rat io n T o o l. Type the system-config-printer command at a shell prompt to launch the Prin t er C o n f ig u rat io n T o o l.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 7. Updating drivers during installation on Intel and AMD systems In most cases, Red Hat Enterprise Linux already includes drivers for the devices that make up your system. However, if your system contains hardware that has been released very recently, drivers for this hardware might not yet be included.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation process, consider performing an initial RAM disk driver update — refer to Section 7.2.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 7.2.1. Preparing t o use a driver updat e image file 7 .2 .1 .1 . Pre paring t o use an im age file o n lo cal st o rage To make the ISO image file available on local storage, such as a USB flash drive, USB hard drive, or local ID E hard drive, simply copy the file onto the storage device. You can rename the file if you find it helpful to do so, but you must not change the filename extension, which must remain .iso.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems Refer to Section 7.3.2, “ Let the installer prompt you for a driver update” and Section 7.3.4, “ Use a boot option to specify a driver update image file on a network” to learn how to specify this network location during installation. 7.2.2. Preparing a driver updat e disk You can use a variety of media to create a driver update disk, including CD , D VD , floppy disk, and USB storage devices such as USB flash drives 7 .2 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide 2. Right-click on this file and choose Write to disc. You will see a window similar to the following: Fig u re 7.3. C D /D VD C reat o r' s Writ e t o D isc d ialo g 3. Click the Write button. If a blank disc is not already in the drive, C D /D VD C reat o r will prompt you to insert one. After you burn a driver update disk CD or D VD , verify that the disk was created successfully by inserting it into your system and browsing to it using the file manager.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems Fig u re 7.4 . C o n t en t s o f a t yp ical d river u p d at e d isc o n C D o r D VD If you see only a single file ending in .iso, then you have not created the disk correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system. Refer to Section 7.3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 1. Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example, /dev/fd0 for a floppy disk in the first floppy drive on your system. If you do not know the device name, become root and use the command fdisk -l on the command line. You will see a list of all storage devices available on your system.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img 5. Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation. This directory is placed under the /tftpboot/pxelinux/ directory. For example, /tftpboot/pxelinux/r5su3/ might hold the PXE target for Red Hat Enterprise Linux 5.3 Server. 6. Edit the /tftpboot/pxelinux/pxelinux.
Red Hat Ent erprise Linux 5 Inst allat ion G uide installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 7.2.1.1, “ Preparing to use an image file on local storage” to prepare a storage device for the installer to find. 7.3.2. Let t he inst aller prompt you for a driver updat e 1. Begin the installation normally for whatever method you have chosen.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems Fig u re 7.6 . T h e d river d isk p ro mp t 2. Insert the driver update disk that you created on CD , D VD , floppy disk, or USB storage device and select Yes. The installer examines the storage devices that it can detect.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 7.4 . Specifying t he locat ion of a driver updat e image file or driver updat e disk If the installer detects more than one possible device that could hold a driver update, it prompts you to select the correct device. If you are not sure which option represents the device on which the driver update is stored, try the various options in order until you find the correct one. Fig u re 7.7.
Chapt er 7 . Updat ing drivers during inst allat ion on Int el and AMD syst ems Fig u re 7.8. Select in g a d river d isk p art it io n The installer prompts you to specify which file contains the driver update: Fig u re 7.9 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a floppy disk, CD , or D VD . Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk).
Chapt er 8 . Addit ional Boot O pt ions for Int el® and AMD Syst ems Chapter 8. Additional Boot Options for Intel® and AMD Systems This section 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide this command gives you the option of testing the integrity of the install source (if an ISObased method). this command works with the CD , D VD , hard drive ISO, and NFS ISO installation methods. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during an installation. mem=xxxm this command allows you to override the amount of memory the kernel detects for the machine.
Chapt er 8 . Addit ional Boot O pt ions for Int el® and AMD Syst ems nopass this command disables the passing of keyboard and mouse information to stage 2 of the installation program. It can be used to test keyboard and mouse configuration screens during stage 2 of the installation program when performing a network installation. nopcmcia this command ignores any PCMCIA controllers in system. noprobe this command disables hardware detection and instead prompts the user for hardware information.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 9 . T he G RUB Boot Loader 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. 9.1.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 3. The Stage 2 or secondary boot loader is read into memory. The secondary boot loader displays the GRUB menu and command environment. This interface allows the user to select which kernel or operating system to boot, pass arguments to the kernel, or look at system parameters. 4. The secondary boot loader reads the operating system or kernel as well as the contents of /boot/sysroot/ into memory.
Chapt er 9 . T he G RUB Boot Loader Before installing GRUB, make sure to use the latest GRUB package available or use the GRUB package from the installation CD -ROMs. For instructions on installing packages, see the chapter titled Package Management with RPM in the Red Hat Enterprise Linux D eployment Guide. Once the GRUB package is installed, open a root shell prompt and run the command /sbin/grubinstall , where is the location that the GRUB Stage 1 boot loader should be installed.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The is the BIOS device number. The primary ID E hard drive is numbered 0 and a secondary ID E hard drive is numbered 1. This syntax is roughly equivalent to that used for devices by the kernel. For example, the a in hda for the kernel is analogous to the 0 in hd0 for GRUB, the b in hdb is analogous to the 1 in hd1, and so on. The specifies the number of a partition on a device.
Chapt er 9 . T he G RUB Boot Loader This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200. Knowing how to write blocklists is useful when using GRUB to load operating systems which require chain loading. It is possible to leave off the offset number of blocks if starting at block 0.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Refer to Section 9.7, “ GRUB Menu Configuration File” for more information on configuring this interface. Menu Entry Editor Interface To access the menu entry editor, press the e key from the boot loader menu.
Chapt er 9 . T he G RUB Boot Loader boot — Boots the operating system or chain loader that was last loaded. chainloader — Loads the specified file as a chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, +1, instead of the file name. The following is an example chainloader command: chainloader +1 displaymem — D isplays the current use of memory, based on information from the BIOS.
Red Hat Ent erprise Linux 5 Inst allat ion G uide root (,) — Configures the root partition for GRUB, such as (hd0,0), and mounts the partition. The following is an example root command: root (hd0,0) rootnoverify (,) — Configures the root partition for GRUB, just like the root command, but does not mount the partition. Other commands are also available; type help --all for a full list of commands.
Chapt er 9 . T he G RUB Boot Loader Configuring a GRUB menu configuration file to boot multiple operating systems is beyond the scope of this chapter. Consult Section 9.9, “ Additional Resources” for a list of additional resources. 9.7.2. Configurat ion File Direct ives The following are directives commonly used in the GRUB menu configuration file: chainloader — Loads the specified file as a chain loader. Replace with the absolute path to the chain loader.
Red Hat Ent erprise Linux 5 Inst allat ion G uide splashimage= — Specifies the location of the splash screen image to be used when GRUB boots. title group-title — Specifies a title to be used with a particular group of commands used to load a kernel or operating system. To add human-readable comments to the menu configuration file, begin the line with the hash mark character (#). 9.8.
Chapt er 9 . T he G RUB Boot Loader Red Hat Enterprise Linux D eployment Guide; Red Hat, Inc. — The Workstation Security chapter explains, in a concise manner, how to secure the GRUB boot loader. [4] Fo r mo re o n the s ys tem BIO S and the MBR, refer to Sec tio n 33.2.1, “ The BIO S” .
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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: / — The Intel website on the Itanium Processor http://developer.intel.com/technology/efi/index.htm?iid=sr+efi — The Intel website for the Extensible Firmware Interface (EFI) http://www.itanium.
P art II. IBM PO WER Archit ect ure - Inst allat ion and Boot ing 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 11. Steps to Get You Started 11.1. Upgrade or Inst all? For information to help you determine whether to perform an upgrade or an installation refer to Chapter 24, Upgrading Your Current System. 11.2. Preparat ion for IBM eServer Syst em p and Syst em i The IBM eServer System p and IBM eServer System i systems introduce many options for partitioning, virtual or native devices, and consoles.
Chapt er 1 1 . St eps t o G et You St art ed have one or more partitions that may be deleted, thereby freeing up enough disk space to install Red Hat Enterprise Linux. To gain a better sense of how much space you really need, refer to the recommended partitioning sizes discussed in Section 12.19.4, “ Recommended Partitioning Scheme” . 11.4 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide where dvd refers to your D VD drive device. 11.5.1. Preparing for FT P and HT T P inst allat ion If you are setting up an installation tree for NFS, FTP, or HTTP installations, you must copy the RELEASE-NOTES files and all files from the RedHat directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD -ROM/ISO image): 1.
Chapt er 1 1 . St eps t o G et You St art ed Ensure that the /publicly/available/directory directory is exported via NFS via an entry in /etc/exports. To export to a specific system: /publicly/available/directory client.ip.address To export to all systems use an entry such as: /publicly/available/directory * Start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start).
Red Hat Ent erprise Linux 5 Inst allat ion G uide [5] Unp artitio ned d is k s p ac e means that availab le d is k s p ac e o n the hard d rive(s ) yo u are ins talling to has no t b een d ivid ed into s ec tio ns fo r d ata. When yo u p artitio n a d is k, eac h p artitio n b ehaves like a s ep arate d is k d rive.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems 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 D VD /CD -ROM, using the graphical, mouse-based installation program.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 12.2. Boot ing t he IBM Syst em i or IBM Syst em p Inst allat ion Program To boot an IBM System i or IBM System p system from a CD -ROM, you must specify the install boot device in the System Management Services (SMS) menu. To enter the System Management Services GUI, press the 1 key during the boot process when you hear the chime sound. This brings up a graphical interface similar to the one described in this section.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems The Red Hat Enterprise Linux installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five virtual consoles, among which you can switch using a single keystroke combination.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.2. In st allat io n Pro g ram Wid g et s as seen in Boot Loader Configuration Fig u re 12.3.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems 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.3, “ Installation Program Widgets as seen in D isk D ruid” : Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior). 12.6. Beginning Inst allat ion 12.6.1. Inst alling from DVD/CD-ROM To install Red Hat Enterprise Linux from a D VD /CD -ROM, place the D VD or CD #1 in your D VD /CD ROM drive and boot your system from the D VD /CD -ROM.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.4 . Select in g Part it io n D ialo g f o r H ard D rive In st allat io n 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 /.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.5. T C P/IP C o n f ig u rat io n 12.9. Inst alling via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected N FS Imag e 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.6 . N FS Set u p D ialo g 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. 12.10. Inst alling via FT P The FTP dialog applies only if you are installing from an FTP server (that is, if you used the askmethod boot options and selected FT P in the Installation Method dialog).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.7. FT P Set u p D ialo g 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems The HTTP dialog applies only if you are installing from an HTTP server (that is, if you used the askmethod boot option and selected H T T P in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 12.12. Welcome t o Red Hat Ent erprise 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.11 by clicking on the Release Notes button. Click on the Next button to continue. 12.13. Language Select ion Using your mouse, select a language to use for the installation (refer to Figure 12.9, “ Language Selection” ).
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.9 . Lan g u ag e Select io n Once you select the appropriate language, click Next to continue. 12.14 . Keyboard Configurat ion 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.10. K eyb o ard C o n f ig u rat io n Note To change your keyboard layout type after you have completed the installation, use the K eyb o ard C o n f ig u rat io n T o o l. Type the system-config-keyboard command in a shell prompt to launch the K eyb o ard C o n f ig u rat io n T o o l. If you are not root, it prompts you for the root password to continue. 12.15.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.11. In st allat io n N u mb er 12.16. Disk Part it ioning Set up 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 26, An Introduction to Disk Partitions for more information.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning The U p d at e Ag en t 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. Fig u re 12.12. D isk Part it io n in g Set u p If you choose to create a custom layout using D isk D ru id , refer to Section 12.19, “ Partitioning Your System” .
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: " The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL D ATA on this drive." No matter what type of installation you are performing, backups of the existing data on your systems should always be made.
Red Hat Ent erprise Linux 5 Inst allat ion G uide ISCSI target and clicking on the Add Drive button. If a network connection is not already active, the installer prompts you to provide details of your network interface. Select your network interface from the drop-down menu, then either leave the Use dynamic IP configuration box checked, or uncheck it to enter the IP address of your system and the IP addresses of the gateway and nameserver on your network. Ensure that the Enable IPv4 box remains checked.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.15. C o n f ig u re ISC SI Paramet ers 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. 12.18. Creat e Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.16 . C reat e D ef au lt Layo u t 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. Warning It is always a good idea to back up any data that you have on your systems.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Note [This text does not apply to iSeries system users.] If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the /boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.17. Part it io n in g wit h D isk D ru id o n IB M Syst em p an d Syst em i syst ems The partitioning tool used by the installation program is D isk D ru id . With the exception of certain esoteric situations, D isk D ru id can handle the partitioning requirements for a typical installation. 12.19.1. Graphical Display of Hard Drive(s) D isk D ru id offers a graphical representation of your hard drive(s).
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems 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. You can also edit free space as represented in the graphical display to create a new partition within that space.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Hide RAID device/LVM Volume Group members: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created. 12.19.4 . Recommended Part it ioning Scheme Unless you have a reason for doing otherwise, we recommend that you create the following partitions: A swap partition (at least 256 MB) — swap partitions are used to support virtual memory.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups. Warning — do not place /var on network storage Red Hat Enterprise Linux 5.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.18. C reat in g a N ew Part it io n 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. Force to be a primary partition: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to Section 26.1.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 12.20. Net work Configurat ion 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 12.21, “ Time Z one Configuration” . Fig u re 12.19 . N et wo rk C o n f ig u rat io n The installation program automatically detects any network devices you have and displays them in the Network Devices list. When you have selected a network device, click Edit.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.20. Ed it in g a N et wo rk D evice Note D o 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 12.21. T ime Zone Configurat ion 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Note To change your time zone configuration after you have completed the installation, use the T ime an d D at e Pro p ert ies T o o l. Type the system-config-date command in a shell prompt to launch the T ime an d D at e Pro p ert ies T o o l. If you are not root, it prompts you for the root password to continue. To run the T ime an d D at e Pro p ert ies T o o l as a text-based application, use the command timeconfig. 12.22.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.22. R o o t Passwo rd 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. Note 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Note D o not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk. Note To change your root password after you have completed the installation, use the R o o t Passwo rd T o o l. Type the system-config-rootpassword command in a shell prompt to launch the R o o t Passwo rd T o o l. If you are not root, it prompts you for the root password to continue. 12.23.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 12.23. Packag e G ro u p Select io n 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.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems Fig u re 12.24 . Packag e G ro u p D et ails 12.24 . Preparing t o Inst all 12.24 .1. Prepare t o Inst all 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 12.25. Inst alling 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. 12.26. Inst allat ion Complet e Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot.
Chapt er 1 2 . Inst alling on IBM Syst em i and IBM Syst em p syst ems [7] A ro o t p as s wo rd is the ad minis trative p as s wo rd fo r yo ur Red Hat Enterp ris e Linux s ys tem. Yo u s ho uld o nly lo g in as ro o t when need ed fo r s ys tem maintenanc e. The ro o t ac c o unt d o es no t o p erate within the res tric tio ns p lac ed o n no rmal us er ac c o unts , s o c hang es mad e as ro o t c an have imp lic atio ns fo r yo ur entire s ys tem.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 13. Updating drivers during installation on IBM POWER systems In most cases, Red Hat Enterprise Linux already includes drivers for the devices that make up your system. However, if your system contains hardware that has been released very recently, drivers for this hardware might not yet be included.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation process, consider performing an initial RAM disk driver update — refer to Section 13.2.3, “ Preparing an initial RAM disk update” .
Red Hat Ent erprise Linux 5 Inst allat ion G uide 13.2.1. Preparing t o use a driver updat e image file 1 3.2 .1 .1 . Pre paring t o use an im age file o n lo cal st o rage To make the ISO image file available on local storage, such as a USB flash drive, USB hard drive, or local ID E hard drive, simply copy the file onto the storage device. You can rename the file if you find it helpful to do so, but you must not change the filename extension, which must remain .iso.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems Refer to Section 13.3.2, “ Let the installer prompt you for a driver update” and Section 13.3.4, “ Use a boot option to specify a driver update image file on a network” to learn how to specify this network location during installation. 13.2.2. Preparing a driver updat e disk You can use a variety of media to create a driver update disk, including CD , D VD , floppy disk, and USB storage devices such as USB flash drives 1 3.2 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide 2. Right-click on this file and choose Write to disc. You will see a window similar to the following: Fig u re 13.3. C D /D VD C reat o r' s Writ e t o D isc d ialo g 3. Click the Write button. If a blank disc is not already in the drive, C D /D VD C reat o r will prompt you to insert one.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems Fig u re 13.4 . C o n t en t s o f a t yp ical d river u p d at e d isc o n C D o r D VD If you see only a single file ending in .iso, then you have not created the disk correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system. Refer to Section 13.3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 1. Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example, /dev/fd0 for a floppy disk in the first floppy drive on your system. If you do not know the device name, become root and use the command fdisk -l on the command line. You will see a list of all storage devices available on your system.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img 5. Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation. This directory is placed under the /tftpboot/pxelinux/ directory. For example, /tftpboot/pxelinux/r5su3/ might hold the PXE target for Red Hat Enterprise Linux 5.3 Server. 6. Edit the /tftpboot/pxelinux/pxelinux.
Red Hat Ent erprise Linux 5 Inst allat ion G uide installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 13.2.1.1, “ Preparing to use an image file on local storage” to prepare a storage device for the installer to find. 13.3.2. Let t he inst aller prompt you for a driver updat e 1. Begin the installation normally for whatever method you have chosen.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems Fig u re 13.6 . T h e d river d isk p ro mp t 2. Insert the driver update disk that you created on CD , D VD , floppy disk, or USB storage device and select Yes. The installer examines the storage devices that it can detect.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 13.4 . Specifying t he locat ion of a driver updat e image file or driver updat e disk If the installer detects more than one possible device that could hold a driver update, it prompts you to select the correct device. If you are not sure which option represents the device on which the driver update is stored, try the various options in order until you find the correct one. Fig u re 13.7.
Chapt er 1 3. Updat ing drivers during inst allat ion on IBM PO WER syst ems Fig u re 13.8. Select in g a d river d isk p art it io n The installer prompts you to specify which file contains the driver update: Fig u re 13.9 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a floppy disk, CD , or D VD . Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk).
Chapt er 1 4 . T roubleshoot ing Inst allat ion on an IBM PO WER Syst em 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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. One possible solution is to try using the resolution= boot option. Refer to Chapter 15, Additional Boot Options for IBM Power Systems for more information.
Chapt er 1 4 . T roubleshoot ing Inst allat ion on an IBM PO WER Syst em No matter what type of installation you are performing, backups of the existing data on your systems should always be made. 14 .3.4 . Ot her Part it ioning Problems for IBM™ POWER Syst em Users If you are using D isk D ru id to create partitions, but cannot move to the next screen, you probably have not created all the partitions necessary for D isk D ru id 's dependencies to be satisfied.
Red Hat Ent erprise Linux 5 Inst allat ion G uide http://fedoraproject.org/wiki/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.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/ 14 .4 . Problems Aft er Inst allat ion 14 .4 .1.
Chapt er 1 4 . T roubleshoot ing Inst allat ion on an IBM PO WER Syst em Warning Change only the number of the default runlevel from 3 to 5. Your changed line should look like the following: id:5:initdefault: When you are satisfied with your change, save and exit the file using the Ctrl+Q keys. A window appears and asks if you would like to save the changes. Click Save. The next time you log in after rebooting your system, you are presented with a graphical login prompt. 14 .4 .3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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. If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at: http://hardware.redhat.com/hcl/ 14 .4 .6.
Chapt er 1 5. Addit ional Boot O pt ions for IBM Power Syst ems Chapter 15. Additional Boot Options for IBM Power Systems This section 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide megabytes. mpath enables multipath support. Important — mandatory for installation on multipath devices If you install Red Hat Enterprise Linux 5.11 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. noeject do not eject optical discs after installation.
Chapt er 1 5. Addit ional Boot O pt ions for IBM Power Syst ems resolution= tells the installation program which video mode to run. it accepts any standard resolution, such as 640x480, 800x600, 1024x768, and so on. serial this command turns on serial console support. text this command disables the graphical installation program and forces the installation program to run in text mode.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 1 6 . St eps t o G et You St art ed Chapter 16. Steps to Get You Started 16.1. Pre-Inst allat ion 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/ 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The network configuration must be determined beforehand. Red Hat Enterprise Linux for IBM System z supports QD IO-enabled (Queued D irect 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.
Chapt er 1 6 . St eps t o G et You St art ed 16.4 .1. Preparing for FT P and HT T P inst allat ion If you are setting up an installation tree for NFS, FTP, or HTTP installations, you must copy the RELEASE-NOTES files and all files from the RedHat directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD -ROM/ISO image): 1. Insert CD -ROM or D VD -ROM. 2. mount /media/cdrom 3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide /publicly/available/directory client.ip.address To export to all systems use an entry such as: /publicly/available/directory * Start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload). Be sure to test the NFS share following the directions in the Red Hat Enterprise Linux D eployment Guide. 16.5.
Chapt er 1 6 . St eps t o G et You St art ed 16.6. Inst alling under z /VM Log onto z/VM as the Linux guest account. You can use x3270 or c3270 (from the x3270-text package in Red Hat Enterprise Linux) to log in to z/VM from other Linux systems. Alternatively, use the 3270 terminal emulator on the IBM System z management console. If you are working from a Windows based machine, Jolly Giant (http://www.jollygiant.com) offers an SSL-enabled 3270 emulator. If you are not in CMS mode, enter it now.
Red Hat Ent erprise Linux 5 Inst allat ion G uide root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc The content of the redhat.exec file shipped by Red Hat is: /* */ 'cl rdr' 'purge rdr all' 'spool punch * rdr' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'ch rdr all keep nohold' 'i 00c' Example redhat.conf file: HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.
Chapt er 1 6 . St eps t o G et You St art ed qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id, data_device_bus_id" lcs: SUBCHANNELS="read_device_bus_id,write_device_bus_id" For example (a sample qeth SUBCHANNEL statement): SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 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: lcs, or qeth.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Where mtu is the Maximum Transmission Unit (MTU) for this connection. DNS=server1:server2::serverN Where server1:server2::serverN is a list of D NS servers, separated by colons. For example: DNS=10.0.0.1:10.0.0.2 SEARCHDNS=domain1:domain2::domainN Where domain1:domain2::domainN is a list of the search domains, separated by colons. For example: SEARCHDNS=example.com:example.
Chapt er 1 6 . St eps t o G et You St art ed Update for Red Hat Enterprise Linux 5.3 Anaconda now supports both ports on CHPID for OSA Express3 cards. The installer will prompt for the port number in the initial stage of the installation. The value provided for the port also affects installed network interface startup script. When port 1 is selected, the value " portno=1" is added to OPTIONS parameter of ifcfg-eth* file.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Once all questions have been answered, you are ready to begin the core installation program, lo ad er. To continue with the installation, refer to Chapter 17, Installing on IBM System z Systems for further instructions. 16.7. Inst alling in an LPAR using t he Red Hat Ent erprise Linux LPAR CD The following steps must be taken when installing onto an LPAR.
Chapt er 1 6 . St eps t o G et You St art ed Click Continue. In the dialog that follows, keep the default selection of redhat.ins and click Continue. Refer to Section 16.9, “ Installing in an LPAR (Common Steps)” to continue. 16.9. Inst alling in an LPAR (Common St eps) 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 O p erat in g Syst em Messag es.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.1. In st allat io n Pro g ram Wid g et s as seen in D isk D ru id Here is a list of the most important widgets shown in Figure 17.1, “ Installation Program Widgets as seen in D isk D ruid” : Text Widget — Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes.
Red Hat Ent erprise Linux 5 Inst allat ion G uide To " press" a button, position the cursor over the button (using Tab, for example) and press Space or Enter. To select an item from a list of items, move the cursor to the item you wish to select and press Enter. To select an item with a checkbox, move the cursor to the checkbox and press Space to select an item. To deselect, press Space a second time.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems the Linux Image. Allow the Linux image to connect to the workstation using the command xhost +linuxvm on the local workstation. If the graphical installation via NFS does not automatically begin for you, verify the DISPLAY= variable settings in the parm file. If performing a VM installation, rerun the installation to load the new parm file on the reader.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 17.2. N FS Set u p D ialo g 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. 17.6. Inst alling via FT P The FTP dialog applies only if you are installing from an FTP server (that is, if you used the askmethod boot options and selected FT P in the Installation Method dialog).
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.3. FT P Set u p D ialo g 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The HTTP dialog applies only if you are installing from an HTTP server (that is, if you used the askmethod boot option and selected H T T P in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems 17.8. Welcome t o Red Hat Ent erprise 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.11 by clicking on the Release Notes button. Click on the Next button to continue. 17.9. Language Select ion Using your mouse, select a language to use for the installation (refer to Figure 17.5, “ Language Selection” ).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 17.5. Lan g u ag e Select io n Once you select the appropriate language, click Next to continue. 17.10. Ent er t he Inst allat ion Number Enter your Installation Number (refer to Figure 17.6, “ Installation Number” ). This number will determine the package selection set that is available to the installer. If you choose to skip entering the installation number you will be presented with a basic selection of packages to install later on.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.6 . In st allat io n N u mb er 17.11. Disk Part it ioning Set up 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).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning — vdisks, tdisks, and default layout The default layout uses all devices made available to the installer. This includes any temporary storage devices such as vdisks or tdisks. If temporary storage devices are used with the default layout, the system might become inaccessible when these devices are redefined and the device contents are lost (for example, on logoff and relogon of z/VM guests).
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: " The partition table on device dasda was unreadable. To create new partitions it must be initialized, causing the loss of ALL D ATA on this drive." you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
Red Hat Ent erprise Linux 5 Inst allat ion G uide For more information on these values, refer to the hardware documentation that came with your system and check with the system administrator who has setup the network for this system. Fig u re 17.8. Ad van ced St o rag e O p t io n s To configure a Fiber Channel Protocol SCSI device invoke the 'Add FCP device' dialog by selecting 'Add Z FCP LUN' and clicking on the 'Add D rive' button.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.9 . C o n f ig u re FC P D evice The newly added device should then be present and usable during the Disk Druid portion of the installation.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 17.10. C o n f ig u re FC P D evice Note The installer requires that at least one ECKD D ASD be defined. In the situation where a SCSIonly installation is desired a D ASD = 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 D ASD , while resulting in a SCSI-only environment. 17.13.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Warning If you select this option, all data on the selected D ASD and SCSI storage drive(s) is removed by the installation program. D o 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Warning 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.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems 17.14 .1. Graphical Display of DASD Device(s) D isk D ru id offers a graphical representation of your D ASD device(s). Using your mouse, click once to highlight a particular field in the graphical display. D ouble-click to edit an existing partition or to create a partition out of existing free space.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Hide RAID device/LVM Volume Group members: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created. 17.14 .4 . Recommended Part it ioning Scheme Configuring efficient swap space for Linux on System z is a complex task. It very much depends on the specific environment and should be tuned to the actual system load.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.13. N et wo rk C o n f ig u rat io n The installation program automatically detects any network devices you have and displays them in the Network Devices list. When you have selected a network device, click Edit. From the Edit Interface dialog, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device to use D HCP or to use static settings.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 17.14 . Ed it in g a N et wo rk D evice Note D o 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.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection. Fig u re 17.15. C o n f ig u rin g t h e T ime Z o n e Select System Clock uses UTC if you know that your system is set to UTC. Note To change your time zone configuration after you have completed the installation, use the T ime an d D at e Pro p ert ies T o o l.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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. The root account is used to install packages, upgrade RPMs, and perform most system maintenance. Logging in as root gives you complete control over your system.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Note 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 password [10 ] for your system. You cannot proceed 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.17, “ Package Group Selection” ). Fig u re 17.17.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems Fig u re 17.18. Packag e G ro u p D et ails 17.19. Preparing t o Inst all 17.19.1. Preparing t o Inst all 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 17.20. Inst alling 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. 17.21. Inst allat ion Complet e Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot.
Chapt er 1 7 . Inst alling on IBM Syst em z Syst ems For information on registering your Red Hat Enterprise Linux subscription, refer to Chapter 25, Register Your System and Apply Subscriptions. [10 ] A ro o t p as s wo rd is the ad minis trative p as s wo rd fo r yo ur Red Hat Enterp ris e Linux s ys tem. Yo u s ho uld o nly lo g in as ro o t when need ed fo r s ys tem maintenanc e.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 18. Removing Red Hat Enterprise Linux To remove from the S/390 you can either remove the D ASD allocation from the VM or you can start the installation program and re-format all of the D ASD partitions. Instead of selecting OK you will select Cancel to exit the installation program.
Chapt er 1 9 . Sample Paramet er Files Chapter 19. Sample Parameter Files The IBM System z architectures use a special parameter file to set up networking before the installation program (an aco n d a) 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 D ASD should be used to configure the initial network setup and the D ASD specification.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 1 9 . Sample Paramet er Files PORTNAME=osa_portname | lcs_portnumber This variable supports OSA devices operating in qdio mode or in non-qdio mode. When using qdio mode: osa_portname is the portname specified on the OSA device when operating in qeth mode. PORTNAME is only required for z/VM 4.3 or older without APARs VM63308 and PQ73878. When using non-qdio mode: lcs_portnumber is used to pass the relative port number as integer in the range of 0 through 15.
Red Hat Ent erprise Linux 5 Inst allat ion G uide root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc Example of redhat.conf file (pointed to by CMSCONFFILE in redhat.parm) DASD=200 HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.
Chapt er 2 0 . Addit ional Boot O pt ions Chapter 20. Additional Boot Options This section 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. You can also store kernel boot options for the z/IPL boot loader in the zipl.conf file, either by editing the file manually or using the z ip l tool. Kernel parameters in zipl.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Important — mandatory for installation on multipath devices If you install Red Hat Enterprise Linux 5.11 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. noeject do not eject optical discs after installation.
Chapt er 2 1 . T roubleshoot ing Inst allat ion on an IBM Syst em z Syst em Chapter 21. Troubleshooting Installation on an IBM System z System This appendix discusses some common installation problems and their solutions. 21.1. You are Unable t o Boot Red Hat Ent erprise Linux 21.1.1. Is Your Syst em 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide A partition of type swap Note When defining a partition's type as swap, do not assign it a mount point. D isk D ru id automatically assigns the mount point for you. 21.2.4 . Are You Seeing Pyt hon Errors? D uring some upgrades or installations of Red Hat Enterprise Linux, the installation program (also known as an aco n d a) may fail with a Python or traceback error.
Chapt er 2 1 . T roubleshoot ing Inst allat ion on an IBM Syst em z Syst em 21.3.1. Remot e Graphical Deskt ops and XDMCP If you have installed the X Window System and would like to log in to your Red Hat Enterprise Linux system using a graphical login manager, enable the X Display Manager Control Protocol (XD MCP). This protocol allows users to remotely log in to a desktop environment from any X Window System compatible client (such as a network-connected workstation or X terminal).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Type the system-config-printer command at a shell prompt to launch the Prin t er C o n f ig u rat io n T o o l. If you are not root, it prompts you for the root password to continue. 21.3.4 . Apache-based httpd service/Sendmail Hangs During St art up If you are having trouble with the Apache-based httpd service or Sendmail hanging at startup, make sure the following line is in the /etc/hosts file: 127.0.0.1 222 localhost.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users Chapter 22. Additional Information for IBM System z Users 22.1. T he sysfs File Syst em 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 22.2. Using t he zFCP Driver D uring the initial installation, you are prompted to enter SCSI/FCP information. If this information is entered, it creates the /etc/zfcp.conf file which contains your SCSI configuration. It also adds the line alias scsi_hostadapter zFCP to /etc/modprobe.conf. This loads the required zFCP modules. # cat /etc/zfcp.conf 0.0.010a 0x01 0x5005076300c18154 0x00 0x5719000000000000 # cat /etc/modprobe.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/scsi_host_no 0x0 # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id 0x1 # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun 0x0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.
Red Hat Ent erprise Linux 5 Inst allat ion G uide `/tmp/initrd.cT1534/lib/dasd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_eckd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_fba_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko' -> `/tmp/initrd.cT1534/lib/jbd.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko' -> `/tmp/initrd.cT1534/lib/ext3.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users Create a RAID device Create a multipath device 22.3.1. Creat ing a RAID Device Wit h mdadm To create a RAID device, edit the /etc/mdadm.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Spare Devices : 0 Chunk Size : 64K Number Major Minor RaidDevice State 0 8 1 0 active sync 1 8 17 1 active sync 2 8 33 2 active sync 3 8 49 3 active sync UUID : 25c0f2a1:e882dfc0:c0fe135e:6940d932 Events : 0.1 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 22.3.2.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users Version : 00.90.00 Creation Time : Tue Mar 2 10:56:37 2004 Raid Level : multipath Array Size : 3905408 (3.72 GiB 3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 00: 010A QDIO-ELIGIBLE Ready; T=0.01/0.01 15:51:29 QIOASSIST-ELIGIBLE i 010a 00: I 010A 00: HCPLDI2816I Acquiring the machine loader from the processor controller. 00: HCPLDI2817I Load completed from the processor controller. 00: HCPLDI2817I Now starting machine loader version 0001. 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 00. 00: MLOEVL012I: Machine loader up and running (version 0.13).
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users # cat online 0 3. If it is not online, run the following command to bring it online: # echo 1 > online # cat online 1 4.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 32768 blocks per group, 32768 fragments per group 15840 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 39 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Using modules: ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: 'linux' Syncing disks... Done. 22.6. Adding a Net work Device The process of adding a network device has changed with the migration of the 2.4 kernel to the 2.6 kernel: The proc file system is no longer used to control or obtain status on network devices. The new sys file system now provides facilities for controlling devices.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users # echo 0.0.0600,0.0.0601,0.0.0602 > /sys/bus/ccwgroup/drivers/qeth/group Next, verify that the qeth group device was created properly: # ls /sys/bus/ccwgroup/drivers/qeth 0.0.0600 0.0.09a0 group notifier_register You may optionally add a portname. First, you must check to see if a portname is required: # cat /sys/bus/ccwgroup/drivers/qeth/0.0.
Red Hat Ent erprise Linux 5 Inst allat ion G uide fake_ll ipa_takeover portno priority_queueing recover route4 rxip ungroup vipa For information on how these features work, refer to http://www-05.ibm.com/ebusiness/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC33-8289-02 (Device Drivers, Features, and Commands - SC33-8289-02). Now you need to create the configuration file for your new interface. The network interface configuration files are placed in /etc/sysconfig/network-scripts/.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users Make sure the SUBCHANNELS statement matches the hardware addresses for your qeth device. /etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.70.87 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet A qeth device requires an alias definition in /etc/modprobe.conf. Edit this file and add an alias for your interface. /etc/modprobe.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Destination 192.168.70.0 9.12.20.0 169.254.0.0 default Gateway * * * pdlrouter-if5.p Genmask 255.255.255.0 255.255.255.0 255.255.0.0 0.0.0.0 Flags U U U UG Metric 0 0 0 0 Ref 0 0 0 0 Use 0 0 0 0 Iface eth1 eth0 eth1 eth0 Verify your changes by using the ping command to ping the gateway: # ping -c 1 192.168.70.8 PING 192.168.70.8 (192.168.70.8) 56(84) bytes of data. 64 bytes from 192.168.70.8: icmp_seq=0 ttl=63 time=8.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users OSA cards can provide up to 16 ports for a single CHPID . By default, the LCS group device uses port 0. To use a different port, issue a command similar to the following: # echo portno > /sys/bus/ccwgroup/drivers/lcs/device_bus_id/portno For more information about configuration of the LCS driver, refer to the following: http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The QETH network device driver supports IBM System z HiperSockets, OSA-Express Fast Ethernet, Gigabit Ethernet (including 1000Base-T), High Speed Token Ring, and ATM features (running Ethernet LAN emulation) in QD IO mode.
Chapt er 2 2 . Addit ional Informat ion for IBM Syst em z Users 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 Based on the type interface being added, the D EVICE parameter should be like one of the following: DEVICE=hsin DEVICE=ethn DEVICE=trn Activate the device. Based on the type interface being added, issue an ifup command: # ifup hsin # ifup ethn # ifup trn 22.7.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Note D isabling periodic timer interrupts can violate basic assumptions in system accounting tools. If you notice a malfunction related to system accounting, verify that the malfunction disappears if periodic timer interrupts are enabled, then submit a bug at http://bugzilla.redhat.com/bugzilla/ (for malfunctioning bundled tools), or inform the tool vendor (for malfunctioning third-party tools).
P art IV. Common T asks 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 23. Updating Your System 23.1. Driver updat e rpm packages Occasionally, when a new piece of hardware is not yet supported in the kernel that you have installed, Red Hat or a hardware vendor might make a driver update available.
Chapt er 2 3. Updat ing Your Syst em To install a new driver update rpm package: 1. D ownload the driver update rpm package from the location specified by Red Hat or your hardware vendor. The package file name will begin with kmod (short for kernel module) and have a form similar to this example: kmod-i pw3945-1 .2.04 .17.el5.i686.rpm In the example, the driver update rpm package supplies an Intel IPW3945 WiFi driver update with version number 1.2.0-4.17 for Red Hat Enterprise Linux 5, on i686 systems.
Red Hat Ent erprise Linux 5 Inst allat ion G uide $ rpm -ivh kmod-ipw3945-1.2.04.17.el5.i686 3. Whether you used a graphical install, or a command line install, reboot your system to ensure your system is using the new driver. If Red Hat ships a kernel errata update before the next release of Red Hat Enterprise Linux, your system will continue to use the driver updates that you have installed. There is no need to re-install driver updates following an errata update.
Chapt er 2 4 . Upgrading Your Current Syst em Chapter 24. Upgrading Your Current System This chapter explains the various methods available for upgrading your Red Hat Enterprise Linux system. 24 .1. Det ermining Whet her t o Upgrade or Re-Inst all Red Hat does not support upgrades from earlier major versions Although an aco n d a provides an option for upgrading from earlier major versions of Red Hat Enterprise Linux to Red Hat Enterprise Linux 5.11, Red Hat does not currently support this.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The upgrade process preserves existing configuration files by renaming them with an .rpmsave extension (for example, sendmail.cf.rpmsave). The upgrade process also creates a log of its actions in /root/upgrade.log. Warning As software evolves, configuration file formats can change. It is very important to carefully compare your original configuration files to the new files before integrating your changes.
Chapt er 2 4 . Upgrading Your Current Syst em 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 25. Register Your System and Apply Subscriptions 25.1. Regist ering t he Syst em Before you can access service and software maintenance information and enhanced support included as part of your subscription, you must register your new system with Red Hat and associate or attach the appropriate subscriptions with your system.
Chapt er 2 5. Regist er Your Syst em and Apply Subscript ions Important The user credentials to use depend on the subscription service. When registering with the Customer Portal, use the Red Hat Network credentials for the administrator or company account. However, for Subscription Asset Manager or CloudForms System engine, the user account to use is created within the on-premise service and probably is not the same as the Customer Portal user account.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Note Red Hat Subscription Manager (GUI and CLI) must be run as root. To register from the command line, use the register command with the --autosubscribe option so that the best-matched subscriptions are automatically attached. For example: [root@server ~]# subscription-manager register --autosubscribe Username: admin@example.
Chapt er 2 5. Regist er Your Syst em and Apply Subscript ions [root@server1 ~]# subscription-manager unregister From the Subscription Manager UI: 1. Launch Subscription Manager. For example: [root@server ~]# subscription-manager-gui 2. In the System menu of the Subscription Manager window, select the U n reg ist er item.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 26. 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 26.1.
Chapt er 2 6 . An Int roduct ion t o Disk Part it ions Fig u re 26 .2. D isk D rive wit h a File Syst em As Figure 26.2, “ D isk D rive 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. A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as blocks.
Red Hat Ent erprise Linux 5 Inst allat ion G uide As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used. 26.1.2.
Chapt er 2 6 . An Int roduct ion t o Disk Part it ions type, to flag the partition as being associated with a particular operating system, to indicate that the partition contains a bootable operating system, or some combination of the three. By this point, you might be wondering how all this additional complexity is normally used. Refer to Figure 26.6, “ D isk D rive With Single Partition” , for an example. Fig u re 26 .6 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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 reasonablysized 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 26.1, “ Partition Types” , there is an " Extended" partition type.
Chapt er 2 6 . An Int roduct ion t o Disk Part it ions 2 6 .1 .4 .1 . Using Unpart it io ne d Fre e 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 26.8, “ D isk D rive with Unpartitioned Free Space” , shows what this might look like. Fig u re 26 .8. D isk D rive wit h U n p art it io n ed Free Sp ace In Figure 26.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 2 6 .1 .4 .3. Using Fre e Space fro m an Act ive Part it io n This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data.
Chapt er 2 6 . An Int roduct ion t o Disk Part it ions There are several disk management software products on the market. D o some research to find the one that is best for your situation. While the process of non-destructive repartitioning is rather straightforward, there are a number of steps involved: Compress and backup existing data Resize the existing partition Create new partition(s) Next we will look at each step in a bit more detail. 26 .1.4 .3.1. C o mp ress exist in g d at a As Figure 26.
Red Hat Ent erprise Linux 5 Inst allat ion G uide It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case we have illustrated, it would be best to delete the new D OS partition and create the appropriate Linux partition(s). 26 .1.4 .3.3. C reat e n ew p art it io n ( s) As the previous step implied, it may or may not be necessary to create new partitions.
Chapt er 2 6 . An Int roduct ion t o Disk Part it ions The drive letter can then be used to refer to that partition as well as the file system contained on that partition. Red Hat Enterprise Linux uses a naming scheme that is more flexible and conveys more information than the approach used by other operating systems. The naming scheme is file-based, with file names in the form of /dev/xxyN.
Red Hat Ent erprise Linux 5 Inst allat ion G uide This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. The main difference is that each partition is used to form part of the storage necessary to support a single set of files and directories. This is done by associating a partition with a directory through a process known as mounting. Mounting a partition makes its storage available starting at the specified directory (known as a mount point).
P art V. Basic Syst em Recovery 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, single-user mode, and emergency mode, where you can use your own knowledge to repair the system..
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 27. 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, single-user mode, and emergency mode, where you can use your own knowledge to repair the system. 27.1.
Chapt er 2 7 . Basic Syst em Recovery As the name implies, rescue mode is provided to rescue you from something. D uring 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. However, there may be times when you are unable to get Red Hat Enterprise Linux running completely enough to access files on your system's hard drive.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If you selected Continue to mount your partitions automatically and they were mounted successfully, you are in single-user mode. Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5).
Chapt er 2 7 . Basic Syst em Recovery 27.2.1. Reinst alling t he Boot Loader In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems. The following steps detail the process on how GRUB is reinstalled on the master boot record: Boot the system from an installation boot medium. Type linux rescue at the installation boot prompt to enter the rescue environment. Type chroot /mnt/sysimage to mount the root partition.
Red Hat Ent erprise Linux 5 Inst allat ion G uide [12] Refer to the earlier s ec tio ns o f this g uid e fo r mo re d etails .
Chapt er 2 8 . Rescue Mode on PO WER Syst ems Chapter 28. 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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.
Chapt er 2 9 . Disk Encrypt ion G uide Chapter 29. Disk Encryption Guide Note Red Hat Enterprise Linux 5.3 now contains support during installation for file system encryption. This is not supported for earlier versions of Red Hat Enterprise Linux. 29.1. What is block device encrypt ion? Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication.
Red Hat Ent erprise Linux 5 Inst allat ion G uide What LUKS does not do: LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device. LUKS is not well-suited for applications requiring file-level encryption. For more information on LUKS, refer to http://code.google.com/p/cryptsetup/ 29.2.2.
Chapt er 2 9 . Disk Encrypt ion G uide Important — Global Passphrases Not Supported D evices encrypted with LUKS can share a global passphrase. When a system contains more than two encrypted block devices, an aco n d a offers you the option to set a global passphrase for them. However, although an aco n d a can set this passphrase correctly, the use of global passphrases is not supported by the init scripts in Red Hat Enterprise Linux 5.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems): dd if=/dev/urandom of= Fastest way, which provides lower quality random data: badblocks -c 10240 -s -w -t random -v 29.4 .3. Format t he device as a dm-crypt /LUKS encrypt ed device Warning The command below will destroy any existing data on the device.
Chapt er 2 9 . Disk Encrypt ion G uide There should now be a device node, /dev/mapper/, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device. To see some information about the mapped device, use the following command: dmsetup info T ip For more information, read the dmsetup(8) man page. 29.4 .5.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Add an entry to /etc/fstab. This is only necessary if you want to establish a persistent association between the device and a mountpoint. Use the decrypted device, /dev/mapper/ in the /etc/fstab file. In many cases it is desirable to list devices in /etc/fstab by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: /dev/sda4) changes.
Chapt er 30 . Inst alling T hrough VNC Chapter 30. Installing Through VNC Many enterprise customers perform interactive installations on systems in datacenters. These systems are often, but not always, installed in a rack environment and do not have a display, keyboard, or mouse. Additionally, a lot of these systems even lack the ability to connect a graphical display. Given that enterprise hardware rarely needs that ability at the physical system, this hardware configuration is acceptable.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 30.2. VNC Modes in Anaconda Anaconda offers two modes for VNC installation. The mode you select will depend on the network configuration in your environment. 30.2.1. Direct Mode D irect mode VNC in anaconda is when the client initiates a connection to the VNC server running in anaconda. Anaconda will tell you when to initiate this connection in the VNC viewer.
Chapt er 30 . Inst alling T hrough VNC Now that you have installed a VNC viewer application and selected a VNC mode for use in anaconda, you are ready to begin the installation. 30.3.1. Inst allat ion Example The easiest way to perform an installation using VNC is to connect another computer directly to the network port on the target system. The laptop on a datacenter crash cart usually fills this role. If you are performing your installation this way, make sure you follow these steps: 1.
Red Hat Ent erprise Linux 5 Inst allat ion G uide If your target system will be booting over the network, VNC is still available. Just add the vnc command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file. If you are using D HCP for the target system, the reverse vncconnect method may work better for you.
Chapt er 31 . Kickst art Inst allat ions Chapter 31. Kickstart Installations 31.1. What are Kickst art Inst allat ions? 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item). Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.
Chapt er 31 . Kickst art Inst allat ions table. The --only-use option specifies that only the disks listed will be used during installation. The ignoredisk option is also useful if you have multiple paths to your disks. The syntax is: ignoredisk --drives=drive1,drive2,... where driveN is one of sda, sdb,..., hda,... etc. --only-use — specifies a list of disks for the installer to use. All other disks are ignored.
Red Hat Ent erprise Linux 5 Inst allat ion G uide --ldapserver= — If you specified either --enableldap or --enableldapauth, use this option to specify the name of the LD AP server to use. This option is set in the /etc/ldap.conf file. --ldapbasedn= — If you specified either --enableldap or --enableldapauth, use this option to specify the D N in your LD AP directory tree under which user information is stored. This option is set in the /etc/ldap.conf file.
Chapt er 31 . Kickst art Inst allat ions --enablesmbauth — Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UID s, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LD AP, NIS, or Hesiod or by using the /usr/sbin/useradd command to make their accounts known to the workstation. To use this option, you must have the pam_smb package installed.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Note If the clearpart command is used, then the --onpart command cannot be used on a logical partition. Important — unformatted DASDs on System z Red Hat Enterprise Linux 5 cannot use unformatted D ASD s when installing with kickstart and the cmdline user interface.
Chapt er 31 . Kickst art Inst allat ions --opts= — Mount options to use for mounting the NFS export. Any options that can be specified in /etc/fstab for an NFS mount are allowed. The options are listed in the nfs(5) man page. Multiple options are separated with a comma. driverdisk ( o p t io n al) D river diskettes can be used during kickstart installations. You must copy the driver diskettes's contents to the root directory of a partition on the system's hard drive.
Red Hat Ent erprise Linux 5 Inst allat ion G uide packets on port 1234 through, specify 1234:udp. To specify multiple ports, separate them by commas. firstboot ( o p t io n al) D etermine whether the Set u p Ag en t starts the first time the system is booted. If enabled, the firstboot package must be installed. If not specified, this option is disabled by default. --enable or --enabled — The Set u p Ag en t is started the first time the system boots.
Chapt er 31 . Kickst art Inst allat ions nfs — Install from the NFS server specified. --server= Server from which to install (hostname or IP). --dir= D irectory containing the variant directory of the installation tree. --opts= Mount options to use for mounting the NFS export. (optional) For example: nfs --server=nfsserver.example.com --dir=/tmp/install-tree url — Install from an installation tree on a remote server via FTP or HTTP.
Red Hat Ent erprise Linux 5 Inst allat ion G uide --password= — the password that corresponds with the username specified for the target --reverse-user= — the username required to authenticate with the initiator from a target that uses reverse CHAP authentication --reverse-password= — the password that corresponds with the username specified for the initiator iscsiname ( o p t io n al) Assigns a name to an iSCSI node specified by the iscsi parameter.
Chapt er 31 . Kickst art Inst allat ions The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the %packages section of your kickstart file.
Red Hat Ent erprise Linux 5 Inst allat ion G uide --host= — Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging. --port= — If the remote syslogd process uses a port other than the default, it may be specified with this option. --level= — One of debug, info, warning, error, or critical. Specify the minimum level of messages that appear on tty3. All messages will still be sent to the log file regardless of this level, however.
Chapt er 31 . Kickst art Inst allat ions Configures network information for the system. If the kickstart installation requires networking (when the Kickstart file is accessed over HTTP, FTP or NFS), the device specified in the first network command is activated with configuration specified by the command. If the --device= option is not specified and multiple network devices are available, the device used to access the Kickstart file over the network is selected, or the user is asked to choose the device.
Red Hat Ent erprise Linux 5 Inst allat ion G uide network --bootproto=query --device= — Used to specify the network device being configured. For example: network --bootproto=dhcp --device=eth0 The above example configures device eth0 for D HCP. --ip= — IP address for the machine to be installed. --gateway= — D efault gateway as an IP address. --nameserver= — Primary nameserver, as an IP address. --nodns — D o not configure any D NS server. --netmask= — Netmask for the installed system.
Chapt er 31 . Kickst art Inst allat ions / For example, /, /usr, /home swap The partition is used as swap space. To determine the size of the swap partition automatically, use the --recommended option: swap --recommended The recommended maximum swap size for machines with less than 2GB of RAM is twice the amount of RAM. For machines with 2GB or more, this recommendation changes to 2GB plus the amount of RAM. raid. The partition is used for software RAID (refer to raid). pv.
Red Hat Ent erprise Linux 5 Inst allat ion G uide partition /home --onpart=hda1 puts /home on /dev/hda1, which must already exist. --ondisk= or --ondrive= — Forces the partition to be created on a particular disk. For example, --ondisk=sdb puts the partition on the second SCSI disk on the system. --asprimary — Forces automatic allocation of the partition as a primary partition, or the partitioning fails. --type= (replaced by fstype) — This option is no longer available. Use fstype.
Chapt er 31 . Kickst art Inst allat ions The poweroff option is roughly equivalent to the shutdown -p command. Note The poweroff option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The following example shows how to create a RAID level 1 partition for /, and a RAID level 5 for /usr, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive. part raid.01 --size=60 --ondisk=sda part raid.02 --size=60 --ondisk=sdb part raid.03 --size=60 --ondisk=sdc part swap --size=128 --ondisk=sda part swap --size=128 --ondisk=sdb part swap --size=128 --ondisk=sdc part raid.
Chapt er 31 . Kickst art Inst allat ions --mirrorlist= — The URL pointing at a list of mirrors for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --baseurl, not both. rootpw ( req u ired ) Sets the system's root password to the argument. rootpw [--iscrypted] --iscrypted — If this is present, the password argument is assumed to already be encrypted.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Do not include spaces in the list of services If you include spaces in the comma-separated list, kickstart will enable or disable only the services up to the first space. For example: services --disabled auditd, cups,smartd, nfslock will disable only the au d it d service.
Chapt er 31 . Kickst art Inst allat ions --groups= — In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created. --homedir= — The home directory for the user. If not provided, this defaults to /home/. --password= — The new user's password. If not provided, the account will be locked by default.
Red Hat Ent erprise Linux 5 Inst allat ion G uide For a detailed example of volgroup in action, refer to Section 31.4.1, “ Advanced Partitioning Example” . xconfig ( o p t io n al) Configures the X Window System. If this option is not given, the user must configure X manually during the installation, if X was installed; this option should not be used if X is not installed on the final system. --driver — Specify the X driver to use for the video hardware.
Chapt er 31 . Kickst art Inst allat ions part part part part part part part part raid.13 raid.14 raid.15 raid.21 raid.22 raid.23 raid.24 raid.25 --size --size --size --size --size --size --size --size 2000 8000 1 --grow 1000 1000 2000 8000 1 --grow --asprimary --asprimary --asprimary --asprimary --ondrive=hda --ondrive=hda --ondrive=hda --ondrive=hdc --ondrive=hdc --ondrive=hdc --ondrive=hdc --ondrive=hdc # You can add --spares=x raid / --fstype ext3 --device md0 --level=RAID1 raid.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Administration Tools Authoring and Publishing D evelopment Libraries D evelopment Tools D NS Name Server Eclipse Editors Engineering and Scientific FTP Server GNOME D esktop Environment GNOME Software D evelopment Games and Entertainment Graphical Internet Graphics Java D evelopment KD E (K D esktop Environment) KD E Software D evelopment Legacy Network Server Legacy Software D evelopment Legacy Software Support Mail Server Misc Multimedia MySQL D atabase N
Chapt er 31 . Kickst art Inst allat ions System Tools Text-based Internet Web Server Windows File Server Windows PV D rivers X Software D evelopment X Window System In most cases, it is only necessary to list the desired groups and not individual packages. Note that the Core and Base groups are always selected by default, so it is not necessary to specify them in the %packages section.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 31.6. Pre-inst allat ion Script You can add commands to run on the system immediately after the ks.cfg has been parsed. This section must be at the end of the kickstart file (after the commands) and must start with the %pre command. You can access the network in the %pre section; however, name service has not been configured at this point, so only IP addresses work. Note Note that the pre-install script is not run in the change root environment.
Chapt er 31 . Kickst art Inst allat ions %include /tmp/part-include The partitioning commands selected in the script are used. 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. 31.7.
Red Hat Ent erprise Linux 5 Inst allat ion G uide nochroot: This command is available in Red Hat Enterprise Linux 5.5 and later. %post --log=/root/ks-post.log with --nochroot: %post --nochroot --log=/mnt/sysimage/root/ks-post.log 31.7.1. Examples Register the system to a Subscription Asset Manager server, using the --log option to log the result (in Red Hat Enterprise Linux 5.5 and later): %post --log=/root/ks-post.log /usr/sbin/subscription-manager register --username=admin@example.
Chapt er 31 . Kickst art Inst allat ions To perform a CD -ROM-based kickstart installation, the kickstart file must be named ks.cfg and must be located in the boot CD -ROM's top-level directory. Since a CD -ROM is read-only, the file must be added to the directory used to create the image that is written to the CD -ROM. Refer to Section 2.4.1, “ Alternative Boot Methods” for instructions on creating boot media; however, before making the file.iso image file, copy the ks.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Note that if you do not specify a server name, then the client system attempts to use the server that answered the BOOTP/D HCP request as its NFS server. If you do not specify a path or file name, the client system tries to mount /kickstart from the BOOTP/D HCP server and tries to find the kickstart file using the same -kickstart file name as described above. 31.9.
Chapt er 31 . Kickst art Inst allat ions askmethod D o not automatically use the CD -ROM as the install source if we detect a Red Hat Enterprise Linux CD in your CD -ROM drive. autostep Make kickstart non-interactive. Used for debugging and to generate screenshots. This option should not be used when deploying a system because it may disrupt package installation. debug Start up pdb immediately. dd Use a driver disk. dhcpclass= Sends a custom D HCP vendor class identifier.
Red Hat Ent erprise Linux 5 Inst allat ion G uide ks=nfs::/ The installation program looks for the kickstart file on the NFS server , as file . The installation program uses D HCP 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.
Chapt er 31 . Kickst art Inst allat ions The installation program uses this network device to connect to the network. For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command ks=nfs::/ ksdevice=eth1 at the boot: prompt. kssendmac Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems.
Red Hat Ent erprise Linux 5 Inst allat ion G uide D o not load the VGA16 framebuffer required for doing text-mode installation in some languages. nofirewire D o not load support for firewire devices. noipv6 D isable IPv6 networking during installation. T his option is not available during PXE installations D uring installations from a PXE server, IPv6 networking might become active before an aco n d a processes the Kickstart file. If so, this option will have no effect during installation.
Chapt er 31 . Kickst art Inst allat ions rescue Run rescue environment. resolution= Run installer in mode specified, '1024x768' for example. serial Turns on serial console support. skipddc Skips D D C probe of monitor, may help if it's hanging system. syslog=[:] Once installation is up and running, send log messages to the syslog process on , and optionally, on port . Requires the remote syslog process to accept connections (the -r option). text Force text mode install.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Chapter 32. Kickstart Configurator K ickst art C o n f ig u rat o r 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 K ickst art C o n f ig u rat o r, you must be running the X Window System and have K ickst art C o n f ig u rat o r installed on your system.
Chapt er 32 . Kickst art Configurat or Choose the language to use during the installation and as the default language to be used after installation from the D ef au lt Lan g u ag e menu. Select the system keyboard type from the K eyb o ard menu. From the T ime Z o n e menu, choose the time zone to use for the system. To configure the system to use UTC, select Use UTC clock. Enter the desired root password for the system in the Root Password text entry box.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.2. In st allat io n Met h o d The Installation Method screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the Partition Information and Package Selection 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 CD -ROMs.
Chapt er 32 . Kickst art Configurat or intact before you start the installation. To verify them, use an md5sum program as well as the linux mediacheck boot option as discussed in the Red Hat Enterprise Linux Installation Guide. Enter the hard drive partition that contains the ISO images (for example, /dev/hda1) in the Hard Drive Partition text box. Enter the directory that contains the ISO images in the Hard Drive Directory text box. 32.3. Boot Loader Opt ions Fig u re 32.3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Confirm Password text field. To save the password as an encrypted password in the file, select Encrypt GRUB 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. If the password you typed was already encrypted, unselect the encryption option.
Chapt er 32 . Kickst art Configurat or 32.4 .1. Creat ing Part it ions To create a partition, click the Add button. The Partition Options window shown in Figure 32.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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.5. C reat in g Part it io n s 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 32.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.
Chapt er 32 . Kickst art Configurat or 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. Fig u re 32.6 . C reat in g a So f t ware R AID Part it io n 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.7. C reat in g a So f t ware R AID D evice 4. Click OK to add the device to the list. 32.5.
Chapt er 32 . Kickst art Configurat or Fig u re 32.8. N et wo rk C o n f ig u rat io n 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 N et wo rk Ad min ist rat io n T o o l (system-config-network).
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.9 . Au t h en t icat io n In the Authentication section, select whether to use shadow passwords and MD 5 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 LD AP Kerberos 5 Hesiod SMB Name Switch Cache These methods are not enabled by default.
Chapt er 32 . Kickst art Configurat or Fig u re 32.10. Firewall C o n f ig u rat io n 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 D NS replies or D HCP requests.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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 32.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. 32.8.1.
Chapt er 32 . Kickst art Configurat or 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.13. X C o n f ig u rat io n - Mo n it o r 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.
Chapt er 32 . Kickst art Configurat or Fig u re 32.14 . Packag e Select io n The Package Selection window allows you to choose which package groups to install. Package resolution is carried out automatically. Currently, K ickst art C o n f ig u rat o r 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 31.5, “ Package Selection” for details. 32.10.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.15. Pre- In st allat io n Scrip t 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.
Chapt er 32 .
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.16 . Po st - In st allat io n Scrip t 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. Warning D o not include the %post command. It is added for you.
Chapt er 32 . Kickst art Configurat or 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/. For example, if you select Run outside of the chroot environment, the previous example must be changed to the following: echo "Hackers will be punished" > /mnt/sysimage/etc/motd 32.11.2.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Fig u re 32.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 31.10, “ Starting a Kickstart Installation” for information on how to start the kickstart installation.
Chapt er 33. Boot Process, Init , and Shut down Chapter 33. 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide When an x86 computer is booted, the processor looks at the end of system memory for the Basic Input/Output System or BIOS program and runs it. The BIOS controls not only the first step of the boot process, but also provides the lowest level interface to peripheral devices. For this reason it is written into read-only, permanent memory and is always available for use.
Chapt er 33. Boot Process, Init , and Shut down 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. The initramfs is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 file system.
Red Hat Ent erprise Linux 5 Inst allat ion G uide The init program starts all of the background processes by looking in the appropriate rc directory for the runlevel specified as the default in /etc/inittab. The rc directories are numbered to correspond to the runlevel they represent. For instance, /etc/rc.d/rc5.d/ is the directory for runlevel 5. When booting to runlevel 5, the init program looks in the /etc/rc.d/rc5.d/ directory to determine which processes to start and stop.
Chapt er 33. Boot Process, Init , and Shut down S13portmap -> ../init.d/portmap S15mdmonitor -> ../init.d/mdmonitor S15zebra -> ../init.d/zebra S16bgpd -> ../init.d/bgpd S16ospf6d -> ../init.d/ospf6d S16ospfd -> ../init.d/ospfd S16ripd -> ../init.d/ripd S16ripngd -> ../init.d/ripngd S20random -> ../init.d/random S24pcmcia -> ../init.d/pcmcia S25netfs -> ../init.d/netfs S26apmd -> ../init.d/apmd S27ypbind -> ../init.d/ypbind S28autofs -> ../init.d/autofs S40smartd -> ../init.d/smartd S44acpid -> ../init.
Red Hat Ent erprise Linux 5 Inst allat ion G uide 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 33.3, “ Running Additional Programs at Boot Time” for more information about using the rc.local file.
Chapt er 33. Boot Process, Init , and Shut down operate the system at a lower runlevel to perform diagnostic tasks, like fixing disk corruption in runlevel 1. The characteristics of a given runlevel determine which services are halted and started by init. For instance, runlevel 1 (single user mode) halts any network services, while runlevel 3 starts these services.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Red Hat Enterprise Linux provides three such utilities: /sbin/chkconfig — The /sbin/chkconfig utility is a simple command line tool for maintaining the /etc/rc.d/init.d/ directory hierarchy. /u sr/sb in /n t sysv — The ncurses-based /sb in /n t sysv utility provides an interactive text-based interface, which some find easier to use than chkconfig.
Chapt er 34 . PXE Net work Inst allat ions Chapter 34. 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.
Red Hat Ent erprise Linux 5 Inst allat ion G uide -a — Specifies that an OS instance is being added to the PXE configuration. -i " " — Replace " " with a description of the OS instance. -p — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified. -D <0|1> — Specify " 0" which indicates that it is not a diskless configuration since pxeos can be used to configure a diskless environment as well. -s installer.example.
Chapt er 34 . PXE Net work Inst allat ions Fig u re 34 .1. Ad d H o st s The next step is to configure which hosts are allowed to connect to the PXE boot server. For the command line version of this step, refer to Section 34.3.1, “ Command Line Configuration” . To add hosts, click the New button. Fig u re 34 .2.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Multiple IP addresses not accepted Only enter a single IP address. an aco n d a will not use multiple addresses. Operating System — The operating system identifier to install on this client. The list is populated from the network install instances created from the Network Installation Dialog. Serial Console — This option allows use of a serial console. Kickstart File — The location of a kickstart file to use, such as http://server.example.com/kickstart/ks.
Chapt er 34 . PXE Net work Inst allat ions 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. 34 .5. Configuring t he DHCP Server If a D HCP server does not already exist on the network, configure one.
Red Hat Ent erprise Linux 5 Inst allat ion G uide Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Enterprise Linux. R evisio n 3.1- 4 6 T h u Sep 11 2014 Pet r B o ko č Red Hat Enterprise Linux 5.11 GA release of the Installation Guide R evisio n 3.1- 4 5 Mo n Ju n 30 2014 Pet r B o ko č Red Hat Enterprise Linux 5.11 Beta release of the Installation Guide R evisio n 3.
Revision Hist ory Added size limit for ext3 - BZ #843305 R evisio n 3.1- 26 Fri Feb 02 2012 Updated FTP/HTTP installation prep procedure - BZ #240455 Corrected typos - BZ #766441, BZ #676559 Jack R eed R evisio n 3.1- 24 Fri N o v 18 2011 Jack R eed Explained values for pv. in part and volgroup kickstart options - BZ #601834 Corrected current version number for display in the book - BZ #748681 R evisio n 3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide R evisio n 3.1- 11 Wed Jan 5 2011 Clarify pxeos details — BZ #243098 R ü d ig er Lan d man n R evisio n 3.1- 10 Wed Jan 5 2011 R ü d ig er Lan d man n D ocument using clearpart to ensure that D ASD s are formatted during installation — BZ #606048 Expand documentation of multipath kickstart command — BZ #629834 R evisio n 3.1- 9 T u e D ec 21 2010 R ü d ig er Lan d man n Update Figure 4.14.
Revision Hist ory Explain RAID issues BZ #486735 R evisio n 3.0- 19 Mo n Jan 11 2010 Fix some line breaks per BZ #486735 R ü d ig er Lan d man n R evisio n 3.0- 18 Mo n Jan 11 2010 Remove nokill as a kickstart command BZ #513693 R ü d ig er Lan d man n R evisio n 3.0- 17 Mo n Jan 11 2010 R ü d ig er Lan d man n Link to Red Hat Knowledgebase article on RAID 1 failures BZ #486735 R evisio n 3.
Red Hat Ent erprise Linux 5 Inst allat ion G uide migrated to new automated build system Index Symbols /b o o t / p art it io n - recommended partitioning, Recommended Partitioning Scheme, Recommended Partitioning Scheme /b o o t /ef i/ , It an iu m syst ems /ro o t /in st all.
Index b o o t lo ad er p asswo rd , x86 , AMD 6 4 , an d In t el® 6 4 B o o t Lo ad er C o n f ig u rat io n b o o t lo ad ers, G R U B - (see also GRUB) - definition of, The GRUB Boot Loader - types of - ELILO, Boot Loaders and System Architecture - GRUB, Boot Loaders and System Architecture - OS/400, Boot Loaders and System Architecture - YABOOT, Boot Loaders and System Architecture - z/IPL, Boot Loaders and System Architecture b o o t met h o d - overview, Basic Overview of the Boot Method b o o t met
Red Hat Ent erprise Linux 5 Inst allat ion G uide - x86, AMD 64 and Intel 64, Booting the Installation Program on x86, AMD 64, and Intel® 64 Systems - rescue mode, Booting into Rescue Mode - single-user mode, Booting into Single-User Mode b o o t in g t h e in st allat io n p ro g ram - IBM System i and IBM System p , Booting the IBM System i or IBM System p Installation Program C can celin g t h e in st allat io n , In st allin g f ro m D VD /C D - R O M CD-RO M - ATAPI, Installing from D VD /CD -ROM, I
Index D isk Part it io n er - adding partitions, Adding Partitions, Adding Partitions d isk p art it io n in g , D isk Part it io n in g Set u p , D isk Part it io n in g Set u p , D isk Part it io n in g Set u p d isk sp ace, D o Yo u H ave En o u g h D isk Sp ace?, D o Yo u H ave En o u g h D isk Sp ace?, D o Yo u H ave En o u g h D isk Sp ace? d iskless en viro n men t - D HCP configuration, Configuring the D HCP Server d mraid - installation, Advanced Storage Options , Advanced Storage Options , Advan
Red Hat Ent erprise Linux 5 Inst allat ion G uide - x11 forwarding, Installation using X11 Forwarding G R U B , x86 , AMD 6 4 , an d In t el® 6 4 B o o t Lo ad er C o n f ig u rat io n , B o o t Lo ad ers an d Syst em Arch it ect u re, T h e B o o t Lo ad er - (see also boot loaders) - additional resources, Additional Resources - installed documentation, Installed D ocumentation - related books, Related Books - useful websites, Useful Websites - alternatives to, Alternative Boot Loaders - commercial produc
Index - partitioning of, An Introduction to D isk Partitions h ard d rive in st allat io n , In st allin g f ro m a H ard D rive, In st allin g f ro m a H ard D rive - preparing for, Preparing for a Hard D rive Installation, Preparing for a Hard D rive Installation, Preparing for a Hard D rive Installation h ard ware - compatibility, Is Your Hardware Compatible? - configuration, System Specifications List - preparation, Additional Hardware Preparation for System z h ard ware p rep arat io n , eServer Syst
Red Hat Ent erprise Linux 5 Inst allat ion G uide - CD -ROM, Installing on Intel® and AMD Systems, Installing on IBM System i and IBM System p systems, Installing on IBM System z Systems - hard drive, Preparing for a Hard D rive Installation, Installing from a Hard D rive, Preparing for a Hard D rive Installation, Installing from a Hard D rive, Preparing for a Hard D rive Installation - HTTP, Preparing for a Network Installation, Installing via HTTP, Preparing for a Network Installation, Installing via HTT
Index in st allat io n p ro g ram - Itanium - booting, Booting the Installation Program on Itanium Systems - starting, Running the Installation Program - x86, AMD 64 and Intel 64 - booting, Booting the Installation Program on x86, AMD 64, and Intel® 64 Systems in st allin g - without the LPAR CD - using a recent SEW, Installing in an LPAR without the Red Hat Enterprise Linux for System z CD -ROMs - without the Red Hat Enterprise Linux for IBM System z CD -ROMs, Installing in an LPAR without the Red Hat En
Red Hat Ent erprise Linux 5 Inst allat ion G uide - installation key, Basic Configuration installation method selection, Installation Method interactive, Basic Configuration keyboard, Basic Configuration language, Basic Configuration network configuration, Network Configuration package selection, Package Selection partitioning, Partition Information - software RAID , Creating Software RAID Partitions - preview, Kickstart Configurator - reboot, Basic Configuration - root password, Basic Configuration - en
Index - multipath , Kickstart Options - network , Kickstart Options - network-based, Making the Kickstart File Available on the Network, Making the Installation Tree Available - options, Kickstart Options - partitioning examples, Advanced Partitioning Example - package selection specification, Package Selection part , Kickstart Options partition , Kickstart Options post-installation configuration, Post-installation Script poweroff , Kickstart Options pre-installation configuration, Pre-installation Scrip
Red Hat Ent erprise Linux 5 Inst allat ion G uide - installing - common steps, Installing in an LPAR (Common Steps) - using the LPAR CD , Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD - without the Red Hat Enterprise Linux for IBM System z CD -ROMs, Installing in an LPAR without the Red Hat Enterprise Linux for System z CD -ROMs LS- 120 b o o t d isket t e - creating from boot image file, Booting the Installation Program from an LS-120 D iskette LS- 120 b o o t .
Index - performing, Performing a Network Installation, Performing a Network Installation - preparing for, Preparing for a Network Installation, Preparing for a Network Installation, Preparing for a Network Installation N FS - installation, Preparing for a Network Installation, Installing via NFS, Preparing for a Network Installation, Installing via NFS, Preparing for a Network Installation, Installing via NFS n t sysv , R u n level U t ilit ies - (see also services) O O S/2 b o o t man ag er, Ad van ced
Red Hat Ent erprise Linux 5 Inst allat ion G uide - how many partitions, Partitions: Turning One D rive Into Many, How Many Partitions? - introduction to, Partitions: Turning One D rive Into Many - making room for partitions, Making Room For Red Hat Enterprise Linux - mount points and, D isk Partitions and Mount Points - naming partitions, Partition Naming Scheme - non-destructive, Using Free Space from an Active Partition - numbering partitions, Partition Naming Scheme - other operating systems, D isk Par
Index rc.
Red Hat Ent erprise Linux 5 Inst allat ion G uide - (see also halt) sin g le- u ser mo d e, B o o t in g in t o Sin g le- U ser Mo d e SMP mo t h erb o ard s - GRUB, SMP Motherboards and GRUB st art in g - installation, Starting the Installation Program, Installing from D VD /CD -ROM, Installing from D VD /CD -ROM st art u p .
Index T C P/IP co n f ig u rat io n , Perf o rmin g a N et wo rk In st allat io n , Perf o rmin g a N et wo rk In st allat io n t f t p , PXE N et wo rk In st allat io n s, St art in g t h e t f t p Server t ime z o n e - configuration, Time Z one Configuration, Time Z one Configuration, Time Z one Configuration t raceb ack messag es - saving traceback messages without a floppy drive, Saving Traceback Messages Without a D iskette D rive, Saving Traceback Messages Without a D iskette D rive t ro u b lesh o
Red Hat Ent erprise Linux 5 Inst allat ion G uide - signal 11 error, Is Your System D isplaying Signal 11 Errors?, Is Your System D isplaying Signal 11 Errors?, Is Your System D isplaying Signal 11 Errors? - CD -ROM failure - CD -ROM verification, Preparing for a Hard D rive Installation, Additional Boot Options, Preparing for a Hard D rive Installation - during the installation, Trouble D uring the Installation, Trouble D uring the Installation, Trouble D uring the Installation - completing partitions, Ot
Index XD MC P, R emo t e G rap h ical D eskt o p s an d XD MC P Y YAB O O T , B o o t Lo ad ers an d Syst em Arch it ect u re - (see also boot loaders) Z z /IPL, B o o t Lo ad ers an d Syst em Arch it ect u re - (see also boot loaders) z /VM - installing, Installing under z/VM z FC P d river, U sin g t h e z FC P D river 373
