云南龙网

  1. 首页 > 云知道 > >

使用JumpStart快速安装Solaris( 二 )

云知道


　# cd /export/config
　# mkdir sysidcfg1
　# cd sysidcfg1
　# vi sysidcfg
　system_locale=en_US.ISO8859-1
　timezone=US/Pacific
　timeserver=localhost
　terminal=vt100
　name_service=NONE
　security_policy=NONE
　root_passWord=
　network_interface=bge0 {hostname=client1
　netmask=255.255.255.0
　protocol_ipv6=no
　default_route=172.16.64.1}
　:wq
　# cd ../
　# mkdir sysidcfg2
　# cd sysidcfg2
　# vi sysidcfg
　system_locale=en_US.ISO8859-1
　timezone=US/Pacific
　timeserver=localhost
　terminal=vt100
　name_service=NONE
　security_policy=NONE
　root_password=
　network_interface=bge0 {hostname=client2
　netmask=255.255.255.0
　protocol_ipv6=no
　default_route=172.16.64.1}
　:wqc. Create the rules file:
The next file to create is the rules file. This is a text file that contains a rule for each clIEnt or group of clients on which the Solaris OS will be installed. Each line of the rules file tells JumpStart which begin, profile, and finish files to use for each client or group of clients.
There is only one rules file. It can contain multiple lines depending upon how many unique configurations are needed. The following shows the contents of a rules file that contains information for two separate clients:
　# cd /export/config
　# vi rules
　hostname client1 begin1 profile1 finish1
　hostname client2 begin2 profile2 finish2
　:wqThe rules file is used by the check script when it creates the rules.ok file. Successful creation of the rules.ok file is required for custom JumpStart installations.
d. Create the begin file:
The begin file is a user-defined Bourne shell script that is used to perform tasks on the client before the installation of the Solaris OS begins. Typical tasks include creating derived profiles and the backing up of files before upgrading.
Multiple begin files can be used if desired. The following shows the creation of two begin files:
　# cd /export/config
　# vi begin1
　#!/bin/sh
　echo "Begin Script for JumpStart client1..."
　:wq
　# vi begin2
　#!/bin/sh
　echo "Begin Script for JumpStart client2..."
　:wq
　# chmod 755 begin*During installation on the client, output from the begin file is written to /tmp/begin.log. After the installation is done, the log file can be found in /var/sadm/system/logs/begin.log.
The Solaris 10 Installation Guide includes a Custom JumpStart Environment Variables section that describes variables you can use in begin scripts.
e. Create the finish file:
The finish file is a user-defined Bourne shell script that is used to perform tasks on the clIEnt after the installation of the Solaris OS has completed. This script is typically used to add additional files, add packages and patches, customize the root environment, and install additional software.
Multiple finish files can be used if desired. The following shows the creation of two finish files:
　# cd /export/config
　# vi finish1
　#!/bin/sh
　echo "Finish Script for JumpStart client1..."
　echo "Get rid of the nfs prompt during the initial boot"
　touch /a/etc/.NFS4inst_state.domain
　:wq
　# vi finish2
　#!/bin/sh
　echo "Finish Script for JumpStart client2..."
　echo "Get rid of the nfs prompt during the initial boot"
　touch /a/etc/.NFS4inst_state.domain
　:wq
　# chmod 755 finish*The Solaris installation program mounts the client systems' file systems on /a. The finish script can be used to add, change, or remove files with respect to /a. These file systems remain mounted on /a until the initial system reboot.
The JumpStart Directory, that is, /export/install, is mounted on the directory that is specified by the SI_CONFIG_DIR variable. The directory is set to /tmp/install_config by default. Files can be copied from the JumpStart directory to the client by commands run in the finish script. Files that are to be added to the installed system are placed in the JumpStart directory and are then accessible by the client.

推荐阅读


上一篇：花生地下害虫怎么治

下一篇：超能战联娜雅菲技能使用方法