Bienvenue sur le site admin-sys

Installation

Jerome ROBERT — 2008-09-17T17:25:44Z

Création du/des dépôt(s) :

exemple : mkdir -p /jumpstart/images/Version_OS/type_OS/

# mkdir -p /jumpstart/images/S8_02-02/sparc/

# mkdir -p /jumpstart/images/S8_02-02/x86/ ( pour version PC )

Copie du cdrom 1/2 dans le dépôt :

# cd /CD_mount_point/Solaris_8/Tools

# ./setup_install_server /jumpstart/images/S8_02-02/sparc/

Copie du cdrom 2/2 dans le dépôt :

# cd /CD_mount_point/Solaris_8/Tools

# ./add_to_install_server /jumpstart/images/S8_02-02/sparc/

Copie du cdrom language (si nécessaire )

# cd /CD_mount_point/Tools

# ./add_to_install_server /jumpstart/images/S8_02-02/sparc/

Ajouter au fichier /etc/dfs/dfstab :

share -F nfs -o ro,anon=0 /jumpstart

Ajout de client jumpstart

# cd /jumpstart/images/S8_02-02/sparc/Solaris_8/Tools (si solaris8 )

# ./add_install_client ....... (pour l'ajout de client ... )

Configuration

Jerome ROBERT — 2008-09-17T17:25:13Z

Jumpstart:

Création d'un fichier sysidcfg :

network_interface=primary {hostname=calais protocol_ipv6=no netmask=255.255.0.0 ip_address=172.16.50.146 default_route=none }

security_policy=none

name_service=none

timezone=MET

system_locale=en_US.ISO8859-1

#mot de passe: root

root_password=EykO4BPBhuF5I

terminal=vt100

timeserver=localhost

Attention:

ne pas oubliez "default_route" en solaris 9. default_route=none Ã©tait par dÃ©faut en solaris infÃ©rieur.

pour la variable system_locale: mettre locale.clavier (exemple: en_US.ISO8859-1 )

pour un savoir plus cliquez ici

Création du fichier rules:

hostname calais - calais_class -

pour un savoir plus cliquez ici

Création du fichier calais_class:

install_type initial_install

system_type standalone

partitioning default

filesys any 128 swap

cluster SUNWCall

dontuse c1t0d0

locale en_US

pour un savoir plus cliquez ici

Variables jumpstart:

pour un savoir plus

sysidcfg (sun)

Jerome ROBERT — 2008-09-17T17:24:38Z

Mots clés pour sysidcfg:

Syntax Rules for the `sysidcfg` File

You can use two types of keywords in the sysidcfg file: independent and dependent. Dependent keywords are guaranteed to be unique only within independent keywords. A dependent keyword exists only when it is identified with its associated independent keyword.

In this example, name_service is the independent keyword, while domain_name and name_server are the dependent keywords:

name_service=NIS {domain_name=marquee.central.sun.com name_server=connor(129.152.112.3)}

