Skip to ContentSun and Oracle Channel Sun How to Buy Log In

SPARC: Installing Solaris Software

Содержащиеся в

Solaris 2.4 System Administrator AnswerBook

Найти другие документы

Ресурсы поддержки

Загрузить это руководство в формате PDF

Preparing to Install Solaris Over a Network

3

*How to Create an Install Server*	*page 25*
*How to Create a Boot Server on a Subnet*	*page 28*
*How to Set Up Servers for Network Installation of a Standalone, Server, or Dataless Client*	*page 31*
*How to Set Up Servers for Network Installation of a Diskless Client*	*page 41*
*How to Preconfigure Network Information*	*page 45*
*How to Preconfigure Default Locale Using NIS*	*page 48*
*How to Preconfigure Default Locale Using NIS+*	*page 51*

About Installing Solaris Over a Network

A typical way to install Solaris software is to use the installation program to copy the Solaris CD shipped with your system. However, it is uncommon at most sites for every system to have its own local CD-ROM drive. When a system does not have a local CD-ROM drive, you can perform a network installation. Network installation means that you install software over the network--from a system with a CD-ROM drive to a system without a CD-ROM drive.

Note - Instructions in this chapter are valid for either an x86 or SPARC server being used for network installations. An x86 server can provide the Solaris CD image for SPARC systems, and a SPARC server can provide the Solaris CD image for x86 systems.

Servers Required for Network Installation

As shown in Figure 3-1, systems that install Solaris software over the network require:

Install server - a networked system with the CD-ROM drive that provides installation services for other systems.
Name server - a system that manages a distributed network database (such as NIS or NIS+) containing information about users and other systems on the network.

Note - The install server and name server may be the same or separate systems.

Boot server - a system that boots the system to be installed over the network. A boot server and install server are typically the same system. However, if the system to be installed is on a different subnet than the install server, a boot server is required on that subnet.

Diskless and dataless clients also require:

File server - a system that provides files for other systems.

Figure 3-1

Requirements for Hands-Off Network Installation

To set up your site to install Solaris software on systems over the network with no user intervention, you must:

Use the custom JumpStart installation method. (See Chapter 4, "Preparing Custom JumpStart Installations.")
Make sure all systems are properly configured in the name service. (Procedures in this chapter include information on how to add systems to the name service.)
Preconfigure network information, such as the date, time, geographic region, site subnet mask, and language. (See "Preconfiguring Network Information" on page 45 for detailed information.) Doing so provides default values that the Solaris installation program can access, which eliminates many prompts to identify the system during an installation.

Files You Should Know About

Table 3-1 shows files that you may need to modify or monitor to set up a network installation.

Table 3-1

Files	Description
`/cdrom/cdrom0/s0`	File path of the mounted SPARC Solaris CD on a Solaris 2.x system. If more than one CD-ROM drive is attached to the system, the path may vary. (This mount point is created by Volume Management software.)
`/cdrom/cdrom0/s2`	File path of the mounted x86 Solaris CD on a Solaris 2.x system. If more than one CD-ROM drive is attached to the system, the path may vary. (This mount point is created by Volume Management software.)
`/etc/hosts` `/etc/ethers` `/etc/bootparams`	Files containing information necessary for exchanging information between systems on a network.
`/var/nis/`*host`/hosts.org_dir` `/var/nis/`host`/ethers.org_dir` `/var/nis/`host*`/bootparams.org_dir`	The NIS+ tables that correspond to the `/etc` files. These files are only pertinent if the system is using the NIS+ naming service. *host* is the host name of the NIS+ server.
`/etc/nsswitch.conf`	A file that you can edit to specify where (in the `/etc` files or in NIS+ tables) system software should look to find configuration information.
`/etc/inet/inetd.conf`	A configuration file that has information about daemons that may be required for network installation.
`/etc/dfs/dfstab`	A configuration file that specifies file systems that will be shared across the network.
`/etc/mnttab`	A configuration file that specifies file systems that are mounted.

Commands You Should Know About

Table 3-2 shows programs available when you set up for network installation.

Table 3-2

