client_arch Profile Keyword
client_arch karch_value ... |
client_arch specifies that the operating system server is to support a different platform group than the server uses. If you do not specify client_arch in the profile, any diskless client that uses the operating system server must contain the same platform group as the server. You must specify each platform group that you want the operating system server to support.
Valid values for karch_value are sun4m and sun4u. For a detailed list of platform names and various systems, see Solaris 9 Sun Hardware Guide.
Note - You can use client_arch only when system_type is specified as server.
client_root Profile Keyword
client_root root_size |
client_root defines the amount of root space, root_size in Mbytes, to allocate for each client. If you do not specify client_root in a server's profile, the installation software allocates 15 Mbytes of root space per client. The size of the client root area is used in combination with the num_clients keyword to determine how much space to reserve for the /export/root file system.
Note - You can use client_root only when system_type is specified as server.
client_swap Profile Keyword
client_swap swap_size |
client_swap defines the amount of swap space, swap_size in Mbytes, to allocate for each diskless client. If you do not specify client_swap in the profile, 32 Mbytes of swap space is allocated by default.
Example:
client_swap 64 |
The example specifies that each diskless client is to have a swap space of 64 Mbytes.
Note - You can use client_swap only when system_type is specified as server.
How the Size of swap Is Determined
If a profile does not specify the size of swap, the JumpStart program determines the size of the swap space, based on the system's physical memory. Table 28-5 shows how the size of swap is determined during a custom JumpStart installation.
Table 28-5 Determining swap Size
Physical Memory (in Mbytes) | Swap Space (in Mbytes) |
|---|---|
16-64 | 32 |
64-128 | 64 |
128-512 | 128 |
Greater than 512 | 256 |
The JumpStart program makes the size of swap no more than 20 percent of the disk where swap is located, unless the disk contains free space after laying out the other file systems. If free space exists, the JumpStart program allocates the free space to swap, and if possible, allocates the amount that is shown in Table 28-5.
Note - Physical memory plus swap space must total a minimum of 32 Mbytes.
cluster Profile Keyword (Adding Software Groups)
cluster group_name |
cluster designates the software group to add to the system. The group_name for each software group is listed in the following table.
Software Group | group_name |
|---|---|
Core | SUNWCreq |
End User Solaris Software Group | SUNWCuser |
Developer Solaris Software Group | SUNWCprog |
Entire Solaris Software Group | SUNWCall |
Entire Solaris Software Group Plus OEM Support | SUNWCXall |
You can specify only one software group in a profile. The software group must be specified before other cluster and package entries. If you do not specify a software group with cluster in the profile, the end-user software group, SUNWCuser, is installed on the system.
cluster Profile Keyword (Adding or Deleting Clusters)
cluster cluster_name add_delete_switch |
Note - cluster (adding or deleting clusters) can be used with both the initial installation and upgrade options.
cluster designates whether a cluster is to be added or deleted from the software group that is to be installed on the system.
cluster_name must be in the form SUNWCname. To view detailed information about clusters and their names, start Admintool on an installed system and choose Software from the Browse menu.
add_delete_switch represents the option add or delete. Use add_delete_switch to indicate whether to add or delete the cluster that is specified. If you do not specify add_delete_switch, add is used by default.
When you use cluster (adding or deleting clusters) during an upgrade, the following condition apply:
All clusters that are already on the system are automatically upgraded.
If you specify cluster_name add, and cluster_name is not installed on the system, the cluster is installed.
If you specify cluster_name delete, and cluster_name is installed on the system, the package is deleted before the upgrade begins.
dontuse Profile Keyword
dontuse disk_name ... |
By default, the JumpStart program uses all of the operational disks on the system when partitioning default is specified. dontuse designates one or more disks that you do not want the JumpStart program to use. disk_name must be specified in the form cxtydz, for example, c0t0d0.
Note - You cannot specify the dontuse keyword and the usedisk keyword in the same profile.
filesys Profile Keyword (Mounting Remote File Systems)
filesys server:path server_address mount_pt_name [mount_options] |
By using filesys with the listed values, the JumpStart program sets up the installed system to automatically mount remote file systems when the system boots. You can specify filesys more than once.
Example:
filesys sherlock:/export/home/user2 - /home |
server: - The name of the server where the remote file system is located, followed by a colon.
path - The remote file system's mount-point name. For example, /usr or /export/home.
server_address - The IP address of the server that is specified in server:path. If a name service is not running on the network, the server_address value can be used to populate the /etc/hosts file with the server's host name and IP address. If you are not specifying the server's IP address, you must specify a minus sign (-). For example, if you have a name service that is running on the network, you do not need to specify the server's IP address.
mount_pt_name - The name of the mount point on which the remote file system is to be mounted.
mount_options - One or more mount options, which is the same as the -o option of the mount(1M) command. The mount options are added to the /etc/vfstab entry for the specified mount_pt_name.
Note - If you need to specify more than one mount option, the mount options must be separated by commas and no spaces (ro,quota, for example).
filesys Profile Keyword (Creating Local File Systems)
filesys slice size [file_system optional_parameters] |
By using filesys with the values that are listed, the JumpStart program creates local file systems during the installation. You can specify filesys more than once.
slice - Use one of the following values:
any - The JumpStart program places the file system on any disk.
Note - You cannot specify any when size is existing, all, free, start:size, or ignore.
cwtxdysz - The disk slice where the JumpStart program places the file system, for example, c0t0d0s0 or c0d0s0.
rootdisk.sn - The variable that contains the value for the system's root disk, which is determined by the JumpStart program as described in "How the System's Root Disk Is Determined". The sn suffix indicates a specific slice on the disk.
size - Use one of the following values:
num - The size of the file system is set to num in Mbytes.
existing - The current size of the existing file system is used.
Note - When you use the existing value, you can change the name of an existing slice by specifying file_system as a different mount_pt_name.
auto - The size of the file system is automatically determined, depending on the software that is selected.
all - The specified slice uses the entire disk for the file system. When you specify the all value, no other file systems can be placed on the specified disk.
free - The remaining unused space on the disk is used for the file system.
Note - If free is used as the value to filesys, the filesys entry must be the last entry in a profile.
start:size - The file system is explicitly partitioned. start is the cylinder where the slice begins. size is the number of cylinders for the slice.
file_system - The file_system value is optional and used when slice is specified as any or cwtxdysz. If file_system is not specified, unnamed is set by default. If unnamed is set, you cannot specify the optional_parameters value. Use one of the following values:
mount_pt_name - The file system's mount-point name, for example, /var.
swap - The specified slice is used as swap.
overlap - The specified slice is defined as a representation of a disk region. The VTOC value is V_BACKUP. By default, slice 2 is an overlap slice that is a representation of the whole disk.
Note - You can specify overlap only when size is existing, all, or start:size.
unnamed - The specified slice is defined as a raw slice, so slice does not have a mount-point name. If you do not specify file_system, unnamed is used by default.
ignore - The specified slice is not used or recognized by the JumpStart program. You can use this option to specify that you want a file system to be ignored on a disk during installation. The JumpStart program creates a new file system on the same disk with the same name. You can use ignore only when partitioning existing is specified.