Cari di RHE Linux 
    Red Hat Enterprise Linux Manual
Daftar Isi
(Sebelumnya) 1 : 32.5. Package Selection - ...1 : Part V. After installation ... (Berikutnya)

Installation Guide

Chapter 33. Kickstart Configurator

Kickstart Configurator allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file.
Kickstart Configurator is not installed by default on Red Hat Enterprise Linux 6. Run su - yum install system-config-kickstart or use your graphical package manager to install the software.
To launch Kickstart Configurator, boot your system into a graphical environment, then run system-config-kickstart, or click ApplicationsSystem ToolsKickstart on the GNOME desktop or Kickoff Application Launcher+ApplicationsSystemKickstart on the KDE desktop.
As you are creating a kickstart file, you can click FilePreview at any time to review your current selections.
To start with an existing kickstart file, select FileOpen and select the existing file.

33.1. Basic Configuration

Basic Configuration
Basic Configuration

Figure 33.1. Basic Configuration


Choose the language to use during the installation and as the default language to be used after installation from the Default Language menu.
Select the system keyboard type from the Keyboard menu.
From the Time Zone menu, choose the time zone to use for the system. To configure the system to use UTC, select Use UTC clock.
Enter the desired root password for the system in the Root Password text entry box. Type the same password in the Confirm Password text box. The second field is to make sure you do not mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select Encrypt root password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it. Because a kickstart file is a plain text file that can be easily read, it is recommended that an encrypted password be used.
Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation.
Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation.
Choosing Reboot system after installation reboots your system automatically after the installation is finished.
Kickstart installations are performed in graphical mode by default. To override this default and use text mode instead, select the Perform installation in text mode option.
You can perform a kickstart installation in interactive mode. This means that the installation program uses all the options pre-configured in the kickstart file, but it allows you to preview the options in each screen before continuing to the next screen. To continue to the next screen, click the Next button after you have approved the settings or change them before continuing the installation. To select this type of installation, select the Perform installation in interactive mode option.

33.2. Installation Method

Installation Method
Kickstart Installation Method

Figure 33.2. Installation Method


The Installation Method screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the Partition Information and Package Selection options are disabled. They are not supported for kickstart upgrades.
Choose the type of kickstart installation or upgrade from the following options:
  • DVD - Choose this option to install or upgrade from the Red Hat Enterprise Linux DVD.
  • NFS - Choose this option to install or upgrade from an NFS shared directory. In the text field for the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the variant directory of the installation tree. For example, if the NFS server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/ for the NFS directory.
  • FTP - Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the variant directory. For example, if the FTP server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the FTP directory. If the FTP server requires a username and password, specify them as well.
  • HTTP - Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the variant directory. For example, if the HTTP server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the HTTP directory.
  • Hard Drive - Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an md5sum program as well as the linux mediacheck boot option as discussed in Section 28.6.1, "Verifying boot media". 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.

33.3. Boot Loader Options

Boot Loader Options
Boot Loader Options

Figure 33.3. Boot Loader Options