Syntax Rule	Example
Independent keywords can be listed in any order.	pointer=MS-S display=ati {size=15-inch}
Keywords are not case sensitive.	TIMEZONE=US/Central terminal=PC Console
Enclose all dependent keywords in curly braces ({}) to tie them to their associated independent keyword.	name_service=NIS {domain_name=marquee.central.sun.com name_server=connor(129.152.112.3)}
You can optionally enclosed values in single (`) or double quotes (").	network_interface='none'
Only one instance of a keyword is valid. However, if you specify the keyword more than once, only the first instance of the keyword is used.	network_interface=none network_interface=le0

`sysidcfg` File Keywords

The following table describes the keywords you can use in the sysidcfg file .

Table 12 - Keywords You Can Use in sysidcfg

Configuration Information	Platform	Keywords	Values or Examples
Name service, domain name, name server	All	`name_service=NIS, NIS+, DNS, LDAP, NONE`
		Options for NIS and NIS+: `{domain_name=` `domain_namename_server=hostname`(`ip_address` )}	`name_service=NIS {domain_name=west.arp.com name_server=timber(129.221.2.1)}` `name_service=NIS+ {domain_name=west.arp.com. name_server=timber(129.221.2.1)}`
		Options for DNS: `{domain_name=` `domain_name` `name_server=ip_address`,`ip_address` , `ip_address` (three maximum) `search=domain_name` ,`domain_name`,`domain_name`,`domain_name`, `domain_namedomain_name` (six maximum, total length less than or equal to 250 characters)`}`,	`name_service=DNS {domain_name=west.arp.com name_server=10.0.1.10,10.0.1.20 search=arp.com,east.arp.com}` Note: Choose only one value for `name_service`. Include either, both, or neither the `domain_name` and `name_server` keywords, as needed. If neither keyword is used, omit the curly braces {}.
		`Options for LDAP: {domain_name=` `domain_name` `profile=profile_nameprofile_server=` `ip_address`}	`name_service=LDAP {domain_name=west.arp.com profile=default profile_server=129.221.2.1}`
Network interface, host name, Internet Protocol (IP) address, netmask, DHCP, IPv6	All	`network_interface=NONE, PRIMARY, or value` where: NONE turns networking off PRIMARY is the first up, non-loopback interface found on the system. The order is the same as with "ifconfig." If no interfaces are up, then the first non-loopback interface is used. If no non-loopback interfaces are found, then the system is set to NON-NETWORKED. `value` specifies an interface such as le0 or hme0
		If DHCP is to be used, specify: `{dhcp protocol_ipv6=yes_or_no }`	`network_interface=primary {dhcp protocol_ipv6=yes}`
		If DHCP is not to be used, specify: `{hostname=host_name default_route=ip_address ip_address=ip_address netmask= netmask protocol_ipv6=yes_or_no}`	`network_interface=le0 {hostname=feron default_route=129.146.88.1 ip_address=129.146.88.210 netmask=255.255.0.0 protocol_ipv6=no}` Note: Choose only one value for `network_interface`. Include any combination or none of the `hostname`, `ip_address`, and `netmask` keywords, as needed. If you do not use any of these keywords, omit the curly braces ({}). Note: If you do not use DHCP, you do not need to specify `protocol_ipv6` and `default_route`. But, a JumpStart installation requires `protocol_ipv6` to be specified now or you will be prompted interactively later.
Root password	All	`root_password=root_password`	Encrypted from `/etc/shadow`.
Security policy	All	`security_policy=kerberos, NONE` Options for Kerberos: `{default_realm=FQDN admin_server=FQDN kdc=FQDN1, FQDN2, FQDN3}` where `FQDN` is a fully qualified domain name.	security_policy=kerberos {default_realm=Yoursite.COM admin_server=krbadmin.Yoursite.COM kdc=kdc1.Yoursite.COM, kdc2.Yoursite.COM} Note: You can list a maximum of three key distribution centers (KDCs), but at least one is required.
Language in which to display the install program and desktop	All	`system_locale=locale`	The `/usr/lib/locale` directory
Terminal type	All	`terminal=terminal_type`	The subdirectories in the `/usr/share/lib/terminfo` directory provide the valid terminal values.
Time zone	All	`timezone=timezone`	The directories and files in the `/usr/share/lib/zoneinfo` directory provide the valid time zone values. The time zone value is the name of the path relative to the `/usr/share/lib/zoneinfo` directory. For example, the time zone value for mountain standard time in the United States is `US/Mountain`. The time zone value for Japan is `Japan` . You can also specify any valid Olson time zone.
Date and time	All	`timeserver=localhost, hostname , ip_addr`	If you specify `localhost` as the time server, the system's time is assumed to be correct. If you are not running a name service and you specify the `hostname` or `ip_addr` of a system, that system's time is used to set the time.
Monitor type	IA	`monitor=monitor_type`	On the system you want to install, run `kdmconfig -d filename`. Append output to `sysidcfg` file.
Keyboard language, keyboard layout	IA	`keyboard=keyboard_language {layout=value}`	On the system you want to install, run `kdmconfig -d filename`. Append output to `sysidcfg` file.
Graphics card, screen size, color depth, display resolution	IA	`display=graphics_card {size= screen_size depth=color_depth resolution=screen_resolution }`	On the system you want to install, run `kdmconfig -d filename`. Append output to `sysidcfg` file.
Pointing device, number of buttons, IRQ level	IA	`pointer=pointing_device {nbuttons= number_buttons irq=value}`	On the system you want to install, run `kdmconfig -d filename`. Append output to `sysidcfg` file.

SPARC: Example `sysidcfg` File

The following is an example of a sysidcfg file for a group of SPARC based systems. The host names, IP addresses, and netmask of these systems have been preconfigured by editing the name service. Because all of the system configuration information is preconfigured in this file, you can use a custom JumpStart profile to perform a custom JumpStart installation.

system_locale=en_US timezone=US/Central terminal=sun-cmd timeserver=localhost name_service=NIS {domain_name=marquee.central.sun.com  name_server=connor(129.152.112.3)} root_password=m4QPOWNY

IA: Example `sysidcfg` File

The following is an example of a sysidcfg file for a group of IA based systems that all use the same type of keyboard, graphics cards, and pointing devices. The device information (keyboard, display, and pointer ) was obtained by running the kdmconfig(1M) command with the -d option. If the following example sysidcfg file is used, a prompt that asks you to select a language (system_locale) is displayed before installation can proceed.

keyboard=ATKBD {layout=US-English} display=ati {size=15-inch} pointer=MS-S timezone=US/Central timeserver=connor terminal=ibm-pc name_service=NIS {domain_name=marquee.central.sun.com  name_server=connor(129.152.112.3)} root_password=URFUni9

rules (sun)

Jerome ROBERT — 2008-09-17T17:23:58Z

Probe Keywords and Values

Note :

Always place probe keywords at or near the beginning of the
rules
file.

**Table 41 - Descriptions of Probe Keywords**
Rule Keyword	Equivalent Probe Keyword	Description of Probe Keyword
`any`	None
`arch`	`arch`	Determines the kernel architecture, i386 or SPARC, and sets `SI_ARCH`.
`disksize`	`disks`	Returns the size of a system's disks in Mbytes in kernel probe order, c0t3d0s0, c0t3d0s1, c0t4d0s0. `disksize` sets `SI_DISKLIST`, `SI_DISKSIZES`, `SI_NUMDISKS`, and `SI_TOTALDISK`.
`domainname`	`domainname`	Returns a system's NIS or NIS+ domain name or blank and sets `SI_DOMAINNAME`. The `dmainname` keyword returns the output of domainname(1M)).
`hostaddress`	`hostaddress`	Returns a system's IP address, the first address that is listed in the output of ifconfig(1M) `-a` that is not lo0, and sets `SI_HOSTADDRESS`.
`hostname`	`hostname`	Returns a system's host name that is the (output from uname(1) `-n` and sets `SI_HOSTNAME`.
`installed`	`installed`	Returns the version name of the Solaris operating environment that is installed on a system and sets `SI_ROOTDISK` and `SI_INSTALLED`. If the JumpStart program finds a Solaris release but is unable to determine the version, the version that is returned is `SystemV`.
`karch`	`karch`	Returns a system's platform group, for example i86pc, sun4m, and sun4, and sets `SI_KARCH`. For a list of platform names, see Solaris 8 Sun Hardware Platform Guide.
`memsize`	`memsize`	Returns the size of physical memory on a system in Mbytes and sets `SI_MEMSIZE`.
`model`	`model`	Returns a system's platform name and sets `SI_MODEL`. For a list of platform names., see the Solaris 8 Sun Hardware Platform Guide.
`network`	`network`	Returns a system's network number, which the JumpStart program determines by performing a logical AND between the system's IP address and the subnet mask. The system's IP address and the subnet mask are extracted from the first address that listed in the output of ifconfig(1M) `-a` that is not lo0. The `network` keyword sets `SI_NETWORK`.
`osname`	`osname`	Returns the version and operating system name of the Solaris operating environment that is found on a CD and sets `SI_OSNAME`. If the JumpStart program finds a Solaris release but is unable to determine the version, the version that is returned is `SystemV`.
	`rootdisk`	Returns the name and size in Mbytes of a system's root disk and sets `SI_ROOTDISK`.
`totaldisk`	`totaldisk`	Returns the total disk space on a system (in Mbytes and sets `SI_TOTALDISK`. The total disk space includes all of the operational disks that are attached to a system.

Rule Keywords and Values

Keyword

Value

Matches

any

minus sign (-)

Anything. The any keyword always succeeds.

arch

processor_type

Valid values for processor_type are the following :

SPARC : sparc
IA : i386

A system's
processor type.

The uname -p command reports
the system's processor type.

disksize

actual_disk_name size_range

actual_disk_name - A disk name in the form cxtydz, such as c0t3d0
or c0d0, or the special word rootdisk.
If rootdisk is used, the disk to be matched is determined
in the following order :

SPARC : The disk that contains the preinstalled boot image,
which is a new SPARC based system with factory JumpStart installed
The c0t3d0s0 disk, if the disk exists
The first available disk (searched in kernel probe order)

size_range - The size of the
disk, which must be specified as a range of Mbytes (x-x).

The
name and size of a system's disk in Mbytes.

Example :

 disksize c0t3d0 250-300

In the
example, the JumpStart program attempts to match a system disk that is named c0t3d0. The disk can hold between 250 and 300 Mbytes of information.

Example :

 disksize rootdisk 750-1000

In the example, the JumpStart program first
attempts to match a system disk that contains a preinstalled boot image. Next,
the JumpStart program attempts to match the c0t3d0s0 disk,
if the disk exists. Finally, the JumpStart program attempts to match the first
available disk that can hold between 750 Mbytes and 1 Gbyte of information.

Note :

When calculating size_range,
remember that a Mbyte equals 1,048,576 bytes. A disk might be advertised as
a "535-Mbyte" disk, but the disk might contain only 510
million bytes of disk space. The JumpStart program views the "535-Mbyte"
disk as a 510-Mbyte disk because 535,000,000 / 1,048,576 = 510. A "535-Mbyte"
disk does not match a size_range equal to 530-550.

domainname

actual_domain_name

A system's domain name, which controls
how a name service determines information.

If you have a system
already installed, the domainname command reports the system's
domain name.

hostaddress

actual_IP_address

A system's IP address.

hostname

actual_host_name

A system's host name.

If you have a system that is already installed, the uname -n
command reports the system's host name.

installed

slice version

slice - A disk
slice name in the form cwtxdysz, such as c0t3d0s5, or the special words any or rootdisk. If any is used, the JumpStart program
attempts to match all of the system's disks in kernel probe order. If rootdisk is used, the disk to be matched is determined in the following
order :

SPARC : The disk that contains the preinstalled boot image,
which is a new SPARC based system with factory JumpStart installed
The c0t3d0s0 disk, if the disk exists
The first available disk searched in kernel probe order

version - A version name or
the special words any or upgrade. If any is used, any Solaris or SunOS release is matched. If upgrade is used, any Solaris 2.1 or compatible release that can
be upgraded is matched.

If the JumpStart program finds a Solaris
release but is unable to determine the version, the version that is returned
is SystemV.

A disk that has a root (/) file system that corresponds
to a particular version of Solaris software.

Example :

 installed c0t3d0s1 Solaris_9

In the example, the JumpStart program attempts to match a system that has
a Solaris 8 root (/) file system on c0t3d0s1.

karch

actual_platform_group

Valid values are sun4m, sun4u, i86pc, prep. A list
of systems and their corresponding platform group is presented in the Solaris 8 Sun Hardware Platform Guide.

A system's platform group.

If you have a system
that is already installed, the arch -k command or the uname -m command reports the system's platform group.

memsize

physical_mem

The
value must be a range of Mbytes , x-x, or a single Mbyte value.

A system's physical memory size in Mbytes.

Example :

 memsize 16-32

The example tries to match a system with a physical memory size between 16
and 32 Mbytes.

If you have a system that is already installed,
the output of the prtconf command, line 2, reports the
system's physical memory size.

model

actual_platform_name

A system's platform name. See the Solaris 8 Sun Hardware Platform Guide for a list of valid platform
names.

To find the platform name of an installed system, use the uname -i command or the output of the prtconf
command, line 5.

Note :

If the actual_platform_name contains spaces, you must replace spaces with underscores (_).

Example :

SUNW,Sun_4_50

network

network_num

A system's network number, which the
JumpStart program determines by performing a logical AND between the system's
IP address and the subnet mask.

Example :

 network 193.144.2.8

The example tries to match
a system with a 193.144.2.8 IP address, if the subnet mask is 255.255.255.0.

osname

Solaris_2.x

A version of Solaris software already installed on a system.

Example :

 osname Solaris_7

In the example, the JumpStart program attempts to match a system with the
Solaris 7 operating environment already installed.

probe

probe_keyword

A valid probe keyword or a valid custom
probe keyword.

Example :

 probe disks

The example returns the size of a system's disks
in Mbytes and in kernel probe order, for example, c0t3d0s1, c0t4d0s0, on a SPARC system. The JumpStart program sets the SI_DISKLIST, SI_DISKSIZES, SI_NUMDISKS,
and SI_TOTALDISK environment variables.

Note :

The probe keyword is unique in that the keyword does not
attempt to match an attribute and run a profile. The probe
keyword returns a value. Consequently, you cannot specify begin scripts, profiles,
and finish scripts with the probe rule keyword.

totaldisk

size_range

The value must be specified as a range of Mbytes (x-x).

The
total disk space on a system in Mbytes. The total disk space includes all
the operational disks that are attached to a system.

Example :

 totaldisk 300-500

In the example,
the JumpStart program tries to match a system with a total disk space between
300 and 500 Mbytes.

Note :

When calculating size_range, remember that one Mbyte equals 1,048,576 bytes. A disk might
be advertised as a "535-Mbyte" disk, but the disk might
have only 510 million bytes of disk space. The JumpStart program views the "535-Mbyte"
disk as a 510-Mbyte disk because 535,000,000 / 1,048,576 = 510. A "535-Mbyte"
disk does not match a size_range equal to 530-550.

classe (sun)

Jerome ROBERT — 2008-09-17T17:23:17Z

Creating a Profile

A profile is a text file that defines how to install the Solaris software
on a system. A profile defines elements of the installation, for example,
the software group to install. Every rule specifies a profile that defines
how a system is to be installed. You can create different profiles for every
rule or the same profile can be used in more than one rule.

A profile consists of one or more profile keywords and their values.
Each profile keyword is a command that controls one aspect of how the JumpStart
program is to install the Solaris software on a system. For example, the following
profile keyword and value specify that the JumpStart program install the system
as a server :


 system_type server

Note :

If you created the JumpStart directory by using the procedures
that are presented in Creating a Profile Server for Networked Systems or Creating a Profile Diskette for Standalone Systems,
sample profiles are already located in the JumpStart directory.

Syntax of Profiles

A profile must contain the following :

The install_type profile keyword as the
first entry
One keyword per line
The root_device keyword if the systems
that are being upgraded by the profile contain more than one root (/) file system that can be upgraded

A profile can contain the following :

Commented text

Any text that is included after the # symbol on a
line is treated by the JumpStart program as commented text. If a line begins
with the # symbol, the entire line is treated as a comment.
One or more blank lines

To Create a Profile

Use a text editor to create a text file. Name the file descriptively.
Or, open a sample profile in the JumpStart directory that you created.

Note :
Ensure that the name of the profile reflects how you intend to
use the profile to install the Solaris software on a system. For example,
you might name the profiles basic_install, eng_profile, or user_profile.

Add profile keywords and values to the profile.

For a list of profile keywords and values, see Profile Keywords and Values.

Note :
Profile keywords and their values are case sensitive.

Save the profile in the JumpStart directory.

Ensure that root owns the profile and that the permissions
are set to 644.

Test the profile (optional).

Testing a Profile contains information about testing
profiles.

Profile Examples

The following examples of profiles show how to use different profile
keywords and profile values to control how the Solaris software is installed
on a system. Profile Keywords and Values contains a description of
profile keywords and values.

Example 16 - Mounting Remote File Systems and Adding and Deleting Packages


 # profile keywords profile values # ----------------- ----------------- install_type initial_install¹ system_type standalone² partitioning default³ filesys any 512 swap # specify size of /swap cluster SUNWCprog⁴ package SUNWman delete⁵ package SUNWolman delete package SUNWxwman delete package SUNWoldem add package SUNWxwdem add package SUNWoldim add package SUNWxwdim add

The install_type keyword is required in
every profile.
The system_type keyword defines that the
system is to be installed as a standalone system.
The file system slices are determined by the software to be
installed with the value default. The size of swap is set to 512 Mbytes and is installed on any disk, value any. The standard man pages are mounted from the file server, s_ref, on the network.
The Developer System Support software group, SUNWCprog, is installed on the system.
Because the man pages are being mounted remotely, the man
page packages are not to be installed on the system. The packages that contain
the OPEN LOOK and X Window System demonstration programs and images are selected
to be installed on the system.

Example 17 - Specifying Where to Install File Systems


 # profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone partitioning explicit¹ filesys c0t0d0s0 auto / filesys c0t3d0s1 auto swap filesys any auto usr cluster SUNWCall²

The file system slices are determined by the filesys keywords, value explicit. The size of root
(/) is based on the selected software, value auto, and is installed on c0t0d0s0. The size
of swap is set to the necessary size and is installed
on c0t3d0s1. usr is based on the selected
software and the installation program determines where usr
is installed, based on the value any.
The Entire Distribution software group, SUNWCall, is installed on the system.

Example 18 - IA : Using the `fdisk` Keyword


 # profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone fdisk c0t0d0 0x04 delete¹ fdisk c0t0d0 solaris maxfree² cluster SUNWCall³ cluster SUNWCacc delete⁴

All fdisk partitions of type DOSOS16 (04
hexadecimal) are deleted from the c0t0d0 disk.
A Solaris fdisk partition is created on
the largest contiguous free space on the c0t0d0 disk.
The Entire Distribution software group, SUNWCall, is installed on the system.
The system accounting utilities, SUNWCacc,
are not to be installed on the system.

Example 19 - Reallocating Disk Space for an Upgrade


 # profile keywords profile values # ---------------- ------------------- install_type upgrade¹ root_device c0t3d0s2² backup_media remote_filesystem timber:/export/scratch³ layout_constraint c0t3d0s2 changeable 100⁴ layout_constraint c0t3d0s4 changeable layout_constraint c0t3d0s5 movable package SUNWbcp delete⁵ package SUNWolman add⁶ package SUNWxwman add cluster SUNWCumux add locale de⁷

The profile upgrades a system by reallocating disk space.
In this example, disk space must be reallocated because some file systems
on the system did not have enough room for the upgrade.
The root file system on c0t3d0s2 is upgraded.
A remote system that is named timber is
to be used to back up data during the disk space reallocation.
The layout_constraint keywords designate
that auto-layout can perform the following when auto-layout attempts to reallocate
disk space for the upgrade.
- Change slices 2 and 4. The slices can be moved to another
  location and the size can be changed.
- Move slice 5. The slice can be moved to another location but
  its size must stay the same.
The binary compatibility package, SUNWbcp,
is not installed on the system after the upgrade.
The code ensures that the OPEN LOOK and X Window System man
pages and the universal multiplexor software are to be installed if they are
not already installed on the system. All packages already on the system are
automatically upgraded.
The German localization packages are to be installed on the
system.

Rubrique suivante

Testing a Profile

Profile Keywords at a Glance

Table 37 provides a quick way to determine
which keywords you can use based on your installation scenario. Unless otherwise
noted in the keyword descriptions, the keyword can only be used with the initial
installation option.

**Table 37 - Overview of Profile Keywords**
	Installation Scenarios
Profile Keywords	Standalone System (Non-Networked)	Standalone System (Networked) or Server	OS Server	Upgrade	Upgrade With Disk Space Reallocation
`archive_location`	[x]	[x]
`backup_media`					[x]
`boot_device`	[x]	[x]	[x]
`client_arch`			[x]
`client_root`			[x]
`client_swap`			[x]
`cluster` (adding software groups)	[x]	[x]	[x]
`cluster` (adding or deleting clusters)	[x]	[x]	[x]	[x]	[x]
`dontuse`	[x]	[x]	[x]
`fdisk` (IA only)	[x]	[x]	[x]
`filesys` (mounting remote file systems)		[x]	[x]
`filesys` (creating local file systems)	[x]	[x]	[x]
`geo`	[x]	[x]	[x]	[x]	[x]
`install_type`	[x]	[x]	[x]	[x]	[x]
`isa_bits`	[x]	[x]	[x]	[x]	[x]
`layout_constraint`					[x]
`locale`	[x]	[x]	[x]	[x]	[x]
`num_clients`			[x]
`package`	[x]	[x]	[x]	[x]	[x]
`partitioning`	[x]	[x]	[x]
`root_device`	[x]	[x]	[x]	[x]	[x]
`system_type`	[x]	[x]	[x]
`usedisk`	[x]	[x]	[x]

Rubrique suivante

Profile Keyword Descriptions and Examples

`archive_location` Keyword


 archive_location retrieval_type location

The values of retrieval_type and location depend on where the Web Start Flash archive is stored.
The following sections contain the values you can use for retrieval_type and location and examples of how
to use the archive_location keyword.

NFS Server

If the archive is stored on an NFS server, use the following syntax
for the archive_location keyword.


 archive_location nfs server_name:/path/filename retry n

Valid `retrieval_type` Values	Valid `location` Values	Specifies
`nfs`	`server_name :/path/filename retry n`	`server_name` is the name of the server where you stored the archive. `path` is the location of the archive to be retrieved from the specified server. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing. `filename` is the name of the Web Start Flash archive file. `retry n` is an optional keyword. `n` is the maximum number of times the Web Start Flash utilities attempt to mount the archive.

Examples :

archive_location nfs golden:/archives/usrarchive archive_location nfs://golden/archives/usrarchive

HTTP Server

If the archive is stored on an HTTP server, use the following syntax
for the archive_location keyword.


 archive_location http server_name:port path/filename optional_keywords

Valid `retrieval_type` Values	Valid `location` Values	Specifies
`http`	`server_name:port path/filename` `optional_keywords`	`server_name` is the name of the server where you stored the archive. `server_name` can be a port number or the name of a TCP service that has a port number that is determined at runtime. `port` is an optional port. If you do not specify a port, the Web Start Flash installation utilities use the default HTTP port number, 80. `path` is the location of the archive to be retrieved from the specified server. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing. `filename` is the name of the Web Start Flash archive file. `optional_keywords` are the optional keywords that you can specify when you retrieve a Web Start Flash archive from an HTTP server.

**Table 38 - Optional Keywords to Use With `archive_location http`**
Keywords	Value Definitions
`auth basic` `user_name password`	If the archive is located on an HTTP server that is password protected, you must include the user name and password that you need to access the HTTP server in the profile file. Note : The use of this authentication method in a profile that is intended for use with custom JumpStart is risky. Unauthorized users might have access to the profile file that contains the password.
`timeout` `min`	The `timeout` keyword enables you to specify, in minutes, the maximum length of time that is allowed to pass without receipt of data from the HTTP server before the connection is closed, reopened, and resumed from the point where the timeout occurred. If you specify a `timeout` value of 0 (zero), the connection is not reopened because of inactivity. If a time-out reconnection occurs, the Web Start Flash installation utilities attempt to resume the installation at the last known position in the archive. If the Web Start Flash installation utilities cannot resume the installation at the last known position, the retrieval restarts from the beginning of the archive and the data that was retrieved prior to the timeout is discarded.
`proxy` `host:port`	The `proxy` keyword allows you to specify a proxy host and proxy port. You can use a proxy host to retrieve a Web Start Flash archive from the other side of a firewall. You must supply a proxy port when you specify the `proxy` keyword.

Examples :

archive_location http silver /archives/usrarchive auth basic user1 secret timeout 5 archive_location http silver /archives/usrarchive auth basic user1 secret timeout 5

Local Tape

If the archive is stored on a tape, use the following syntax for the archive_location keyword.


 archive_location local_tape device  position

Valid `retrieval_type` Values	Valid `location` Values	Specifies
`local_tape`	`device` `position`	`device` is the name of the tape drive where you stored the Web Start Flash archive. If the device name is a canonical path, the Web Start Flash installation utilities retrieve the archive from the path to the device node. If you supply a device name that is not a canonical path, the Web Start Flash installation utilities add `/dev/rmt/` to the path. `position` designates the place on the tape drive where you saved the archive. If you do not supply a position, the Web Start Flash installation utilities retrieve the archive from the current position on the tape drive. By specifying a `position`, you can place a begin script or a `sysidcfg` file on the tape drive before the archive.

Examples :

archive_location local_tape /dev/rmt/0n 5 archive_location local_tape 0n 5

Local Device

You can retrieve a Web Start Flash archive from a local device if
you stored the Web Start Flash archive on a file system-oriented, random-access
device, such as a diskette or a CD-ROM. Use the following syntax for the archive_location keyword.

Note :

You can retrieve an archive from stream-oriented devices, such
as tape, by using the syntax for local tape.


 archive_location local_device device path/filename file_system_type

Valid `retrieval_type` Values	Valid `location` Values	Specifies
`local_device`	`device` `path/filename` `file_system_type`	`device` is the name of the drive where you stored the Web Start Flash archive. If the device name is a canonical path, the device is mounted directly. If you supply a device name that is not a canonical path, the Web Start Flash installation utilities add `/dev/dsk/` to the path. `path` is the path to the Web Start Flash archive, relative to the root of the file system on the device you specified. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing. `filename` is the name of the Web Start Flash archive file. `file_system_type` specifies the type of file system on the device. If you do not supply a file system type, the Web Start Flash installation utilities attempt to mount a UFS file system. If the UFS mount fails, the Web Start Flash installation utilities attempt to mount an HSFS file system.

Examples :

To retrieve an archive from a local hard drive that is formatted as
a UFS file system, use the following command :

archive_location local_device c0t0d0s0 /archives/$HOST

To retrieve an archive from a local CD-ROM that has an HSFS file system,
use the following command :

archive_location local_device c0t0d0s0 /archives/usrarchive

Local File

You can retrieve an archive that you stored in the miniroot from which
you booted the clone system as a local file. When you perform a custom JumpStart
installation, you boot the system from a CD-ROM or an NFS-based miniroot.
The installation software is loaded and run from this miniroot. Therefore,
a Web Start Flash archive that you stored in the CD-ROM or NFS-based miniroot
is accessible as a local file. Use the following syntax for the archive_location keyword.


 archive_location local_file path/filename

Valid `retrieval_type` Values	Valid `location` Values	Specifies
`local_file`	`path/filename`	`path` is the location of the archive. The path must be accessible to the system as a local file while the system is booted from the Solaris 8 Installation CD or from the Solaris 8 DVD. The system cannot access `/net` when it is booted from the Solaris 8 Installation CD or from the Solaris 8 DVD. `filename` is the name of the Web Start Flash archive file.

Examples :

archive_location local_file /archives/usrarchive archive_location local_file /archives/usrarchive

`backup_media` Profile Keyword


 backup_media type path

Note :

You can use backup_media only with the upgrade
option when disk space reallocation is required.

backup_media defines the media that is to be used
to back up file systems if space needs to be reallocated during an upgrade
because of a lack of space. If multiple tapes or diskettes are required for
the backup, you are prompted to insert tapes or diskettes during the upgrade.

Valid `type` Values	Valid `path` Values	Specifies
`local_tape`	`/dev/rmt/n`	A local tape drive on the system that is being upgraded. `path` must be the character (raw) device path for the tape drive, where `n` is the number of the tape drive.
`local_diskette`	`/dev/rdisketten`	A local diskette drive on the system that is being upgraded. `path` must be the character (raw) device path for the diskette drive, where `n` is the number of the diskette drive. Diskettes that you use for the backup must be formatted.
`local_filesystem`	`/dev/dsk/cwtxdysz` `/file_system`	A local file system on the system that is being upgraded. You cannot specify a local file system that is being changed by the upgrade. `path` can be a block device path for a disk slice. For example, the `tx` in `/dev/dsk/cwtxdysz` might not be needed. Or, `path` can be the absolute path to a file system mounted by the `/etc/vfstab` file.
`remote_filesystem`	`host` `:/file_system`	An NFS file system on a remote system. `path` must include the name or IP address of the remote system, `host`, and the absolute path to the NFS file system, `file_system`. The NFS file system must have read/write access.
`remote_system`	`user@host` `:/directory`	A directory on a remote system that can be reached by a remote shell, `rsh`. The system that is being upgraded must have access to the remote system through the remote system's `.rhosts` file. `path` must include the name of the remote system `host` and the absolute path to the directory `directory`. If a user login ID `user` is not specified, `root` is used by default.

Examples :

backup_media local_tape /dev/rmt/0 backup_media local_diskette /dev/rdiskette1 backup_media local_filesystem /dev/dsk/c0t3d0s4 backup_media local_filesystem /export backup_media remote_filesystem system1:/export/temp backup_media remote_system user1@system1:/export/temp

`boot_device` Profile Keyword


 boot_device device eeprom

boot_device designates the device where the JumpStart
program is to install the root (/) file system and the
system's boot device.

If you do not specify the boot_device keyword in
a profile, the following boot_device keyword is specified
by default during the installation : boot_device any update.

device - Use one of the following values.

SPARC : cwtxdysz or cxdysz - The
disk slice where the JumpStart program places the root (/)
file system, for example, c0t0d0s0.
IA : cwtxdy or cxdy - The disk where the JumpStart
program places the root (/) file system, for example, c0d0.
existing - The JumpStart program
places the root (/) file system on the system's existing
boot device.
any - The JumpStart program chooses
where to place the root (/) file system. The JumpStart
program attempts to use the system's existing boot device. The JumpStart program
might choose a different boot device if necessary.

eeprom - Choose to update or preserve
the system's EEPROM.

Choose if you want to update or preserve the system's EEPROM
to the specified boot device.

You must specify the preserve value.

update - The JumpStart program updates
the system's EEPROM to the specified boot device so that the installed system
automatically boots from it.
preserve - The boot device value
in the system's EEPROM is not changed. If you specify a new boot device without
changing the system's EEPROM, you need to change the system's EEPROM manually
so it can automatically boot from the new boot device.

Note SPARC :

On SPARC systems, the eeprom
value also allows you to update the system's EEPROM if you change the system's
current boot device. By updating the system's EEPROM, the system can automatically
boot from the new boot device.

Example :

boot_device c0t0d0s2 update

Note :

boot_device must match any filesys keywords that specify the root (/) file system
and the root_device keyword, if specified.

`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, sun4u, and i86pc. For
a detailed list of platform names and various systems, see Solaris
8 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, 512 Mbytes
of swap space is allocated by default.

Example :

client_swap 512

The example specifies that each diskless client is to have a swap space
of 512 Mbytes.

Note :

You can use client_swap only when system_type is specified as server.

`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 System Support	`SUNWCuser`
Developer System Support	`SUNWCprog`
Entire Distribution	`SUNWCall`
Entire Distribution 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 or cydz, for example, c0t0d0.

Note :

You cannot specify the dontuse keyword and
the usedisk keyword in the same profile.

IA : `fdisk` Profile Keyword


 fdisk disk_name type size

fdisk defines how the fdisk partitions
are set up on an IA based system. You can specify fdisk
more than once. When fdisk partitions an IA based system,
the following occurs :

All fdisk partitions on the disk are preserved,
unless you delete the partitions with the fdisk keyword,
by assigning size the value of delete or 0. Also, all existing fdisk
partitions are deleted when size is set to all.
A Solaris fdisk partition that contains
a root (/) file system is always designated as the active
partition on the disk.

Note IA :
The system boots from the active partition by default.
If the fdisk keyword is not specified in
a profile, the following fdisk keyword is used by default
during the installation :
```
fdisk all solaris maxfree
```
fdisk entries are processed in the order
in which the entries are listed in the profile.

disk_name - Use the following values
to specify where the fdisk partition is to be created or
deleted :

cxtydz or cydz - A specific disk, for example, c0t3d0.
rootdisk - The variable that contains the
value of the system's root disk, which is determined by the JumpStart program
as described in How the System's Root Disk Is Determined.
all - All the selected disks.

type - Use the following values to
specify the type of fdisk partition that is to be created
or deleted on the specified disk :

solaris - A Solaris fdisk partition (SUNIXOS fdisk type).
dosprimary - An alias for primary
DOS fdisk partitions, not for fdisk
paritions that are extended or reserved for data DOS. When youe delete fdisk partitions by assigning size the
value delete, dosprimary is an alias
for the DOSHUGE, DOSOS12, and DOSOS16 fdisk types. When
you create an fdisk partition, dosprimary
is an alias for the DOSHUGE fdisk partition.
DDD - An integer fdisk partition. DDD is an integer between
1 and 255 inclusive.

Note IA :
You can specify this value only if size is delete.
0xHH - A hexadecimal fdisk partition. HH is a hexadecimal
number between 01 and FF.

Note IA :
You can specify this value only if size is delete.

The following table shows the integer and hexadecimal numbers for some
of the fdisk types.

`fdisk` Type	`DDD`	`HH`
DOSOS12	`1`	`01`
PCIXOS	`2`	`02`
DOSOS16	`4`	`04`
EXTDOS	`5`	`05`
DOSHUGE	`6`	`06`
DOSDATA	`86`	`56`
OTHEROS	`98`	`62`
UNIXOS	`99`	`63`

size - Use one of the following values :

DDD - An fdisk
partition of size DDD in Mbytes is created on the
specified disk. DDD must be an integer, and the
JumpStart program automatically rounds the number up to the nearest cylinder
boundary. Specifying a value of 0 is the same as specifying delete.
all - An fdisk
partition is created on the entire disk. All existing fdisk
partitions are deleted.

Note IA :
The all value can be specified only
if type is solaris.
maxfree - An fdisk
partition is created in the largest contiguous free space on the specified
disk. If an fdisk partition of the specified type already exists on the disk, the existing fdisk partition is used. A new fdisk partition is not created on the disk.

Note IA :
The disk must contain at least one unused fdisk partition. Also, the disk must have free space or installation
fails. The maxfree value can be specified only if type is solaris or dosprimary.
delete - All fdisk
partitions of the specified type are deleted on
the specified disk.

`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 or cxdysz - 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.

optional_parameters - Use one of the
following values :

preserve - The file system on the
specified slice is preserved.

Note :
preserve can be specified only when size is existing and slice
is cwtxdysz.
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, for example, ro,quota, for example.

`geo` Profile Keyword


 geo locale

Note :

You can use geo with both the initial installation
and upgrade options.

geo designates the regional locale or locales that
you want to install on a system or to add when upgrading a system. Values
you can specify for locale are listed in the following
table :

Value	Description
`N_Africa`	Northern Africa, including Egypt
`C_America`	Central America, including Costa Rica, El Salvador, Guatemala, Mexico, Nicaragua, Panama
`N_America`	North America, including Canada, United States
`S_America`	South America, including Argentina, Bolivia, Brazil, Chile, Colombia, Ecuador, Paraguay, Peru, Uruguay, Venezuela
`Asia`	Asia, including Japan, Republic of Korea, People's Republic of China, Taiwan, Thailand
`Ausi`	Australasia, including Australia, New Zealand
`C_Europe`	Central Europe, including Austria, Czech Republic, Germany, Hungary, Poland, Slovakia, Switzerland
`E_Europe`	Eastern Europe, including Albania, Bosnia, Bulgaria, Croatia, Estonia, Latvia, Lithuania, Macedonia, Romania, Russia, Serbia, Slovenia, Turkey
`N_Europe`	Northern Europe, including Denmark, Finland, Iceland, Norway, Sweden
`S_Europe`	Southern Europe, including Greece, Italy, Portugal, Spain
`W_Europe`	Western Europe, including Belgium, France, Great Britain, Ireland, Netherlands
`M_East`	Middle East, including Israel

A complete list of the component locale values that compose each regional
locale that is listed previously is presented in Chapter 38, Locale Values.

Note :

You can specify a geo keyword for each locale
you need to add to a system.

`install_type` Profile Keyword


 install_type initial_install_upgrade_switch

install_type defines whether to erase and install
a new Solaris operating environment on a system or upgrade the existing Solaris
environment on a system.

Note :

You must specify install_type in a profile,
and install_type must be the first profile keyword in every
profile.

initial_install_upgrade_switch represents
the option initial_install or upgrade,
which you use to indicate the type of installation to be performed.

You must specify initial_install_upgrade_switch.

Note :

Some profile keywords can only be used with the initial_install option. Some profile keywords can only be used with the upgrade option.

`isa_bits` Profile Keyword


 isa_bits bit_switch

isa_bits specifies whether 64-bit or 32-bit Solaris 8
packages are to be installed.

bit_switch represents the option 64 or 32, which you use to indicate whether 64-bit
or 32-bit Solaris 8 packages are to be installed. If you do not set
this keyword in the profile, the JumpStart program installs systems as follows :

64-bit packages on UltraSPARC^(TM) systems
32-bit packages on all other systems

Note :

If you use the isa_bits keyword, you must also
use the latest check script in the solaris_9/Misc/jumpstart_sample directory on the Solaris 8 Software 1 of 2 CD or on the Solaris 8 DVD.

`layout_constraint` Profile Keyword


 layout_constraint slice constraint [minimum_size]

Note :

You can use layout_constraint only for the
upgrade option when you need to reallocate disk space.

layout_constraint designates the constraint auto-layout
has on a file system if auto-layout needs to reallocate space during an upgrade
because of space problems.

If you do not
specify the layout_constraint keyword, the JumpStart program
lays out the disk as follows :

File systems that require more space for the upgrade are marked
changeable.
File systems that are on the same disk as the file system
that requires more space and that are mounted by the /etc/vfstab file are marked changeable.
Remaining file systems are marked fixed because auto-layout
cannot change the file systems.

If you specify one or more layout_constraint keywords,
the JumpStart program lays out the disk as follows :

File systems that require more space for the upgrade are marked
changeable.
File systems for which you specified a layout_constraint keyword are marked with the specified constraint.
The remaining file systems are marked fixed.

You cannot change the constraint on file systems that require more space
for the upgrade because the file systems must be marked changeable. You can
use the layout_constraint keyword to change the minimum_size values on file systems that require more space
for the upgrade.

Note :

To help auto-layout reallocate space, select more file systems
to be changeable or movable, especially those file systems that are located
on the same disks as the file systems that require more space for the upgrade.

slice - slice
specifies the file system's disk slice on which to specify the constraint.
You must specify the system's disk slice in the form cwtxdysz or cxdysz.

constraint - Use one the following
constraints for the specified file system :

changeable - Auto-layout can move
the file system to another location and it can change the file system size.
The changeable constraint can only be specified on file
systems that are mounted by the /etc/vfstab file. You
can change the file system's size by specifying the minimum_size value.

When you mark a file system as changeable and minimum_size is not specified, the file system's minimum size is set to
10 percent more than the minimum size that is required. For example, if the
minimum size for a file system is 100 Mbytes, the changed size is 110 Mbytes.
If minimum_size is specified, any free space that
remains, original size minus minimum size, is used for other file systems.
movable - Auto-layout can move the
file system to another slice on the same disk or different disk. The file
system size remains the same.
available - Auto-layout can use all
of the space on the file system to reallocate space. All of the data in the
file system is lost. The available constraint can only
be specified on file systems that are not mounted by the /etc/vfstab file.
collapse - Auto-layout moves and
collapses the specified file system into the parent file system. You can
use the collapse option to reduce the number of file systems
on a system as part of the upgrade. For example, if a system has the /usr and /usr/share file systems, collapsing
the /usr/share file system moves the file system into /usr, the parent file system. You can specify the collapse constraint only on file systems that are mounted by the /etc/vfstab file.

minimum_size - Specifies the size of
the file system after auto-layout reallocates space. The minimum_size option enables you to change the size of a file system. The
size of the file system might be larger if unallocated space is added to the
file system. But, the size is never less than the value you specify. The minimum_size value is optional. Use this value only if you have
marked a file system as changeable and the minimum size cannot be less than
what the file system needs for the existing file system contents.

Examples :

layout_constraint c0t3d0s1 changeable 200 layout_constraint c0d0s4 movable layout_constraint c0t3d1s3 available layout_constraint c0t2d0s1 collapse

`locale` Profile Keyword


 locale locale_name

Note :

You can use locale with both the initial installation
and upgrade options.

locale designates the locale packages you want to
install or add when upgrading for the specified locale_name.
The locale_name values are the same as those values
that are used for the $LANG environment variable. Chapter 38, Locale Valuescontains a list of valid locale values.

When you use the local keyword, consider the following :

If you have preconfigured a default locale, the locale is
automatically installed. The English language packages are installed by default.
You can specify a locale keyword for each
locale you need to add to a system.

`num_clients` Profile Keyword


 num_clients client_num

When a server is installed, space is allocated for each diskless client's
root (/) and swap file systems. num_clients defines the number of diskless clients, client_num, that a server supports. If you do not specify num_clients in the profile, five diskless clients are allocated
by default.

Note :

You can use num_clients only when system_type is specified as server.

`package` Profile Keyword


 package package_name [add_delete_switch]

Note :

You can use package with both the initial installation
and upgrade options.

package designates whether a package is to be added
to or deleted from the software group that is to be installed on the system.

You must specify package_name in the form SUNWname. To view detailed information
about packages and their names, on an installed system use the pkginfo – l command or Admintool. In Admintool, choose Software from the
Browse menu.

add_delete_switch represents the option add or delete, which you use to indicate whether
to add or delete the specified package. If you do not specify add_delete_switch, add is used by default.

When you use package for an upgrade, the JumpStart
program performs the following actions :

All packages already on the system are automatically upgraded.
If you specify package_name add and package_name is not installed
on the system, the package is installed.
If you specify package_name delete and package_name is installed
on the system, the package is deleted before the upgrade
begins.
If you specify package_name delete and package_name is not installed
on the system, the package is not installed if the package is part of a cluster
that is designated to be installed.

`partitioning` Profile Keyword


 partitioning type

partitioning defines how the disks are divided into
slices for file systems during the installation.

type - Use one of the following values :

default - The JumpStart program selects
the disks and creates the file systems on which to install the specified software,
except for any file systems that are specified by the filesys
keywords. rootdisk is selected first. The JumpStart program
uses additional disks if the specified software does not fit on rootdisk.
existing - The JumpStart program
uses the existing file systems on the system's disks. All file systems except /, /usr, /usr/openwin, /opt, and /var are preserved. The JumpStart
program uses the last mount point field from the file system superblock to
determine which file system mount point the slice represents.

Note :
When you use both the filesys and partitioning existing profile keywords, you must set size size to existing.
explicit - The JumpStart program
uses the disks and creates the file systems that are specified by the filesys keywords. If you specify only the root (/)
file system with the filesys keyword, all of the Solaris
software is installed in the root (/) file system.

Note :
If you use the explicit profile value, you
must use the filesys keyword to specify the disks to use
and file systems to create.

If you do not specify partitioning in the profile,
the default type of partitioning is used by default.

`root_device` Profile Keyword


 root_device slice

Note :

You can use root_device with both the initial
installation and upgrade options.

root_device designates the system's root disk. How the System's Root Disk Is Determined contains additional information.

When you are upgrading a system, root_device designates
the root (/) file system and the file systems that are
mounted by its /etc/vfstab file to be upgraded. You must
specify root_device if more than one root (/) file system can be upgraded on a system. You must specify slice in the form cwtxdysz or cxdysz.

Example :

root_device c0t0d0s2

When you use the root_device keyword, consider the
following :

If you specify root_device on a system
with only one disk, the root_device and the disk must match.
Also, any filesys keywords that specify the root (/) file system must match root_device.
If you are upgrading a mirror, the value specified for root_device should be one side of the mirror. The other side of
the mirror is automatically upgraded.

How the System's Root Disk Is Determined

A system's root disk is the disk on the system that contains the root
(/) file system. In a profile, you can use the rootdisk variable in place of a disk name, which the JumpStart program
sets to the system's root disk. Table 39 describes
how the JumpStart program determines the system's root disk for the installation.

Note :

The JumpStart program only determines a system's root disk size
during an initial installation. You cannot change a system's root disk during
an upgrade.

**Table 39 - How JumpStart Determines a System's Root Disk (Initial Installation)**
Stage	Action
1	If the `root_device` keyword is specified in the profile, the JumpStart program sets `rootdisk` to the root device.
2	If `rootdisk` is not set and the `boot_device` keyword is specified in the profile, the JumpStart program sets `rootdisk` to the boot device.
3	If `rootdisk` is not set and a `filesys cwtxdyszsize /` entry is specified in the profile, the JumpStart program sets `rootdisk` to the disk that is specified in the entry.
4	If `rootdisk` is not set and a `rootdisk.sn` entry is specified in the profile, the JumpStart program searches the system's disks in kernel probe order for an existing root file system on the specified slice. If a disk is found, the JumpStart program sets `rootdisk` to the found disk.
5	If `rootdisk` is not set and `partitioning existing` is specified in the profile, the JumpStart program searches the system's disks in kernel probe order for an existing root file system. If a root file system is not found or more than one is found, an error occurs. If a root file system is found, the JumpStart program sets `rootdisk` to the found disk.
6	If `rootdisk` is not set, the JumpStart program sets `rootdisk` to the disk where the root (`/`) file system is installed.

`system_type` Profile Keyword


 system_type type_switch

system_type defines the type of system on which the
Solaris environment is to be installed.

type_switch represents the option standalone or server, which you use to indicate
the type of system on which the Solaris software is to be installed. If you
do not specify system_type in a profile, standalone is used by default.

`usedisk` Profile Keyword


 usedisk disk_name ...

By default, the JumpStart program uses all of the operational disks
on the system when you specify partitioning default. The usedisk profile keyword designates one or more disks that you want
the JumpStart program to use. You must specify disk_name
in the form cxtydz or cydz, for example, c0t0d0 or c0d0s0.

If you specify usedisk in a profile, the JumpStart
program uses only the disks that you specify after the usedisk
keyword.

Note :

You cannot specify the usedisk keyword and
the dontuse keyword in the same profile.

Rubrique suivante

Custom JumpStart Environment Variables

Flash

Jerome ROBERT — 2008-09-17T17:22:19Z

Création d une image flash

La syntaxe de la commande flarcreate est la suivante :

flarcreate -n nom [-R racine] [-S] [-c] [-t] [-m syst._master] [-a
auteur] [-e descr] [-x exclude] archive

-n	Donne le nom de l'archive
-R	Donne la racine pour la création de l'archive
-S	Ne calcule pas la taille, conseil pour être plus rapide !!
-c	Compresse l'archive en utilisant la commande compress
-t	Crée l'archive sur une bande magnétique
-m	Spécifie le nom du système maître sur lequel vous stockez l'archive
-a	Donne l'auteur de l'archive
-e	Description de l'archive
-x	Exclut un répertoire de l'archive
archive	Spécifie le chemin contenant l'archive, conseil en absolu

L'exemple suivant montre la création d une Flash archive :

# flarcreate -n flash_systeme_archive -c -R / -e systeme_archive
– x /flash -a admin_operator flash_archive1

Attention :

N'oublier pas d'exporter le répertoire contenant les
archives.

Bienvenue sur le site admin-sys

Installation

Création du/des dépôt(s) :

Copie du cdrom 1/2 dans le dépôt :

Copie du cdrom 2/2 dans le dépôt :

Ajouter au fichier /etc/dfs/dfstab :

Ajout de client jumpstart

Configuration

Jumpstart:

Création d'un fichier sysidcfg :

Création du fichier rules:

Création du fichier calais_class:

Variables jumpstart:

sysidcfg (sun)

Mots clés pour sysidcfg:

Syntax Rules for the sysidcfg File

sysidcfg File Keywords

SPARC: Example sysidcfg File

IA: Example sysidcfg File

rules (sun)

Probe Keywords and Values

Rule Keywords and Values

classe (sun)

Creating a Profile

Syntax of Profiles

To Create a Profile

Profile Examples

Example 16 - Mounting Remote File Systems and Adding and Deleting Packages

Example 17 - Specifying Where to Install File Systems

Example 18 - IA : Using the fdisk Keyword

Example 19 - Reallocating Disk Space for an Upgrade

Rubrique suivante

Profile Keywords at a Glance

Rubrique suivante

Profile Keyword Descriptions and Examples

archive_location Keyword

NFS Server

HTTP Server

Local Tape

Local Device

Local File

backup_media Profile Keyword

boot_device Profile Keyword

client_arch Profile Keyword

client_root Profile Keyword

client_swap Profile Keyword

cluster Profile Keyword (Adding Software Groups)

cluster Profile Keyword (Adding or Deleting Clusters)

dontuse Profile Keyword

IA : fdisk Profile Keyword

filesys Profile Keyword (Mounting Remote File Systems)

filesys Profile Keyword (Creating Local File Systems)

geo Profile Keyword

install_type Profile Keyword

isa_bits Profile Keyword

layout_constraint Profile Keyword

locale Profile Keyword

num_clients Profile Keyword

package Profile Keyword

partitioning Profile Keyword

root_device Profile Keyword

How the System's Root Disk Is Determined

system_type Profile Keyword

usedisk Profile Keyword

Rubrique suivante

Flash

Création d une image flash

La syntaxe de la commande flarcreate est la suivante :

L'exemple suivant montre la création d une Flash archive :

Attention :

Syntax Rules for the `sysidcfg` File

`sysidcfg` File Keywords

SPARC: Example `sysidcfg` File

IA: Example `sysidcfg` File

Example 18 - IA : Using the `fdisk` Keyword

`archive_location` Keyword

`backup_media` Profile Keyword

`boot_device` Profile Keyword

`client_arch` Profile Keyword

`client_root` Profile Keyword

`client_swap` Profile Keyword

`cluster` Profile Keyword (Adding Software Groups)

`cluster` Profile Keyword (Adding or Deleting Clusters)

`dontuse` Profile Keyword

IA : `fdisk` Profile Keyword

`filesys` Profile Keyword (Mounting Remote File Systems)

`filesys` Profile Keyword (Creating Local File Systems)

`geo` Profile Keyword

`install_type` Profile Keyword

`isa_bits` Profile Keyword

`layout_constraint` Profile Keyword

`locale` Profile Keyword

`num_clients` Profile Keyword

`package` Profile Keyword

`partitioning` Profile Keyword

`root_device` Profile Keyword

`system_type` Profile Keyword

`usedisk` Profile Keyword