Monday, November 29, 2010

Based on Red Hat Linux network of unattended installation

In this way the user can enter some version of the LABEL (for example, rhel4u2-i386) to select a specific version of the installation.

In order to be able to install what alternative when know, you can have the pxelinux.0 tip to households choose display a list before. This is specified in the default DISPLAY option. In the above example, we'll all alternative RedHatLinux version listed in the file list, pxelinux.cfg/it's content will be pxelinux.0 displayed. In our case,/tftpboot/pxelinux.cfg/list file reads as follows: ChooseoneofthefollowingLinuxdistributionsforyourinstallation: NameDistributionArch.Installationmedia-------------------------------------------------------------------------rhel3u6-i386RHEL3ASU6i386192.168.138.1:/instsvr/i386/rhel3u6rhel3u6-x86_64RHEL3ASU6x86_64192.168.138.1:/instsvr/x86_64/rhel3u6rhel4u2-i386RHEL4ASU2i386192.168.138.1:/instsvr/i386/rhel4u26) start TFTP service. Root @ bsvr] # service xinetdrestart3. step 2: Configure the install Server installation server during installation on Linux installation media provided and unattended installation of the configuration file access. The installation media are stored in a directory on the server, you can use a variety of network protocols to access it, such as HTTP, FTP, and NFS., using the NFS protocol RedHatLinux Installer can support a variety of installation media directory structure, especially support ISO CD image files. Here we choose to use the NFS protocol to access the installation media. Configuring NFS server 1) prepare ISO installation media. Will the ISO RedHatLinux installation media files onto/instsvr directory. Note do not change the file name. Root @ bsvr] # mkdir/instsvrroot @ bsvr] # mv RHEL4-U2-i386-AS-disc1.iso/instsvr/i386/rhel4u2root @ bsvr] # mv RHEL4-U2-i386-AS-disc2.iso/instsvr/i386/rhel4u2root @ bsvr] # mv RHEL4-U2-i386-AS-disc3.iso/instsrv/i386/rhel4u2root @ bsvr] # mv RHEL4-U2-i386-AS-disc4.iso/instsrv/i386/rhel4u22) Edit NFS server configuration file/etc/exports to allow other machines through NFS access directory/instsrv./etc/exports file reads as follows:/instsvr * (ro, no_root_squash, sync) which: * represents any IP address can access the directory. For security reasons, you can also specify a specific IP address. Ro indicates that the remote machine to the directory only read permissions. Other options please refer to the NFS manual. 3) restart NFS service to enable the new configuration to take effect root @ bsvr] # serviceportmaprestart; servicenfsrestart4) detection of directory/instsrv has been properly shared root @ bsvr] # showmount-elocalostExportlistforlocalhost:/instsrv * in this way, we will set up an installation server. Very simple to configure kickstart installation! 5.2, RedHatLinux started to support a feature called kickstart, whose primary purpose is to reduce the installation process of human-computer interaction, increase the efficiency of the installation. Use this method, you simply define a configuration file (usually located in the install server), and let the installer knows the location of the configuration file, during the installation, the installer can read files from the installation configuration, this avoids cumbersome human-computer interaction, achieve unattended automated installation. To use the kickstart, you must: 1) to create kickstart profile. 2) deployment of kickstart profiles, upcoming kickstart configuration files to install on the server, and the installer's kernel parameter specifies the location of the kickstart profile. Create kickstart profile kickstart profile is a simple text file that contains a list of the Setup project. Each item corresponds to an installed option, use keywords. There are several ways to generate kickstart profile: RedHat provides a sample file. On RedHatLinux documentation CD RH-DOCS sample.ks file in the directory. You can be based on the sample to create your own configuration kicksTart file. Whenever you install a RedHatLinux machine, RedHatLinux Installer creates a kickstart profile, record your real installation configuration. If you want to achieve and a system similar to install, can be based on the system of kickstart profiles to generate your own kickstart profile. RedHatLinux provides a graphical kickstart configuration tool. In any of the installed RedHatLinux run the tool on your system, you can easily create your own kickstart profile. Kickstart configuration tool command to redhat-config-kickstart (RHEL3) or system-config-kickstart (RHEL4) read the kickstart profile brochure. Use any text editor you can create your own kickstart profile. Here is a sample kickstart profile: Note: the author to remove the original sample, because of the kickstart, different companies have different installation requirements, put a sample here is really not meant. For kickstart file, it is worth noting that since the representative of the complete post% system after the installation of the command will be executed, we can configure the system, such as adjusting the kernel parameters, configure a host firewall, etc. All to "#" sign at the beginning of the note. File NFS-server = 192.168.138.1-dir =/instsvr/i386/rhel4u2 option tells the installer: the server's NFS shared directory 192.168.138.1/instsvr/i386/rhel4u2 next looking for installation media. RedHatLinux Setup is smart enough to recognize the directory should be read by the ISO CD image file name, all here you do not need to specify the ISO file name. About kickstart profile supports all of the options and believe that description, please refer to the reference material 3. deploying kickstart profile first of all we need to kickstart configuration file in the install server. We put it into/instsvr/ks directory. That is, the file NFS access path is: nfs: 192.168.138.1:/instsvr/ks/ks.cg Secondly, we need to let the installer know where we want it to use the kickstart installation, and tell it where to get kickstart profile. This can be done by adding a parameter to the kernel "ks = kickstart profile path". We only need to launch the server's default file to do some small changes you can do this: LABELrhel4u2-i386KERNELvmlinuz-rhel4u2-i386APPENDks = nfs: 192.168.138.1:/instsvr/ks/ks.cfginitrd = initrd-rhel4u2-i386.imgramdisk_size = 8192 so starts the installation when the parameter ks = nfs: 192.168.138.1:/instsvr/ks/ks.cfg is passed to it, tell it to use this file as the kickstart profile for kickstart installation. 5. step 3: start the machine from the network to complete the installation of the preceding configuration is completed, we will be installing the machine over the network in unattended mode to install RedHatEnterpriseLinuxAS4Update2. boot the machine to be installed, select start from the network card. Exact method of BIOS version.

No comments:

Post a Comment