Program	Description
`add_install_client`	A script that adds information to the `/etc` files on the install server to enable network installation. See the `add_install_client(1m)` man page for more information.
`rm_install_client`	A script that removes information from the `/etc` files on the install server to disable network installation. See the `rm_install_client(1m)` man page for more information.
`setup_install_server`	A script that copies all or part of the Solaris CD onto a server's local disk. This enables you to perform network installations from the install server's disk instead of its CD-ROM drive. (Installing from the install server's disk is faster than installing from the server's CD-ROM drive.) See the `setup_install_server(1m)` man page for more information.
Host Manager	A graphical user interface that is available from within the Administration Tool (`admintool`) program. You can use Host Manager to specify naming services, system's IP and Ethernet addresses, and other information to be used for installations across a network.
`ttyhstmgr`	A text-based equivalent of the Administration Tool Host Manager. See the `ttyhstmgr(1m)` man page for more information.
`mount`	A command that shows mounted file systems, including the Solaris CD file system. See the `mount(1m)` man page for more information.

Table 3-2 (Continued)

Program	Description
`uname -a`	A command for determining system architecture. This information is sometimes required during installation. See the `uname(1)` man page for more information.
`reset`	A command for resetting the terminal settings and display. It is sometimes useful to use `reset` before booting. Or, if you boot and see a series of error messages about I/O interrupts, press the L1 or STOP and A keys at the same time, and then enter `reset` at the `ok` or `>` PROM prompt.
`banner`	A command for displaying system information, such as model name, Ethernet address, or memory installed. Available only from the `ok` or `>` PROM prompt.

Creating an Install Server

If you are installing systems over the network, you must have an install server--a system with a CD-ROM drive or with Solaris software copied to its local disk. This system will provide the installation services for systems on the network that do not have a local CD-ROM drive.

You can create an install server to install the following system types:

Server
Standalone
Dataless

This section describes how to:

Create an install server by mounting the Solaris CD or by copying the Solaris CD to the install server's local disk.

Note - If you intend to do frequent installations over the network, you should copy the Solaris CD image from the Solaris CD to the install server's local disk. Network installations from the install server's local disk are faster than from its CD-ROM drive. Copying Solaris CD image to the install server's disk also frees the CD-ROM drive for other uses.

Create a separate boot server (required only if systems are not on same subnet as the install server).

· How to Create an Install Server

Overview - Creating an install server involves:

Choosing a system with a CD-ROM drive to be the install server
Mounting the Solaris CD
Using the setup_install_server command to copy the Solaris CD to the install server's local disk (optional, but recommended)

Follow this procedure to create an install server.

On the system that is going to be the install server, log in as root.
This system must have a CD-ROM drive.
Insert the Solaris CD into the CD-ROM drive.
Mount the Solaris CD (if needed) and change the directory to the mounted CD:

If the Install Server Is	Then
Running Volume Management	`cd /cdrom/cdrom0/s0` or`cd /cdrom/cdrom0/s2` Note: Volume Management is running if the /vol directory on the system contains files. Systems running Solaris 2.0 or 2.1 do not have Volume Management.
Not running Volume Management	1) `mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom` or`mount -F hsfs -o ro /dev/dsk/c0t6d0p0 /cdrom` 2) `cd /cdrom`

Follow the instructions depending on whether or not you want to copy the Solaris CD to the install server's local disk:

If You	Then
Want to copy the Solaris CD	Go to Step 5.
Do not want to copy the Solaris CD	Go to Step 7.

Use the setup_install_server command to copy the contents of the Solaris CD to the install server's local disk.


  # ./setup_install_server install_dir_path

In this command,

install_dir_path..Specifies the directory where the Solaris CD image will be copied. You can substitute any directory path.

For example, the following command copies the Solaris CD image from the Solaris CD to the /export/install directory on the local disk:

./setup_install_server /export/install

Note - The setup_install_server command will indicate if you do not have enough disk space to copy the Solaris CD image from the Solaris CD. Use the df -a command to determine available disk space.

Type cd install_dir_path and press Return.

Determine your next step based on whether or not the install server is on the same subnet as the system to be installed.

If Install Server Is	Then
On same subnet as the system to be installed	Go to Task Complete on page 27.
Not on the same subnet as the system to be installed	Follow the procedure "How to Create a Boot Server on a Subnet" on page 28. You must complete this procedure when the install server is *not* on the same subnet as the system to be installed. After completing that procedure, go to Task Complete on page 27.

