| Installation GuidePart IV. Advanced installation optionsThis part of the Red Hat Enterprise Linux Installation Guide covers more advanced or uncommon methods of installing Red Hat Enterprise Linux, including: The Red Hat Enterprise Linux installation system includes a range of functions and options for administrators. To use boot options, enter linux option at the boot: prompt. To access the boot: prompt on a system that displays a graphical boot screen, press the Esc key while the graphical boot screen is displayed. If you specify more than one option, separate each of the options by a single space. For example: linux option1 option2 option3
28.1. Configuring the Installation System at the Boot MenuYou can use the boot menu to specify a number of settings for the installation system, including: language display resolution interface type Installation method network settings
28.1.1. Specifying the LanguageTo set the language for both the installation process and the final system, specify the ISO code for that language with the lang option. Use the keymap option to configure the correct keyboard layout. For example, the ISO codes el_GR and gr identify the Greek language and the Greek keyboard layout: linux lang=el_GR keymap=gr
28.1.2. Configuring the InterfaceTo use a specific display resolution, enter resolution=setting as a boot option. For example, to set the display resolution to 1024�768, enter: linux resolution=1024x768
To run the installation process in text mode, enter: linux text
To enable support for a serial console, enter serial as an additional option. Use display=ip:0 to allow remote display forwarding. In this command, ip should be replaced with the IP address of the system on which you want the display to appear. On the system you want the display to appear on, you must execute the command xhost +remotehostname, where remotehostname is the name of the host from which you are running the original display. Using the 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. 28.1.3. Updating anacondaYou can install Red Hat Enterprise Linux with a newer version of the anaconda installation program than the one supplied on your installation media. The boot option linux updates presents you with a prompt that asks you for a disk image containing anaconda updates. You do not need to specify this option if you are performing a network installation and have already placed the updates image contents in rhupdates/ on the server. The rhupdates directory should only contain anaconda updates. The installation may fail if you add other files (such as errata RPMs) or if you place too much content in the directory. To load the anaconda updates from a network location instead, use: linux updates= followed by the URL for the location where the updates are stored. 28.1.4. Specifying the Installation MethodUse the askmethod option to display additional menus that enable you to specify the installation method and network settings. You may also configure the installation method and network settings at the boot: prompt itself. Table 28.1. Installation methods | Installation method | Option format |
|---|
| DVD drive | repo=cdrom:device | | Hard Drive | repo=hd:device/path | | HTTP Server | repo=http://host/path | | HTTPS Server | repo=https://host/path | | FTP Server | repo=ftp://username:password@host/path | | NFS Server | repo=nfs:server:/path | | ISO images on an NFS Server | repo=nfsiso:server:/path |
28.1.5. Specifying the Network SettingsNormally, anaconda prompts you to configure a network interface if one is needed during installation. However, you can provide network settings with options at the boot: prompt as follows: ipthe IP address for system netmaskthe netmask for the system gatewaythe IP address of the network gateway dnsthe IP address of the network DNS server ksdevicethe network device to use with these settings ifnamethe name you wish to assign to the network device, followed by the device's MAC address
Each of these settings is required even if you are only configuring a single interface. The following setting is optional: vlanidthe virtual LAN ID number (802.1q tag) for the specified network device
This example configures the network settings for an installation system that uses the IP address 192.168.1.10 for interface eth0. The interface is named primary: linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.3 ksdevice=eth0 ifname=primary:01:23:45:67:89:ab
If you specify the network configuration and network device at the boot: prompt, these settings are used for the installation process and the Networking Devices and Configure TCP/IP dialogs do not appear. 28.1.5.1. Configuring a Bonded InterfaceTo configure a bonded network interface, use the bond option. Name the bonded interface, specify which network connections will be bonded, and list any additional options in the following format: linux bond=<bondname>:<bondslaves>:[:<options>]
For example: linux bond=bond0:eth0,eth1:mode=active-backup,primary=eth1
Available optional parameters are listed in the Working with Kernel Modules chapter of the Red Hat Enterprise Linux Deployment Guide. 28.2. Enabling Remote Access to the Installation SystemYou may access either graphical or text interfaces for the installation system from any other system. Access to a text mode display requires telnet, which is installed by default on Red Hat Enterprise Linux systems. To remotely access the graphical display of an installation system, use client software that supports the VNC (Virtual Network Computing) display protocol. Red Hat Enterprise Linux includes the VNC client vncviewer. To obtain vncviewer, install the tigervnc package. The installation system supports two methods of establishing a VNC connection. You may start the installation, and manually login to the graphical display with a VNC client on another system. Alternatively, you may configure the installation system to automatically connect to a VNC client on the network that is running in listening mode. 28.2.1. Enabling Remote Access with VNC To enable remote graphical access to the installation system, enter two options at the prompt: linux vnc vncpassword=qwerty
The vnc option enables the VNC service. The vncpassword option sets a password for remote access. The example shown above sets the password as qwerty. The VNC password must be at least six characters long. Specify the language, keyboard layout and network settings for the installation system with the screens that follow. You may then access the graphical interface through a VNC client. The installation system displays the correct connection setting for the VNC client: Starting VNC...The VNC server is now running.Please connect to computer.mydomain.com:1 to begin the install...Starting graphical installation...Press <enter> for a shell You may then login to the installation system with a VNC client. To run the vncviewer client on Red Hat Enterprise Linux, choose ⤍ ⤍ , or type the command vncviewer in a terminal window. Enter the server and display number in the VNC Server dialog. For the example above, the VNC Server is computer.mydomain.com:1. 28.2.2. Connecting the Installation System to a VNC ListenerTo have the installation system automatically connect to a VNC client, first start the client in listening mode. On Red Hat Enterprise Linux systems, use the -listen option to run vncviewer as a listener. In a terminal window, enter the command: vncviewer -listen By default, vncviewer uses TCP port 5500 when in listening mode. To permit connections to this port from other systems, choose ⤍ ⤍ . Select Other ports, and Add. Enter 5500 in the Port(s) field, and specify tcp as the Protocol. Once the listening client is active, start the installation system and set the VNC options at the boot: prompt. In addition to vnc and vncpassword options, use the vncconnect option to specify the name or IP address of the system that has the listening client. To specify the TCP port for the listener, add a colon and the port number to the name of the system. For example, to connect to a VNC client on the system desktop.mydomain.com on the port 5500, enter the following at the boot: prompt: linux vnc vncpassword=qwerty vncconnect=desktop.mydomain.com:5500
28.2.3. Enabling Remote Access with sshTo enable remote access to a text mode installation, use the sshd=1 option at the boot: prompt: linux sshd=1
You can then connect to the installation system with the ssh utility. The ssh command requires the name or IP address of the installation system, and a password if you specified one (for example, in a kickstart file). 28.2.4. Enabling Remote Access with TelnetTo enable remote access to a text mode installation, use the telnet option at the boot: prompt: linux text telnet
You may then connect to the installation system with the telnet utility. The telnet command requires the name or IP address of the installation system: telnet computer.mydomain.com
To ensure the security of the installation process, only use the telnet option to install systems on networks with restricted access. 28.3. Logging to a Remote System During the InstallationBy default, the installation process sends log messages to the console as they are generated. You may specify that these messages go to a remote system that runs a syslog service. To configure remote logging, add the syslog option. Specify the IP address of the logging system, and the UDP port number of the log service on that system. By default, syslog services that accept remote messages listen on UDP port 514. For example, to connect to a syslog service on the system 192.168.1.20, enter the following at the boot: prompt: linux syslog=192.168.1.20:514
28.3.1. Configuring a Log ServerRed Hat Enterprise Linux uses rsyslog to provide a syslog service. The default configuration of rsyslog rejects messages from remote systems. The rsyslog configuration detailed below does not make use of any of the security measures available in rsyslog Crackers may slow or crash systems that permit access to the logging service, by sending large quantities of false log messages. In addition, hostile users may intercept or falsify messages sent to the logging service over the network. To configure a Red Hat Enterprise Linux system to accept log messages from other systems on the network, edit the file /etc/rsyslog.conf. You must use root privileges to edit the file /etc/rsyslog.conf. Uncomment the following lines by removing the hash preceding them: $ModLoad imudp.so$UDPServerRun 514
Restart the rsyslog service to apply the change: su -c '/sbin/service rsyslog restart'
Enter the root password when prompted. By default, the syslog service listens on UDP port 514. To permit connections to this port from other systems, choose ⤍ ⤍ . Select Other ports, and Add. Enter 514 in the Port(s) field, and specify udp as the Protocol. 28.4. Automating the Installation with KickstartYou can allow an installation to run unattended by using Kickstart. A Kickstart file specifies settings for an installation. Once the installation system boots, it can read a Kickstart file and carry out the installation process without any further input from a user. The Red Hat Enterprise Linux installation process automatically writes a Kickstart file that contains the settings for the installed system. This file is always saved as /root/anaconda-ks.cfg. You may use this file to repeat the installation with identical settings, or modify copies to specify settings for other systems. Firstboot does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the user option in the Kickstart file before installing additional systems from it (refer to Section 32.4, "Kickstart Options" for details) or log into the installed system with a virtual console as root and add users with the adduser command. Red Hat Enterprise Linux includes a graphical application to create and modify Kickstart files by selecting the options that you require. Use the package system-config-kickstart to install this utility. To load the Red Hat Enterprise Linux Kickstart editor, choose ⤍ ⤍ . Kickstart files list installation settings in plain text, with one option per line. This format lets you modify your Kickstart files with any text editor, and write scripts or applications that generate custom Kickstart files for your systems. To automate the installation process with a Kickstart file, use the ks option to specify the name and location of the file: linux ks=location/kickstart-file.cfg You may use Kickstart files that are held on either removable storage, a hard drive, or a network server. Refer to Table 28.2, "Kickstart sources" for the supported Kickstart sources. Table 28.2. Kickstart sources | Kickstart source | Option format |
|---|
| DVD drive | ks=cdrom:/directory/ks.cfg | | Hard Drive | ks=hd:/device/directory/ks.cfg | | Other Device | ks=file:/device/directory/ks.cfg | | HTTP Server | ks=http://server.mydomain.com/directory/ks.cfg | | HTTPS Server | ks=https://server.mydomain.com/directory/ks.cfg | | FTP Server | ks=ftp://server.mydomain.com/directory/ks.cfg | | NFS Server | ks=nfs:server.mydomain.com:/directory/ks.cfg |
To obtain a Kickstart file from a script or application on a Web server, specify the URL of the application with the ks= option. If you add the option kssendmac, the request also sends HTTP headers to the Web application. Your application can use these headers to identify the computer. This line sends a request with headers to the application http://server.mydomain.com/kickstart.cgi: linux ks=http://server.mydomain.com/kickstart.cgi kssendmac
28.5. Enhancing Hardware SupportBy default, Red Hat Enterprise Linux attempts to automatically detect and configure support for all of the components of your computer. Red Hat Enterprise Linux supports the majority of hardware in common use with the software drivers that are included with the operating system. To support other devices you may supply additional drivers during the installation process, or at a later time. 28.5.1. Overriding Automatic Hardware DetectionFor some models of device automatic hardware configuration may fail, or cause instability. In these cases, you may need to disable automatic configuration for that type of device, and take additional steps to manually configure the device after the installation process is complete. Refer to the Release Notes for information on known issues with specific devices. To override the automatic hardware detection, use one or more of the following options: Table 28.3. Hardware Options | Compatibility | Option |
|---|
| Disable all hardware detection | noprobe | | Disable graphics, keyboard, and mouse detection | headless | | Disable passing keyboard and mouse information to stage 2 of the installation program | nopass | | Use basic VESA driver for video | xdriver=vesa | | Disable shell access on virtual console 2 during installation | noshell | | Disable advanced configuration and power interface (ACPI) | acpi=off | | Disable machine check exception (MCE) CPU self-diagnosis. | nomce | | Disable non-uniform memory access on the AMD64 architecture | numa-off | Force kernel to detect a specific amount of memory, where xxx is a value in megabytes | mem=xxxm | | Enable DMA only for IDE and SATA drives | libata.dma=1 | | Disable BIOS-assisted RAID | nodmraid | | Disable Firewire device detection | nofirewire | | Disable parallel port detection | noparport | | Disable PC Card (PCMCIA) device detection | nopcmcia | | Disable all probing of network hardware | nonet |
The isa option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer. Other kernel boot options have no particular meaning for anaconda and do not affect the installation process. However, if you use these options to boot the installation system, anaconda will preserve them in the bootloader configuration. 28.6. Using the Maintenance Boot Modes28.6.1. Verifying boot mediaYou can test the integrity of an ISO-based installation source before using it to install Red Hat Enterprise Linux. These sources include DVD, and ISO images stored on a hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation. Red Hat Enterprise Linux offers you two ways to test installation ISOs: 28.6.2. Booting Your Computer with the Rescue ModeYou may boot a command-line Linux system from either a rescue disc or an installation disc, without installing Red Hat Enterprise Linux on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on your computer. The rescue disc starts the rescue mode system by default. To load the rescue system with the installation disc, choose from the boot menu. Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer. By default, rescue mode attaches an existing operating system to the rescue system under the directory /mnt/sysimage/. 28.6.3. Upgrading your computerA previous boot option, upgrade, has been superceded by a stage in the installation process where the installation program prompts you to upgrade or reinstall earlier versions of Red Hat Enterprise Linux that it detects on your system. However, the installation program may not correctly detect a previous version of Red Hat Enterprise Linux if the contents of the /etc/redhat-release file have changed. The boot option upgradeany relaxes the test that the installation program performs and allows you to upgrade a Red Hat Enterprise Linux installation that the installation program has not correctly identified. Chapter 29. Installing Without MediaThis procedure assumes you are already using Red Hat Enterprise Linux or another relatively modern Linux distribution, and the GRUB boot loader. It also assumes you are a somewhat experienced Linux user. This section discusses how to install Red Hat Enterprise Linux on your system without making any additional physical media. Instead, you can use your existing GRUB boot loader to start the installation program. 29.1. Retrieving Boot FilesTo perform an installation without media or a PXE server, your system must have two files stored locally, a kernel and an initial RAM disk. Copy the vmlinuz and initrd.img files from a Red Hat Enterprise Linux DVD (or DVD image) to the /boot/ directory, renaming them to vmlinuz-install and initrd.img-install. You must have root privileges to write files into the /boot/ directory. 29.2. Editing the GRUB ConfigurationThe GRUB boot loader uses the configuration file /boot/grub/grub.conf. To configure GRUB to boot from the new files, add a boot stanza to /boot/grub/grub.conf that refers to them. A minimal boot stanza looks like the following listing: title Installation root (hd0,0) kernel /vmlinuz-install initrd /initrd.img-install You may wish to add options to the end of the kernel line of the boot stanza. These options set preliminary options in Anaconda which the user normally sets interactively. For a list of available installer boot options, refer to Chapter 28, Boot Options. The following options are generally useful for medialess installations: When you are finished, change the default option in /boot/grub/grub.conf to point to the new first stanza you added: default 0 29.3. Booting to InstallationReboot the system. GRUB boots the installation kernel and RAM disk, including any options you set. You may now refer to the appropriate chapter in this guide for the next step. If you chose to install remotely using VNC, refer to Section 28.2, "Enabling Remote Access to the Installation System" for assistance in connecting to the remote system. Chapter 30. Setting Up an Installation ServerThe following steps must be performed to prepare for a network installation: Configure the network (NFS, FTP, HTTP, HTTPS) server to export the installation tree. Configure the files on the tftp server necessary for network booting. Configure which hosts are allowed to boot from the network configuration. Start the tftp service. Configure DHCP. Boot the client, and start the installation.
30.1. Setting up the Network Server30.2. Network Boot ConfigurationThe next step is to copy the files necessary to start the installation to the 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. The PXE boot configuration procedure differs for BIOS and EFI. A separate yaboot configuration procedure is provided for Power Systems servers. 30.2.1. Configuring PXE boot for BIOSIf tftp-server is not yet installed, run yum install tftp-server. In the tftp-server config file at /etc/xinet.d/tftp, change the disabled parameter from yes to no. Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the DHCP Servers chapter in the Red Hat Enterprise Linux Deployment Guide.) A sample configuration in /etc/dhcp/dhcpd.conf might look like: option space pxelinux; option pxelinux.magic code 208 = string; option pxelinux.configfile code 209 = text; option pxelinux.pathprefix code 210 = text; option pxelinux.reboottime code 211 = unsigned integer 32; subnet 10.0.0.0 netmask 255.255.255.0 { option routers 10.0.0.254; range 10.0.0.2 10.0.0.253; class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; next-server 10.0.0.1; if option arch = 00:06 { filename "pxelinux/bootia32.efi"; } else if option arch = 00:07 { filename "pxelinux/bootx64.efi"; } else { filename "pxelinux/pxelinux.0"; } } host example-ia32 { hardware ethernet XX:YY:ZZ:11:22:33; fixed-address 10.0.0.2; } }You now need the pxelinux.0 file from the SYSLINUX package in the ISO image file. To access it, run the following commands as root: mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/Packages/syslinux-version-architecture.rpm /publicly_available_directoryumount /mount_point
Extract the package: rpm2cpio syslinux-version-architecture.rpm | cpio -dimv
Create a pxelinux directory within tftpboot and copy pxelinux.0 into it: mkdir /var/lib/tftpboot/pxelinuxcp publicly_available_directory/usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/pxelinux
Create a pxelinux.cfg directory within pxelinux: mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
Add a config file to this directory. The file should either be named default or named after the IP address. For example, if your machine's IP address is 10.0.0.1, the filename would be 0A000001. A sample config file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/default might look like: default vesamenu.c32prompt 1timeout 600display boot.msglabel linux menu label ^Install or upgrade an existing system menu default kernel vmlinuz append initrd=initrd.imglabel vesa menu label Install system with ^basic video driver kernel vmlinuz append initrd=initrd.img xdriver=vesa nomodesetlabel rescue menu label ^Rescue installed system kernel vmlinuz append initrd=initrd.img rescuelabel local menu label Boot from ^local drive localboot 0xfffflabel memtest86 menu label ^Memory test kernel memtest append - Copy the splash image into your tftp root directory: cp /boot/grub/splash.xpm.gz /var/lib/tftpboot/pxelinux/splash.xpm.gz
Copy the boot images into your tftp root directory: cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/rhel6/
Reboot the system, and select the network device as your boot device when prompted.
30.2.2. Configuring PXE boot for EFIIf tftp-server is not yet installed, run yum install tftp-server. In the tftp-server config file at /etc/xinet.d/tftp, change the disabled parameter from yes to no. Create a directory path within tftpboot for the EFI boot images, and then copy them from your boot directory: mkdir /var/lib/tftpboot/pxelinuxmkdir /var/lib/tftpboot/pxelinux/bootx64.eficp /boot/efi/EFI/redhat/grub.efi /var/lib/tftpboot/pxelinux/bootx64.efi
Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the DHCP Servers chapter in the Red Hat Enterprise Linux Deployment Guide.) A sample configuration in /etc/dhcp/dhcpd.conf might look like: option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option arch code 93 = unsigned integer 16; # RFC4578 subnet 10.0.0.0 netmask 255.255.255.0 { option routers 10.0.0.254; range 10.0.0.2 10.0.0.253; class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; next-server 10.0.0.1; if option arch = 00:06 { filename "pxelinux/bootia32.efi"; } else if option arch = 00:07 { filename "pxelinux/bootx64.efi"; } else { filename "pxelinux/pxelinux.0"; } } host example-ia32 { hardware ethernet XX:YY:ZZ:11:22:33; fixed-address 10.0.0.2; } }Create a pxelinux.cfg directory within pxelinux: mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
Add a config file to this directory. The file should either be named efidefault or named after the IP address. For example, if your machine's IP address is 10.0.0.1, the filename would be 0A000001. A sample config file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault might look like: default=0timeout=1splashimage=(nd)/splash.xpm.gzhiddenmenutitle RHEL root (nd) kernel /rawhide-x86_64/vmlinuz initrd /rawhide-x86_64/initrd.img Copy the splash image into your tftp root directory: cp /boot/grub/splash.xpm.gz /var/lib/tftpboot/pxelinux/splash.xpm.gz
Copy the boot images into your tftp root directory: cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/rhel6/
Reboot the system, and select the network device as your boot device when prompted.
30.2.3. Configuring for Power Systems serversIf tftp-server is not yet installed, run yum install tftp-server. In the tftp-server config file at /etc/xinet.d/tftp, change the disabled parameter from yes to no. Configure your DHCP server to use the boot images packaged with yaboot. (If you do not have a DHCP server installed, refer to the DHCP Servers chapter in the Red Hat Enterprise Linux Deployment Guide.) A sample configuration in /etc/dhcp/dhcpd.conf might look like: host bonn { filename "yaboot"; next-server 10.32.5.1; hardware ethernet 00:0e:91:51:6a:26; fixed-address 10.32.5.144; }You now need the yaboot binary file from the yaboot package in the ISO image file. To access it, run the following commands as root: mkdir /publicly_available_directory/yaboot-unpackmount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/Packages/yaboot-version.ppc.rpm /publicly_available_directory/yaboot-unpack
Extract the package: cd /publicly_available_directory/yaboot-unpack rpm2cpio yaboot-version.ppc.rpm | cpio -dimv Create a yaboot directory within tftpboot and copy the yaboot binary file into it: mkdir /var/lib/tftpboot/yabootcp publicly_available_directory/yaboot-unpack/usr/lib/yaboot/yaboot /var/lib/tftpboot/yaboot
Add a config file named yaboot.conf to this directory. A sample config file might look like: init-message = "\nWelcome to the Red Hat Enterprise Linux 6 installer!\n\n"timeout=60default=rhel6image=/rhel6/vmlinuz-RHEL6 label=linux alias=rhel6 initrd=/rhel6/initrd-RHEL6.img append="repo=http://10.32.5.1/mnt/archive/redhat/released/RHEL-6/6.x/Server/ppc64/os/" read-only Copy the boot images from the extracted ISO into your tftp root directory: cp /mount_point/images/ppc/ppc64/vmlinuz /var/lib/tftpboot/yaboot/rhel6/vmlinuz-RHEL6cp /mount_point/images/ppc/ppc64/initrd.img /var/lib/tftpboot/yaboot/rhel6/initrd-RHEL6.img
Clean up by removing the yaboot-unpack directory and unmounting the ISO: rm -rf /publicly_available_directory/yaboot-unpack umount /mount_point Reboot the system, and select the network device as your boot device when prompted.
30.3. Starting the tftp ServerOn the DHCP server, verify that the tftp-server package is installed with the command rpm -q tftp-server. tftp is an xinetd-based service; start it with the following commands:
/sbin/chkconfig --level 345 xinetd on/sbin/chkconfig --level 345 tftp on
These commands configure the tftp and xinetd services to start at boot time in runlevels 3, 4, and 5. 30.4. Adding a Custom Boot MessageOptionally, modify /var/lib/tftpboot/linux-install/msgs/boot.msg to use a custom boot message. 30.5. Performing the InstallationFor instructions on how to configure the network interface card to boot from the network, consult the documentation for the NIC. It varies slightly per card. |
| |
