Preconfiguring With the Naming Service

The following table provides a high-level overview of the naming service databases that you need to edit and populate to preconfigure system information.

System Information to Preconfigure	Naming Service Database
Host name and Internet Protocol (IP) address	`hosts`
Date and time	`hosts`. Specify the `timehost` alias next to the host name of the system that will provide the date and time for the systems that are being installed.
Time zone	`timezone`
Netmask	`netmasks`

You cannot preconfigure the locale for a system with the DNS or LDAP name service. If you use the NIS or NIS+ name service, follow the procedure below to use your naming service to preconfigure the locale for a system.

Note - In order to successfully preconfigure your system locale by using NIS or NIS+, the following requirements must be met:

You must boot the system from the network by using the following command:
```
ok boot net
```
You can use options with this command. See details in Step 2 of theSPARC: To Install the Client Over the Network (DVD) procedure.
The NIS or NIS+ server must be available to access during the installation.

If these requirements are fulfilled, the installer uses the preconfigured settings and does not prompt for the locale during the installation. If either requirement is not fulfilled, the installer prompts for your locale information during the installation.

To Preconfigure the Locale Using NIS
To Preconfigure the Locale Using NIS+

To Preconfigure the Locale Using NIS

Become superuser or assume an equivalent role on the name server.

Change /var/yp/Makefile to add the locale map.

Insert this shell procedure after the last variable.time shell procedure.

locale.time:  $(DIR)/locale
        -@if [ -f $(DIR)/locale ]; then \
               sed -e "/^#/d" -e s/#.*$$// $(DIR)/locale \
               | awk '{for (i = 2; i<=NF; i++) print $$i, $$0}' \
               | $(MAKEDBM) - $(YPDBDIR)/$(DOM)/locale.byname; \
               touch locale.time; \
               echo "updated locale"; \
               if [ ! $(NOPUSH) ]; then \
                       $(YPPUSH) locale.byname; \
                       echo "pushed locale"; \
               else \
               : ; \
               fi \
        else \
               echo "couldn't find $(DIR)/locale"; \
        fi

Find the string all: and, at the end of the list of variables, insert the word locale.

all: passwd group hosts ethers networks rpc services protocols \
    netgroup bootparams aliases publickey netid netmasks c2secure \
    timezone auto.master auto.home locale

Near the end of the file, after the last entry of its type, insert the string locale: locale.time on a new line.

passwd: passwd.time
group: group.time
hosts: hosts.time
ethers: ethers.time
networks: networks.time
rpc: rpc.time
services: services.time
protocols: protocols.time
netgroup: netgroup.time
bootparams: bootparams.time
aliases: aliases.time
publickey: publickey.time
netid: netid.time
passwd.adjunct: passwd.adjunct.time
group.adjunct: group.adjunct.time
netmasks: netmasks.time
timezone: timezone.time
auto.master: auto.master.time
auto.home: auto.home.time
locale: locale.time

Save the file.

Create the file /etc/locale and make one entry for each domain or specific system:
- Enter locale domain_name.
  For example, the following entry specifies that French is the default language that is used in the example.com domain:
```
fr example.com
```
  Note - International Language Environments Guide contains a list of valid locales.
- Or, enter locale system_name.
  The following example specifies that Belgian French is the default locale that is used by a system named myhost:
```
fr_BE myhost
```
Note - Locales are available on the Solaris DVD or Solaris Software - 1 CD.
Make the maps:
```
# cd /var/yp; make
```
Systems that are specified by domain or individually in the locale map are now set up to use the default locale. The default locale that you specified is used during installation and by the desktop after the system is rebooted.

More Information

Continuing the Installation

If you plan to use the NIS name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 4, Installing From the Network (Overview).

If you plan to use the NIS name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, Custom JumpStart (Overview), in Solaris Express Installation Guide: Custom JumpStart and Advanced Installations.

To Preconfigure the Locale Using NIS+

The following procedure assumes the NIS+ domain is set up. Setting up the NIS+ domain is documented in the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Log in to a name server as superuser or as a user in the NIS+ administration group.

Create the locale table:

# nistbladm -D access=og=rmcd,nw=r -c locale_tbl name=SI,nogw=
locale=,nogw= comment=,nogw= locale.org_dir.`nisdefaults -d`

Add needed entries to the locale.
```
# nistbladm -a name=namelocale=locale comment=comment
locale.org_dir.`nisdefaults -d`
```
name

Either the domain name or a specific system name for which you want to preconfigure a default locale.

locale

The locale you want to install on the system and use on the desktop after the system is rebooted. International Language Environments Guide contains a list of valid locales.

comment

The comment field. Use double quotation marks to begin and end comments that are longer than one word.

Note - Locales are available on the Solaris DVD or Solaris Software - 1 CD.

Systems that are specified by domain or individually in the locale table are now set up to use the default locale. The default locale you specified is used during installation and by the desktop after the system is rebooted.

More Information

Continuing the Installation

If you plan to use the NIS+ name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 4, Installing From the Network (Overview).

If you plan to use the NIS+ name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, Custom JumpStart (Overview), in Solaris Express Installation Guide: Custom JumpStart and Advanced Installations.