The install server is now created. Next, you must add information to the install server's configuration files so it recognizes the systems to be installed. To continue, go to the appropriate section in this chapter:

"How to Set Up Servers for Network Installation of a Standalone, Server, or Dataless Client" on page 31.

· How to Create a Boot Server on a Subnet

You can install Solaris software over the network from any install server on the network. However, a system that will use an install server on another subnet requires a separate boot server on its own subnet.

Overview - Creating a boot server involves:

Choosing a system with a CD-ROM drive to be the boot server for the subnet
Mounting the Solaris CD
Using the setup_install_server -b command to copy required architecture information from the Solaris CD to the local disk

Follow this procedure to set up a boot server on a subnet.

On the system that will be the boot server for the subnet, log in as root.
This system must have a CD-ROM drive or an NFS mount of a Solaris CD image. The system must also be in the NIS or NIS+ name service. (If your site doesn't use the NIS or NIS+ name service, you must distribute information about this system by following your site's policies.)
Insert the Solaris CD into the CD-ROM drive.
Mount the Solaris CD (if needed) and change the directory to the mounted CD:

If the Boot Server Is	Then
Running Volume Management	`cd /cdrom/cdrom0/s0` or`cd /cdrom/cdrom0/s2` Note: Volume Management is running if the /vol directory on the system contains files. Systems running Solaris 2.0 or 2.1 do not have Volume Management.
Not running Volume Management	1) `mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom` or`mount -F hsfs -o ro /dev/dsk/c0t6d0p0 /cdrom` 2) `cd /cdrom`

Use the setup_install_server command to set up the boot server for the subnet.
The setup_install_server command copies specified kernel architecture information to the local disk. Enter this command once for each type of system to be installed over the network.


  # ./setup_install_server -b boot_dir_path architecture

In this command,

`-b`	Specifies that the system will be set up as a boot server.
*boot_dir_path*	Specifies the directory where the kernel architecture will be copied. You can substitute any directory path.
*architecture*	Specifies the kernel architecture of the system to be installed. Sample valid values include sun4e, sun4d, sun4c, sun4m, and i86pc. (For a detailed list of kernel architectures, see Appendix C, "Kernel Architectures.")

For example, the following command copies kernel architecture information necessary for booting SPARC sun4c systems to be installed over the network:

./setup_install_server -b /export/install sun4c

Note - The setup_install_server command will indicate if you do not have enough disk space to copy the kernel architecture information. Use the df -a command to determine available disk space.

The boot server is now set up to boot systems on a subnet. To continue, go to the appropriate section in this chapter:

"How to Set Up Servers for Network Installation of a Standalone, Server, or Dataless Client" on page 31.

Setting Up Servers for Network Installation

This section describes how to set up appropriate servers necessary to install a system over a network. The next table shows servers required for each system type you want to install.

1 If System Type You Are Installing Is	Then You Need This Server Support
Standalone System	Install Server
Server	Install Server
Dataless Client	Install Server and File Server
Diskless Client	File Server

1. Systems also require a boot server if they are on a different subnet than the install server.

Note - When you install a SPARC server, you don't have the option to support x86 clients. If you want your SPARC server to serve x86 dataless or diskless clients, you must use Software Manager (swmtool) and add services for the x86 architecture after the server has been installed. To do this, select Add Client Support from the swmtool Edit menu.

Choose from the following procedures, based on the type of systems you are going to install Solaris software on:

· How to Set Up Servers for Network Installation of a Standalone, Server, or Dataless Client

The procedure to add standalone systems and servers for installation over the network is the same. The procedure to add dataless clients involves the added step of specifying a file server. This section describes both procedures.

Overview - This procedure involves:

Starting the Administration Tool Host Manager to update the name service and (if necessary) set up a file server
Using the add_install_client command to add information about the standalone, server, or dataless clients to the install server configuration files

Note - If you have a character-based terminal, you can use ttyhstmgr to add systems for network installation. To start ttyhstmgr, type ttyhstmgr and press Return.

Follow this procedure to set up the install server to install a standalone system, server, or dataless client on the network.

Follow the instructions in the following table.

If the System to Be Installed Is	And the System Is	Then
Not in the NIS or NIS+ name service	Standalone, server, or dataless client	Go to Step 2.
In the NIS or NIS+ name service	Dataless client	Go to Step 2.
In the NIS or NIS+ name service	Standalone or server	Go to Step 11.

