Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations Oracle Solaris 10 1/13 Information Library |
Part I Planning to Install Over the Network
1. Where to Find Oracle Solaris Installation Planning Information
2. Preconfiguring System Configuration Information (Tasks)
3. Preconfiguring With a Naming Service or DHCP
Preconfiguring System Configuration Information With the DHCP Service (Tasks)
Creating DHCP Options and Macros for Oracle Solaris Installation Parameters
Using DHCP Manager to Create Install Options and Macros
Writing a Script That Uses dhtadm to Create Options and Macros
Part II Installing Over a Local Area Network
4. Installing From the Network (Overview)
5. Installing From the Network With DVD Media (Tasks)
6. Installing From the Network With CD Media (Tasks)
7. Patching the Miniroot Image (Tasks)
8. Installing Over the Network (Examples)
9. Installing From the Network (Command Reference)
Part III Installing Over a Wide Area Network
11. Preparing to Install With WAN Boot (Planning)
12. Installing With WAN Boot (Tasks)
13. SPARC: Installing With WAN Boot (Tasks)
14. SPARC: Installing With WAN Boot (Examples)
The following table provides a high-level overview of the naming service databases that you need to edit and populate to preconfigure system information.
|
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 procedures in this section to use your naming service to preconfigure the locale for a system.
Before You Begin
The NIS server must be available to access during the installation.
ok boot net
ok boot net - text
ok boot net - nowin
The system boots from the network.
Note - Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
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
all: passwd group hosts ethers networks rpc services protocols \ netgroup bootparams aliases publickey netid netmasks c2secure \ timezone auto.master auto.home locale
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
For example, the following entry specifies that French is the default language that is used in the example.com domain:
fr example.com
The following example specifies that Belgian French is the default locale that is used by a system named myhost:
fr_BE myhost
Note - International Language Environments Guide contains a list of valid locales.
Locales are available on the Oracle Solaris DVD or Oracle Solaris Software - 1 CD.
# 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.
Next Steps
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 JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, JumpStart (Overview), in Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations.
See Also
For more information about the NIS name service, see Part III, NIS Setup and Administration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
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). The NIS+ server must be available to access during installation.
ok boot net
ok boot net - text
ok boot net - nowin
The system boots from the network.
# nistbladm -D access=og=rmcd,nw=r -c locale_tbl name=SI,nogw= locale=,nogw= comment=,nogw= locale.org_dir.`nisdefaults -d`
# nistbladm -a name=namelocale=locale comment=comment locale.org_dir.`nisdefaults -d`
Either the domain name or a specific system name for which you want to preconfigure a default 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.
The comment field. Use double quotation marks to begin and end comments that are longer than one word.
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.
Next Steps
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 JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, JumpStart (Overview), in Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations.
See Also
For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+).