Edition 3.1
1801 Varsity Drive
Raleigh, NC 27606-2072 USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
No devices found to install Red Hat Enterprise Linux Error Messagehttpd service/Sendmail Hangs During Startuphttpd service/Sendmail Hangs During Startup/etc/crypttab/etc/fstabMono-spaced Bold
To see the contents of the filemy_next_bestselling_novelin your current working directory, enter thecat my_next_bestselling_novelcommand at the shell prompt and press Enter to execute the command.
Press Enter to execute the command.Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 to return to your X-Windows session.
mono-spaced bold. For example:
File-related classes includefilesystemfor file systems,filefor files, anddirfor directories. Each class has its own associated set of permissions.
Choose → → from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).To insert a special character into a gedit file, choose → → from the main menu bar. Next, choose → from the Character Map menu bar, type the name of the character in the Search field and click . The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the button. Now switch back to your document and choose → from the gedit menu bar.
Mono-spaced Bold ItalicProportional Bold Italic
To connect to a remote machine using ssh, typesshat a shell prompt. If the remote machine isusername@domain.nameexample.comand your username on that machine is john, typessh john@example.com.Themount -o remountcommand remounts the named file system. For example, to remount thefile-system/homefile system, the command ismount -o remount /home.To see the version of a currently installed package, use therpm -qcommand. It will return a result as follows:package.package-version-release
Publican is a DocBook publishing system.
mono-spaced roman and presented thus:
books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
mono-spaced roman but add syntax highlighting as follows:
package org.jboss.book.jca.ex1; import javax.naming.InitialContext; public class ExClient { public static void main(String args[]) throws Exception { InitialContext iniCtx = new InitialContext(); Object ref = iniCtx.lookup("EchoBean"); EchoHome home = (EchoHome) ref; Echo echo = home.create(); System.out.println("Created Echo"); System.out.println("Echo.echo('Hello') = " + echo.echo("Hello")); } }
/usr/share/doc/redhat-release-notes-5<variant>/ directory after installation, where <variant> is Server, Client, or Desktop.
| Feature | Change | Note |
|---|---|---|
| Chapter 7, Updating drivers during installation on Intel and AMD systems, Chapter 13, Updating drivers during installation on IBM POWER systems, and Section 23.1, “Driver update rpm packages” | New chapters on driver updates | Documentation of driver updates during installation and with rpm packages after installation has been completely revised and brought up-to-date. |
| Section 31.4, “Kickstart Options” |
New option for the bootloader kickstart command.
|
--hvargs specifies Xen hypervisor arguments.
|
| Section 31.5, “Package Selection” |
@Everything no longer supported
| Red Hat no longer supports installations performed with this option. |
/usr/share/doc/redhat-release-notes-5<variant>/ directory after installation, where <variant> is Server, Client, or Desktop.
Table of Contents
No devices found to install Red Hat Enterprise Linux Error Messagehttpd service/Sendmail Hangs During Startupedit, type, cp, rm, and mkdir. For a list of utilities and other commands, type help at the EFI Shell prompt.
http://developer.intel.com/technology/efi/index.htm
map command can be used to list all devices and file systems that EFI can recognize. When your Itanium system boots into the EFI shell, it probes your system in the following order:
mapmap command might look like the following:
Device mapping table fs0 : VenHw(Unknown Device:00)/HD(Part1,Sig00000000) fs1 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) fs2 : VenHw(Unknown Device:FF)/CDROM(Entry1)/HD(Part1,Sig00000000) blk0 : VenHw(Unknown Device:00) blk1 : VenHw(Unknown Device:00)/HD(Part1,Sig00000000) blk2 : VenHw(Unknown Device:80) blk3 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) blk4 : VenHw(Unknown Device:80)/HD(Part2,Sig00000000) blk5 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000) blk6 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000)/HD(Part1,Sig725F7772) blk7 : VenHw(Unknown Device:FF) blk8 : VenHw(Unknown Device:FF)/CDROM(Entry1) blk9 : VenHw(Unknown Device:FF)/CDROM(Entry1)/HD(Part1,Sig00000000)
fs are FAT16 file systems that EFI can read. All the listings beginning with blk are block devices that EFI recognizes. Both the file systems and block devices are listed in the order they are probed. Therefore, fs0 is the system partition on the LS-120, fs1 is the system partition on the hard drive, and fs2 is the system partition on the CD-ROM.
/boot/efi/. This partition contains the installed Linux kernel(s) as well as the ELILO configuration file (elilo.conf). The elilo.conf file contains a list of kernels from which you can boot your system.
http://hardware.redhat.com/hcl/
/ and swap) must be dedicated to Red Hat Enterprise Linux. For Itanium systems, at least three partitions (/, /boot/efi/, and swap) must be dedicated to Red Hat Enterprise Linux.
Applications folder.
sdc instead of sda.
dmesg to identify the device name for the drive. If you run dmesg shortly after you attach the drive, the device name appears in the most recent lines of output. For example, the following dmesg output shows a flash drive that receives the device name /dev/sdb:
Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. Vendor: USB 2.0 Model: Flash Disk Rev: 5.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 2043904 512-byte hdwr sectors (1046 MB) sdb: Write Protect is off sdb: Mode Sense: 0b 00 00 08 sdb: assuming drive cache: write through SCSI device sdb: 2043904 512-byte hdwr sectors (1046 MB) sdb: Write Protect is off sdb: Mode Sense: 0b 00 00 08 sdb: assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: Attached scsi removable disk sdb sd 2:0:0:0: Attached scsi generic sg1 type 0 usb-storage: device scan complete
mount command to find any mounted partitions on the flash drive. For example, the following output shows a single partition on /dev/sdb is mounted, the partition named /dev/sdb1:
$ mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sda1 on /boot type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/sdb1 on /media/BOOTUSB type vfat (rw,nosuid,nodev,uid=500,utf8,shortname=mixed,flush)
umount command. For example, to unmount /dev/sdb1, run:
umount /dev/sdb1umount for each partition on the flash drive that is mounted.
fdisk to partition the flash drive to contain a single partition only, with the following parameters:
1.
b (W95 FAT32).
mkdosfs to format the partition created in the previous step as FAT. For example:
mkdosfs /dev/sdb1mount /dev/sdb1 /mntisolinux/ directory of the installation DVD or CD-ROM#1 onto the flash drive.
isolinux.cfg to syslinux.cfg. For example, if the flash drive is mounted on /mnt, run:
cd /mnt/; mv isolinux.cfg syslinux.cfgsyslinux.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
images/pxeboot/initrd.img file from the installation DVD or CD-ROM#1 onto the flash drive.
umount /dev/sdb1syslinux /dev/sdb1mount /dev/sdb1 /mntgrub-install --root-directory=/mnt /dev/sdbmkdir -p /mnt/boot/grubboot/grub/grub.conf file on the flash drive as follows:
default=0 timeout=5 root (hd1,0) title Red Hat Enterprise Linux installer kernel /vmlinuz initrd /initrd.img
umount /dev/sdb1isolinux (not available for Itanium systems) is used for booting the Red Hat Enterprise Linux installation CD. To create your own CD-ROM to boot the installation program, use the following instructions:
isolinux/ directory from the Red Hat Enterprise Linux DVD or CD #1 into a temporary directory (referred to here as <path-to-workspace>) using the following command:
cp -r <path-to-cd>/isolinux/ <path-to-workspace><path-to-workspace> directory you have created:
cd <path-to-workspace>
chmod u+w isolinux/*mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot \ -boot-load-size 4 -boot-info-table -R -J -v -T isolinux/
file.iso and located in <path-to-workspace>) to a CD-ROM as you normally would.
boot: prompt (prepend with elilo for Itanium systems):
linux mediacheck/location/of/disk/space/publicly/available/directory. For example, /location/of/disk/space/var/isos. /publicly/available/directory/var/www/html/rhel5, for an HTTP install.
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
dvd refers to your DVD drive device.
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):
mount /media/cdrom
cp -a /media/cdrom/Server <target-directory>
cp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory> (Installation CD 1 or DVD only)
cp /media/cdrom/images <target-directory> (Installation CD 1 or DVD only)
umount /media/cdrom
<target-directory>/publicly/available/directory mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory/etc/exports.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload).
dd if=/dev/cdrom of=/tmp/file-name.iso
md5sum program (many md5sum programs are available for various operating systems). An md5sum program should be available on the same Linux machine as the ISO images.
boot: prompt (prepend with elilo for Itanium systems):
linux mediacheckupdates.img exists in the location from which you install, it is used for updates to anaconda, the installation program. Refer to the file install-methods.txt in the anaconda RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
/dev/hda1=/home, /dev/hda2=/ (fill this in once you know where they will reside)
example.com
cookie, southpark
X key command combination as a way of clicking on buttons or making other screen selections, where X is replaced with any underlined letter appearing within that screen.
boot: prompt:
linux text
elilo linux text| console | keystrokes | contents |
|---|---|---|
| 1 | ctrl+alt+f1 | installation dialog |
| 2 | ctrl+alt+f2 | shell prompt |
| 3 | ctrl+alt+f3 | install log (messages from installation program) |
| 4 | ctrl+alt+f4 | system-related messages |
| 5 | ctrl+alt+f5 | other messages |
| 6 | ctrl+alt+f6 | x graphical display |
/root/anaconda-screenshots.
autostep --autoscreenshot option to generate a screenshot of each step of the installation automatically. Refer to Section 31.3, “Creating the Kickstart File” for details of configuring a Kickstart file.
boot: prompt should appear. The screen contains information on a variety of boot options. Each boot option also has one or more help screens associated with it. To access a help screen, press the appropriate function key as listed in the line at the bottom of the screen.
boot: prompt appears, the installation program automatically begins if you take no action within the first minute. To disable this feature, press one of the help screen function keys.
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. To change to the fs1 file system, type fs1: at the prompt.
elilo linux to boot into the installation program.
images/boot.img. To create this diskette in Linux, insert a blank LS-120 diskette and type the following command at a shell prompt:
dd if=boot.img of=/dev/hda bs=180kboot.img with the full path to the boot image file and /dev/hda with the correct device name for the LS-120 diskette drive.
boot.img. If you are performing a local CD-ROM installation but booting off the LS-120 diskette, insert the Red Hat Enterprise Linux CD #1 also. If you are performing a hard drive, NFS, FTP, or HTTP installation, you do not need the CD-ROM.
Shell> prompt, change the device to the LS-120 drive by typing the command fs0:, using the example map output above.
elilo linux to boot into the installation program.
elilo linux option
linux text
linux mediacheckimages/ directory is the boot.iso file. This file is an ISO image than can be used to boot the installation program. To use the boot.iso, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. You must then burn the boot.iso file onto a recordable/rewriteable CD-ROM.
linux console=<device>
linux text console=<device><device> should be the device you are using (such as ttyS0 or ttyS1). For example, linux text console=ttyS0.
utf8 command as a boot-time option to the installation program. For example:
linux console=ttyS0 utf8
linux updates
linux text updatesrhupdates/ on the server.
linux askmethod boot option). Refer to Section 4.7, “Installing from a Hard Drive”, for hard drive installation instructions.
linux askmethod boot option). Refer to Section 4.9, “Installing via NFS” for network installation instructions. Note that NFS installations may also be performed in GUI mode.
linux askmethod boot option). Refer to Section 4.10, “Installing via FTP”, for FTP installation instructions.
linux askmethod boot option). Refer to Section 4.11, “Installing via HTTP”, for HTTP installation instructions.
askmethod boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition.
/. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/, and the images are in /home/new/, you would enter /new/.
askmethod boot option, the Configure TCP/IP dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually. If manually, you have the option to enter IPv4 and/or IPv6 information. Enter the IP address you are using during installation and press Enter. Note that you need to supply IPv4 information if you wish to perform an NFS installation.
eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field.
/export/directory/
askmethod boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
askmethod boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue.
/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.
mapper/mpath instead.
/boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/ partition is also necessary for software RAID setups.
/boot/ partition.
/boot/efi/ partition of approximately 100 MB and of type FAT (VFAT), a swap partition of at least 512 MB, and an appropriately-sized root (/) partition.
/boot/efi/ partition (100 MB minimum) — the partition mounted on /boot/efi/ contains all the installed kernels, the initrd images, and ELILO configuration files.
/boot/efi/ partition of type VFAT and at least 100 MB in size as the first primary partition.
| Amount of RAM in the System | Recommended Amount of Swap Space |
|---|---|
| 4GB of RAM or less | a minimum of 2GB of swap space |
| 4GB to 16GB of RAM | a minimum of 4GB of swap space |
| 16GB to 64GB of RAM | a minimum of 8GB of swap space |
| 64GB to 256GB of RAM | a minimum of 16GB of swap space |
| 256GB to 512GB of RAM | a minimum of 32GB of swap space |
/" (the root directory) is located. In this setup, all files (except those stored in /boot/efi) are on the root partition.
| Amount of RAM in the System | Recommended Amount of Swap Space |
|---|---|
| 4GB of RAM or less | a minimum of 2GB of swap space |
| 4GB to 16GB of RAM | a minimum of 4GB of swap space |
| 16GB to 64GB of RAM | a minimum of 8GB of swap space |
| 64GB to 256GB of RAM | a minimum of 16GB of swap space |
| 256GB to 512GB of RAM | a minimum of 32GB of swap space |
/boot/ partition (250 MB) — the partition mounted on /boot/ contains the operating system kernel (which allows your system to boot Red Hat Enterprise Linux), along with files used during the bootstrap process. Due to limitations, creating a native ext3 partition to hold these files is required. For most users, a 250 MB boot partition is sufficient.
/boot/ partition if you want the / (root) partition to use all of the remaining space on your hard drive.
/boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
root partition (3.0 GB - 5.0 GB) — this is where "/" (the root directory) is located. In this setup, all files (except those stored in /boot) are on the root partition.
home partition (at least 100 MB) — for storing user data separately from system data. This will be a dedicated partition within a volume group for the /home directory. This will enable you to upgrade or reinstall Red Hat Enterprise Linux without erasing user data files.
/var on network storage/var on a network filesystem (for example, NFS, iSCSI, or NBD) The /var directory contains critical data that must be read from or written to during the boot process before establishing network services.
/var/spool, /var/www or other subdirectories on a separate network disk, just not the complete /var filesystem.
/; 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.
fsck [2] the file system. The ext3 file system is selected by default and is highly recommended.
/boot/efi/ partition on Itanium systems.
Red Hat Enterprise Linux (for GRUB). Other partitions may also have boot labels. To add or change the boot label for other partitions that have been detected by the installation program, click once on the partition to select it. Once selected, you can change the boot label by clicking the button.
/boot/ partition was created.
/boot/ partition. If you have a system which supports the LBA32 extension for booting operating systems above the 1024 cylinder limit, and you want to place your /boot/ partition above cylinder 1024, you should select this option.
/boot Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
parted, 1024 cylinders equals 528MB. For more information, refer to:
http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html
/dev/mapper/mpath0.
linux rescue at the installation boot prompt. Itanium users should type elilo linux rescue to enter rescue mode.
localhost.
system-config-network command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue.
system-config-date command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig.
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.
su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
system-config-rootpassword command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
/root/install.log once you reboot your system.
login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
eliloelilo, the default kernel listed in the /boot/efi/elilo.conf configuration file is loaded. (The first kernel listed in the file is the default.)
/boot/efi/elilo.conf after the elilo command. For example, to load the kernel named linux, type:
elilo linux/boot/efi/elilo.conf file in EFI with the following instructions:
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.
ls at the fs0:\> to make sure you are in the correct partition.
Shell>type elilo.conf
label followed by a label name for that kernel. The label name is what you type after elilo to boot the different kernels.
single for single user mode or mem=1024M to force Red Hat Enterprise Linux to use 1024 MB of memory. To pass options to the boot loader, enter the following at the EFI Shell prompt (replace linuxoption
elilo linux optionelilo and any boot options at the EFI Shell prompt each time you wish to boot your Itanium system. However, if you wish to configure your system to boot into Red Hat Enterprise Linux automatically, you need to configure the EFI Boot Manager.
/boot/efi/ in Linux.
elilo.efi file.
Enter New Description: prompt, type Red Hat Enterprise Linux 5, or any name that you want to appear on the EFI Boot Manager menu.
Enter Boot Option Data Type: prompt, enter N for if you do not want to pass options to the ELILO boot loader. This option works for most cases. If you want to pass options to the boot loader, you can configure it in the /boot/efi/elilo.conf configuration file instead.
Yes to the Save changes to NVRAM prompt. This returns you to the EFI Boot Maintenance Manager menu.
startup.nsh. The last command should be elilo to boot into Linux.
startup.nsh script should be in the /boot/efi partition (/boot/efi/startup.nsh) and contain the following text:
echo -off your set of commands eliloelilo.
Shell> prompt, change devices to the system partition (mounted as /boot/efi in Linux). For example, if fs0 is the system boot partition, type fs0: at the EFI Shell prompt. Type ls to make sure you are in the correct partition. Then type edit startup.nsh. Type the contents of the file and save it.
startup.nsh file and use it to boot the system. To stop EFI from loading the file, type Ctrl+c . This aborts the process, and returns you to the EFI shell prompt.
fsck application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
fdisk utility to create a new MBR with the undocumented flag /mbr. This ONLY rewrites the MBR to boot the primary DOS partition. The command should look like the following:
fdisk /mbrfdisk, you will experience the Partitions exist but they do not exist problem. The best way to remove non-DOS partitions is with a tool that understands partitions other than DOS.
linux rescue. This starts the rescue mode program.
list-harddrives. This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes.
parted. Start parted, where /dev/hda is the device on which to remove the partition:
parted /dev/hda
print command, view the current partition table to determine the minor number of the partition to remove:
print command also displays the partition's type (such as linux-swap, ext2, ext3, and so on). Knowing the type of the partition helps you in determining whether to remove the partition.
rm. For example, to remove the partition with minor number 3:
rm 3
print command to confirm that it is removed from the partition table.
quit to quit parted.
parted, type exit at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If it does not, you can reboot your computer using Control+Alt+Delete .
No devices found to install Red Hat Enterprise Linux Error Messagehttpd service/Sendmail Hangs During StartupGRUB: ) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
/boot partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/ partition.
boot: or yaboot: prompt (prepend with elilo for Itanium systems):
linux mediacheck
http://www.bitwizard.nl/sig11/resolution= boot option. This option may be most helpful for laptop users. Another solution to try is the driver= option to specify the driver that should be loaded for your video card. If this works, it should be reported as a bug as the installer has failed to autodetect your videocard. Refer to Chapter 8, Additional Boot Options for Intel® and AMD Systems for more information on boot options.
nofb boot option. This command may be necessary for accessibility with some screen reading hardware.
No devices found to install Red Hat Enterprise Linux Error MessageNo devices found to install Red Hat Enterprise Linux, there is probably a SCSI controller that is not being recognized by the installation program.
scp the error message to a remote system.
/tmp/anacdump.txt. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys Ctrl+Alt+F2 and scp the message written to /tmp/anacdump.txt to a known working remote system.
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
swap and a / (root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.
/boot partition if you want the / (root) partition to use all of the remaining space on your hard drive.
/ (root) partition
/boot/efi/ partition of type VFAT
/ (root) partition
/tmp/directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/ are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
/boot/grub/grub.conf file.
grub.conf file, comment out the line which begins with splashimage by inserting the # character at the beginning of the line.
b to boot the system.
grub.conf file is reread and any changes you have made take effect.
grub.conf file.
startx.
/etc/inittab, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
su command.
gedit /etc/inittab to edit the file with gedit. The file /etc/inittab opens. Within the first screen, a section of the file which looks like the following appears:
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
# id:3:initdefault:
id:3:initdefault: from a 3 to a 5.
3 to 5.
id:5:initdefault: df -h
df command should help you diagnose which partition is full. For additional information about df and an explanation of the options available (such as the -h option used in this example), refer to the df man page by typing man df at a shell prompt.
/home/ and /tmp/ partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
linux single.
elilo followed by the boot command.
e for edit when the GRUB boot screen has loaded. You are presented with a list of items in the configuration file for the boot label you have selected.
kernel and type e to edit this boot entry.
kernel line, add:
singleb to boot the system.
# prompt, you must type passwd root, which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password.
su - and enter your root password when prompted. Then, type passwd <username>. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/cat /proc/meminfo command.
/boot/grub/grub.conf:
mem=xxMxx with the amount of RAM you have in megabytes.
/boot/grub/grub.conf, the above example would look similar to the following:
# NOTICE: You have a /boot partition. This means that # all kernel paths are relative to /boot/ default=0 timeout=30 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Enterprise Linux (2.6.9-5.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.EL ro root=/dev/hda3 mem=128M
grub.conf are reflected on your system.
e for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
kernel and type e to edit this boot entry.
kernel line, add
mem=xxMxx equals the amount of RAM in your system.
b to boot the system.
elilo followed by the boot command.
xx with the amount of RAM in your system. Press Enter to boot.
system-config-printer command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
system-config-soundcard) utility.
system-config-soundcard command at a shell prompt to launch the Sound Card Configuration Tool. If you are not root, it prompts you for the root password to continue.
.iso. In the following example, the file is named dd.iso:
OEMDRV, the installation program will automatically examine it for driver updates and load any that it detects. This behavior is controlled by the dlabel=on boot option, which is enabled by default. Refer to Section 7.3.1, “Let the installer automatically find a driver update disk”.
.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.
/dev/fd0 for a floppy disk in the first floppy drive on your system.
fdisk -l on the command line. You will see a list of all storage devices available on your system. Compare the output of fdisk -l when the disk inserted or the storage device is attached with the output of this command when the disk is removed or the storage device is disconnected.
dd if=image of=deviceimage is the image file, and device is the device name. For example, to create a driver disk on floppy disk /dev/fd0 from driver update image file dd.iso, you would use:
dd if=dd.iso of=/dev/fd0.iso.
/tmp/initrd_update directory.
dd.img.
/tmp/initrd_update directory, type the following command, and press Enter:
find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img
/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.
/tftpboot/pxelinux/pxelinux.cfg/default file to include an entry that includes the initial RAM disk update that you just created, in the following format:
labeltarget-dd kerneltarget/vmlinuz append initrd=target/initrd.img,target/dd.img
target is the target that you want to use for installation.
driver_update.iso is a driver update image file that you downloaded from the Internet to a directory on your PXE server. The target that you want to PXE boot from is located in /tftpboot/pxelinux/r5su3
$ cp driver_update.iso /tmp/initrd_update/dd.img $ cd /tmp/initrd_update $ find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img $ cp /tmp/initrd_update.img /tftpboot/pxelinux/r5su3/dd.img
/tftpboot/pxelinux/pxelinux.cfg/default file and include the following entry:
label r5su3-dd kernel r5su3/vmlinuz append initrd=r5su3/initrd.img,r5su3/dd.img
OEMDRV before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 7.2.1.1, “Preparing to use an image file on local storage” to prepare a storage device for the installer to find.
linux dd at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk:
linux dd=URL (where URL is the HTTP, FTP, or NFS address of a driver update image) at the boot prompt at the start of the installation process and press Enter. The installer will retrieve the driver update image from that address and use it during installation.
network boot in your computer's BIOS or boot menu. The procedure to specify this option varies widely among different computers. Consult your hardware documentation or the hardware vendor for specifics relevant to your computer.
r5su3-dd in the /tftpboot/pxelinux/pxelinux.cfg/default file on your PXE server, type r5su3-dd at the prompt and press Enter.
boot: prompt.
askmethodapicdddd=urldisplay=ip:0ip should be replaced with the IP address of the system on which you want the display to appear.
xhost +remotehostname, where remotehostname is the name of the host from which you are running the original display. Using the command xhost +remotehostname limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
driverdiskdd command and also prompts you to use a driver diskette during the installation of Red Hat Enterprise Linux.
linux upgradeany/etc/redhat-release file. If your /etc/redhat-release file has been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5. Use this option only if your existing Red Hat Enterprise Linux installation was not detected.
mediacheckmem=xxxmxxx should be replaced with the amount of memory in megabytes.
mpathnmi_watchdog=1noapicnoejectnomcenonetnopassnopcmcianoprobenoshellnostoragenousbnousbstoragenuma=offreboot=brescueresolution=640x480, 800x600, 1024x768, and so on.
serialtextupdatesrhupdates/ on the server.
updates=vncvncpassword=| Architecture | Boot Loaders |
|---|---|
| AMD® AMD64 | GRUB |
| IBM® eServer™ System i™ | OS/400® |
| IBM® eServer™ System p™ | YABOOT |
| IBM® System z® | z/IPL |
| IBM® System z® | z/IPL |
| Intel® Itanium™ | ELILO |
| x86 | GRUB |
/boot/ partition is above the 1024 cylinder head of the hard drive or when using LBA mode. The Stage 1.5 boot loader is found either on the /boot/ partition or on a small part of the MBR and the /boot/ partition.
/boot/sysroot/ into memory. Once GRUB determines which operating system or kernel to start, it loads it into memory and transfers control of the machine to that operating system.
/boot/grub/grub.conf, every time the system boots, eliminating the need for the user to write a new version of the first stage boot loader to the MBR when configuration changes are made. The only time a user needs to reinstall GRUB on the MBR is if the physical location of the /boot/ partition is moved on the disk. For details on installing GRUB to the MBR, refer to Section 9.3, “Installing GRUB”.
/sbin/grub-install <location>, where <location> is the location that the GRUB Stage 1 boot loader should be installed. For example, the following command installs GRUB to the MBR of the master IDE device on the primary IDE bus:
/sbin/grub-install /dev/hda/boot directory must reside on a single, specific disk partition. The /boot directory cannot be striped across multiple disks, as in a level 0 RAID. To use a level 0 RAID on your system, place /boot on a separate partition outside the RAID.
/boot directory must reside on a single, specific disk partition, GRUB cannot boot the system if the disk holding that partition fails or is removed from the system. This is true even if the disk is mirrored in a level 1 RAID. The following Red Hat Knowledgebase article describes how to make the system bootable from another disk in the mirrored set: http://kbase.redhat.com/faq/docs/DOC-7095
(<type-of-device><bios-device-number>,<partition-number>)
<type-of-device> specifies the type of device from which GRUB boots. The two most common options are hd for a hard disk or fd for a 3.5 diskette. A lesser used device type is also available called nd for a network disk. Instructions on configuring GRUB to boot over the network are available online at http://www.gnu.org/software/grub/manual/.
<bios-device-number> is the BIOS device number. The primary IDE hard drive is numbered 0 and a secondary IDE hard drive is numbered 1. This syntax is roughly equivalent to that used for devices by the kernel. For example, the a in hda for the kernel is analogous to the 0 in hd0 for GRUB, the b in hdb is analogous to the 1 in hd1, and so on.
<partition-number> specifies the number of a partition on a device. Like the <bios-device-number>, most types of partitions are numbered starting at 0. However, BSD partitions are specified using letters, with a corresponding to 0, b corresponding to 1, and so on.
0, not 1. Failing to make this distinction is one of the most common mistakes made by new users.
(hd0) and the second as (hd1). Likewise, GRUB refers to the first partition on the first drive as (hd0,0) and the third partition on the second hard drive as (hd1,2).
hd. The letters fd are used to specify 3.5 diskettes.
(hd0) specifies the MBR on the first device and (hd3) specifies the MBR on the fourth device.
(<device-type><device-number>,<partition-number>)</path/to/file>
<device-type> with hd, fd, or nd. Replace <device-number> with the integer for the device. Replace </path/to/file> with an absolute path relative to the top-level of the device.
0+50,100+25,200+1
(hd0,0)+1chainloader command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:
chainloader +1(hd0,0)/grub/splash.xpm.gz is located within the /grub/ directory at the top-level (or root) of the (hd0,0) partition (which is actually the /boot/ partition for the system).
kernel command is executed with the location of the kernel file as an option. Once the Linux kernel boots, it sets up the root file system that Linux users are familiar with. The original GRUB root file system and its mounts are forgotten; they only existed to boot the kernel file.
bash shell.
boot — Boots the operating system or chain loader that was last loaded.
chainloader </path/to/file> — Loads the specified file as a chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, +1, instead of the file name.
chainloader command:
chainloader +1displaymem — Displays the current use of memory, based on information from the BIOS. This is useful to determine how much RAM a system has prior to booting it.
initrd </path/to/initrd> — Enables users to specify an initial RAM disk to use when booting. An initrd is necessary when the kernel needs certain modules in order to boot properly, such as when the root partition is formatted with the ext3 file system.
initrd command:
initrd /initrd-2.6.8-1.523.imginstall <stage-1> <install-disk> <stage-2> p config-file — Installs GRUB to the system MBR.
<stage-1>(hd0,0)/grub/stage1.
<install-disk>(hd0).
<stage-2>(hd0,0)/grub/stage2.
p <config-file>install command to look for the menu configuration file specified by <config-file>(hd0,0)/grub/grub.conf.
install command overwrites any information already located on the MBR.
kernel </path/to/kernel> <option-1> <option-N> ... — Specifies the kernel file to load when booting the operating system. Replace </path/to/kernel> with an absolute path from the partition specified by the root command. Replace <option-1> with options for the Linux kernel, such as root=/dev/VolGroup00/LogVol00 to specify the device on which the root partition for the system is located. Multiple options can be passed to the kernel in a space separated list.
kernel command:
kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00hda5 partition.
root (<device-type><device-number>,<partition>) — Configures the root partition for GRUB, such as (hd0,0), and mounts the partition.
root command:
root (hd0,0)rootnoverify (<device-type><device-number>,<partition>) — Configures the root partition for GRUB, just like the root command, but does not mount the partition.
help --all for a full list of commands. For a description of all GRUB commands, refer to the documentation available online at http://www.gnu.org/software/grub/manual/.
/boot/grub/grub.conf), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The commands given in Section 9.6, “GRUB Commands” can be used, as well as some special commands that are only available in the configuration file.
/boot/grub/grub.conf. The commands to set the global preferences for the menu interface are placed at the top of the file, followed by stanzas for each operating kernel or operating system listed in the menu.
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux Server (2.6.18-2.el5PAE) root (hd0,0) kernel /boot/vmlinuz-2.6.18-2.el5PAE ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.18-2.el5PAE.img # section to load Windows title Windows rootnoverify (hd0,0) chainloader +1
title line in the GRUB configuration file. For the Windows section to be set as the default in the previous example, change the default=0 to default=1.
chainloader </path/to/file> — Loads the specified file as a chain loader. Replace </path/to/file> with the absolute path to the chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, +1.
color <normal-color> <selected-color> — Allows specific colors to be used in the menu, where two colors are configured as the foreground and background. Use simple color names such as red/black. For example:
color red/black green/bluedefault=<integer> — Replace <integer> with the default entry title number to be loaded if the menu interface times out.
fallback=<integer> — Replace <integer> with the entry title number to try if the first attempt fails.
hiddenmenu — Prevents the GRUB menu interface from being displayed, loading the default entry when the timeout period expires. The user can see the standard GRUB menu by pressing the Esc key.
initrd </path/to/initrd> — Enables users to specify an initial RAM disk to use when booting. Replace </path/to/initrd> with the absolute path to the initial RAM disk.
kernel </path/to/kernel> <option-1> <option-N> — Specifies the kernel file to load when booting the operating system. Replace </path/to/kernel> with an absolute path from the partition specified by the root directive. Multiple options can be passed to the kernel when it is loaded.
password=<password> — Prevents a user who does not know the password from editing the entries for this menu option.
password=<password> directive. In this case, GRUB restarts the second stage boot loader and uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file.
root (<device-type><device-number>,<partition>) — Configures the root partition for GRUB, such as (hd0,0), and mounts the partition.
rootnoverify (<device-type><device-number>,<partition>) — Configures the root partition for GRUB, just like the root command, but does not mount the partition.
timeout=<integer> — Specifies the interval, in seconds, that GRUB waits before loading the entry designated in the default command.
splashimage=<path-to-image> — Specifies the location of the splash screen image to be used when GRUB boots.
title group-title — Specifies a title to be used with a particular group of commands used to load a kernel or operating system.
#).
kernel command.
<space><runlevel> at the end of the boot options line to boot to the desired runlevel. For example, the following entry would initiate a boot process into runlevel 3:
grub append> ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3/usr/share/doc/grub-<version-number>/ — This directory contains good information about using and configuring GRUB, where <version-number> corresponds to the version of the GRUB package installed.
info grub — The GRUB info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB and its usage.
Table of Contents
httpd service/Sendmail Hangs During Startupyaboot: prompt:
linux mediacheck/location/of/disk/space/publicly/available/directory. For example, /location/of/disk/space/var/isos. /publicly/available/directory/var/www/html/rhel5, for an HTTP install.
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
dvd refers to your DVD drive device.
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):
mount /media/cdrom
cp -a /media/cdrom/Server <target-directory>
cp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory> (Installation CD 1 or DVD only)
cp /media/cdrom/images <target-directory> (Installation CD 1 or DVD only)
umount /media/cdrom
<target-directory>/publicly/available/directory mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory/etc/exports.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload).
dd if=/dev/cdrom of=/tmp/file-name.iso
md5sum program (many md5sum programs are available for various operating systems). An md5sum program should be available on the same Linux machine as the ISO images.
updates.img exists in the location from which you install, it is used for updates to anaconda, the installation program. Refer to the file install-methods.txt in the anaconda RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
X key command combination as a way of clicking on buttons or making other screen selections, where X is replaced with any underlined letter appearing within that screen.
yaboot: prompt:
linux text
boot: prompt. Press Enter or wait for the timeout to expire for the installation to begin.
images/netboot/ppc64.img file on CD #1.
| console | keystrokes | contents |
|---|---|---|
| 1 | ctrl+alt+f1 | installation dialog |
| 2 | ctrl+alt+f2 | shell prompt |
| 3 | ctrl+alt+f3 | install log (messages from installation program) |
| 4 | ctrl+alt+f4 | system-related messages |
| 5 | ctrl+alt+f5 | other messages |
| 6 | ctrl+alt+f6 | x graphical display |
askmethod boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition.
/. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/, and the images are in /home/new/, you would enter /new/.
askmethod boot option, the Configure TCP/IP dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually. If manually, you have the option to enter IPv4 and/or IPv6 information. Enter the IP address you are using during installation and press Enter. Note that you need to supply IPv4 information if you wish to perform an NFS installation.
eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field.
/export/directory/variant/askmethod boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
askmethod boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue.
/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.
mapper/mpath instead.
/boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
/boot/ partition is also necessary for software RAID setups.
/boot/ partition.
/) partition, a /boot/ partition, PPC PReP boot partition, and a swap partition equal to twice the amount of RAM you have on the system.
| Amount of RAM in the System | Recommended Amount of Swap Space |
|---|---|
| 4GB of RAM or less | a minimum of 2GB of swap space |
| 4GB to 16GB of RAM | a minimum of 4GB of swap space |
| 16GB to 64GB of RAM | a minimum of 8GB of swap space |
| 64GB to 256GB of RAM | a minimum of 16GB of swap space |
| 256GB to 512GB of RAM | a minimum of 32GB of swap space |
/boot/ partition (100 MB) — the partition mounted on /boot/ contains the operating system kernel (which allows your system to boot Red Hat Enterprise Linux), along with files used during the bootstrap process. Due to the limitations of most PC firmware, creating a small partition to hold these is a good idea. For most users, a 100 MB boot partition is sufficient.
root partition (3.0 GB - 5.0 GB) — this is where "/" (the root directory) is located. In this setup, all files (except those stored in /boot) are on the root partition.
/var on network storage/var on a network filesystem (for example, NFS, iSCSI, or NBD) The /var directory contains critical data that must be read from or written to during the boot process before establishing network services.
/var/spool, /var/www or other subdirectories on a separate network disk, just not the complete /var filesystem.
/; 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.
fsck [6] the file system. The ext3 file system is selected by default and is highly recommended.
system-config-network command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue.
system-config-date command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig.
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.
su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
system-config-rootpassword command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
/root/install.log once you reboot your system.
E1F1, then press 1 to enter the System Management Services GUI. Click on . Select . Select . Select the disk containing Red Hat Enterprise Linux. Set the other devices as you wish. Then exit the SMS menus to boot your new system.
boot: prompt for a list of valid boot labels.)
login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
fsck application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
.iso. In the following example, the file is named dd.iso:
OEMDRV, the installation program will automatically examine it for driver updates and load any that it detects. This behavior is controlled by the dlabel=on boot option, which is enabled by default. Refer to Section 13.3.1, “Let the installer automatically find a driver update disk”.
.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.
/dev/fd0 for a floppy disk in the first floppy drive on your system.
fdisk -l on the command line. You will see a list of all storage devices available on your system. Compare the output of fdisk -l when the disk inserted or the storage device is attached with the output of this command when the disk is removed or the storage device is disconnected.
dd if=image of=deviceimage is the image file, and device is the device name. For example, to create a driver disk on floppy disk /dev/fd0 from driver update image file dd.iso, you would use:
dd if=dd.iso of=/dev/fd0.iso.
/tmp/initrd_update directory.
dd.img.
/tmp/initrd_update directory, type the following command, and press Enter:
find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img
/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.
/tftpboot/pxelinux/pxelinux.cfg/default file to include an entry that includes the initial RAM disk update that you just created, in the following format:
labeltarget-dd kerneltarget/vmlinuz append initrd=target/initrd.img,target/dd.img
target is the target that you want to use for installation.
driver_update.iso is a driver update image file that you downloaded from the Internet to a directory on your PXE server. The target that you want to PXE boot from is located in /tftpboot/pxelinux/r5su3
$ cp driver_update.iso /tmp/initrd_update/dd.img $ cd /tmp/initrd_update $ find . | cpio --quiet -c -o | gzip -9 >/tmp/initrd_update.img $ cp /tmp/initrd_update.img /tftpboot/pxelinux/r5su3/dd.img
/tftpboot/pxelinux/pxelinux.cfg/default file and include the following entry:
label r5su3-dd kernel r5su3/vmlinuz append initrd=r5su3/initrd.img,r5su3/dd.img
OEMDRV before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 13.2.1.1, “Preparing to use an image file on local storage” to prepare a storage device for the installer to find.
linux dd at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk:
linux dd=URL (where URL is the HTTP, FTP, or NFS address of a driver update image) at the boot prompt at the start of the installation process and press Enter. The installer will retrieve the driver update image from that address and use it during installation.
network boot in your computer's BIOS or boot menu. The procedure to specify this option varies widely among different computers. Consult your hardware documentation or the hardware vendor for specifics relevant to your computer.
r5su3-dd in the /tftpboot/pxelinux/pxelinux.cfg/default file on your PXE server, type r5su3-dd at the prompt and press Enter.
httpd service/Sendmail Hangs During Startuphttp://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html
boot: or yaboot: prompt (prepend with elilo for Itanium systems):
linux mediacheck
http://www.bitwizard.nl/sig11/resolution= boot option. Refer to Chapter 15, Additional Boot Options for IBM Power Systems for more information.
nofb boot option. This command may be necessary for accessibility with some screen reading hardware.
No devices found to install Red Hat Enterprise Linux Error MessageNo devices found to install Red Hat Enterprise Linux, there is probably a SCSI controller that is not being recognized by the installation program.
scp the error message to a remote system.
/tmp/anacdump.txt. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys Ctrl+Alt+F2 and scp the message written to /tmp/anacdump.txt to a known working remote system.
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
/ (root) partition
/tmp/directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/ are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
startx.
/etc/inittab, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
su command.
gedit /etc/inittab to edit the file with gedit. The file /etc/inittab opens. Within the first screen, a section of the file which looks like the following appears:
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
# id:3:initdefault:
id:3:initdefault: from a 3 to a 5.
3 to 5.
id:5:initdefault: df -h
df command should help you diagnose which partition is full. For additional information about df and an explanation of the options available (such as the -h option used in this example), refer to the df man page by typing man df at a shell prompt.
/home/ and /tmp/ partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
linux single.
# prompt, you must type passwd root, which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password.
su - and enter your root password when prompted. Then, type passwd <username>. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/system-config-printer command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
boot: prompt.
askmethoddddd=urldisplay=ip:0ip should be replaced with the IP address of the system on which you want the display to appear.
xhost +remotehostname, where remotehostname is the name of the host from which you are running the original display. Using the command xhost +remotehostname limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
driverdiskdd command and also prompts you to use a driver diskette during the installation of Red Hat Enterprise Linux.
ide=nodmamediacheckmem=xxxmxxx should be replaced with the amount of memory in megabytes.
mpathnoejectnopassnopcmcianoprobenoshellnostoragenousbnousbstoragerescueresolution=640x480, 800x600, 1024x768, and so on.
serialtextupdatesrhupdates/ on the server.
vncvncpassword=Table of Contents
http://www.redbooks.ibm.com/
clearpart documentation in Section 31.4, “Kickstart Options” for a method to ensure that DASDs are formatted during installation.
kernel.img), the ram disk (initrd.img), and if using z/VM, an optional CMS configuration file (redhat.conf) and a parameter file. Sample parameter and CMS configuration files are provided (redhat.parm and redhat.conf). You should edit the CMS configuration file and add information about your DASD. You may also want to add some information about your network configuration. Once this is started on the IBM System z, the networking is configured. You can then use ssh on another computer to log into your installation image. Now you can start an installation script to install Red Hat Enterprise Linux.
/location/of/disk/space/publicly/available/directory. For example, /location/of/disk/space/var/isos. /publicly/available/directory/var/www/html/rhel5, for an HTTP install.
dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso
dvd refers to your DVD drive device.
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):
mount /media/cdrom
cp -a /media/cdrom/Server <target-directory>
cp -a /media/cdrom/Client <target-directory>
cp /media/cdrom/RELEASE-NOTES* <target-directory> (Installation CD 1 or DVD only)
cp /media/cdrom/images <target-directory> (Installation CD 1 or DVD only)
umount /media/cdrom
<target-directory>/publicly/available/directory mv /location/of/disk/space/RHEL5.iso /publicly/available/directory/
mv /location/of/disk/space/disk*.iso /publicly/available/directory/
/publicly/available/directory/etc/exports.
/publicly/available/directory client.ip.address
/publicly/available/directory *
/sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload).
dd if=/dev/cdrom of=/tmp/file-name.iso
md5sum program (many md5sum programs are available for various operating systems). An md5sum program should be available on the same Linux machine as the ISO images.
updates.img exists in the location from which you install, it is used for updates to anaconda, the installation program. Refer to the file install-methods.txt in the anaconda RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as well as how to apply the installation program updates.
i cms
vmlink tcpmaint 592 592
set qioassist off
kernel.img and initrd.img), log in, and execute the following commands. Use the (repl option if you are overwriting existing kernel.img, initrd.img, generic.prm, or redhat.exec files:
cd/location/of/boot/images//images/locsite fix 80binget kernel.img (replget initrd.img (replasciiget generic.prm (replget redhat.exec (replquit
redhat.parm). Refer to Chapter 19, Sample Parameter Files for sample parm files. Below is an explanation of the parm file contents.
.parm file is still required for the real kernel parameters, such as root=/dev/ram0 ro ip=off ramdisk_size=40000, and single parameters which are not assigned to variables, such as vnc. Two parameters which are used in z/VM installs to point the installation program at the new CMS configuration file need to be added to the .parm file:
CMSDASD=191 CMSCONFFILE=redhat.conf
variable="value" pairs, one on each line.
redhat.parm file:
root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc
redhat.exec file shipped by Red Hat is:
/* */ 'cl rdr' 'purge rdr all' 'spool punch * rdr' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'ch rdr all keep nohold' 'i 00c'
redhat.conf file:
HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096"
DASD=dasd-list
dasd-listDASD= parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in an unusable system.
root=file-system
file-system/dev/ram0, which is the ramdisk containing the Red Hat Enterprise Linux installation program.
SUBCHANNELS=
qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id, data_device_bus_id" lcs: SUBCHANNELS="read_device_bus_id,write_device_bus_id"
SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
HOSTNAME=string
stringNETTYPE=type
typelcs, or qeth.
lcs for:
qeth for:
IPADDR=IP
IPNETWORK=network
networkNETMASK=netmask
netmaskBROADCAST=broadcast
broadcastGATEWAY=gw
gweth device.
MTU=mtu
mtuDNS=server1:server2::serverN
server1:server2::serverNDNS=10.0.0.1:10.0.0.2
SEARCHDNS=domain1:domain2::domainN
domain1:domain2::domainNSEARCHDNS=example.com:example.org
PORTNAME=osa_portname | lcs_portnumberosa_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.
lcs_portnumber is used to pass the relative port number as integer in the range of 0 through 15.
FCP_n="device_number SCSI_ID WWPN SCSI_LUN FCP_LUN"
FCP_1="0.0.5000 0x01 0x5105074308c212e9 0x0 4010"n is an integer value (e.g. FCP_1, FCP_2, ...).
device_number is used to specify the address of the FCP device ( 0.0.5000 for device 5000, for example).
SCSI_ID is specified in hex-value, typically sequential values (e.g. 0x01, 0x02 ... ) are used over multiple FCP_ variables.
WWPN is the world wide port name used for routing (often in conjunction with multipathing) and is as a 16-digit hex value (e.g. 0x5105074308c212e9).
SCSI_LUN refers to the local SCSI logical unit value and is specified as a hex-value, typically sequential values (e.g. 0x00, 0x01, ...) are used over multiple FCP_ variables.
FCP_LUN refers to the storage logical unit identifier and is specified as a hex-value (such as 0x4010).
PORTNO=0 (to use port 0) or PORTNO=1 (to use port 1) to the CMS configuration file to avoid being prompted for the mode.
LAYER2=0 or LAYER2=1 to the CMS configuration file. Use LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode.
LAYER2=1, you can also specify VSWITCH=1 when connecting to a VSWITCH, or VSWITCH=0 when connecting directly to the OSA. If a VSWITCH is not in use, specify the MAC address in the CMS configuration file using the parameter MACADDR=<MAC address>.
RUNKS=value
value1 if you want to run the installation program in noninteractive (kickstart) mode in the 3270 terminal, or 0 otherwise.
cmdline
cmdline is specified, 3270 terminal output becomes much more readable, as the installer disables most escape terminal sequences that are applicable to unix-like consoles, but not supported on the 3270 console.
parm file, a prompt appears during the installation boot process.
i cms
redhat.exec that contains the commands necessary to IPL the kernel image and start the installation. After having IPLed CMS, enter redhat on the 3270 console and press the Enter key to execute this script.
parm file.
generic.ins then click Continue.
ftp.redhat.com)
/pub/redhat/linux/rawhide/s390x)
redhat.ins and click .
dasda has dasda[123].
X key command combination as a way of clicking on buttons or making other screen selections, where X is replaced with any underlined letter appearing within that screen.
ssh to the configured Linux install system on the IBM System z.
DISPLAY= variable in the parm file. The text-based installation is similar to the graphical installation; however, the graphical installation offers more package selection details and other options not available in text-based installs. It is strongly recommended to use the graphical installation whenever possible.
ssh -X linuxvm.example.com-X option enables X11 forwarding.
DISPLAY= variable. Add the parameter DISPLAY=workstationname:0.0 in the parameter file, replacing workstationname with the hostname of the client workstation connecting to the Linux Image. Allow the Linux image to connect to the workstation using the command xhost +linuxvm on the local workstation.
DISPLAY= variable settings in the parm file. If performing a VM installation, rerun the installation to load the new parm file on the reader. Additionally, make sure when performing an X11 forwarded display that the X server is started on the workstation machine. Finally, make sure either the NFS, FTP or HTTP protocols are selected, as all 3 methods support graphical installations.
loader will start the installation program.
loader starts, several screens appear for selecting the installation method.
askmethod boot options and selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition.
/. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/, and the images are in /home/new/, you would enter /new/.
eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field.
/export/directory/askmethod boot options and selected in the Installation Method dialog). This dialog allows you to identify the FTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
askmethod boot option and selected in the Installation Method dialog). This dialog prompts you for information about the HTTP server from which you are installing Red Hat Enterprise Linux. If you used the repo=http boot option, you already specified a server and path.
variant//mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
mkdir discX
mount -o loop RHEL5-discX.iso discX
X with the corresponding disc number.
/home partition that persistently contains user information).
/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.
mapper/mpath instead.
Disk Druid portion of the installation.
/boot. The kernel files and bootloader sector will be associated with this device. For most common cases, the first DASD or SCSI LUN will be used, but for some unusual cases, this may not be the case. The device number will be used when re-ipling the post-installed system.
qdio/qeth devices that are configured with OSA layer 3 support. Layer 3 does not provide MAC address or Address Resolution Protocol (ARP) abilities and so can not be used with network services that require them.
system-config-date command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.
timeconfig.
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.
su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
system-config-rootpassword command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue.
/root/install.log once you reboot your system.
/boot partition for Red Hat Enterprise Linux has been installed.
200 on the 3270 console you may issue the command #cp i 200. Often, especially in DASD only environments where automatic partitioning (clearing data from all partitions) was chosen, the first dasd (dasda) is where the /boot partition is located.
/boot on a SCSI LUN in a z/VM guest account, it may be necessary to provide WWPN and LUN information through which a zFCP device can ipl. As an example,
#CP SET LOADDEV PORTNAME 50050763 FCCD9689 LUN 83030000 00000000
0x50050763FCCD9689 is the example WWPN, and 8303 is the SCSI LUN). Then the zFCP device information can be queried and used to start the IPL:
#cp q v fcp
4322 in this example) could be ipl-ed with a command like:
#cp ipl 4322
/boot partition is located.
#cp disc instead of #cp logout or #cp log. This allows for the virtual system running Red Hat Enterprise Linux for IBM System z to continue even when not connected to the 3270 console.
ssh. It is important to note that the only place you can log in as root is from the 3270 or from other devices as listed in /etc/securetty.
.parm file should contain the real kernel parameters, such as root=/dev/ram0 ro ip=off ramdisk_size=40000, and single parameters which are not assigned to variables, such as vnc. Two new parameters which point the installation program at the new configuration file need to be added to the .parm file. They are CMSDASD and CMSCONF .
CMSDASD=cmsdasd_address cmsdasd_address represents the list of the device ID of the CMS DASD device which contains the configuration file. This is usually the CMS user's 'A' disk. This option is applicable only for users who have a CMS formatted disk (z/VM) available.
CMSDASD=191
CMSCONFFILE=configuration_file configuration_file represents the name of the configuration file. This value must be specified in lower case. It is specified in a Linux style file name format. The CMS file REDHAT CONF is specified as redhat.conf. This option is applicable only for users who have a CMS formatted disk (z/VM) available.
CMSCONFFILE=redhat.conf
DASD=dasd-list dasd-list represents the list of DASD devices to be used by Red Hat Enterprise Linux.
DASD= parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the guest. This can result in an unusable system.
DASD=0.0.0100,0.0201-0.0.0204
SUBCHANNELS=qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id,
data_device_bus_id"
lcs: SUBCHANNELS="read_device_bus_id,write_device_bus_id"SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
HOSTNAME=string string is the hostname of the newly-installed Linux guest.
NETTYPE=type type must be one of the following: qeth or lcs.
IPADDR=IP IP is the IP address of the new Linux guest.
NETWORK=network network is the address of your network.
NETMASK=netmask netmask is the netmask.
BROADCAST=broadcast broadcast is the broadcast address.
GATEWAY=gw gw is the gateway-IP for your eth device.
MTU=mtu mtu is the Maximum Transmission Unit (MTU) for this connection.
DNS=server1:server2:additional_server_terms:serverN server1:server2:additional_server_terms:serverN is a list of DNS servers, separated by colons. For example:
DNS=10.0.0.1:10.0.0.2
SEARCHDNS=domain1:domain2:additional_dns_terms:domainN domain1:domain2:additional_dns_terms:domainN is a list of the search domains, separated by colons. For example:
SEARCHDNS=example.com:example.org
PORTNAME=osa_portname | lcs_portnumber 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.
lcs_portnumber is used to pass the relative port number as integer in the range of 0 through 15.
PORTNO=portnumberPORTNO=0 (to use port 0) or PORTNO=1 (to use port 1) to the CMS configuration file to avoid being prompted for the mode.
PORTNO= setting also works on LPAR, but you must place it directly in the parmfile rather than the CMS configuration file.
LAYER2=LAYER2=0 or LAYER2=1 to the CMS configuration file to make the mode persistent when installing on a System z guest.
LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode.
VSWITCH=LAYER2=1, you can also specify VSWITCH=1 when connecting to a VSWITCH, or VSWITCH=0 when connecting directly to the OSA.
MACADDR=MAC_addressLAYER2=1 and a VSWITCH is not in use, you can use this parameter to specify the MAC address in the CMS configuration file.
root=/dev/ram0 DASD=200
redhat.parm file:
root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf vnc
redhat.conf file (pointed to by CMSCONFFILE in redhat.parm)
DASD=200 HOSTNAME="foobar.systemz.example.com" DASD="200-203" NETTYPE="qeth" IPADDR="192.168.17.115" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096"
boot: prompt.
zipl.conf file, either by editing the file manually or using the zipl tool.
zipl.conf that contain quotation marks parameters="vmhalt='LOGOFF'" is correct, while parameters='vmhalt="LOGOFF"' is not correct and may lead to unexpected behavior.
askmethoddd=urldisplay=ip:0ip should be replaced with the IP address of the system on which you want the display to appear.
xhost +remotehostname, where remotehostname is the name of the host from which you are running the original display. Using the command xhost +remotehostname limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
mediacheckmpathnoejectnoproberescuetextvncvncpassword=noipv6cmdlineRUNKS=1cmdline option) kickstart installation for IBM System z.
No devices found to install Red Hat Enterprise Linux Error MessageNo devices found to install Red Hat Enterprise Linux, then there may be an issue with your DASD devices. If you encounter this error, add the DASD=<disks> parameter to your parm file (where disks is the DASD range reserved for installation) and start the install again.
dasdfmt command within a Linux root shell, instead of formatting the DASDs using CMS.
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
/ (root) partition
/tmp/directory. The error may look similar to:
Traceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run rc = self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall self.fstab.savePartitions () File "fstab.py", line 221, in savePartitions sys.exit(0) SystemExit: 0 Local variables in innermost frame: self: <fstab.GuiFstab instance at 8446fe0> sys: <module 'sys' (built-in)> ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
/tmp/ are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
http://www.redhat.com/support/errata/
http://fedoraproject.org/wiki/Anaconda
http://bugzilla.redhat.com/bugzilla/
http://www.redhat.com/apps/activate/
/etc/gdm/custom.conf file on the Red Hat Enterprise Linux system with a text editor such as vi or nano:
Enable=true, save the file, and exit the text editor. Switch to runlevel 5 to start the X server:
/sbin/init 5
X. For example:
X :1 -query s390vm.example.coms390vm.example.com with the hostname of the remote X server) and displays the remote graphical login screen on display :1 of the client system (usually accessible by using the Ctrl-Alt-F8 key combination).
Xnest allows users to open a remote desktop nested within their local X session. For example, run Xnest using the following command, replacing s390vm.example.com with the hostname of the remote X server:
Xnest :1 -query s390vm.example.comlinux single.
# prompt, you must type passwd root, which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password.
su - and enter your root password when prompted. Then, type passwd <username>. This allows you to enter a new password for the specified user account.
http://hardware.redhat.com/hcl/system-config-printer command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
sysfs File Systemsysfs file system. The sysfs file system is described as a union of the proc, devfs, and devpty file systems. The sysfs file system enumerates the devices and busses attached to the system into a file system hierarchy that can be accessed from user space. It is designed to handle the device and driver specific options that have previously resided in /proc/, and encompass the dynamic device addition previously offered by devfs.
sysfs file system is mounted at /sys/ and contains directories that organize the devices attached to the system in several different ways. The /sysfs/ subdirectories include:
/devices/ directory
/css0/ directory. Its subdirectories represent all the subchannels detected by the Linux kernel. Subchannel directories are named in the form 0.0.nnnn where nnnn is the subchannel number in hex between 0000 and ffff. Subchannel directories in turn contain status files and another subdirectory which represents the actual device. The device directory is named 0.0.xxxx where xxxx is the unit address for the device. The /devices/ directory also contains status information as well as configuration options for the device.
/bus/ directory
/ccw/ subdirectory and a /ccwgroup/ subdirectory. CCW devices are accessed using channel command words. Devices in the /ccw/ directory only use one subchannel on the mainframe channel subsystem. CCW group devices are also accessed with channel command words, but they use more than one subchannel per device. For example, a 3390-3 DASD device uses one subchannel, while a QDIO network connection for an OSA adapter uses three subchannels. The /ccw/ and the /ccwgroup/ directories both contain directories called devices and drivers:
/devices/ directory contains a symbolic link to the device directories in the /sys/devices/css0/ directory.
/drivers/ directory contains directories for each device driver currently loaded on the system. Drivers associated with devices such as dasd, console, qeth, and zfcp have directory entries here. The /driver/ directory contains settings for the device driver, as well as symbolic links to the devices it is using (in the /sys/devices/css0/ directory).
/class/ directory
/block/ directory
sysfs is the need to refer to devices by their sysfs name. On a 2.4 kernel image, the zFCP driver was passed as its device addresses. On the 2.6 Kernel image system the driver is passed as 0.0.1600.
zFCP Driver/etc/zfcp.conf file which contains your SCSI configuration. It also adds the line alias scsi_hostadapter zFCP to /etc/modprobe.conf. This loads the required zFCP modules.
# cat /etc/zfcp.conf 0.0.010a 0x01 0x5005076300c18154 0x00 0x5719000000000000 # cat /etc/modprobe.conf alias eth0 qeth options dasd_mod dasd=201,4b2e alias scsi_hostadapter zfcp
# cd /lib/modules/2.6.7-1.451.2.3/kernel/drivers/s390/scsi # modprobe zfcp # lsmod Module Size Used by zfcp 221460 0 [permanent] autofs4 39944 0 qeth 166288 0 qdio 60240 3 zfcp,qeth ccwgroup 25344 1 qeth ipt_REJECT 23552 1 ipt_state 18944 5 ip_conntrack 57904 1 ipt_state iptable_filter 19712 1 ip_tables 37888 3 ipt_REJECT,ipt_state,iptable_filter sd_mod 39688 0 scsi_mod 182904 2 zfcp,sd_mod dm_mod 86408 0 ext3 179056 2 jbd 92720 1 ext3 dasd_fba_mod 25344 0 dasd_eckd_mod 77056 4 dasd_mod 85328 6 dasd_fba_mod,dasd_eckd_mod # cd /sys/bus/ccw/drivers/zfcp/0.0.010a # echo 1 > online # cat online 1 # echo 0x5005076300c18154 > /sys/bus/ccw/drivers/zfcp/0.0.010a/port_add # ls 0x5005076300c18154 failed lic_version s_id availability fc_link_speed nameserver status card_version fc_service_class online wwnn cmb_enable fc_topology port_add wwpn cutype hardware_version port_remove detach_state host2 scsi_host_no devtype in_recovery serial_number # cd /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154 # echo 0x5719000000000000 > unit_add # ls 0x5719000000000000 d_id in_recovery status unit_remove detach_state failed scsi_id unit_add wwnn # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/scsi_host_no 0x0 # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id 0x1 # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun 0x0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.010a # cat /sys/bus/scsi/devices/0\:0\:1\:0/wwpn 0x5005076300c18154 # cat /sys/bus/scsi/devices/0\:0\:1\:0/fcp_lun 0x5719000000000000 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/dev 8:0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/sda1/dev 8:1 # cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: 2105F20 Rev: .123 Type: Direct-Access ANSI SCSI revision: 03 # fdisk /dev/sda # mke2fs -j /dev/sda1 # mount /dev/sda1 /mnt # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2344224 1427948 797196 65% / none 511652 0 511652 0% /dev/shm /dev/dasdb1 2365444 32828 2212456 2% /opt /dev/sda1 3844088 32828 3615988 1% /mnt # cd /boot # mv initrd-2.6.7-1.451.2.3.img initrd-2.6.7-1.451.2.3.img.orig # mkinitrd -v --with=scsi_mod --with=zfcp --with=sd_mod initrd-2.6.7-1.451.2.3.img 2.6.7-1.451.2.3 Looking for deps of module ide-disk Looking for deps of module dasd_mod Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Looking for deps of module scsi_mod Looking for deps of module zfcp qdio scsi_mod Looking for deps of module qdio Looking for deps of module scsi_mod Looking for deps of module sd_mod scsi_mod Looking for deps of module scsi_mod Using modules: ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/s390/cio/qdio.ko ./kernel/drivers/s390/scsi/zfcp.ko ./kernel/drivers/scsi/sd_mod.ko Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.cT1534/bin/nash /sbin/insmod.static -> /tmp/initrd.cT1534/bin/insmod `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko'-> `/tmp/initrd.cT1534/lib/dasd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_eckd_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_fba_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko' -> `/tmp/initrd.cT1534/lib/jbd.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko' -> `/tmp/initrd.cT1534/lib/ext3.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/scsi_mod.ko' -> `/tmp/initrd.cT1534/lib/scsi_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/cio/qdio.ko' -> `/tmp/initrd.cT1534/lib/qdio.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/scsi/zfcp.ko' -> `/tmp/initrd.cT1534/lib/zfcp.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/sd_mod.ko' -> `/tmp/initrd.cT1534/lib/sd_mod.ko' ... Loading module dasd_mod with options dasd=201,4b2e Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3 Loading module scsi_mod Loading module qdio Loading module zfcp Loading module sd_mod # zipl -V Using config file '/etc/zipl.conf' Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: 0201 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 3308 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 595416 Building bootmap '/boot//bootmap' Building menu 'rh-automatic-menu' Adding #1: IPL section 'linux' (default) kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000 kernel parmline...: 'root=LABEL=/' at 0x1000 initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000 Preparing boot device: dasda (0201). Preparing boot menu Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: 'linux' Syncing disks... Done.
mdadm to Configure RAID-Based and Multipath Storageraidtools package set, the mdadm command can be used to perform all the necessary functions related to administering multiple-device sets. This section explains how mdadm can be used to:
mdadm/etc/mdadm.conf file to define appropriate DEVICE and ARRAY values:
DEVICE /dev/sd[abcd]1 ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
DEVICE line is using traditional file name globbing (refer to the glob(7) man page for more information) to define the following SCSI devices:
/dev/sda1
/dev/sdb1
/dev/sdc1
/dev/sdd1
ARRAY line defines a RAID device (/dev/md0) that is comprised of the SCSI devices defined by the DEVICE line.
/proc/mdstat file shows no active RAID devices:
Personalities : read_ahead not set Event: 0 unused devices: none
mdadm command to create a RAID 0 array:
mdadm -C /dev/md0 --level=raid0 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 \ /dev/sdd1 Continue creating array? yes mdadm: array /dev/md0 started.
mdadm --detail /dev/md0:
/dev/md0:
Version : 00.90.00
Creation Time : Mon Mar 1 13:49:10 2004
Raid Level : raid0
Array Size : 15621632 (14.90 GiB 15.100 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Mar 1 13:49:10 2004
State : dirty, no-errors
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
UUID : 25c0f2a1:e882dfc0:c0fe135e:6940d932
Events : 0.1mdadmmdadm can also be used to take advantage of hardware supporting more than one I/O path to individual SCSI LUNs (disk drives). The goal of multipath storage is continued data availability in the event of hardware failure or individual path saturation. Because this configuration contains multiple paths (each acting as an independent virtual controller) accessing a common SCSI LUN (disk drive), the Linux kernel detects each shared drive once "through" each path. In other words, the SCSI LUN (disk drive) known as /dev/sda may also be accessible as /dev/sdb, /dev/sdc, and so on, depending on the specific configuration.
mdadm includes an additional parameter to its level option. This parameter multipath directs the md layer in the Linux kernel to re-route I/O requests from one pathway to another in the event of an I/O path failure.
/etc/mdadm.conf file to define values for the DEVICE and ARRAY lines that reflect your hardware configuration.
/etc/mdadm.conf must represent different physical disk drives), each device in this file refers to the same shared disk drive.
multipath parameter:
mdadm -C /dev/md0 --level=multipath --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 Continue creating array? yes mdadm: array /dev/md0 started.
/dev/md0 is created, all I/O operations referencing /dev/md0 are directed to /dev/sda1, /dev/sdb1, /dev/sdc1, or /dev/sdd1 (depending on which path is currently active and operational).
/dev/md0 can be examined more closely using the command mdadm --detail /dev/md0 to verify that it is, in fact, a multipath device:
/dev/md0:
Version : 00.90.00
Creation Time : Tue Mar 2 10:56:37 2004
Raid Level : multipath
Array Size : 3905408 (3.72 GiB 3.100 GB)
Raid Devices : 1
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Mar 2 10:56:37 2004
State : dirty, no-errors
Active Devices : 1
Working Devices : 4
Failed Devices : 0
Spare Devices : 3
Number Major Minor RaidDevice State
0 8 49 0 active sync /dev/sdd1
1 8 17 1 spare /dev/sdb1
2 8 33 2 spare /dev/sdc1
3 8 1 3 spare /dev/sda1
UUID : 4b564608:fa01c716:550bd8ff:735d92dc
Events : 0.1mdadm is the ability to force a device (be it a member of a RAID array or a path in a multipath configuration) to be removed from an operating configuration. In the following example, /dev/sda1 is flagged as being faulty, is then removed, and finally is added back into the configuration. For a multipath configuration, these actions would not affect any I/O activity taking place at the time:
# mdadm /dev/md0 -f /dev/sda1 mdadm: set /dev/sda1 faulty in /dev/md0 # mdadm /dev/md0 -r /dev/sda1 mdadm: hot removed /dev/sda1 # mdadm /dev/md0 -a /dev/sda1 mdadm: hot added /dev/sda1 #
SET LOADDEV command.
#cp set loaddev portname 50050763 00c18154 lun 57190000 00000000 Ready; T=0.01/0.01 15:47:53 q loaddev PORTNAME 50050763 00C18154 LUN 57190000 00000000 BOOTPROG 0 BR_LBA 00000000 00000000 Ready; T=0.01/0.01 15:47:56
q fcp 00: FCP 010A ON FCP 010ACHPID C1 SUBCHANNEL = 0000 00: 010A QDIO-ELIGIBLE QIOASSIST-ELIGIBLE Ready; T=0.01/0.01 15:51:29 i 010a 00: I 010A 00: HCPLDI2816I Acquiring the machine loader from the processor controller. 00: HCPLDI2817I Load completed from the processor controller. 00: HCPLDI2817I Now starting machine loader version 0001. 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 00. 00: MLOEVL012I: Machine loader up and running (version 0.13). 00: MLOPDM003I: Machine loader finished, moving data to final storage location. Linux version 2.6.7-1.451.2.3 (bhcompile@example.z900.redhat.com) (gcc version 3.4 .1 20040702 (Red Hat Linux 3.4.1-2)) #1 SMP Wed Jul 14 17:52:22 EDT 2004 We are running under VM (64 bit mode)
CP LINK RHEL4X 4B2E 4B2E MR DASD 4B2E LINKED R/W
cd command to change to the /sys/ directory that represents that volume:
# cd /sys/bus/ccw/drivers/dasd-eckd/0.0.4b2e/ # ls -l total 0 -r--r--r-- 1 root root 4096 Aug 25 17:04 availability -rw-r--r-- 1 root root 4096 Aug 25 17:04 cmb_enable -r--r--r-- 1 root root 4096 Aug 25 17:04 cutype -rw-r--r-- 1 root root 4096 Aug 25 17:04 detach_state -r--r--r-- 1 root root 4096 Aug 25 17:04 devtype -r--r--r-- 1 root root 4096 Aug 25 17:04 discipline -rw-r--r-- 1 root root 4096 Aug 25 17:04 online -rw-r--r-- 1 root root 4096 Aug 25 17:04 readonly -rw-r--r-- 1 root root 4096 Aug 25 17:04 use_diag
# cat online 0
# echo 1 > online # cat online 1
# ls -l total 0 -r--r--r-- 1 root root 4096 Aug 25 17:04 availability lrwxrwxrwx 1 root root 0 Aug 25 17:07 block -> ../../../../block/dasdb -rw-r--r-- 1 root root 4096 Aug 25 17:04 cmb_enable -r--r--r-- 1 root root 4096 Aug 25 17:04 cutype -rw-r--r-- 1 root root 4096 Aug 25 17:04 detach_state -r--r--r-- 1 root root 4096 Aug 25 17:04 devtype -r--r--r-- 1 root root 4096 Aug 25 17:04 discipline -rw-r--r-- 1 root root 0 Aug 25 17:04 online -rw-r--r-- 1 root root 4096 Aug 25 17:04 readonly -rw-r--r-- 1 root root 4096 Aug 25 17:04 use_diag
/dev/dasdb.
# chccwdev -e 4b2e
/root directory and format the device:
# cd # dasdfmt -b 4096 -d cdl -f /dev/dasdb -l LX4B2E -p -y cyl 97 of 3338 |#----------------------------------------------| 2%
fdasd to partition the device:
# fdasd -a /dev/dasdb auto-creating one partition for the whole disk... writing volume label... writing VTOC... checking ! wrote NATIVE! rereading partition table...
# mke2fs -j /dev/dasdb1
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
300960 inodes, 600816 blocks
30040 blocks (5.00%) reserved for the super user
First data block=0
19 block groups
32768 blocks per group, 32768 fragments per group
15840 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.# mount /dev/dasdb1 /opt # mount /dev/dasda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /dev/shm type tmpfs (rw) /dev/dasdb1 on /opt type ext3 (rw)
/etc/fstab so that the file system is mounted at IPL time:
# vi /etc/fstab # cat /etc/fstab LABEL=/ / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/dasdb1 /opt ext3 defaults 1 2
/etc/modprobe.conf Make sure to add the new device at the end of the list, otherwise it changes the device number : devnode mapping and file systems are not on the devices they used to be on.
# vi /etc/modprobe.conf # cat /etc/modprobe.conf alias eth0 qeth options dasd_mod dasd=201,4B2E
mkinitrd to pick up the changes to modprobe.conf so that the device can be online and mountable after the next IPL:
/tmp/initrd.AR1182/lib/dasd_mod.ko(elf64-s390).
# cd /boot # mv initrd-2.6.7-1.451.2.3.img initrd-2.6.7-1.451.2.3.img.old # mkinitrd -v initrd-2.6.7-1.451.2.3.img 2.6.7-1.451.2.3 Looking for deps of module ide-disk Looking for deps of module dasd_mod Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Using modules: ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.AR1182/bin/nash /sbin/insmod.static -> /tmp/initrd.AR1182/bin/insmod copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_mod.ko(elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_eckd_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_fba_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko(elf64-s390) to /tmp/initrd.AR1182/lib/jbd.ko(elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko(elf64-s390) to /tmp/initrd.AR1182/lib/ext3.ko(elf64-s390) Loading module dasd_mod with options dasd=201,4B2E Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3
zipl to save the changes to initrd for the next IPL:
# zipl -V Using config file '/etc/zipl.conf' Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: 0201 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 3308 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 595416 Building bootmap '/boot//bootmap' Building menu 'rh-automatic-menu' Adding #1: IPL section 'linux' (default) kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000 kernel parmline...: 'root=LABEL=/' at 0x1000 initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000 Preparing boot device: dasda (0201). Preparing boot menu Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: 'linux' Syncing disks... Done.
proc file system is no longer used to control or obtain status on network devices.
sys file system now provides facilities for controlling devices.
/sys/class/net/interface_name/device now provides status on active devices.
interface_name is a name such as eth0 or eth2 that is given to a network interface by the device driver when the device is configured.
/etc/chandev.conf no longer exists.
sys file system now contains the information that was placed in /etc/chandev.conf.
/etc/modules.conf no longer exists.
/etc/modprobe.conf.
qeth Device” describes in detail how to add a qeth device to an existing instance of Red Hat Enterprise Linux. Section 22.6.2, “Quick Reference for Adding Network Devices” is a quick reference for installing other IBM System z network interfaces.
qeth Deviceqeth device driver modules are loaded.
# lsmod | grep qeth qeth 135240 0 qdio 45360 2 qeth ipv6 303984 13 qeth ccwgroup 15104 1 qeth
lsmod command shows that the modules are not loaded, you must run the modprobe command to load them:
# modprobe qeth
qeth group device.
# echoread_device_bus_id,write_device_bus_id,data_device_bus_id> /sys/bus/ccwgroup/drivers/qeth/group
read_device_bus_id is 0.0.0600, write_device_bus_id is 0.0.0601, and data_device_bus_id is 0.0.0602. The device is a z/VM virtual NIC and the IP address to be assigned to this interface is 192.168.70.69.
# echo 0.0.0600,0.0.0601,0.0.0602 > /sys/bus/ccwgroup/drivers/qeth/group
qeth group device was created properly:
# ls /sys/bus/ccwgroup/drivers/qeth 0.0.0600 0.0.09a0 group notifier_register
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/portname no portname required
# echo portname > /sys/bus/ccwgroup/drivers/qeth/0.0.0600/portname# echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0600/online
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/online 1
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/if_name eth1
add_hhlen
broadcast_mode
buffer_count
canonical_macaddr
checksumming
detach_state
fake_broadcast
fake_ll
ipa_takeover
portno
priority_queueing
recover
route4
rxip
ungroup
vipa
/etc/sysconfig/network-scripts/.
device, where device is the value found in the if_name file in the qeth group device that was created earlier. In this example it is eth1.
# cd /etc/sysconfig/network-scripts # cp ifcfg-eth0 ifcfg-eth1
ifcfg-eth0 as a template.
/etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 BOOTPROTO=static HWADDR=00:06:29:FB:5F:F1 IPADDR=9.12.20.136 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.09a0,0.0.09a1,0.0.09a2 TYPE=Ethernet
ifcfg-eth1 file.
if_name file from your ccwgroup.
yes .
qeth device.
/etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.70.87 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet
qeth device requires an alias definition in /etc/modprobe.conf. Edit this file and add an alias for your interface.
/etc/modprobe.conf alias eth0 qeth alias eth1 qeth options dasd_mod dasd=0.0.0100,0.0.4b19
# ifup eth1
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:01
inet addr:192.168.70.87 Bcast:192.168.70.255 Mask:255.255.255.0
inet6 addr: fe80::ff:fe00:1/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:644 (644.0 b) TX bytes:264 (264.0 b)HWaddr field in the first line of the ifconfig command output. The value after that must be added to the ifcfg-eth1 file. Add a line like the following to that file:
HWADDR=02:00:00:00:00:01
ifcfg-eth1 looks similar to the following:
# IBM QETH DEVICE=eth1 HWADDR=02:00:00:00:00:01 BOOTPROTO=static IPADDR=192.168.70.69 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet
# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.70.0 * 255.255.255.0 U 0 0 0 eth1 9.12.20.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 default pdlrouter-if5.p 0.0.0.0 UG 0 0 0 eth0
ping command to ping the gateway:
# ping -c 1 192.168.70.8 PING 192.168.70.8 (192.168.70.8) 56(84) bytes of data. 64 bytes from 192.168.70.8: icmp_seq=0 ttl=63 time=8.07 ms
/etc/sysconfig/network accordingly.
n for OSA-Express Fast Ethernet and Gigabit Ethernet trn for Token Ring, where n is an integer that uniquely identifies the device. n is 0 for the first device of that type, 1 for the second, and so on.
# modprobe lcs
# echo read_device_bus_id,write_device_bus_id > /sys/bus/ccwgroup/drivers/lcs/group
# echo portno > /sys/bus/ccwgroup/drivers/lcs/device_bus_id/portno
# echo 1 > /sys/bus/ccwgroup/drivers/lcs/read_device_bus_id/online
/etc/modprobe.conf that is similar to one of the following:
ethnalias lcs trnalias lcs
/etc/sysconfig/network-scripts/ with a name like one of the following:
ifcfg-ethnifcfg-trn
/etc/sysconfig/network-scripts/ifcfg-eth0
# IBM LCS
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:06:29:FB:5F:F1
IPADDR=9.12.20.136
NETMASK=255.255.255.0
ONBOOT=yes
NETTYPE=lcs
SUBCHANNELS=0.0.09a0,0.0.09a1
PORTNAME=0
TYPE=EthernetDEVICE=ethnDEVICE=trn
ifup command:
# ifup ethn# ifup trn
n for HiperSocket devices
n for OSA-Express Fast Ethernet and Gigabit Ethernet
n for Token Ring
n is an integer that uniquely identifies the device. n is 0 for the first device of that type, 1 for the second, and so on.
# modprobe qeth
# echo read_device_bus_id,write_device_bus_id,data_device_bus_id > /sys/bus/ccwgroup/drivers/qeth/group
# echo 1 > /sys/bus/ccwgroup/drivers/qeth/read_device_bus_id/online
/etc/modprobe.conf that is like one of the following:
hsinalias qeth ethnalias qeth trnalias qeth
/etc/sysconfig/network-scripts/ with a name like one of the following:
ifcfg-hsinifcfg-ethnifcfg-trn
/etc/sysconfig/network-scripts/ifcfg-eth0
# IBM QETH
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:06:29:FB:5F:F1
IPADDR=9.12.20.136
NETMASK=255.255.255.0
ONBOOT=yes
NETTYPE=qeth
SUBCHANNELS=0.0.09a0,0.0.09a1,0.0.09a2
TYPE=EthernetDEVICE=hsinDEVICE=ethnDEVICE=trn
ifup command:
# ifup hsin# ifup ethn# ifup trn
/proc/ file system. To disable periodic timer interrupts, issue the following command:
echo 0 > /proc/sys/kernel/hz_timer
echo 1 > /proc/sys/kernel/hz_timer
/etc/sysctl.conf to disable periodic timer interrupts:
kernel.hz_timer = 0
Table of Contents
kmod- (notice the final -) and click .
$ rpm -qa | egrep ^kmod-Note the
- on the end of kmod. This will list all installed packages that begin with kmod-, which should include all driver updates that are currently installed on your system. Additional drivers provided by third-party update software are not listed in this output. Contact the third-party vendor for details.
kmod (short for kernel module) and have a form similar to this example:
kmod-ipw3945-1.2.04.17.el5.i686.rpm
xen in the package name:
kmod-ipw3945-xen-1.2.04.17.el5.i686.rpm
$ rpm --checksig -v filename.rpm
where filename.rpm is the driver update rpm package file name. This verifies the package against using the standard Red Hat GPG package signing key that is already installed on any Red Hat Enterprise Linux 5.8 system. If you need this key for verification purposes on another system, you can can obtain it from: https://www.redhat.com/security/team/key/
$ rpm -ivh kmod-ipw3945-1.2.04.17.el5.i686
.rpmsave extension (for example, sendmail.cf.rpmsave). The upgrade process also creates a log of its actions in /root/upgrade.log.
/etc/redhat-release file have been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5.8.
linux upgradeany
linux upgradeany command if your Red Hat Enterprise Linux installation was not given as an option to upgrade.
https://www.redhat.com/wapps/ugc/register.html
https://www.redhat.com/wapps/sso/lostPassword.html
rhn_register from the command line as the root user.
etc/sysconfig/rhn/systemid
| Partition Type | Value | Partition Type | Value |
|---|---|---|---|
| Empty | 00 | Novell Netware 386 | 65 |
| DOS 12-bit FAT | 01 | PIC/IX | 75 |
| XENIX root | 02 | Old MINIX | 80 |
| XENIX usr | 03 | Linux/MINUX | 81 |
| DOS 16-bit <=32M | 04 | Linux swap | 82 |
| Extended | 05 | Linux native | 83 |
| DOS 16-bit >=32 | 06 | Linux extended | 85 |
| OS/2 HPFS | 07 | Amoeba | 93 |
| AIX | 08 | Amoeba BBT | 94 |
| AIX bootable | 09 | BSD/386 | a5 |
| OS/2 Boot Manager | 0a | OpenBSD | a6 |
| Win95 FAT32 | 0b | NEXTSTEP | a7 |
| Win95 FAT32 (LBA) | 0c | BSDI fs | b7 |
| Win95 FAT16 (LBA) | 0e | BSDI swap | b8 |
| Win95 Extended (LBA) | 0f | Syrinx | c7 |
| Venix 80286 | 40 | CP/M | db |
| Novell | 51 | DOS access | e1 |
| PPC PReP Boot | 41 | DOS R/O | e3 |
| GNU HURD | 63 | DOS secondary | f2 |
| Novell Netware 286 | 64 | BBT | ff |
parted utility. This is a freely available program that can resize partitions.
parted, it is important that you be familiar with disk storage and that you perform a backup of your computer data. You should make two copies of all the important data on your computer. These copies should be to removable media (such as tape, CD-ROM, or diskettes), and you should make sure they are readable before proceeding.
parted, be aware that after parted runs you are left with two partitions: the one you resized, and the one parted created out of the newly freed space. If your goal is to use that space to install Red Hat Enterprise Linux, you should delete the newly created partition, either by using the partitioning utility under your current operating system or while setting up partitions during installation.
/dev/xxyN.
/dev//dev/.
xxhd (for IDE disks) or sd (for SCSI disks).
y/dev/hda (the first IDE hard disk) or /dev/sdb (the second SCSI disk).
N1 through 4. Logical partitions start at 5. So, for example, /dev/hda3 is the third primary or extended partition on the first IDE hard disk, and /dev/sdb6 is the second logical partition on the second SCSI hard disk.
/dev/hda5 is mounted on /usr/, that would mean that all files and directories under /usr/ physically reside on /dev/hda5. So the file /usr/share/doc/FAQ/txt/Linux-FAQ would be stored on /dev/hda5, while the file /etc/gdm/custom.conf would not.
/usr/ would be mount points for other partitions. For instance, a partition (say, /dev/hda7) could be mounted on /usr/local/, meaning that /usr/local/man/whatis would then reside on /dev/hda7 rather than /dev/hda5.
swap, /boot/ (or a /boot/efi/ partition for Itanium systems), a /var/ partition for Itanium systems, and / (root).
Table of Contents
/ partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the /boot/grub/grub.conf file.
rescue as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt:
linux rescueThe rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage. You can then make any changes required to your system. If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'. If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.
/mnt/sysimage/. If it fails to mount a partition, it notifies you. If you select , it attempts to mount your file system under the directory /mnt/sysimage/, but in read-only mode. If you select , your file system is not mounted. Choose if you think your file system is corrupted.
sh-3.00b#
chroot /mnt/sysimagerpm that require your root partition to be mounted as /. To exit the chroot environment, type exit to return to the prompt.
/foo
mount -t ext3 /dev/mapper/VolGroup00-LogVol02 /foo/foo/dev/mapper/VolGroup00-LogVol02ext2, replace ext3 with ext2.
fdisk -l
pvdisplay
vgdisplay
lvdisplayssh, scp, and ping if the network is started
dump and restore for users with tape drives
parted and fdisk for managing partitions
rpm for installing or upgrading software
joe for editing configuration files
emacs, pico, or vi, the joe editor is started.
linux rescue at the installation boot prompt to enter the rescue environment.
chroot /mnt/sysimage to mount the root partition.
/sbin/grub-install bootpart to reinstall the GRUB boot loader, where bootpart is the boot partition (typically, /dev/sda).
/boot/grub/grub.conf file, as additional entries may be needed for GRUB to control additional operating systems.
a to append the line.
single as a separate word (press the Spacebar and then type single). Press Enter to exit edit mode.
init files are not loaded. If init is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation.
single with the keyword emergency.
'rescue' (including the quotes), or to 'dd rescue' if you need to load the SCSI driver. On other systems, specify the rescue or dd rescue (without quotes) after the default kernel name at the YABOOT prompt.
exit 0. This causes a reboot from the C side. To reboot from the A or B side or from *NWSSTG, you should vary off the system instead of exiting the shell.
linux rescue askmethod command. This allows you to manually select NFS as the source of your rescue media instead of defaulting to the CD-ROM drive.
boot.img on your IFS (from step 1, above).
Table of Contents
/etc/crypttab/etc/fstab/etc/crypttab/etc/fstabdm-crypt module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the cryptsetup utility.
swap devices.
kickstart to set a separate passphrase for each new encrypted block device.
parted, pvcreate, lvcreate and mdadm.
/dev/sda3) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time.
dd if=/dev/urandom of=<device>
badblocks -c 10240 -s -w -t random -v <device>
cryptsetup luksFormat <device>
cryptsetup(8) man page.
cryptsetup isLuks <device> && echo Success
cryptsetup luksDump <device>
device-mapper.
/dev/sda3), is guaranteed to remain constant as long as the LUKS header remains intact. To find a LUKS device's UUID, run the following command:
cryptsetup luksUUID <device>
luks-<uuid>, where <uuid> is replaced with the device's LUKS UUID (eg: luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8). This naming convention might seem unwieldy but is it not necessary to type it often.
cryptsetup luksOpen <device> <name>
/dev/mapper/<name>, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device.
dmsetup info <name>
dmsetup(8) man page.
/dev/mapper/<name>) as any other block device. To create an ext2 filesystem on the mapped device, use the following command:
mke2fs /dev/mapper/<name>
/mnt/test, use the following command:
/mnt/test must exist before executing this command.
mount /dev/mapper/<name> /mnt/test
/etc/crypttab/etc/crypttab file. If the file doesn't exist, create it and change the owner and group to root (root:root) and change the mode to 0744. Add a line to the file with the following format:
<name> <device> none
cryptsetup luksUUID <device>. This ensures the correct device will be identified and used even if the device node (eg: /dev/sda5) changes.
/etc/crypttab file, read the crypttab(5) man page.
/etc/fstab/dev/mapper/<name> in the /etc/fstab file.
/etc/fstab by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: /dev/sda4) changes. LUKS device names in the form of /dev/mapper/luks-<luks_uuid> are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in /etc/fstab.
/etc/fstab file, read the fstab(5) man page.
$HOME/keyfile.
dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1 chmod 600 $HOME/keyfile
cryptsetup luksAddKey <device> ~/keyfile
cryptsetup luksAddKey <device>
cryptsetup luksRemoveKey <device>
# yum install vnc
vnc://SERVER:DISPLAY, where SERVER is the IP address or DNS host name of the VNC server you wish to connect to and DISPLAY is the VNC display number (usually 1), and click Connect.
vnc as a boot argument.
vnc command in the kickstart file used for installation.
Running anacondaVERSION, thePRODUCTsystem installer - please wait...
vncconnect boot parameter:
boot: linux vncconnect=HOST
vnc is passed as a boot parameter. To add the vnc parameter, you will need a console attached to the target system that allows you to interact with the boot process. Enter the following at the prompt:
boot: linux vnc
vnc command to the kickstart file. If the target system is using DHCP, add vncconnect=HOST to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Enter the following at the prompt:
boot: linux vncconnect=HOST
vnc command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file.
vncconnect method may work better for you. Rather than adding the vnc boot parameter to the kickstart file, add the vncconnect=HOST parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. See the next section for more details on using the vncconnect mode.
vnc boot parameter, you may also want to pass the vncpassword parameter in these scenarios. While the password is sent in plain text over the network, it does provide an extra step before a viewer can connect to a system. Once the viewer connects to the target system over VNC, no other connections are permitted. These limitations are usually sufficient for installation purposes.
vncpassword option. It should not be a password you use on any systems, especially a real root password.
vncconnect parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass vncconnect=HOST at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address).
/root/anaconda-ks.cfg. You should be able to edit it with any text editor or word processor that can save files as ASCII text.
%packages section — Refer to Section 31.5, “Package Selection” for details.
%pre and %post sections — These two sections can be in any order and are not required. Refer to Section 31.6, “Pre-installation Script” and Section 31.7, “Post-installation Script” for details.
upgrade keyword
autopart (optional) /) partition, a swap partition, and an appropriate boot partition for the architecture. One or more of the default partition sizes can be redefined with the part directive.
--encrypted — Should all devices with support be encrypted by default? This is equivalent to checking the Encrypt checkbox on the initial partitioning screen.
--passphrase= — Provide a default system-wide passphrase for all encrypted devices.
ignoredisk (optional) ignoredisk, attempting to deploy on a SAN-cluster the kickstart would fail, as the installer detects passive paths to the SAN that return no partition table. The --only-use option specifies that only the disks listed will be used during installion.
ignoredisk option is also useful if you have multiple paths to your disks.
ignoredisk --drives=drive1,drive2,...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. For example, to use disk sda during installation and ignore all other disks:
ignoredisk --only-use=sda
autostep (optional) --autoscreenshot — Take a screenshot at every step during installation and copy the images over to /root/anaconda-screenshots after installation is complete. This is most useful for documentation.
auth or authconfig (required) authconfig command, which can be run after the install. By default, passwords are normally encrypted and are not shadowed.
--enablemd5 — Use md5 encryption for user passwords.
--enablenis — Turns on NIS support. By default, --enablenis uses whatever domain it finds on the network. A domain should almost always be set by hand with the --nisdomain= option.
--nisdomain= — NIS domain name to use for NIS services.
--nisserver= — Server to use for NIS services (broadcasts by default).
--useshadow or --enableshadow — Use shadow passwords.
--enableldap — Turns on LDAP support in /etc/nsswitch.conf, allowing your system to retrieve information about users (UIDs, home directories, shells, etc.) from an LDAP directory. To use this option, you must install the nss_ldap package. You must also specify a server and a base DN (distinguished name) with --ldapserver= and --ldapbasedn=.
--enableldapauth — Use LDAP as an authentication method. This enables the pam_ldap module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the nss_ldap package installed. You must also specify a server and a base DN with --ldapserver= and --ldapbasedn=.
--ldapserver= — If you specified either --enableldap or --enableldapauth, use this option to specify the name of the LDAP server to use. This option is set in the /etc/ldap.conf file.
--ldapbasedn= — If you specified either --enableldap or --enableldapauth, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is set in the /etc/ldap.conf file.
--enableldaptls — Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.
--enablekrb5 — Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the /usr/sbin/useradd command. If you use this option, you must have the pam_krb5 package installed.
--krb5realm= — The Kerberos 5 realm to which your workstation belongs.
--krb5kdc= — The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, separate their names with commas (,).
--krb5adminserver= — The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.
--enablehesiod — Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in /usr/share/doc/glibc-2.x.x/README.hesiod, which is included in the glibc package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.
--hesiodlhs — The Hesiod LHS ("left-hand side") option, set in /etc/hesiod.conf. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.
--hesiodrhs — The Hesiod RHS ("right-hand side") option, set in /etc/hesiod.conf. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.
jim:*:501:501:Jungle Jim:/home/jim:/bin/bash). For groups, the situation is identical, except jim.group<LHS><RHS> would be used.
--enablesmbauth — Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LDAP, NIS, or Hesiod or by using the /usr/sbin/useradd command to make their accounts known to the workstation. To use this option, you must have the pam_smb package installed.
--smbservers= — The name of the server(s) to use for SMB authentication. To specify more than one server, separate the names with commas (,).
--smbworkgroup= — The name of the workgroup for the SMB servers.
--enablecache — Enables the nscd service. The nscd service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using NIS, LDAP, or hesiod.
--passalgo — Enables SHA256 or SHA512 hashing for passphrases. Use --passalgo=sha256 or --passalgo=sha512 and remove the --enablemd5 if present.
bootloader (required)--append= — Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:
bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"
--driveorder — Specify which drive is first in the BIOS boot order. For example:
bootloader --driveorder=sda,hda
--hvargs — If using GRUB, specifies Xen hypervisor arguments. To specify multiple parameters, separate them with spaces. For example:
bootloader --hvargs="dom0_mem=2G dom0_max_vcpus=4"
--location= — Specifies where the boot record is written. Valid values are the following: mbr (the default), partition (installs the boot loader on the first sector of the partition containing the kernel), or none (do not install the boot loader).
--password= — If using GRUB, sets the GRUB boot loader password to the one specified with this option. This should be used to restrict access to the GRUB shell, where arbitrary kernel options can be passed.
--md5pass= — If using GRUB, similar to --password= except the password should already be encrypted.
--upgrade — Upgrade the existing boot loader configuration, preserving the old entries. This option is only available for upgrades.
clearpart (optional) clearpart command is used, then the --onpart command cannot be used on a logical partition.
clearpart --initlabel --drives=names_of_DASDsclearpart --initlabel --drives=dasda,dasdb,dasdc
--all — Erases all partitions from the system.
--drives= — Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:
clearpart --drives=hda,hdb --all
--initlabel — Initializes the disk label to the default for your architecture (for example msdos for x86 and gpt for Itanium). It is useful so that the installation program does not ask if it should initialize the disk label if installing to a brand new hard drive.
--linux — Erases all Linux partitions.
--none (default) — Do not remove any partitions.
cmdline (optional) device (optional) device command, which tells the installation program to install extra modules, is in this format:
device<type><moduleName>--opts=<options>
<type> — Replace with either scsi or eth.
<moduleName> — Replace with the name of the kernel module which should be installed.
--opts= — Mount options to use for mounting the NFS export. Any options that can be specified in /etc/fstab for an NFS mount are allowed. The options are listed in the nfs(5) man page. Multiple options are separated with a comma.
driverdisk (optional) driverdisk command to tell the installation program where to look for the driver disk.
driverdisk<partition>[--type=<fstype>]
driverdisk --source=ftp://path/to/dd.img driverdisk --source=http://path/to/dd.img driverdisk --source=nfs:host:/path/to/img
<partition> — Partition containing the driver disk.
--type= — File system type (for example, vfat or ext2).
firewall (optional) firewall --enabled|--disabled [--trust=] <device> [--port=]--enabled or --enable — Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
--disabled or --disable — Do not configure any iptables rules.
--trust= — Listing a device here, such as eth0, allows all traffic coming from that device to go through the firewall. To list more than one device, use --trust eth0 --trust eth1. Do NOT use a comma-separated format such as --trust eth0, eth1.
<incoming> — Replace with one or more of the following to allow the specified services through the firewall.
--ssh
--telnet
--smtp
--http
--ftp
--port= — You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify imap:tcp. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify 1234:udp. To specify multiple ports, separate them by commas.
firstboot (optional) firstboot package must be installed. If not specified, this option is disabled by default.
--enable or --enabled — The Setup Agent is started the first time the system boots.
--disable or --disabled — The Setup Agent is not started the first time the system boots.
--reconfig — Enable the Setup Agent to start at boot time in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
halt (optional) halt option is roughly equivalent to the shutdown -h command.
poweroff, reboot, and shutdown kickstart options.
graphical (optional) install (optional) cdrom, harddrive, nfs, or url (for FTP or HTTP installations). The install command and the installation method command must be on separate lines.
cdrom — Install from the first CD-ROM drive on the system.
harddrive — Install from a Red Hat installation tree on a local drive, which must be either vfat or ext2.
--biospart=
--partition=
--dir=
variantharddrive --partition=hdb2 --dir=/tmp/install-tree
nfs — Install from the NFS server specified.
--server=
--dir=
variant--opts=
nfs --server=nfsserver.example.com --dir=/tmp/install-tree
url — Install from an installation tree on a remote server via FTP or HTTP.
url --url http://<server>/<dir>
url --url ftp://<username>:<password>@<server>/<dir>
interactive (optional) autostep command.
iscsi (optional)iscsi parameter, you must also assign a name to the iSCSI node, using the iscsiname parameter. The iscsiname parameter must appear before the iscsi parameter in the kickstart file.
iscsi parameter. Anaconda automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the kickstart file.
iscsi parameter, ensure that networking is activated at the beginning of the installation, and that the iscsi parameter appears in the kickstart file before you refer to iSCSI disks with parameters such as clearpart or ignoredisk.
--port= (mandatory) — the port number (typically, --port=3260)
--user= — the username required to authenticate with the target
--password= — the password that corresponds with the username specified for the target
--reverse-user= — the username required to authenticate with the initiator from a target that uses reverse CHAP authentication
--reverse-password= — the password that corresponds with the username specified for the initiator
iscsiname (optional) key (optional)--skip — Skip entering a key. Usually if the key command is not given, anaconda will pause at this step to prompt for a key. This option allows automated installation to continue if you do not have a key or do not want to provide one.
keyboard (required) be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2, ru_win, se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup, speakup-lt, sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua, uk, us, us-acentos
/usr/lib/python2.2/site-packages/rhpl/keyboard_models.py also contains this list and is part of the rhpl package.
lang (required)
lang en_US
/usr/share/system-config-language/locale-list provides a list of the valid language codes in the first column of each line and is part of the system-config-language package.
langsupport (deprecated)
%packages section of your kickstart file. For instance, adding support for French means you should add the following to %packages:
@french-support
logvol (optional)
logvol<mntpoint>--vgname=<name>--size=<size>--name=<name><options>
--noformat — Use an existing logical volume and do not format it.
--useexisting — Use an existing logical volume and reformat it.
--fstype= — Sets the file system type for the logical volume. Valid values are xfs, ext2, ext3, ext4, swap, vfat, and hfs.
--fsoptions= — Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.
--bytes-per-inode= — Specifies the size of inodes on the filesystem to be made on the logical volume. Not all filesystems support this option, so it is silently ignored for those cases.
--size= — The minimum size of the logical volume in megabytes. Specify an integer value here, and do not append the number with MB. If the logical volume is set to grow, the minimum size must be provided.
--grow= — Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting, while conforming to other limitations.
--maxsize= — The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here, and do not append the number with MB.
--recommended= — Determine the size of the logical volume automatically.
--percent= — Specify the size of the logical volume as a percentage of available space in the volume group.
part pv.01 --size 3000 volgroup myvg pv.01 logvol / --vgname=myvg --size=2000 --name=rootvol
logging (optional)
--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.
mediacheck (optional)
monitor (optional)
--hsync= — Specifies the horizontal sync frequency of the monitor.
--monitor= — Use specified monitor; monitor name should be from the list of monitors in /usr/share/hwdata/MonitorsDB from the hwdata package. The list of monitors can also be found on the X Configuration screen of the Kickstart Configurator. This is ignored if --hsync or --vsync is provided. If no monitor information is provided, the installation program tries to probe for it automatically.
--noprobe= — Do not try to probe the monitor.
--vsync= — Specifies the vertical sync frequency of the monitor.
mouse (deprecated)
multipath (optional)
multipath --name=mpathX--device=device_name--rule=policy
multipath --name=mpath0 --device=/dev/sdc --rule=failover
--name= — the name for the multipath device, in the format mpathX, where X is an integer.
--device= — the block device connected as a multipath device.
--rule= — a multipath policy: failover, multibus, group_by_serial, group_by_prio, or group_by_node_name. Refer to the multipath manpage for a description of these policies.
network (optional)
network option configures networking information for kickstart installations via a network as well as for the installed system.
--bootproto= — One of dhcp, bootp, or static.
dhcp. bootp and dhcp are treated the same.
network --bootproto=dhcp
network --bootproto=bootp
network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=10.0.2.1
network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
--device= — Used to select a specific Ethernet device for installation. Note that using --device= is not effective unless the kickstart file is a local file (such as ks=floppy), since the installation program configures the network to find the kickstart file. For example:
network --bootproto=dhcp --device=eth0
--ip= — IP address for the machine to be installed.
--gateway= — Default gateway as an IP address.
--nameserver= — Primary nameserver, as an IP address.
--nodns — Do not configure any DNS server.
--netmask= — Netmask for the installed system.
--hostname= — Hostname for the installed system.
--ethtool= — Specifies additional low-level settings for the network device which will be passed to the ethtool program. When autoneg is not specified, autoneg off is inserted automatically.
--essid= — The network ID for wireless networks.
--wepkey= — The encryption key for wireless networks.
--onboot= — Whether or not to enable the device at boot time.
--dhcpclass= — The DHCP class.
--mtu= — The MTU of the device.
--noipv4 — Disable IPv4 on this device.
--noipv6 — Disable IPv6 on this device.
part or partition (required for installs, ignored for upgrades) --noformat and --onpart are used.
part in action, refer to Section 31.4.1, “Advanced Partitioning Example”.
<mntpoint> — The <mntpoint> is where the partition is mounted and must be of one of the following forms:
/<path>
/, /usr, /home
swap
--recommended option:
swap --recommended
raid.<id>
raid).
pv.<id>
logvol).
<id>--size= — The minimum partition size in megabytes. Specify an integer value here such as 500. Do not append the number with MB.
--grow — Tells the partition to grow to fill available space (if any), or up to the maximum size setting.
--grow= without setting --maxsize= on a swap partition, Anaconda will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
--maxsize= — The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here, and do not append the number with MB.
--noformat — Tells the installation program not to format the partition, for use with the --onpart command.
--onpart= or --usepart= — Put the partition on the already existing device. For example:
partition /home --onpart=hda1
/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.
--fstype= — Sets the file system type for the partition. Valid values are xfs, ext2, ext3, ext4, swap, vfat, and hfs.
--start= — Specifies the starting cylinder for the partition. It requires that a drive be specified with --ondisk= or ondrive=. It also requires that the ending cylinder be specified with --end= or the partition size be specified with --size=.
--end= — Specifies the ending cylinder for the partition. It requires that the starting cylinder be specified with --start=.
--bytes-per-inode= — Specifies the size of inodes on the filesystem to be made on the partition. Not all filesystems support this option, so it is silently ignored for those cases.
--recommended — Determine the size of the partition automatically.
--onbiosdisk — Forces the partition to be created on a particular disk as discovered by the BIOS.
--encrypted — Specifies that this partition should be encrypted.
--passphrase= — Specifies the passphrase to use when encrypting this partition. Without the above --encrypted option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
--fsoptions= — Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.
--label= — assign a label to an individual partition.
poweroff (optional) halt option is used as default.
poweroff option is roughly equivalent to the shutdown -p command.
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.
halt, reboot, and shutdown kickstart options.
raid (optional) raid<mntpoint>--level=<level>--device=<mddevice><partitions*>
<mntpoint> — Location where the RAID file system is mounted. If it is /, the RAID level must be 1 unless a boot partition (/boot) is present. If a boot partition is present, the /boot partition must be level 1 and the root (/) partition can be any of the available types. The <partitions*> (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
--level= — RAID level to use (0, 1, 4, 5, 6, or 10).
--device= — Name of the RAID device to use (such as md0 or md1). RAID devices range from md0 to md15, and each may only be used once.
--bytes-per-inode= — Specifies the size of inodes on the filesystem to be made on the RAID device. Not all filesystems support this option, so it is silently ignored for those cases.
--spares= — Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.
--fstype= — Sets the file system type for the RAID array. Valid values are xfs, ext2, ext3, ext4, swap, vfat, and hfs.
--fsoptions= — Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.
--noformat — Use an existing RAID device and do not format the RAID array.
--useexisting — Use an existing RAID device and reformat it.
--encrypted — Specifies that this RAID device should be encrypted.
--passphrase= — Specifies the passphrase to use when encrypting this RAID device. Without the above --encrypted option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
/, and a RAID level 5 for /usr, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive.
part raid.01 --size=60 --ondisk=sda part raid.02 --size=60 --ondisk=sdb part raid.03 --size=60 --ondisk=sdc
part swap --size=128 --ondisk=sda part swap --size=128 --ondisk=sdb part swap --size=128 --ondisk=sdc
part raid.11 --size=1 --grow --ondisk=sda part raid.12 --size=1 --grow --ondisk=sdb part raid.13 --size=1 --grow --ondisk=sdc
raid / --level=1 --device=md0 raid.01 raid.02 raid.03 raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
raid in action, refer to Section 31.4.1, “Advanced Partitioning Example”.
reboot (optional) reboot option is roughly equivalent to the shutdown -r command.
reboot to automate installation fully when installing in cmdline mode on System z.
halt, poweroff, and shutdown kickstart options.
halt option is the default completion method if no other methods are explicitly specified in the kickstart file.
reboot option may result in an endless installation loop, depending on the installation media and method.
repo (optional)
repo --name=<repoid>[--baseurl=<url>| --mirrorlist=<url>]
--name= — The repo id. This option is required.
--baseurl= — The URL for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --mirrorlist, not both.
--mirrorlist= — The URL pointing at a list of mirrors for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --baseurl, not both.
rootpw (required) rootpw [--iscrypted] <password>--iscrypted — If this is present, the password argument is assumed to already be encrypted.
selinux (optional) selinux [--disabled|--enforcing|--permissive]
--enforcing — Enables SELinux with the default targeted policy being enforced.
selinux option is not present in the kickstart file, SELinux is enabled and set to --enforcing by default.
--permissive — Outputs warnings based on the SELinux policy, but does not actually enforce the policy.
--disabled — Disables SELinux completely on the system.
services (optional) --disabled — Disable the services given in the comma separated list.
--enabled — Enable the services given in the comma separated list.
services --disabled auditd, cups,smartd, nfslock
services --disabled auditd,cups,smartd,nfslock
shutdown (optional) halt option is used as default.
shutdown option is roughly equivalent to the shutdown command.
halt, poweroff, and reboot kickstart options.
skipx (optional) text (optional) timezone (required) timezone [--utc] <timezone>--utc — If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
upgrade (optional) user (optional) user --name=<username>[--groups=<list>] [--homedir=<homedir>] [--password=<password>] [--iscrypted] [--shell=<shell>] [--uid=<uid>]
--name= — Provides the name of the user. This option is required.
--groups= — In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created.
--homedir= — The home directory for the user. If not provided, this defaults to /home/<username>.
--password= — The new user's password. If not provided, the account will be locked by default.
--iscrypted= — Is the password provided by --password already encrypted or not?
--shell= — The user's login shell. If not provided, this defaults to the system default.
--uid= — The user's UID. If not provided, this defaults to the next available non-system UID.
vnc (optional) vnc [--host=<hostname>] [--port=<port>] [--password=<password>]
--host= — Instead of starting a VNC server on the install machine, connect to the VNC viewer process listening on the given hostname.
--port= — Provide a port that the remote VNC viewer process is listening on. If not provided, anaconda will use the VNC default.
--password= — Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
volgroup (optional) volgroup<name><partition><options>
pv.<id>. Any value can be assigned for <id> fields, as long as these values are consistent across volumes and volume groups. The default and lowest value is 01.
--noformat — Use an existing volume group and do not format it.
--useexisting — Use an existing volume group and reformat it.
--pesize= — Set the size of the physical extents.
part pv.01 --size 3000 volgroup myvg pv.01 logvol / --vgname=myvg --size=2000 --name=rootvol
volgroup in action, refer to Section 31.4.1, “Advanced Partitioning Example”.
xconfig (optional) --driver — Specify the X driver to use for the video hardware.
--videoram= — Specifies the amount of video RAM the video card has.
--defaultdesktop= — Specify either GNOME or KDE to set the default desktop (assumes that GNOME Desktop Environment and/or KDE Desktop Environment has been installed through %packages).
--startxonboot — Use a graphical login on the installed system.
--resolution= — Specify the default resolution for the X Window System on the installed system. Valid values are 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be sure to specify a resolution that is compatible with the video card and monitor.
--depth= — Specify the default color depth for the X Window System on the installed system. Valid values are 8, 16, 24, and 32. Be sure to specify a color depth that is compatible with the video card and monitor.
zerombr (optional) zerombr is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables.
zerombr yes. This form is now deprecated; you should now simply specify zerombr in your kickstart file instead.
zfcp (optional) zfcp [--devnum=<devnum>] [--fcplun=<fcplun>] [--scsiid=<scsiid>] [--scsilun=<scsilun>] [--wwpn=<wwpn>]
%include (optional)clearpart, raid, part, volgroup, and logvol kickstart options in action:
clearpart --drives=hda,hdc --initlabel # Raid 1 IDE config part raid.11 --size 1000 --asprimary --ondrive=hda part raid.12 --size 1000 --asprimary --ondrive=hda part raid.13 --size 2000 --asprimary --ondrive=hda part raid.14 --size 8000 --ondrive=hda part raid.15 --size 1 --grow --ondrive=hda part raid.21 --size 1000 --asprimary --ondrive=hdc part raid.22 --size 1000 --asprimary --ondrive=hdc part raid.23 --size 2000 --asprimary --ondrive=hdc part raid.24 --size 8000 --ondrive=hdc part raid.25 --size 1 --grow --ondrive=hdc # You can add --spares=x raid / --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21 raid /safe --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22 raid swap --fstype swap --device md2 --level=RAID1 raid.13 raid.23 raid /usr --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24 raid pv.01 --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25 # LVM configuration so that we can resize /var and /usr/local later volgroup sysvg pv.01 logvol /var --vgname=sysvg --size=8000 --name=var logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal
@Everything is not supported@Everything or simply * in the %packages section. Red Hat does not support this type of installation.
@Conflicts group. If you specify @Everything in a kickstart file, be sure to exclude @Conflicts or the installation will fail:
@Everything -@Conflicts
@Everything in a kickstart file, even if you exclude @Conflicts.
%packages command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
variant/repodata/comps-*.xmlCore and Base groups are always selected by default, so it is not necessary to specify them in the %packages section.
%packages selection:
%packages @ X Window System @ GNOME Desktop Environment @ Graphical Internet @ Sound and Video dhcp
@ symbol, a space, and then the full group name as given in the comps.xml file. Groups can also be specified using the id for the group, such as gnome-desktop. Specify individual packages with no additional characters (the dhcp line in the example above is an individual package).
-autofs
%packages option:
--nobase--resolvedeps--ignoredeps--ignoremissing%packages --ignoremissing
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.
--interpreter /usr/bin/python/usr/bin/python with the scripting language of your choice.
%pre section:
%pre #!/bin/sh hds="" mymedia="" for file in /proc/ide/h* do mymedia=`cat $file/media` if [ $mymedia == "disk" ] ; then hds="$hds `basename $file`" fi done set $hds numhd=`echo $#` drive1=`echo $hds | cut -d' ' -f1` drive2=`echo $hds | cut -d' ' -f2` #Write out partition scheme based on whether there are 1 or 2 hard drives if [ $numhd == "2" ] ; then #2 drives echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include echo "clearpart --all" >> /tmp/part-include echo "part /boot --fstype ext3 --size 75 --ondisk hda" >> /tmp/part-include echo "part / --fstype ext3 --size 1 --grow --ondisk hda" >> /tmp/part-include echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" >> /tmp/part-include else #1 drive echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include echo "clearpart --all" >> /tmp/part-include echo "part /boot --fstype ext3 --size 75" >> /tmp/part-include echo "part swap --recommended" >> /tmp/part-include echo "part / --fstype ext3 --size 2048" >> /tmp/part-include echo "part /home --fstype ext3 --size 2048 --grow" >> /tmp/part-include fi
%include /tmp/part-include
%post command. This section is useful for functions such as installing additional software and configuring an additional nameserver.
%post section. If you configured the network for DHCP, the /etc/resolv.conf file has not been completed when the installation executes the %post section. You can access the network, but you can not resolve IP addresses. Thus, if you are using DHCP, you must specify IP addresses in the %post section.
--nochroot/etc/resolv.conf to the file system that was just installed.
%post --nochroot cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
--interpreter /usr/bin/python/usr/bin/python with the scripting language of your choice.
--log /path/to/logfile--nochroot option. For example, without --nochroot:
%post --log=/root/ks-post.log
--nochroot:
%post --nochroot --log=/mnt/sysimage/root/ks-post.log
%post
( # Note that in this example we run the entire %post section as a subshell for logging.
wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash
/usr/sbin/rhnreg_ks --activationkey=<activationkey>
# End the subshell and capture any output to a post-install log file.
) 1>/root/post_install.log 2>&1
--log option to log the result in Red Hat Enterprise Linux 5.5 and later:
%post --log=/root/ks-post.log
wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash
/usr/sbin/rhnreg_ks --activationkey=<activationkey>runme from an NFS share:
mkdir /mnt/temp mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w -- /mnt/temp/runme umount /mnt/temp
-o nolock is required when mounting an NFS mount.
ks.cfg.
ks.cfg and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to Section 2.4.1, “Alternative Boot Methods” for instructions on creating boot media; however, before making the file.iso image file, copy the ks.cfg kickstart file to the isolinux/ directory.
ks.cfg and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the ks.cfg file.
dhcpd.conf file for the DHCP server:
filename"/usr/new-machine/kickstart/"; next-serverblarg.redhat.com;
filename with the name of the kickstart file (or the directory in which the kickstart file resides) and the value after next-server with the NFS server name.
<ip-addr>-kickstart<ip-addr>10.10.0.1-kickstart.
/kickstart from the BOOTP/DHCP server and tries to find the kickstart file using the same <ip-addr>-kickstartks command line argument is passed to the kernel.
linux ks=floppy command also works if the ks.cfg file is located on a vfat or ext2 file system on a diskette and you boot from the Red Hat Enterprise Linux CD-ROM #1.
boot: prompt:
linux ks=hd:fd0:/ks.cfg
dd option as well. For example, to boot off a boot diskette and use a driver disk, enter the following command at the boot: prompt:
linux ks=floppy dd
boot: prompt (where ks.cfg is the name of the kickstart file):
linux ks=cdrom:/ks.cfg
askmethodautostepdebugdddhcpclass=<class>dns=<dns>driverdiskexpertgateway=<gw>graphicalisaip=<ip>keymap=<keymap>ks=nfs:<server>:/<path><server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share /mydir/ks.cfg, the correct boot command would be ks=nfs:server.example.com:/mydir/ks.cfg.
ks=http://<server>/<path><server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory /mydir/ks.cfg, the correct boot command would be ks=http://server.example.com/mydir/ks.cfg.
ks=floppyks.cfg on a vfat or ext2 file system on the diskette in /dev/fd0.
ks=floppy:/<path>/dev/fd0, as file <path>.
ks=hd:<device>:/<file><device> (which must be vfat or ext2), and look for the kickstart configuration file as <file> in that file system (for example, ks=hd:sda3:/mydir/ks.cfg).
ks=file:/<file><file> from the file system; no mounts are done. This is normally used if the kickstart file is already on the initrd image.
ks=cdrom:/<path><path>.
ksks is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from the "bootServer" from the DHCP response as if it is an NFS server sharing the kickstart file. By default, the bootServer is the same as the DHCP server. The name of the kickstart file is one of the following:
/, the boot file provided by DHCP is looked for on the NFS server.
/, the boot file provided by DHCP is looked for in the /kickstart directory on the NFS server.
/kickstart/1.2.3.4-kickstart, where 1.2.3.4 is the numeric IP address of the machine being installed.
ksdevice=<device>ks=nfs:<server>:/<path> ksdevice=eth1 at the boot: prompt.
kssendmaclang=<lang>loglevel=<level>lowresmediacheckmethod=cdrommethod=ftp://<path>method=hd:<dev>:<path>method=http://<path>method=nfs:<path>netmask=<nm>nofallbacknofbnofirewirenoipv6nomountnonetnoparportnopassnopcmcianoprobenoshellnostoragenousbnousbstoragerescueresolution=<mode>serialskipddcsyslog=<host>[:<port>]<host>, and optionally, on port <port>. Requires the remote syslog process to accept connections (the -r option).
textupdatesupdates=ftp://<path>updates=http://<path>upgradeanyvncvncconnect=<host>[:<port>]<host>, and optionally use port <port>.
vncpassword=<password>/usr/sbin/system-config-kickstart.
variant/mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/ for the NFS directory.
variant/mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the FTP directory. If the FTP server requires a username and password, specify them as well.
variant/mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the HTTP directory.
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.
/boot partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
cdrecord by configuring hdd=ide-scsi as a kernel parameter (where hdd is the CD-ROM device).
msdos for x86 and gpt for Itanium), select Initialize the disk label if you are installing on a brand new hard drive.
anaconda and kickstart support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the Kickstart Configurator.
/dev/hda), specify hda as the drive. Do not include /dev in the drive name.
/dev/hda1), specify hda1 as the partition. Do not include /dev in the partition name.
system-config-network). Refer to the Red Hat Enterprise Linux Deployment Guide for details.
port:protocol. For example, to allow IMAP access through the firewall, specify imap:tcp. Numeric ports can also be specified explicitly; to allow UDP packets on port 1234 through the firewall, enter 1234:udp. To specify multiple ports, separate them with commas.
skipx option is written to the kickstart file.
/etc/inittab configuration file.
%packages section of the kickstart file after you save it. Refer to Section 31.5, “Package Selection” for details.
/usr/bin/python2.4 can be specified for a Python script. This option corresponds to using %pre --interpreter /usr/bin/python2.4 in your kickstart file.
addgroup, adduser, adjtimex, ar, arping, ash, awk, basename, bbconfig, bunzip2, busybox, bzcat, cal, cat, catv, chattr, chgrp, chmod, chown, chroot, chvt, cksum, clear, cmp, comm, cp, cpio, crond, crontab, cut, date, dc, dd, deallocvt, delgroup, deluser, devfsd, df, diff, dirname, dmesg, dnsd, dos2unix, dpkg, dpkg-deb, du, dumpkmap, dumpleases, e2fsck, e2label, echo, ed, egrep, eject, env, ether-wake, expr, fakeidentd, false, fbset, fdflush, fdformat, fdisk, fgrep, find, findfs, fold, free, freeramdisk, fsck, fsck.ext2, fsck.ext3, fsck.minix, ftpget, ftpput, fuser, getopt, getty, grep, gunzip, gzip, hdparm, head, hexdump, hostid, hostname, httpd, hush, hwclock, id, ifconfig, ifdown, ifup, inetd, insmod, install, ip, ipaddr, ipcalc, ipcrm, ipcs, iplink, iproute, iptunnel, kill, killall, lash, last, length, less, linux32, linux64, ln, load_policy, loadfont, loadkmap, login, logname, losetup, ls, lsattr, lsmod, lzmacat, makedevs, md5sum, mdev, mesg, mkdir, mke2fs, mkfifo, mkfs.ext2, mkfs.ext3, mkfs.minix, mknod, mkswap, mktemp, modprobe, more, mount, mountpoint, msh, mt, mv, nameif, nc, netstat, nice, nohup, nslookup, od, openvt, passwd, patch, pidof, ping, ping6, pipe_progress, pivot_root, printenv, printf, ps, pwd, rdate, readlink, readprofile, realpath, renice, reset, rm, rmdir, rmmod, route, rpm, rpm2cpio, run-parts, runlevel, rx, sed, seq, setarch, setconsole, setkeycodes, setlogcons, setsid, sh, sha1sum, sleep, sort, start-stop-daemon, stat, strings, stty, su, sulogin, sum, swapoff, swapon, switch_root, sync, sysctl, tail, tar, tee, telnet, telnetd, test, tftp, time, top, touch, tr, traceroute, true, tty, tune2fs, udhcpc, udhcpd, umount, uname, uncompress, uniq, unix2dos, unlzma, unzip, uptime, usleep, uudecode, uuencode, vconfig, vi, vlock, watch, watchdog, wc, wget, which, who, whoami, xargs, yes, zcat, zcip
busybox command --help
anaconda, bash, bzip2, jmacs, ftp, head, joe, kudzu-probe, list-harddrives, loadkeys, mtools, mbchk, mtools, mini-wm, mtools, jpico, pump, python, python2.4, raidstart, raidstop, rcp, rlogin, rsync, setxkbmap, sftp, shred, ssh, syslinux, syslogd, tac, termidx, vncconfig, vncpasswd, xkbcomp, Xorg, Xvnc, zcat
%pre command. It is added for you.
%post command. It is added for you.
%post section:
echo "Hackers will be punished" > /etc/motd--nochroot option in the %post section.
/mnt/sysimage/.
echo "Hackers will be punished" > /mnt/sysimage/etc/motd/usr/bin/python2.2 can be specified for a Python script. This option corresponds to using %post --interpreter /usr/bin/python2.2 in your kickstart file.
/var/log/boot.log. This functionality is not available in Red Hat Enterprise Linux 5.
/boot/ partition.
/sbin/init program.
/sbin/init program loads all services and user-space tools, and mounts all partitions listed in /etc/fstab.
/boot/grub/grub.conf — at boot time. Refer to Section 9.7, “GRUB Menu Configuration File” for information on how to edit this file.
/boot/ directory. The kernel binary is named using the following format — /boot/vmlinuz-<kernel-version> file (where <kernel-version>/sysroot/, a RAM-based virtual file system, via cpio. The initramfs is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 file system.
initramfs image(s) are loaded into memory, the boot loader hands control of the boot process to the kernel.
init command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel.
initramfs image(s) in a predetermined location in memory, decompresses it directly to /sysroot/, and loads all necessary drivers. Next, it initializes virtual devices related to the file system, such as LVM or software RAID, before completing the initramfs processes and freeing up all the memory the disk image once occupied.
/sbin/init program.
/sbin/init Program/sbin/init program (also called init) coordinates the rest of the boot process and configures the environment for the user.
init command starts, it becomes the parent or grandparent of all of the processes that start up automatically on the system. First, it runs the /etc/rc.d/rc.sysinit script, which sets the environment path, starts swap, checks the file systems, and executes all other steps required for system initialization. For example, most systems use a clock, so rc.sysinit reads the /etc/sysconfig/clock configuration file to initialize the hardware clock. Another example is if there are special serial port processes which must be initialized, rc.sysinit executes the /etc/rc.serial file.
init command then runs the /etc/inittab script, which describes how the system should be set up in each SysV init runlevel. Runlevels are a state, or mode, defined by the services listed in the SysV /etc/rc.d/rc<x>.d/ directory, where <x> is the number of the runlevel. For more information on SysV init runlevels, refer to Section 33.4, “SysV Init Runlevels”.
init command sets the source function library, /etc/rc.d/init.d/functions, for the system, which configures how to start, kill, and determine the PID of a program.
init program starts all of the background processes by looking in the appropriate rc directory for the runlevel specified as the default in /etc/inittab. The rc directories are numbered to correspond to the runlevel they represent. For instance, /etc/rc.d/rc5.d/ is the directory for runlevel 5.
init program looks in the /etc/rc.d/rc5.d/ directory to determine which processes to start and stop.
/etc/rc.d/rc5.d/ directory:
K05innd -> ../init.d/innd K05saslauthd -> ../init.d/saslauthd K10dc_server -> ../init.d/dc_server K10psacct -> ../init.d/psacct K10radiusd -> ../init.d/radiusd K12dc_client -> ../init.d/dc_client K12FreeWnn -> ../init.d/FreeWnn K12mailman -> ../init.d/mailman K12mysqld -> ../init.d/mysqld K15httpd -> ../init.d/httpd K20netdump-server -> ../init.d/netdump-server K20rstatd -> ../init.d/rstatd K20rusersd -> ../init.d/rusersd K20rwhod -> ../init.d/rwhod K24irda -> ../init.d/irda K25squid -> ../init.d/squid K28amd -> ../init.d/amd K30spamassassin -> ../init.d/spamassassin K34dhcrelay -> ../init.d/dhcrelay K34yppasswdd -> ../init.d/yppasswdd K35dhcpd -> ../init.d/dhcpd K35smb -> ../init.d/smb K35vncserver -> ../init.d/vncserver K36lisa -> ../init.d/lisa K45arpwatch -> ../init.d/arpwatch K45named -> ../init.d/named K46radvd -> ../init.d/radvd K50netdump -> ../init.d/netdump K50snmpd -> ../init.d/snmpd K50snmptrapd -> ../init.d/snmptrapd K50tux -> ../init.d/tux K50vsftpd -> ../init.d/vsftpd K54dovecot -> ../init.d/dovecot K61ldap -> ../init.d/ldap K65kadmin -> ../init.d/kadmin K65kprop -> ../init.d/kprop K65krb524 -> ../init.d/krb524 K65krb5kdc -> ../init.d/krb5kdc K70aep1000 -> ../init.d/aep1000 K70bcm5820 -> ../init.d/bcm5820 K74ypserv -> ../init.d/ypserv K74ypxfrd -> ../init.d/ypxfrd K85mdmpd -> ../init.d/mdmpd K89netplugd -> ../init.d/netplugd K99microcode_ctl -> ../init.d/microcode_ctl S04readahead_early -> ../init.d/readahead_early S05kudzu -> ../init.d/kudzu S06cpuspeed -> ../init.d/cpuspeed S08ip6tables -> ../init.d/ip6tables S08iptables -> ../init.d/iptables S09isdn -> ../init.d/isdn S10network -> ../init.d/network S12syslog -> ../init.d/syslog S13irqbalance -> ../init.d/irqbalance S13portmap -> ../init.d/portmap S15mdmonitor -> ../init.d/mdmonitor S15zebra -> ../init.d/zebra S16bgpd -> ../init.d/bgpd S16ospf6d -> ../init.d/ospf6d S16ospfd -> ../init.d/ospfd S16ripd -> ../init.d/ripd S16ripngd -> ../init.d/ripngd S20random -> ../init.d/random S24pcmcia -> ../init.d/pcmcia S25netfs -> ../init.d/netfs S26apmd -> ../init.d/apmd S27ypbind -> ../init.d/ypbind S28autofs -> ../init.d/autofs S40smartd -> ../init.d/smartd S44acpid -> ../init.d/acpid S54hpoj -> ../init.d/hpoj S55cups -> ../init.d/cups S55sshd -> ../init.d/sshd S56rawdevices -> ../init.d/rawdevices S56xinetd -> ../init.d/xinetd S58ntpd -> ../init.d/ntpd S75postgresql -> ../init.d/postgresql S80sendmail -> ../init.d/sendmail S85gpm -> ../init.d/gpm S87iiim -> ../init.d/iiim S90canna -> ../init.d/canna S90crond -> ../init.d/crond S90xfs -> ../init.d/xfs S95atd -> ../init.d/atd S96readahead -> ../init.d/readahead S97messagebus -> ../init.d/messagebus S97rhnsd -> ../init.d/rhnsd S99local -> ../rc.local
/etc/rc.d/rc5.d/ directory. Rather, all of the files in /etc/rc.d/rc5.d/ are symbolic links pointing to scripts located in the /etc/rc.d/init.d/ directory. Symbolic links are used in each of the rc directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
K or an S. The K links are processes that are killed on that runlevel, while those beginning with an S are started.
init command first stops all of the K symbolic links in the directory by issuing the /etc/rc.d/init.d/<command> stop command, where <command> is the process to be killed. It then starts all of the S symbolic links by issuing /etc/rc.d/init.d/<command> start.
/etc/rc.d/init.d/httpd stop stops the Apache HTTP Server.
init program executes is the /etc/rc.d/rc.local file. This file is useful for system customization. Refer to Section 33.3, “Running Additional Programs at Boot Time” for more information about using the rc.local file.
init command has progressed through the appropriate rc directory for the runlevel, the /etc/inittab script forks an /sbin/mingetty process for each virtual console (login prompt) allocated to the runlevel. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The /sbin/mingetty process opens communication pathways to tty devices[14], sets their modes, prints the login prompt, accepts the user's username and password, and initiates the login process.
/etc/inittab runs a script called /etc/X11/prefdm. The prefdm script executes the preferred X display manager[15] — gdm, kdm, or xdm, depending on the contents of the /etc/sysconfig/desktop file.
/etc/rc.d/rc.local script is executed by the init command at boot time or when changing runlevels. Adding commands to the bottom of this script is an easy way to perform necessary tasks like starting special services or initialize devices without writing complex initialization scripts in the /etc/rc.d/init.d/ directory and creating symbolic links.
/etc/rc.serial script is used if serial ports must be setup at boot time. This script runs setserial commands to configure the system's serial ports. Refer to the setserial man page for more information.
init launches or halts when initializing a runlevel. SysV init was chosen because it is easier to use and more flexible than the traditional BSD-style init process.
/etc/rc.d/ directory. Within this directory, are the rc, rc.local, rc.sysinit, and, optionally, the rc.serial scripts as well as the following directories:
init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/init.d/ directory contains the scripts used by the /sbin/init command when controlling services. Each of the numbered directories represent the six runlevels configured by default under Red Hat Enterprise Linux.
init. For instance, runlevel 1 (single user mode) halts any network services, while runlevel 3 starts these services. By assigning specific services to be halted or started on a given runlevel, init can quickly change the mode of the machine without the user manually stopping and starting services.
0— Halt1— Single-user text mode2— Not used (user-definable)3— Full multi-user text mode4— Not used (user-definable)5— Full multi-user graphical mode (with an X-based login screen)6— Reboot
/etc/inittab. To find out the default runlevel for a system, look for the line similar to the following near the top of /etc/inittab:
id:5:initdefault:/etc/inittab as root.
/etc/inittab. Simple typos can cause the system to become unbootable. If this happens, either use a boot diskette, enter single-user mode, or enter rescue mode to boot the computer and repair the file.
/etc/rc.d/.
/sbin/chkconfig — The /sbin/chkconfig utility is a simple command line tool for maintaining the /etc/rc.d/init.d/ directory hierarchy.
chkconfig.
system-config-services) program is a flexible utility for configuring runlevels.
/sbin/shutdown command. The shutdown man page has a complete list of options, but the two most common uses are:
/sbin/shutdown -h now
/sbin/shutdown -r now-h option halts the machine, and the -r option reboots.
reboot and halt commands to shut down the system while in runlevels 1 through 5. For more information about PAM console users, refer to the Red Hat Enterprise Linux Deployment Guide.
tty devices.
askmethod boot option with the Red Hat Enterprise Linux CD #1. Alternatively, if the system to be installed contains a network interface card (NIC) with Pre-Execution Environment (PXE) support, it can be configured to boot from files on another networked system rather than local media such as a CD-ROM.
tftp server (which provides the files necessary to start the installation program), and the location of the files on the tftp server. This is possible because of PXELINUX, which is part of the syslinux package.
tftp server necessary for PXE booting.
tftp service.
tftp server so they can be found when the client requests them. The tftp server is usually the same server as the network server exporting the installation tree.
pxeos command line utility, which is part of the system-config-netboot-cmd package, can be used to configure the tftp server files as described in Section 34.4, “TFTPD”:
pxeos -a -i "<description>" -p <NFS|HTTP|FTP> -D 0 -sinstaller.example.com\ -L<location>-k<kernel>-K<kickstart><os-identifer>
-a — Specifies that an OS instance is being added to the PXE configuration.
-i "<description>" — Replace "<description>" with a description of the OS instance.
-p <NFS|HTTP|FTP> — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified.
-D <0|1> — Specify "0" which indicates that it is not a diskless configuration since pxeos can be used to configure a diskless environment as well.
-s installer.example.com — Provide the name of the NFS, FTP, or HTTP server after the -s option.
-L <location> — Provide the location of the installation tree on that server after the -L option.
/install/rhel5 on an NFS share, specify -L /install/rhel5.
-k <kernel> — Provide the specific kernel for booting. Installation trees can contain multiple kernels.
vmlinuz-du alongside the standard kernel named vmlinuz, use -k vmlinuz-du to specify the patched kernel.
-K <kickstart> — Provide the location of the kickstart file, if available. Specify this location as a full path, including the protocol; for example: -K nfs:192.168.0.1:/install/rhel5/ks.cfg
<os-identifer> — Specify the OS identifier, which is used as the directory name in the /tftpboot/linux-install/ directory.
<os-identifer> in the previous command:
-A 0 -u<username>-p<password>
/tftpboot/linux-install/pxelinux.cfg/pxeos.xml file.
pxeos command, refer to the pxeos man page.
/tftpboot/linux-install/pxelinux.cfg/pxeos.xml file and uses similar options to pxeos. Refer to the pxeboot man page for more detail.
http://server.example.com/kickstart/ks.cfg. This file can be created with the Kickstart Configurator. Refer to Chapter 32, Kickstart Configurator for details.
pxeboot utility, a part of the system-config-netboot package, can be used to add hosts which are allowed to connect to the PXE server:
pxeboot -a -K<kickstart>-O<os-identifier>-r<value><host>
-a — Specifies that a host is to be added.
-K <kickstart> — The location of the kickstart file, if available.
-O <os-identifier> — Specifies the operating system identifier as defined in Section 34.2, “PXE Boot Configuration”.
-r <value> — Specifies the ram disk size.
<host> — Specifies the IP address or hostname of the host to add.
pxeboot command, refer to the pxeboot man page.
tftp Servertftp-server package is installed with the command rpm -q tftp-server. If it is not installed, install it via Red Hat Network or the Red Hat Enterprise Linux CD-ROMs. tftp is an xinetd-based service; start it with the following commands:
/sbin/chkconfig --level 345 xinetd on/sbin/chkconfig --level 345 tftp on
tftp and xinetd services to immediately turn on and also configure them to start at boot time in runlevels 3, 4, and 5.
allow booting;
allow bootp;
class "pxeclients" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
next-server <server-ip>;
filename "linux-install/pxelinux.0"; }
<server-ip> should be replaced with the IP address of the tftp server.
/tftpboot/linux-install/msgs/boot.msg to use a custom boot message.
Table of Contents
| Revision History | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Revision 3.1-26 | Fri Feb 02 2012 | ||||||||||||
| |||||||||||||
| Revision 3.1-24 | Fri Nov 18 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-22 | Wed Nov 9 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-21 | Fri Nov 4 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-20 | Thu Oct 13 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-19 | Thu Sep 29 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-18 | Fri Sep 23 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-17 | Mon Sep 19 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-16 | Thu Jul 21 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-15 | Fri Jun 10 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-14 | Mon Apr 11 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-13 | Thu Jan 6 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-12 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-11 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-10 | Wed Jan 5 2011 | ||||||||||||
| |||||||||||||
| Revision 3.1-9 | Tue Dec 21 2010 | ||||||||||||
| |||||||||||||
| Revision 3.1-5 | Thu Oct 7 2010 | ||||||||||||
| |||||||||||||
| Revision 3.1-2 | Mon Apr 19 2010 | ||||||||||||
| |||||||||||||
| Revision 3.1-1 | Mon Apr 19 2010 | ||||||||||||
| |||||||||||||
| Revision 3.1-0 | Tue Apr 6 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-23 | Tue Apr 6 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-22 | Wed Mar 31 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-21 | Tue Jan 12 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-20 | Tue Jan 12 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-19 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-18 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-17 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-16 | Mon Jan 11 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-15 | Fri Jan 8 2010 | ||||||||||||
| |||||||||||||
| Revision 3.0-14 | Tue Dec 22 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-13 | Mon Dec 21 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-12 | Thu Dec 17 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-11 | Wed Dec 16 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-10 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-9 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-8 | Fri Dec 11 2009 | ||||||||||||
| |||||||||||||
| Revision 3.0-1 | Tue Aug 04 2009 | , | |||||||||||
| |||||||||||||
| Revision 2.0-1 | Mon Jan 05 2009 | ||||||||||||
| |||||||||||||
| Revision 1.0-1 | Fri Oct 03 2008 | ||||||||||||
| |||||||||||||