On the install server, log in as a user in the administration group (group 14).

Caution - If your system is part of the NIS+ name service, you must run Administration Tool while logged in as a user in the NIS+ admin group. Otherwise, you will not have permission to update configuration information on the name server.

Start Administration Tool with the following command.


  $ /usr/bin/admintool &

After the Administration Tool main window appears, click on the Host Manager icon.

Note - If your site uses the Domain Name Service (DNS), you will have to modify the /etc/nsswitch.conf file and create the /etc/resolv.conf file manually. For detailed information, see the Name Services Administration Guide.

On the Host Manager: Select Naming Service screen, select a naming service and click on the Apply button.
See the sample Naming Service screen below.

If the Name Service Is	Then Select
NIS+	NIS+. Host Manager will update the NIS+ tables.
NIS	None. Host Manager will store the information you provide in `/etc` files. You will need to update NIS maps manually.
None	None. Host Manager will store the information you provide in the `/etc` files. This will provide enough information for systems to boot, and to install Solaris software over the network.

On the Host Manager screen, choose Add Host from the Edit menu command.

Determine your next step based on what kind of system you want to install.

System To Be Installed Is	Then
Standalone or Server	Go to Step 8.
Dataless Client	Go to Step 10.

On the Host Manager: Add Host screen, complete all fields and click on the Add button.

Go to Step 11.
Step 10 is required only for adding dataless clients for network installation.

On the Host Manager: Add Host screen, complete all fields and click on the Add button.

Make sure the install server has been set up.
See "How to Create an Install Server" on page 25 for instructions.
Determine your next step based on whether the standalone system or server is on the same subnet as the install server.

If Standalone System or Server Is	Then
On same subnet as install server	Go to Step 13.
Not on same subnet as install server	Go to Step 16.

On the install server, change the directory to the mounted Solaris CD or the directory where the Solaris CD image has been copied.
Use the add_install_client command to add information about the system to be installed to the install server's configuration files.


  # ./add_install_client [-c server:jumpstart_dir_path] host_name architecture

In this command,

-c........Specifies a JumpStart directory for custom JumpStart installations. This option and its arguments are required only for custom JumpStart installations.

Note: This option is unnecessary if you have completed the procedure "How to Enable All Systems to Access the JumpStart Directory" on page 74.

server:jumpstart_dir_path

server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path of the JumpStart directory.

*host_name*	Is the host name of the standalone system or the server where Solaris software will be installed over the network. (This is not the host name of the install server). The host must be in the name service for this command to work.
*architecture*	Is the kernel architecture of the system to be installed. Sample valid values include sun4e, sun4d, sun4c, sun4m, and i86pc. (For a detailed list of kernel architectures, See Appendix C, "Kernel Architectures.")

Go to Task Complete on page 40.
Step 16 through Step 18 are required only if you are using a boot server.
On the boot server, log in as root.
Change the directory to the boot directory.
The boot directory is created when you set up a system as a boot server, as described in "How to Create a Boot Server on a Subnet" on page 28.


  # cd /boot_dir_path

In this command,

/boot_dir_path..Is the absolute path to the directory that contains the kernel architecture information necessary for booting a system.

For example, the following command changes to a sample boot directory named boot_dir.

cd /boot_dir

Use the add_install_client command to add information about the system to be installed to the boot server configuration files.


  # ./add_install_client [-c server:jumpstart_dir_path] -s install_server:install_dir_path host_name architecture

In this command,

-c........Specifies a JumpStart directory for custom JumpStart installations. This option and its arguments are required only for custom JumpStart installations.

Note: This option is unnecessary if you have completed the procedure "How to Enable All Systems to Access the JumpStart Directory" on page 74.

server:jumpstart_dir_path

server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path of the JumpStart directory.

-s........Specifies the install server.

install_server:install_dir_path

install_server is the host name of the install server. install_dir_path is the absolute path name of the mounted Solaris CD or the directory that has the copy of the Solaris CD image.

*host_name*	Is the host name of the standalone system or the server where Solaris software will be installed over the network. (This is not the host name of the install server). The host must be in the name service for this command to work.
*architecture*	Is the kernel architecture of the system to be installed. Sample valid values include sun4e, sun4d, sun4c, sun4m, and i86pc. (For a detailed list of kernel architectures, See Appendix C, "Kernel Architectures.")

