man Pages(4): File Formats

sysidcfg(4)

NAME | DESCRIPTION | EXAMPLES | SEE ALSO

NAME

sysidcfg- system identification configuration file

DESCRIPTION

When a diskless client boots for the first time or a system installs over the network, the booting software tries to obtain configuration information about the system (such as the system's root password or name service) from a sysidcfg file first and then the name service databases. If the booting software cannot find the information, it prompts the user to provide the appropriate information. Like the name service databases, the sysidcfg file can be used to avoid all the prompts and provide a totally hands-off booting process.

The sysidcfg file preconfigures information through a set of keywords, and you can specify one or more of the keywords to preconfigure as much information as you want. Also, every system that requires different configuration information must have a different sysidcfg file. For example, you can use the same sysidcfg file to preconfigure the time zone for multiple systems if you want all the systems to have the same time zone configured. However, if you want to preconfigure a different root password for each of those systems, then each system would need its own sysidcfg file.

Where To Put the sysidcfg File

The sysidcfg file can reside on a shared NFS network directory or the root directory on a UFS or PCFS diskette in the system's diskette drive. If you put the sysidcfg file on a shared NFS network directory, you have to use the -p option of the add_install_client(1M) command (see install_scripts(1M)) to specify where the system being installed can find the sysidcfg file. If you put the sysidcfg file on a diskette, you need to make sure the diskette is in the system's diskette drive when the system boots (on x86 systems, the sysidcfg file should reside on the Solaris Device Configuration Assistant diskette).

Only one sysidcfg file can reside in a directory or diskette. If you are creating more than one sysidcfg file, they must reside in different directories or diskettes.

Keyword Syntax Rules

The following rules apply to the keywords in a sysidcfg file:

Keywords can be in any order
Keywords are not case sensitive
Keyword values can be optionally enclosed in single (') or double (") quotes
Only the first instance of a keyword is valid; if you specify the same keyword more than once, the first keyword specified will be used.

Keywords

`Platform`	`.nf Configuration Information`	`Keywords`	`Where to Find Values/Example`
All	.nf Name service, domain name, name server	.nf `name_service=NIS`, `NIS+`, `OTHER`, `NONE` `{domain_name=domain_name` `name_server=hostname(ip_address)}`	.nf `name_service=NIS` `{domain_name=chandy.West.Arp.COM name_server=timber(129.221.2.1)}`
All	.nf Network interface, host name, IP address, netmask	.nf `network_interface=NONE`, `PRIMARY`, `value` `{hostname=host_name` `ip_address=ip_address` `netmask=netmask}`	.nf `network_interface=le0 {hostname=feron` `ip_address=129.222.2.1 netmask=255.255.0.0}`
All	Root password	`root_password=root_password`	Encrypted from `/etc/shadow`
All	.nf Language in which to display the install program	`system_locale=locale`	`/usr/lib/locale`
All	Terminal type	`terminal=terminal_type`	`/usr/share/lib/terminfo/?/*`
All	Time zone	`timezone=timezone`	`/usr/share/lib/zoneinfo/*`
All	Time and date	.nf `timeserver=localhost,` `hostname,` `ip_address`	.nf If you specify `localhost` as the time server, the system's time is assumed to be correct. If you specify the `hostname` or `ip_address` (if you are not running a name service) of a system, that system's time is used to set the time.
x86	Monitor type	`monitor=monitor_type`	.nf Run `kdmconfig -d` `filename`; append output to `sysidcfg` file
x86	.nf Keyboard language, keyboard layout	.nf `keyboard=keyboard_language` `{layout=value}`	.nf Run `kdmconfig -d` `filename`; append output to `sysidcfg` file
x86	.nf Graphics card, color depth, display resolution, screen size	.nf `display=graphics_card` `{size=screen_size` `depth=color_depth` `resolution=screen_resolution}`	.nf Run `kdmconfig -d` `filename`; append output to `sysidcfg` file
x86	.nf Pointing device, number of buttons, IRQ level	.nf `pointer=pointing_device` `{nbuttons=number_buttons` `irq=value}`	.nf Run `kdmconfig -d` `filename`; append output to `sysidcfg` file

EXAMPLES

Example 1 Sample `sysidcfg` files.

The following example is a sysidcfg file for a group of SPARC systems to install over the network. (The host names, IP addresses, and netmask of these systems have been preconfigured by editing the name service.) Because all the system configuration information has been preconfigured, an automated installation can be created by using a custom JumpStart profile.

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

The following example is a sysidcfg file created for a group of x86 systems to install over the network that all have the same keyboard, graphics cards, and pointing devices. The device information (keyboard, display, and pointer) was captured from running kdmconfig -d (see kdmconfig(1M)). In this example, users would see only the prompt to select a language (system_locale) for displaying the rest of the Solaris installation program.

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