It allows the administrator to have available different custom jumpstart configurations based on rule sets. This is very helpful when different groups within an organization require different system configurations. Below are examples of a profile. Profiles contain filesystem layout and package information. A derived profile is a profile that is dynamically created by a begin script during a custom JumpStart installation.
Derived profiles are needed when you cannot set up the rules file to match specific systems to a profile when you need more flexibility than the rules file can provide. The rules file is a text file used to create the rules. The rules file is a look-up table consisting of one or more rules that define matches between system attributes and profiles. For example, the rule. Note : Solaris 8 will prompt for two new options, ipv6, and kerberos. To avoid user interaction you must include answers to these options in the sysidcfg file.
Profile floppy disks cannot be created on a platform with a different architecture than the Jumpstart client. X86 Solaris install will prompt during the install for openwindows parameters. To be able to automate these values you must pass them to the client through rplboot system.
Directory where our tools are found. Directory to store all files and other information that need to be backed up for the particular machine. The root disk device specified as an argument to migrate. Where packages are installed on the server migrate. The JumpStart directory on the server. Is a predefined lexical unit or word that describes a general system attribute, such as host name hostname or memory size memsize. It is used with the rule value to match a system with the same attribute to a profile.
See Table 19 for the list of rule keywords. Is a value that provides the specific system attribute for the corresponding rule keyword. Rule values are described in Table Is a symbol you must use to join rule keyword and rule value pairs together in the same rule a logical AND.
During a custom JumpStart installation, a system must match every pair in the rule before the rule matches. Is the name of an optional Bourne shell script that can be executed before the installation begins.
If no begin script exists, you must enter a minus sign - in this field. All begin scripts must be located in the JumpStart directory. Other files require little or no administration. This file contains the IP interface names of the routers that are directly connected to the network. The existence of this file in the system is optional. If the file exists, then the system is configured to support static routing.
This file contains the IPv4 addresses in the network together with the corresponding interface names on which the addresses are configured. This file contains the network number, such as See the netmasks 4 man page for more information. This file contains parameters that determine the boot processes for systems that are configured to boot in network client mode.
The file is the basis for the creation of the bootparams database that the name service uses if you are not using the local files mode. To obtain specific information about the content and format of this file, refer to the bootparams 4 man page.
The file associates hostnames with their MAC addresses. The file is the basis for the creation of an ethers database for use in the network where systems are configured as network clients. For more information, see the ethers 4 man page. This file associates network names and network numbers. Comments can also be added to further clarify each entry in the database.
This file enables applications to use and display the network names instead of network numbers. For example, the netstat program uses the information in this database to produce status tables. All the subnetworks that connect to the local network through routers must be included in this file. Create profile for the client — The profile file contains the information about which software cluster to install in client.
It also explicitly supplies the disk partitioning parameters. I would be using a simple disk partition for this example. Create the sysidcfg The sysidcfg file is used for configuring the client and contains information like IP address, hostname, time zone etc. The minimum information required for an automated install is :. Edit the rules file — The rules file is used to create the rules. Check the rules file Run the check script in the config directory to check the syntax of the rules file.
NFS sharing the jupstart directories Make sure you add the config and install directories to the dfstab for NFS sharing them.
0コメント