For example, the following command copies boot information from Solaris CD image on an install server's local disk in /export/install. add_install_client sets up the /tftpboot directory on the local system, which will be the boot server. The system that will be installed is named basil, and it is a SPARCstation^(TM) IPC^(TM), which has a sun4c kernel architecture:

./add_install_client -s install_server1:/export/install basil sun4c

The standalone system, server, or dataless client is now added for network installation. You are now ready to boot and install over the network. To find the correct booting and installing procedure in this book, see the appropriate chapter for the installation you want to perform:

· How to Set Up Servers for Network Installation of a Diskless Client

Technically speaking, diskless clients do not get Solaris software installed over the network. They just receive file services from a file server. However, diskless clients do require boot services of a server on the network. The following procedure describes how to specify:

Where the diskless client will get its files
Which server will boot the diskless client

Overview - The procedure to add diskless clients for installation involves:

Logging in to the install server
Using the Administration Tool Host Manager to add information about the diskless client to the install server configuration files

Note - If you have a character-based terminal, you can use the ttyhstmgr to add systems for network installation. To start ttyhstmgr, type ttyhstmgr and press Return.

Follow this procedure to add a diskless client to the install server.

On the install server, log in as a user in the administration group (group 14).

Start Administration Tool with the following command.


  $ /usr/bin/admintool &

After the Administration Tool main window appears, click on the Host Manager icon.

On the Host Manager: Select Naming Service screen, select a naming service and click on the Apply button.
See the sample Naming Service screen below.

If the Name Service Is	Then Select
NIS	None. Host Manager will store the information you provide in `/etc` files. You will need to update NIS maps manually.
NIS+	NIS+. Host Manager will update the NIS+ tables.
None	None. Host Manager will store the information you provide in the `/etc` files. This will provide enough information for systems to boot, and to install Solaris software over the network.

On the Host Manager screen, choose Add Host from the Edit menu command.

On the Host Manager: Add Host screen, complete all fields and click on the Add button.

On the diskless system, type the appropriate boot command from the PROM ok prompt. Choose from the following table:

If Diskless System Type Is	Then Boot Using
Sun-4^(TM)/3xx	`b le()`
Sun-4/110 Sun-4/2xx Sun-4/4xx	`b ie()`
*^(R) All other Sun systems*	`boot net`

Caution - You may need to verify that the bootparams search path is correct in the /etc/nsswitch.conf file. If the search path is incorrect, the diskless client will report "timeout waiting for ARP/RARP" messages and the boot will fail. See the nsswitch.conf(4) man page for detailed information.

The diskless system is now set up to boot over the network. After you turn on the diskless system, it will boot over the network and the proper file systems will be mounted from the specified file server.

Preconfiguring Network Information

Preconfiguring network information provides default values for the following network-wide information:

Date and time
Geographic region
Site subnet mask

Setting up network default values eliminates the need to supply this information after the system boots. After you set up this information in the name service, the Solaris installation program finds it automatically and does not prompt the user for it.

You can also preconfigure the language (called the locale) provided by Solaris software. See "Preconfiguring the Default Locale" on page 48 for detailed information.

Note - To preconfigure a system's host name and Ethernet address, use the Administration Tool's Host Manager as described in "How to Set Up Servers for Network Installation of a Standalone, Server, or Dataless Client" on page 31.

· How to Preconfigure Network Information

Overview - The procedure to preconfigure network information involves:

Using the vi text editor to edit files in the /etc directory
Updating the name service (NIS or NIS+) files with the information you've added to the files in the /etc directory

Follow this procedure to preconfigure the date and time, the geographic region, and the subnet mask used at your site. (You can do Step 2, Step 3, or Step 4, one or all, as long as you complete Step 5.)

On the NIS or NIS+ name server, log in as root.

Edit the /etc/hosts file.
In the /etc/hosts file, choose an entry for the server that will supply the date and time for systems being installed over the network. At the end of this entry, add the timehost alias. Use the following syntax:


  IP_address  host_name timehost

Note - The /etc/hosts file has read-only permissions. Using the vi editor, you must exit the file using :wq! to force the file to be saved with your changes.

In the /etc/timezone file, specify the domain that will supply the geographic region for systems being installed over the network. To do this, add a valid time zone and the network domain name. Use the following syntax:


  timezone domain_name