Please note that this screen will be disabled if you have specified a target architecture other than x86 / x86_64.
GRUB is the default boot loader for Red Hat Enterprise Linux on x86 / x86_64 architectures. If you do not want to install a boot loader, select Do not install a boot loader. If you choose not to install a boot loader, make sure you create a boot diskette or have another way to boot your system, such as a third-party boot loader.
You must choose where to install the boot loader (the Master Boot Record or the first sector of the /boot partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
To pass any special parameters to the kernel to be used when the system boots, enter them in the Kernel parameters text field. For example, if you have an IDE CD-ROM Writer, you can tell the kernel to use the SCSI emulation driver that must be loaded before using cdrecord by configuring hdd=ide-scsi as a kernel parameter (where hdd is the CD-ROM device).
You can password protect the GRUB boot loader by configuring a GRUB password. Select Use GRUB password, and enter a password in the Password field. Type the same password in the Confirm Password text field. To save the password as an encrypted password in the file, select Encrypt GRUB password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. If the password you typed was already encrypted, uncheck the encryption option.
If Upgrade an existing installation is selected on the Installation Method page, select Upgrade existing boot loader to upgrade the existing boot loader configuration, while preserving the old entries.

33.4. Partition Information

Partition Information
Kickstart Partition Information

Figure 33.4. Partition Information


Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions.
To initialize the disk label to the default for the architecture of the system (for example, msdos for x86), select Initialize the disk label if you are installing on a brand new hard drive.

Note

Although anaconda and kickstart support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the Kickstart Configurator.

33.4.1. Creating Partitions

To create a partition, click the Add button. The Partition Options window shown in Figure 33.5, "Creating Partitions" appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following:
  • In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
  • Force the partition to be created as a primary partition.
  • Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk (/dev/hda), specify hda as the drive. Do not include /dev in the drive name.
  • Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk (/dev/hda1), specify hda1 as the partition. Do not include /dev in the partition name.
  • Format the partition as the chosen file system type.
Creating Partitions
Creating Partitions for Kickstart

Figure 33.5. Creating Partitions


To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Figure 33.5, "Creating Partitions", except it reflects the values for the selected partition. Modify the partition options and click OK.
To delete an existing partition, select the partition from the list and click the Delete button.

33.4.1.1. Creating Software RAID Partitions

To create a software RAID partition, use the following steps:
  1. Click the RAID button.
  2. Select Create a software RAID partition.
  3. Configure the partitions as previously described, except select Software RAID as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use.
Creating a Software RAID Partition
Software RAID Partition

Figure 33.6. Creating a Software RAID Partition


Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions.
After creating all the partitions needed to form a RAID device, follow these steps:
  1. Click the RAID button.
  2. Select Create a RAID device.
  3. Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device.
    Creating a Software RAID Device
    Software RAID Device

    Figure 33.7. Creating a Software RAID Device


  4. Click OK to add the device to the list.

33.5. Network Configuration

Network Configuration
Network Configuration for Kickstart

Figure 33.8. Network Configuration


If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the Network Configuration page.
Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the Network Administration Tool (system-config-network). Refer to the Red Hat Enterprise Linux Deployment Guide for details.
For each Ethernet card on the system, click Add Network Device and select the network device and network type for the device. Select eth0 to configure the first Ethernet card, eth1 for the second Ethernet card, and so on.

33.6. Authentication

Authentication
Authentication for Kickstart

Figure 33.9. Authentication


In the Authentication section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default.
The Authentication Configuration options allow you to configure the following methods of authentication:
  • NIS
  • LDAP
  • Kerberos 5
  • Hesiod
  • SMB
  • Name Switch Cache
These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to Enable, and enter the appropriate information for the authentication method. Refer to the Red Hat Enterprise Linux Deployment Guide for more information about the options.

33.7. Firewall Configuration

The Firewall Configuration window is similar to the screen in the installation program and the Security Level Configuration Tool.
Firewall Configuration
Firewall Configuration for Kickstart

Figure 33.10. Firewall Configuration


If Disable firewall is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied.
Selecting Enable firewall configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is required, you can choose to allow specific services through the firewall.
Only devices configured in the Network Configuration section are listed as available Trusted devices. Connections from any devices selected in the list are accepted by the system. For example, if eth1 only receives connections from internal system, you might want to allow connections from it.
If a service is selected in the Trusted services list, connections for the service are accepted and processed by the system.
In the Other ports text field, list any additional ports that should be opened for remote access. Use the following format: 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.

33.7.1. SELinux Configuration

Kickstart can set SELinux to enforcing, permissive or disabled mode. Finer grained configuration is not possible at this time.

33.8. Display Configuration

If you are installing the X Window System, you can configure it during the kickstart installation by checking the Configure the X Window System option on the Display Configuration window as shown in Figure 33.11, "X Configuration". If this option is not chosen, the X configuration options are disabled and the skipx option is written to the kickstart file.
X Configuration
X Configuration for Kickstart

Figure 33.11. X Configuration


Select whether to start the Setup Agent the first time the installed system boots. The Setup Agent is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.

33.9. Package Selection

Package Selection
Package Selection for Kickstart

Figure 33.12. Package Selection


The Package Selection window allows you to choose which package groups to install.
Package resolution is carried out automatically.
Currently, Kickstart Configurator does not allow you to select individual packages. To install individual packages, modify the %packages section of the kickstart file after you save it. Refer to Section 32.5, "Package Selection" for details.

33.10. Pre-Installation Script

Pre-Installation Script
Pre-Installation Script for Kickstart

Figure 33.13. Pre-Installation Script


You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area.

Important - anaconda no longer uses busybox

The version of anaconda in previous releases of Red Hat Enterprise Linux included a version of busybox that provided shell commands in the pre-installation and post-installation environments. The version of anaconda in Red Hat Enterprise Linux 6 no longer includes busybox, and uses GNU bash commands instead.
Refer to Appendix G, Alternatives to busybox commands for more information.
To specify a scripting language to use to execute the script, select the Use an interpreter option and enter the interpreter in the text box beside it. For example, /usr/bin/python2.6 can be specified for a Python script. This option corresponds to using %pre --interpreter /usr/bin/python2.6 in your kickstart file.
Only the most commonly used commands are available in the pre-installation environment:
arping, awk, basename, bash, bunzip2, bzcat, cat, chattr, chgrp, chmod, chown, chroot, chvt, clear, cp, cpio, cut, date, dd, df, dirname, dmesg, du, e2fsck, e2label, echo, egrep, eject, env, expr, false, fdisk, fgrep, find, fsck, fsck.ext2, fsck.ext3, ftp, grep, gunzip, gzip, hdparm, head, hostname, hwclock, ifconfig, insmod, ip, ipcalc, kill, killall, less, ln, load_policy, login, losetup, ls, lsattr, lsmod, lvm, md5sum, mkdir, mke2fs, mkfs.ext2, mkfs.ext3, mknod, mkswap, mktemp, modprobe, more, mount, mt, mv, nslookup, openvt, pidof, ping, ps, pwd, readlink, rm, rmdir, rmmod, route, rpm, sed, sh, sha1sum, sleep, sort, swapoff, swapon, sync, tail, tar, tee, telnet, top, touch, true, tune2fs, umount, uniq, vconfig, vi, wc, wget, xargs, zcat.

Important

Do not include the %pre command. It is added for you.

Note

The pre-installation script is run after the source media is mounted and stage 2 of the bootloader has been loaded. For this reason it is not possible to change the source media in the pre-installation script.

33.11. Post-Installation Script

Post-Installation Script
Post-Installation Script for Kickstart

Figure 33.14. Post-Installation Script


You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area.

Important - anaconda no longer uses busybox

The version of anaconda in previous releases of Red Hat Enterprise Linux included a version of busybox that provided shell commands in the pre-installation and post-installation environments. The version of anaconda in Red Hat Enterprise Linux 6 no longer includes busybox, and uses GNU bash commands instead.
Refer to Appendix G, Alternatives to busybox commands for more information.

Important

Do not include the %post command. It is added for you.
For example, to change the message of the day for the newly installed system, add the following command to the %post section:
echo "Hackers will be punished" > /etc/motd

Note

More examples can be found in Section 32.7.1, "Examples".

33.11.1. Chroot Environment

To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the Post-Installation window. This is equivalent to using the --nochroot option in the %post section.
To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/.
For example, if you select Run outside of the chroot environment, the previous example must be changed to the following:
echo "Hackers will be punished" > /mnt/sysimage/etc/motd

33.11.2. Use an Interpreter

To specify a scripting language to use to execute the script, select the Use an interpreter option and enter the interpreter in the text box beside it. For example, /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.

33.12. Saving the File

To review the contents of the kickstart file after you have finished choosing your kickstart options, select File => Preview from the pull-down menu.
Preview
Preview

Figure 33.15. Preview


To save the kickstart file, click the Save to File button in the preview window. To save the file without previewing it, select File => Save File or press Ctrl+S . A dialog box appears. Select where to save the file.
After saving the file, refer to Section 32.10, "Starting a Kickstart Installation" for information on how to start the kickstart installation.
(Sebelumnya) 1 : 32.5. Package Selection - ...1 : Part V. After installation ... (Berikutnya)