For example, the following entry in the /etc/timezone file configures all systems in the xx.yy.zz.COM domain into the U.S. Central time zone:

   US/Central xx.yy.zz.COM

For information on valid time zone names, see the /usr/share/lib/zoneinfo directory.

Note - The Administration Tool Host Manager sets the geographic region for each system rather than for all systems within a network domain.

In the /etc/netmasks file, specify the subnet mask to be used by systems being installed over the network.
To do this, add the network number and the corresponding netmask. Use the following syntax:


  network_address subnet_mask

For example, the following entry in the /etc/netmasks file sets the subnet mask for the network address 128.32.0.0:

      128.32.0.0 255.255.255.0

Update the NIS or NIS+ tables with the information you added to the
/etc/hosts, /etc/timezone, and /etc/netmasks files.

If Your Site Uses	Then
NIS	`/var/yp/make`
NIS+	`/usr/lib/nis/nispopulate -F -p /etc hosts timezone netmasks`

The date and time, geographic region, and netmask are now configured in the network. During a network installation of a system, the Solaris installation program will automatically use the default values you have configured.

Preconfiguring the Default Locale

When installing a localized version of Solaris software, you are prompted for the locale (the language) you want to use for the duration of the installation process. The locale you choose for installing Solaris software is also the default locale the installed version of Solaris will provide to the system's user.

You can set up a default locale of your choice. You do this by modifying the naming service (NIS or NIS+). After you modify the name service, as described in this section, the operating system will use this default locale for users. Also, the installation software will use the default locale for all future installations.

Choose from the following two procedures, depending on whether your site uses the NIS or NIS+ name service.

· How to Preconfigure Default Locale Using NIS

Overview - The procedure to preconfigure the default locale at sites using the NIS name service involves:

Using the vi text editor to edit files in the /var/yp/Makefile file
Creating a locale file in the /etc directory
Updating the NIS maps

Follow these instructions to set up a default locale for the system being installed over the network.

On the name server, log in as root and edit the /var/yp/Makefile file. Add the following text after the other *.time entries.


  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

Edit the /var/yp/Makefile file.
a. Add locale to the line starting with the word all. b. Add locale: locale.time on a new line.


  all: passwd group hosts ethers networks rpc services protocols netgroup bootparams aliases \  
  timezone locale  
  locale: locale.time

Create the file /etc/locale and make one entry for each domain.


  domain_name locale

The entry specifies the default locale for the domain. For example, the following line specifies French to be the default locale for the worknet.com domain:

worknet.com fr

You can also use a host name instead of the domain name to specify the default locale for a particular host. For example, the following line specifies Korean to be the default locale for system named sherlock:

sherlock ko

See the table on page 52 for a list of valid locale values.

Note - Not all locales are available on all Solaris CDs. The locale you select will be used for installation if it is present on the Solaris CD.

Make the maps.


  # /var/yp/make

This completes the procedure to set up a default locale for systems running the NIS name server. The default language you have specified will be used during the installation and will also be the language provided to system users.

· How to Preconfigure Default Locale Using NIS+

Overview - The procedure to preconfigure the default locale at sites using the NIS+ name service involves:

Using the nistbladm command to create a locale table and add information to it
Updating the NIS+ tables

Follow these instructions to set up a default locale for a system being installed over the network. (This procedure assumes the NIS+ domain is set up. Setting up the NIS+ domain is documented in the Name Services Administration Guide.)

Log in to a name server as root or as a user in the NIS+ admin group.
Use the following nistbladm command to 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 an entry to the locale.org_dir table by typing the following nistbladm command.


  # nistbladm -a name=domain_name locale=locale comment=comment locale.org_dir.'nisdefaults -d'

In this command,

*domain_name*	Is either the domain name or a specific host name for which you want to preconfigure a default locale.
*locale*	Is the locale you want to use to install the system and the locale you want to come up on users' systems. The following table shows valid values for *locale*.
Language
*comment*	Is the comment field. Use double quotation marks to begin and end comments that are longer than one word.

Note - Not all locales are available on all Solaris CDs. The locale you select will be used for installation if it is present on the Solaris CD.

This completes the procedure to set up a default locale for systems running the NIS+ name server. The default language you have specified will be used during the installation and will also be the language provided to system users.