installing solaris on sparc

7/31/2019 Installing Solaris on Sparc

1/229

2550 Garcia AvenueMoun tain View, CA 94043U.S.A.

SPARC: Installing Solaris Software

A Sun Microsystems, Inc. Business


2/229

PleaseRecycle

1995 Sun Microsystem s, Inc. 2550 Garcia Avenu e, Mou ntain View, Californ ia 94043-1100 U.S.A.

All rights reserved. This produ ct or documen t is protected by copyr ight and distributed un der licenses restricting its use,copying, distribution and decompilation. No p art of this product or document m ay be reprodu ced in any form by any m eanswithou t pr ior written au thorization of Sun and its licensors, if any.

Portions of this produ ct may be d erived from the UNIX system , licensed from UNIX System s Laborator ies, Inc., a wh ollyown ed su bsidiary of N ovell, Inc., and from the Berkeley 4.3 BSD system, licensed from the Un iversity of California. Third-par tysoftware, including font technology in this prod uct, is protected by copy right and licensed from Suns Sup pliers.

RESTRICTED RIGHTS LEGEND: Use, dup lication, or d isclosure by the governm ent is sub ject to restrictions as set forth insubparag rap h (c)(1)(ii) of the Rights in Technical Data and Compu ter Software clause at DFARS 252.227-7013 and FAR 52.227-19.

The prod uct described in this manu al may be protected by one or m ore U.S. patents, foreign patents, or pend ing app lications.

TRADEMARKSSun, Sun Microsystem s, the Sun logo, Sun Soft, the SunSoft logo, Solaris, Sun OS, Op enWind ows, DeskSet, ONC, ONC+, NFS,Sun Ultra, and Ultra are tradem arks or registered trad emarks of Sun Microsystems, Inc. in th e United States and oth er countries.UNIX is a registered trad emark in th e United States and other countries, exclusively licensed throu gh X/ Open Comp any, Ltd.OPEN LOOK is a registered tradem ark of N ovell, Inc. PostScript an d Display PostScript are trad emarks o f Adobe Systems, Inc.Motif is a registered trad emark of Op en Software Found ation, Inc. FrameMaker is a registered trad emark of FrameTechnology Corporation. Island Draw is a registered trad emark of Island Grap hics Corporation.

All SPARC trademar ks are trad emarks or registered tr adem arks of SPARC International, Inc. in th e United States and othercount ries. SPARCcent er, SPARCclus ter, SPARCompiler, SPARCd esign , SPARC811, SPARCengine, SPARCpr inter, SPARCserver,SPARCstation, SPARCstorage, SPARCworks, m icroSPARC, microSPARC-II, and UltraSPARC are licensed exclusively to SunMicrosystems, Inc. Produ cts bearing SPARC trademar ks are based u pon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK and Sun Graphical User Interfaces were d eveloped b y Sun M icrosystems, Inc. for its users and licensees.Sun acknow ledges the pioneering efforts of Xerox in researching and developing the concept of visual or graph ical userinterfaces for the comp uter indu stry. Sun holds a non -exclusive license from Xerox to the Xerox Graph ical User Interface, wh ichlicense also covers Suns licensees who implemen t OPEN LOOK GUIs and otherw ise comply w ith Suns written licenseagreements.

X Window System is a tr adem ark of X Consortium, Inc.

THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS PUBLICATION COULD INCLUDE TECHN ICAL INACCU RACIES OR TYPOGRAPH ICAL ERRORS. CH AN GES AREPERIODICALLY ADDED TO THE INFORMATION HEREIN, THESE CHANGES WILL BE INCORPORATED IN NEWEDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AN D/ OR CHA NGES INTHE PRODUCT(S) AN D/ OR THE PROGRAM S(S) DESCRIBED IN TH IS PUBLICATION AT AN Y TIME.


3/229

iii

Contents

Abou t This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

1. About Installing Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Definition: Installing Solaris Software. . . . . . . . . . . . . . . . . . . . . 1

2. Preparing to Install Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Why You Should N ot Ignore This Chapter. . . . . . . . . . . . . . . . . 5

Steps to Prepare to Install Solaris. . . . . . . . . . . . . . . . . . . . . . . . . 6

Task Map: Jum pStart Installations . . . . . . . . . . . . . . . . . . . . . . . . 13

Task Map: Interactive Installations . . . . . . . . . . . . . . . . . . . . . . . 14

Task Map: Custom Jum pStart Installation . . . . . . . . . . . . . . . . . 15

3. Preparing to Install Solaris Over a Network . . . . . . . . . . . . . . 17

About Installing Solaris Over a Network . . . . . . . . . . . . . . . . . . 17Servers Required for Network Installation . . . . . . . . . . . . . . . . . 18

Requirements for Hands-Off Network Installation . . . . . . . . . . 20

Command s You Should Know About . . . . . . . . . . . . . . . . . . . . . 21

Creating an Install Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22


4/229

iv SPARC: Installing Solaris SoftwareNovember 1995

w How to Set Up a New System to be an Install Server . . 22

w How to Create an Install Server . . . . . . . . . . . . . . . . . . . . 24

w How to Create a Boot Server on a Subnet. . . . . . . . . . . . 27

Setting Up Servers for Network Installation . . . . . . . . . . . . . . . 30

w Ho w to Set Up Servers for Netw ork Installation of aStandalone, Server, or Dataless Client . . . . . . . . . . . . . . 31

Using add_install_client to Set Up Servers for Netw orkInstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

w How to Use add_install_client to Set Up Servers forNetw ork Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Preconfiguring the Default Locale . . . . . . . . . . . . . . . . . . . . . . . . 40

w How to Preconfigure Default Locale Using NIS . . . . . . 40

w How to Preconfigure Default Locale Using NIS+ . . . . . 43

4. Preparing Custom JumpStart Installations . . . . . . . . . . . . . . . 47

Definition: Custom JumpStart Installation . . . . . . . . . . . . . . . . . 47

Reasons to Choose a Custom JumpStart Installat ion . . . . . . . . 48

Tasks to Prepare for Custom Jum pStart Installations . . . . . . . . 49

What Happens During a Custom Jump Start Installat ion . . . . . 50

Creating a Jum pStart Directory on a Diskette . . . . . . . . . . . . . . 53

w Ho w to Create a JumpStart Directory on a Diskette for x86

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53w Ho w to Create a JumpStart Directory on a Diskette for

SPARC Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Creating a Jum pStart Directory on a Server . . . . . . . . . . . . . . . . 62

w How to Create a JumpStart Directory on a Server . . . . 63

Enabling All Systems to Access the Jum pStart Directory . . . . . 65


5/229

Contents v

w Ho w to Enable All Systems to A ccess the Jum pStartDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

What Is a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Requirements for Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

w How to Create a Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Profile Examp les . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Profile Keyword and Profile Value Descriptions . . . . . . . . . 72

How the Size of Swap Is Determined . . . . . . . . . . . . . . . . . . 82

Creating the rules File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

What Is the rules File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

When Does a System Match a Rule . . . . . . . . . . . . . . . . . . . . 83

w How to Create the rules File. . . . . . . . . . . . . . . . . . . . . . 83

Rule Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Important Information About the rules File . . . . . . . . . . . . 87

Rule Keyword and Rule Value Descriptions . . . . . . . . . . . . 88

How the Installation Program Sets the Value ofrootdisk 91

Using check to Validate th e rules File . . . . . . . . . . . . . . . . . . . 93

w How to Use check to Validate th e rules File . . . . . . . . 94

5. Using Optional Custom JumpStart Features . . . . . . . . . . . . . . 97

Overv iew. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Creating Begin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

What Is a Begin Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Important Information About Begin Scripts . . . . . . . . . . . . 98


6/229

vi SPARC: Installing Solaris SoftwareNovember 1995

Ideas for Begin Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Creating Derived Profiles With Begin Scripts . . . . . . . . . . . 98

Creating Finish Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

What Is a Finish Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Important Information About Finish Scripts . . . . . . . . . . . . 100Ideas for Finish Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Ad din g Files With Finish Scripts . . . . . . . . . . . . . . . . . . . . . . 101

Customizing the Root Environment . . . . . . . . . . . . . . . . . . . 102

Setting the Systems Root Password With Finish Scripts . . 102

Using pfinstall to Test Profiles . . . . . . . . . . . . . . . . . . . . . . . . 104

Why Use pfinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Ways to U se pfinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

w How to Use pfinstall to Test a Profile. . . . . . . . . . . . 105

pfinstall Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

w Ho w to Create a Disk Config uration File for a SPARCSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

w Ho w to Create a Mu ltiple Disk Configu ration File for aSPARC System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Using a Site-Specific Installation Program . . . . . . . . . . . . . . . . . 111

6. Preparing a System for Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 113

Over view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Can You Use Up grad e? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Upgrad ing and Install Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Check Other Software Docum entation . . . . . . . . . . . . . . . . . . . . 114

If Youre Using Custom Jum pStart . . . . . . . . . . . . . . . . . . . . . . . 114


7/229

Contents vii

If You O verrid e the Boot File Location . . . . . . . . . . . . . . . . . . . . 115

Upg rad ing Dataless Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Important Files For Upgrad ing . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Backing Up Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Preserving Local Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . 1167. Booting and Installing Solaris: JumpStart . . . . . . . . . . . . . . . . 119

8. Booting and Installing Solaris: Interactive. . . . . . . . . . . . . . . . 125

9. Booting and Installing Solaris: Custom JumpStart. . . . . . . . . 131

10. Completing an Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Over view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

What Happ ened During the Upgrade. . . . . . . . . . . . . . . . . . . . . 137

Cleaning Up the System After an Upgrade . . . . . . . . . . . . . . . . 137

How to Upgrade Clients With Different Platforms and PlatformGrou ps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

11. Where to Go After Installing Solaris . . . . . . . . . . . . . . . . . . . . . 141

A. Worksheets for the Solaris Installation Program. . . . . . . . . . . 145

B. System Identification Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

C. Platform N ames and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

D. Sample Custom JumpStart Installation . . . . . . . . . . . . . . . . . . 161

E. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

F. Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

G. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Ind ex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189


8/229

viii SPARC: Installing Solaris SoftwareNovember 1995


9/229

ix

About This Book

Who Can Use This Book

This book is for any one installing the Solaris operating environment onnetw orked or non -networked systems. Site policy and / or level of expertisewill determine who can perform the tasks required to install Solaris software.

Dont Read the Entire Book!

Because this book covers different ways of installing the Solaris software toaccommodate a variety of site needs, you do not need to read the entire book.

Read chapters 1 and 2 theyll help you decide w hich method of installing isbest for your site, and point you to a task map that tells you exactly whatsections of the book to use.


10/229

x SPARC: Installing Solaris SoftwareNovember 1995

How This Book Is Organized

This book is organized by tasks in the categories of before, du ring, and afterinstalling Solaris software.

Note This book does not include instructions for setting up system hardwareor other peripherals. Setting up hardware and peripherals is described in yourhardware guides.

Before Install ing Solaris

2 Prepa ring to Install Solaris

3 Prepa ring to Install Solaris Over a Netw ork

4 Preparing for Custom Jum pStart

Installations

6 Preparing a System for Up grade

After Inst all ing Solaris

10 Completing an Upgrade

Inst all ing Solaris

9 Installing Solaris: Custom Jum pStart

8 Installing Solaris: Interactive

7 Installing Solaris: JumpStart

11 Where To Go A fter Installing Solaris

1 Abou t Installing Solaris

5 Using Optional Custom Jum pStart Features


11/229

About This Book xi

Related Information

You may need to refer to the following books or online information wheninstalling Solaris software:

Hard ware vendor online and hardcopy docum entation

Vendor-specific information for installing Solaris software.

Installation Notes

Describes any late-breaking new s abou t installing Solaris software includ ingknown problems.

Solstice AdminSuite 2.1 Users Guide

Describes applications such as Solstice Host Manager, which you can useif youre setting u p n etwork installations.

System Administration Guide, Volume I

Describes how to back up system files.

Solaris 1.x to 2.x Transition Guide

Describes tran sition issues including backing u p 4.1.x files before installingSolaris software, and restoring files after Solaris software is installed.


12/229

xii SPARC: Installing Solaris SoftwareNovember 1995


13/229

1

About Installing Solaris 1

Definition: Installing Solaris Software

As show n on the following pag es, the process of installing Solaris softwaremean s copying it from th e Solaris CD to a systems local disk.


14/229

2 SPARC: Installing Solaris SoftwareNovember 1995

1

Stage Diagram What Happens

1You choose a Solaris CD for

your hardware platform. TheSolaris CD contains theSun OS operating system an dother software.

2 You load the Solaris CD intothe CD-ROM d rive.

Operating system

SunOS

Applications DeskSet

software implementing

the OPEN LOOK

graphical user interface

The Solaris installation

program for installing

Solaris software

Networking

ONC/NFS

Windowing Environment

OpenWindows


15/229

About Installing Solaris 3

1

3 After you pow er on thesystem, you boot the system

using a boot commandspecific to you r systemhardware. (Sample screenshown.)

During the booting phase,checks are performed on thehardware.

4 The Solaris installationprogram copies the Solarissoftware from the CD to thesystems local disk. This isdone interactively using agraph ical (show n) orcharacter interface, orautomatically without userintervention.

Stage Diagram What Happens

okboot sd(0,6,2)

Booting from: sd(0,6,2)

SunOS Release x.x.x Version [UNIX (r) SystemV Release]

Configuring /devices directory

Configuring /dev directory

Continue Exit Help

The Solaris Installation Program

You are now interacting with the Solaris installa-

tion program. The program is divided into aseries of short sections. At the end of each sec-

tion, you will see a summary of the choices

youve made, and be given the opportunity to

make changes.


16/229


1


17/229

5

Preparing to Install Solaris 2

This chapter guides you step-by-step through making decisions andcompleting the tasks required to prepare your system to install the Solarissoftware including:

Why You Should Not Ignore This Chapter

Successfully installing Solaris software requires a clear sense of what youredoing and why, or it can become difficult. This chapter provides all theinformation you need to determine the best way to install the Solaris softwarefor your site. This chapter also directs you to sp ecific chapters of this bookyoull need .

Determine if your syst em is networked. page 6

Determine your sy stem type. page 6

Determine if you have required hardware. page 9

Plan disk space and memory requirements. page 9

Back up your sy stem. page 11

Choose a method for installing Solaris software. page 11

Choose a task map and complete required tasks. page 12


18/229


2

Steps to Prepare to Install Solaris

Follow these steps before turning on your system.

1 Determine if your system is networked.

If your system is networked (connected to a n etwork), an Ethernet connector orsimilar network adapter shou ld be plugged into your system.

2 Determine your system type.

Before installing Solaris software, you mu st determ ine the system type whichdetermines where the system gets imp ortant file systems. Using Figure 2-1 onpage 7, choose a system typ e from the following lists:

Networked systems:

OS server

Standalone system

Dataless client Diskless client

Aut oClient system

Non-networked systems:

Standalone system


19/229


2

Figure 2-1 System Types

Networked systems

OS Server

Provides Solaris operating environment software including services and/or file sys-

tems for systems on the network. For dataless and diskless clients, OS servers pro-

vide the /usr file system. For diskless clients, an OS server provides root (/) and

swap file systems. For AutoClient systems, an OS server provides all system soft-ware except the individual root (/) and /usr file system required for local swapping.

Standalone system

Has a local disk and does not require support from an OS server.

Diskless client

Does not install Solaris software, but receives file services from an OS server, anddoes not have a local disk.

Dataless client

Has a local disk for root (/) and swap. Gets /usr file system from an OS server.

Must mount /usr from a server.

Standalone systems

Have local disks and file systems.

Non-networked systems

AutoClient system

Does not install Solaris software, but receives file services from an OS server. Has

a local disk for swapping and caching its root (/) and /usr file systems.


20/229


2

Note A standalone system in the Solaris operating environment applies toboth networked and non-networked systems. Whether networked or non-netw orked , a stand alone system ha s all of its Solaris softwa re on local harddisk, and does not require services from another system.

3 If you are setting up diskless clients and/ or AutoClientsystems, and the OS server providing Sola ris softwa re isalready installed with Solaris, do not go further in this book.

Diskless clients and Au toClient systems do not install Solaris software; instead,they receive file services from an OS server. If the OS server providing Solarissoftware already has Solaris software installed, refer to th e Solstice AdminSuite2.1 Users Guide for information on setting u p d iskless clients, or the SolsticeAut oClient 1.0 Administration Guide for setting up AutoClients.

If you do not have an OS server set up with Solaris software, continue in thisbook.

4 If you are setting up da taless clients, determine if youhave required software.

If you are setting up dataless clients to boot over the network from an OSserver, you mu st hav e the Solstice Host Manager, which comes with theserver software.

Note SunSoft plans to remove support for the dataless client system typeafter Solaris 2.5. You can select this system type now, but in future releases youwill need to select a d ifferent typ e.


21/229


2

5 Determine if you have required hardware.

For a detailed description of hardware requirements, see your hardwarevendor d ocum entation.

6 Plan disk space a nd memory requirements.

There are many variables involved in determining disk space and memoryrequirements. Determining physical memory is easythe minimum is 16Mbytes, but m ore is better. While a system requ ires 32 Mbytes of virtualmemory (physical and sw ap file/ slices), determining requirements beyond thisis not easy; it is depends on the type of applications that are running.Determining d isk space is also not so easy; it is dep end s on th e following:

System type selected (for example, OS server, diskless client, AutoClientsystem, stand alone system, dataless client)

Langua ge selected (for examp le, Chinese, Japan ese, Korean)

Softwa re grou p selected (see following ta ble)

1.See your hardw are vendor d ocumentation for a list of supported systems.

Table 2-1 Hardware Requirements

Hardware

Platform

Minimum

Memory

Disk

Interfaces

Buses D evice for Installing

Solaris Sof tware

SPARCsystem 1

16 Mbytes SMD IPI SCSI

VMEbus Sbus

You m ust have on e of thefollowing devices forinstalling Solaris software: Local CD-ROM drive Remote CD-ROM drive

available over the n etwork Remote hard disk

available over the n etwork


22/229


2

Softwa re packages that are selected or d eselected in the software grou p (forexamp le, you select Chinese, but d eselect the 200-Mbyte font pa ckage)

Disks selected (for example, ten 104-Mbyte d isks will waste m ore spacetrying to m ake things fit th an a single 1-GByte disk)

Solaris file system overh ead or local file systems (for examp le, mail, printerspooling, users personal file systems, swap space)

Size of other ap plications tha t are run ning (for example, Answ erBooks,SPARC compilers, FrameMaker, IslandDraw)

1. Another software group, entire distribution plus O EM support m ay also be available. It contains hardwaresup port for SPARC clones. Disk space will vary from release to release. To find out if this softwar e group isavailable for your h ardware p latform, see the SPARC Hardware Compatibility Gu ide.

If You Want to Install

This Sof tware Group1 ...

Which Installs ... Then Youll Need

Approximately This

Much Disk Space For

Domestic Solaris CD ...

Core System Su pp ort Th e m in im um softw arerequired to boot and runSolaris software.

80 Mbytes

End User System Support The core group plus therecommended software foran end user includingOpenWindow s and theDeskSet software.

180 Mbytes

Developer SystemSupport

The end user software plussoftware for d evelopingsoftware including libraries,includ e files, man p ages,and programming tools.

Compilers and debuggersare not included.

280 Mbytes

En tire Distr ibu tion Th e en tire Solar is release(everything on the CD).Compilers and debuggersare not included.

350 Mbytes


23/229


2

Depending on wh ich installation m ethod you choose, you can perform a dryrun to determine if you have enough disk space before actually installingSolaris software.

Interactive This m ethod of installation lets you interactively select d isks,locales, software, and lay out file systems; you can determine yourrequirements from a summary at the end of the session, and exit theprogr am p rior to installing Solaris software.

Custom JumpStart This method of installation lets you run thepfinstall comman d to test specific installation profiles withou t actuallyinstalling the Solaris softwa re on a system.

7 Back up your system.

If your system h as any files on it that you wa nt to save, make sure you p erforma backup . The safest way to back up files is to do a level 0 du mp . If you do n othave a backup procedu re in p lace, see Syst em A dministration Guide, Volume Iforinstructions.

8 Choose a method for installing Solaris software.

There are three m ethod s for installing Solaris softwa re:

Jum pSt arteasiest meth od of installing Solaris softwa re. The Jum pStartsoftware autom atically installs a new system as a stand alone (networked ornon-networked) with Solaris software. However, not all new systems havethe Jum pStart software; see Step 1 on page 120 to find out if your systemhas JumpStart software.

Int eractiv eeasy, han ds-on method of installing Solaris software. TheSolaris installation program guides you step-by-step through identifyingyour system an d installing Solaris software. Youre in control all the w ay!

Custom JumpStart(formerly called au to-install)for the ad vanced user withexperience in Bourn e shell scripting. By creating profiles an d rules files, youcan set up systems to au tomatically install Solaris softwa re in d ifferent w ayson different systems. This method requires up-front work before systemsare tu rned on, bu t its the most cost-effective w ay to install Solaris softwa refor large, enterp rise sites. You can even set u p a ha nd s-off installation w herethe user just boots the system and nothing more needs to be don e!


24/229


2

9 Choose a task map a nd complete required tasks.

Choose the task map from the following pa ges that matches the method you vechosen for installing Solaris software: JumpStart, interactive, or customJum pStart. The task map s guide you through all the tasks you need tocomplete before turning on , booting, and installing Solaris softwa re on asystem.

JumpStart

Interactive

Custom

JumpStart

Booting Identifying Your System Installing SolarisMethods

System automaticallyYou interact with theSolaris installation program

to identify your system

Solaris software is

automatically installedboots

You boot system

You interact with the Solarisinstallation program toidentify your system

You interact with theSolaris installationprogram to install Solarissoftware

You boot system

You interact with the Solarisinstallation program toidentify your system

Solaris software isautomatically installedusing a profile that youcreate in advance


25/229


2

Task Map: JumpStart Installations

Figure 2-2 Task Map for JumpStart Installations

Install Solarissoftware

Activity Description For Instructions, Go To

Optional. How to Set Up Serv-

ers for Network Instal-lation of a Standalone,

Server, or Dataless Cli-

ent

page 31

Boot and install Solaris software. Chapter 7, Booting

and Installing Solaris:

JumpStart

page 119

Prepare for net-

work installation



26/229


2

Task M ap: Interactive Installations

Figure 2-3 Task Map for Interactive Installations

Activity Description For Instructions,

Go To

Optional.Use worksheets to gather information that may need

to be supplied during the Solaris installation program.

Appendix A, Work-sheets for the So-

laris Installation

Program

page 113

SunOS 4.x system only

The upgrade option is not available for SunOS 4.x

systems. Backup your system and follow other special

procedures.

Solaris 1.x to 2.x

Transition Guide

Upgrade option only

Perform tasks such as backing up files and preserving

local modifications.

Chapter ,

Preparing a

System for

Upgrade

page 113

From another system on the network

Set up systems (standalone, OS server, or dataless

client) for network installations.

Chapter 3,

Preparing to

Install Solaris Over

a Network

Chapter 8,

Booting and

Installing Solaris:

Interactive

page 17

page 125

From local CD-ROM

Boot and install Solaris software.

Chapter 8,

Booting and

Installing Solaris:Interactive

page 125

Save files fromSunsOS 4.x systems

Gather information

Prepare system forupgrade



27/229


2

Task Map: Custom JumpStart Installation

Figure 2-4 Task Map for Custom JumpStart Installations

Activity Description For Instructions, Go To

SunOS 4.x system only

The upgrade option is not available for SunOS 4.xsystems. Backup your system and follow other

special procedures.

Solaris 1.x to 2.x

Transition Guide

Upgrade option only

Perform tasks such as backing up files and

preserving local modifications.

Chapter , Preparing a

System for Upgrade

page 113

Perform the following tasks:

Create a JumpStart directory

Enable clients to access the JumpStart directory

Create profiles

Create a rules file

Use check to validate the rules file

Chapter 4, Preparing

Custom JumpStart

Installations

page 47

From another system on the network

Set up systems (standalone, OS server, or

dataless client) for network installations.

Chapter 3, Preparing

to Install Solaris Over a

Network

Chapter 9, Booting


Custom JumpStart

page 17

page 131

From local CD-ROM

Boot and install Solaris software.

Chapter 9, Booting


Custom JumpStart

page 131

Prepare system forupgrade

Save files fromSunOS 4.x system

Set up system forcustom JumpStart

Install SolarisSoftware


28/229


2


29/229

17

Preparing to Install Solaris Over aNetwork 3

About Installing Solaris Over a Network

A typ ical way to install Solaris software is to use the installation progra m tocopy the Solaris CD shipped with your system. However, it is uncommon atmost sites for every system to hav e its own local CD-ROM d rive. When a

system does not have a local CD-ROM drive, you can perform a networkinstallation. Network installation means that you install software over thenetworkfrom a system with a CD-ROM drive to a system without aCD-ROM d rive.

How to S et Up a N ew S yst em to be an Inst all Server page 22

How to Create an Install S erver page 24

How to Create a Boot Server on a Subnet page 27How to S et Up Servers for N etwork In stallation of a S tandalone, Server,

or Dataless Client

page 31

How to Preconfigu re Default Locale Using NIS page 40

How to Preconfigu re Default Locale Using NIS+ page 43


30/229


3

Note Instructions in this chap ter are v alid for either an x86 or SPARC serverbeing used for networ k installations. An x86 server can p rovide th e Solaris CDimage for SPARC systems, and a SPARC server can provid e the Solaris CDimage for x86 systems.

Servers Required for Network InstallationAs shown in Figure 3-1, systems that install Solaris software over the netw orkrequire:

Install server A networked system w ith the CD-ROM d rive that providesinstallation services for other systems.

N ame server A system that manages a distributed network database (suchas NIS or NIS+) containing information about users and other systems onthe 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 thenetwork. A boot server and install server are typically the same system.H owever, if the system to be installed is on a differentsubnet than the installserver, a boot server is required on that subnet.

Dataless clients also require:

OS server A system that provides Solaris operating environment softwareinclud ing services and / or file systems. For dataless clients, OS serversprovide the /usr file system.


31/229

Preparing to Install Solaris Over a Network 19

3

Figure 3-1 Netw ork Installation Servers

Name Server

Boot Server

Install/Boot Server

Subnet

OS Server

Standalone StandaloneStandalone Standalone Diskless Dataless

Standalone Standalone Diskless Dataless

NIS

or

NIS+


32/229


3

Requirements for Hands-Off Network Installation

To set up your site to install Solaris softwa re on systems ov er the n etwork withno u ser intervention, you m ust:

Use the custom Jum pStart installation m ethod. (See Chapter 4, PreparingCustom Jum pStart Installations.)

Make sure all systems are properly configured in the name service.(Procedures in this chapter include information on how to add systems tothe n ame service.)

Preconfigure network information, such as the date, time, geographicregion, site subn et mask, and langua ge. By using th e Solstice Host Managerto set up a server for network installations, you automatically preconfigurenetwork information. This eliminates many prompts that are otherwisenecessary to identify the system during an installation.


33/229


3

Commands You Should Know A bout

Table 3-1 shows progra ms available for setting up n etwork installations.

Table 3-1 Network Installation Commands

Program Description

setup_install_server A script tha t copies all or part of the Solaris CD onto aservers local disk. This enables you to performnetwork installations from the install servers diskinstead of its CD-ROM drive. (Installing from theinstall servers disk is faster than installing from theservers CD-ROM drive.) See thesetup_install_server(1m) man p age for moreinformation.

H ost Man ager A grap hical u ser in terface th at is available from w ith inthe Solstice AdminSuite (solstice). You can useHost Manager to specify naming services, systems IPand Ethernet addresses, and other information to beused for installations across a netw ork.

mount A command that shows mounted file systems,including the Solaris CD file system. See themount(1M)page for more information.

uname -i A comman d for d etermining a systems platformnam e (for exam ple, SUN W,SPARCstation-5,). Thisinformation is sometimes required d uring installation.See the uname(1)man page for more information.

reset A comman d for resetting the terminal settings anddisplay. It is sometimes useful to use reset beforebooting. Or, if you boot and see a series of errormessages about I/ O interrup ts, press the L1 or STOPand A keys at the same time, and then enter reset at

th e ok or > PROM promp t.banner A comman d for d isplaying system information, such

as model name, Ethernet address, or memoryinstalled. Available only from the ok or > PROMprompt.


34/229


3

Creating an Install Server

If you are installing systems over the network, you must have an installservera system with a CD-ROM drive or w ith Solaris software copied to itslocal disk. This system w ill provid e the installation services for systems on thenetwork that do not have a local CD-ROM drive.

You can create an install server to install the following system typ es: OS server

Standalone system

Dataless client

This section d escribes how to:

Set up a new system to be an install server.

Create an install server by mounting the Solaris CD or by copying theSolaris CD to the install servers local disk.

Note If you intend to do frequent installations over the network, you shouldcopy th e Solaris CD imag e from th e Solaris CD to th e install servers local disk.Netw ork installations from th e install server s local disk are faster tha n fromits CD-ROM d rive. Copying Solaris CD image to th e install server s d isk alsofrees the CD-ROM drive for other u ses.

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

w How to Set Up a New System to be an Install Server

Overview Setting up a new system to be an install server involves:

Installing the system hardware, including a CD-ROM drive

Connecting the system to a network

Installing Solaris software

Follow th is procedu re to create an install server

1. Install the system hardware, including a CD-ROM drive.

Follow the hardware documentation for detailed information.


35/229


3

2. Connect the system to the network.

Follow the hardware documentation for detailed information.

3. Install Solaris software.

During an interactive installation, you are prompted to select a nameservice. Follow th e gu idelines in the n ext table:

4. If you w ant this sys tem to be a name server, set up a name service after

you have installed the Solaris software. For detailed information, see the

N IS+ and DN S Setup and Configu ration Guide.

The system is now set up so that you can make it an install server. Next, youmu st make a Solaris CD ima ge available to other systems. To continue, go tothe How to Create an Install Server on page 24.

Is a Name S erviceRunning at Your Site ...

Then ...

Yes Select NIS or NIS+, whichever your site uses, whenprom pted for a nam e service. After the Solarissoftware is installed, go to How to Create an InstallServer on page 24.

No Select None when prompted for a name service.After the Solaris software is installed, go to Step 4.

TaskComplete


36/229


3

w 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

Moun ting the Solaris CD

Using the setup_install_server comman d to copy th e Solaris CD to the

install server s local disk (optional, but recomm end ed)

Follow th is procedu re to create an install server.

1. On the system that is going to be the install server, log in and become

root.

This system must have a CD-ROM drive.

2. Insert the Solaris CD in to the CD-ROM drive.

3. Mount the Solaris CD (if need ed) and change the directory to the

mounted CD:

4. Determine your next step based on w hether or not you w ant to copy the

Solaris CD to the install servers local disk:

If the InstallServer Is ...

Then ...

Running VolumeManagement

cd /cdrom/cdrom0/s0

orcd /cdrom/cdrom0/s2

Note: Volume Man agement is run ning if the /vol directoryon the system contains files. Systems running Solaris 2.0 or2.1 do n ot have Volume Man agement.

Not runningVolumeManagement

1) mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

ormount -F hsfs -o ro /dev/dsk/c0t6d0p0 /cdrom

2)cd /cdrom

If You ... Then ...

Want to copy the Solaris CD Go to Step 5.

Do n ot w an t to cop y th e Solaris CD Go to Step 7.


37/229


3

5. Use the setup_install_server command to copy the contents of the

Solaris CD to the install servers local disk.

In this command ,

For example, the following comm and copies the Solaris CD imag e from theSolaris CD to the /export/install directory on th e local disk:

./setup_install_server /export/install

Note The setup_install_server command will indicate if you do nothave en ough disk spa ce to copy the Solaris CD image from th e Solaris CD. Use

th e df -kl command to determine available disk space.

6. Type cd install_dir_path and p ress Return.

# ./setup_install_server install_dir_path

install_dir_path Specifies the d irectory w here the Solaris CD imagewill be copied. You can sub stitute any directorypath.


38/229


3

7. Determine yo ur next step based on w hether or not the install server is on

the same subnet as the s ystem to be i nstalled.

The install server is now created. N ext, you m ust ad d informa tion to the installservers configuration files so it recognizes the systems to be installed. Tocontinue, go to How to Set Up Servers for Netw ork Installation of aStandalone, Server, or Dataless Client on page 31.

If Instal l Server Is ... Then ...

On same subnet as thesystem to be installed

Go to Task Complete on page 26.

Not on the same subnetas the system to beinstalled

Follow the procedu re How to Create a Boot Server on aSubn et on page 27. You mu st complete this procedurewh en the install server is noton the same subnet as thesystem to be installed. After comp leting that p rocedu re,go to Task Complete on page 26.

TaskComplete


39/229


3

w How to Create a Boot Server on a Subnet

You can install Solaris software over the netw ork from an y install server on th enetwork. However, a system that will use an install server on another subnetrequires 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 thesubnet

Moun ting the Solaris CD

Using the setup_install_server -b command to copy requiredplatform inform ation from th e Solaris CD to th e local disk

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

1. On the system that will be the boot server for the subnet, log in and

become root.

This system must have a CD-ROM drive or an NFS mount of a Solaris CDimage. The system m ust also be in the N IS or N IS+ nam e service. (If your

site doesnt use th e NIS or NIS+ name service, you m ust d istributeinformation abou t this system by following you r sites p olicies.)

2. Determine yo ur next step based on w hether the boot server uses a local

CD-ROM drive or an NFS mount of a Solaris CD image.

If the Boot Server Uses .. . Then ...

Local CD-ROM drive 1) Insert the Solaris CD into the CD-ROM drive.2) Go to Step 3.

NFS mount of a SolarisCD image

1) mount -F nfs -o ro server_name:path /mnt

where server_name:path is the host name andabsolute path to the Solaris CD image.

2) cd /mnt3) Go to Step 4.


40/229


3


mounted CD:

If the Boot Se rver

Is ...

Then ...


cd /cdrom/cdrom0/s0


Note: Volume Man agement is run ning if the /vol directoryon the system contains files. Systems running Solaris 2.0 or2.1 do n ot have Volume Man agement.


1) mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom


2)cd /cdrom


41/229


3

4. Use the setup_install_server command to set up the boot server for

the subnet.

The setup_install_server command copies all sup ported platforminformation to th e local disk.

In this command ,

For example, the following comm and copies platform inform ation necessaryfor booting supp orted p latforms over the network:

./setup_install_server -b /export/install

Note The setup_install_server command will indicate if you do nothave enough disk space to copy the platform d ependent information. Use thedf -kl command to determine available disk space.

The boot server is now set up to boot supported systems on a subnet. Tocontinue, go to How to Set Up Servers for Netw ork Installation of aStandalone, Server, or Dataless Client on page 31.

# ./setup_install_server -b boot_dir_path

-b Specifies that the system w ill be set up as a bootserver.

boot_dir_path Specifies the directory wh ere the platforminformation w ill be copied. You can substitute anydirectory path.

TaskComplete


42/229


3

Sett ing Up Servers for Network Installation

This section d escribes how to set up app ropriate servers necessary to install asystem over a n etwork. The next table show s servers required for each systemtype you want to install.

Note When you install a server, you m ust allocate disk space required for theclients that server w ill supp ort. Then, afterthe server is installed, you mu st usethe Solstice Host Manager an d add the platform su pp ort required by thoseclients.

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

If System Type You Are Installing Is 1 . .. Then You Need This Server Support .. .

Stand alone system Install server

OS server Install server

Dataless client Install server and OS server


43/229


3

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

Once you h ave an install server set up, you are ready to u se it to install Solarissoftware on other systems on the network. Before you can actually do that,however, you need to provide some basic system information about thesystems that you are going to install. You do this by u sing the Solstice Host

Manager.

Note SunSoft plans to remove support for the dataless client system typeafter Solaris 2.5. You can set up this system typ e now, bu t in futu re releases youwill need to change it to a d ifferent ty pe (stand alone, OS server, diskless client,or AutoClient system.)

The procedure to add system information about standalone systems, servers,and dataless clients to the install server can all be accomp lished using th eSolstice Host Mana ger. You simp ly fill out a form an d app ly the informationyou provide, and the Solstice Host Manager updates the appropriate files andname server maps or tables.

Overview This procedu re involves:

Using the Solstice Host Manager to update the name service, to addinformation abou t the stand alone, server, or dataless client to the installserver s configu ration files, and, if necessary, to set up a file server

Follow th is procedure to set u p th e install server to install a standalone system,a server, or a d ataless client on the netw ork.

1. On the in stall server, log in as a user in the administration g roup

(group 14).

Caution If your system is part of the NIS+ name service, you must run theSolstice AdminSuite while logged in as a u ser in the N IS+ adm in group.Otherwise, you will not have permission to update configuration informationon the name server.

2. Start the Solstice AdminSuite with the follow ing command.

$ /usr/bin/solstice &


44/229


3

3. After the Solstice AdminSuite main windo w appears, click on the Host

Manager icon.

Note If your site uses the Dom ain N ame Service (DNS), you w ill have tomodify the /etc/nsswitch.conf file and create the /etc/resolv.conf fileman ually. For detailed information, see theN IS+ and FNS Administration Guide.

4. On the Ho st Manager: Select Naming Service screen, select a naming

service and click on the Apply button. See the sample Naming Service

screen below.

5. On the Host Manager main windo w, choose Ad d... from the Edit menu.

If the Name Service Is .. . Then Select .. .

NIS+ NIS+. Host Manager will update the NIS+ tables.

NIS NIS. Host Manager will upd ate the NIS maps.

None None. Host Manager will store the information youprovide in the /etc files. This will provide enoughinformation for systems to boot, and to install Solarissoftware over the network.


45/229


3

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

install.

S ys te m to Be In stal le d Is ... Th en ...

Standalone system Go to Step 7.

OS server Go to Step 10.

Dataless client Go to Step 13.


46/229


3

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

the OK or Apply button.

8. On the Host Manager main w indow, choose Save Changes from the File

menu.

9. Go to Task Complete on page 37.

Step 10 through Step 13 are only required if you are adding an OS server orda taless client.

Type - Select standalone.

Remote Install - Select if setting

up a network installation. The

install server should have beenset up already.

Install Server - If enabling remote

install for a network installation,

specify the install server and set

the path to the location of theSolaris CD image.

Profile Server - If using custom

JumpStart installations, specify

the system with the custom

Jumpstart profiles on it.

Boot Server - If the install client is

on a different subnet than the

install server, specify the boot

server that resides on the install

clients subnet.


47/229


3



11. On the Host Manager main windo w, choose S ave Changes from the File

menu.

12. Go to Task Complete on page 37.

Step 13 is required only for add ing da taless clients for netw ork installation.

Type - Select OS server.

Profile Server - If using custom

JumpStart installations, specify

the system with the custom

Jumpstart profiles on it.

Boot Server - If the install client is

on a different subnet than the

install server, specify the boot

server that resides on the install

clients subnet.

Remote Install - Select if setting

up a network installation. The

install server should have been

set up already.

Install Server - If enabling remote

install for a network installation,

specify the install server and set

the path to the location of the

Solaris CD image.


48/229


3



14. On the Host Manager main w indow, choose Save Changes from the File

menu.

File Server - Specify the system

that you want to provide /usr

file systems for the dataless

client.

OS Release - Select the OS

Release you want installed onthe dataless client. The proper

OS support must reside on the

install server. (You set up this

support by using Host Manager

after the server has been

installed. This is referred to as

adding services.


49/229


3

The standalone system, OS server, or dataless client is now added for networkinstallation. You are n ow ready to boot and install over the netw ork. To findthe correct booting and installing procedure in this book, see the appropriatechapter for the installation you want to perform:

Chap ter 7, Booting and Installing Solaris: Jum pStart

Chap ter 8, Booting an d Installing Solaris: Interactive

Chap ter 9, Booting and Installing Solaris: Custom Jum pStart

Using add_install_client to Set Up Servers for Network Installation

Install servers run ning v ersions of Solaris released pr ior to Solaris 2.4 softwa remay not have access to the Solstice AdminSuite. You can install the Solsticeprod ucts on Solaris 2.3 and 2.4 systems and follow the instructions in How to

Set Up Servers for N etwork Installation of a Stand alone, Server, or DatalessClient on page 31. Alternatively, you can u se the add_install_clientcommand to set up the install server for network installations, as described inthe n ext section.

TaskComplete


50/229


3

w How to Use add_install_client to Set Up Servers for NetworkInstallation

Use the add_install_client comm and to ad d information about thesystem to be installed to the boot server configuration files.

In this comman d,

For example, the following comm and copies boot informa tion from Solaris CDimage on an install server s local disk in /export/install.add_install_client sets up the /tftpboot directory on th e local system,

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

-c Specifies a Jump Start d irectory for customJum pStart installations. This option an d itsargum ents are required only for custom Jum pStartinstallations.

server:jumpstart_dir_path serveris the host name of the server on which theJum pStart d irectory is located.jumpstart_dir_pathis the absolute p ath of th e Jum pStart d irectory.

-s Specifies the install server.install_server:install_dir_path install_serveris the host n ame of the install server.

install_dir_path is the absolute path name of themounted Solaris CD or the directory that has thecopy of the Solaris CD image.

host_name Is the host name of the standalone system or theserver w here Solaris software w ill be installedover the n etwork. (This is not the h ost nam e of theinstall server). The host must be in the nameservice for this command to work.

platform group Is the platform g roup of the system to be installed.(For a d etailed list of platform grou ps, SeeApp endix C, Platform Nam es and Group s.)


51/229


3

wh ich w ill be the boot server. The system th at w ill be installed is nam edbasil, and it is a SPARCstation 10. The platform group for a SPARCstation10 is sun4m.

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

The standalone system, server, or dataless client is now added for networkinstallation. You are n ow ready to boot and install over the netw ork. To findthe booting and installing procedure in this book, see the appropriate chapterfor the installation you want to perform:

Chap ter 7, Booting and Installing Solaris: Jum pStart

Chap ter 8, Booting an d Installing Solaris: Interactive

Chap ter 9, Booting and Installing Solaris: Custom Jum pStart

TaskComplete


52/229


3

Preconfiguring the Default Locale

When installing a localized version of Solaris softwa re, you are p romp ted forthe locale (the language) you want to use for the duration of the installationprocess. The locale you choose for installing Solaris software is also the defaultlocale the installed version of Solaris will provide to the systems user.

You can set up a d efault locale of your choice. You do this by m odifying thenam ing service (NIS or N IS+). After you mod ify th e nam e service, as d escribedin this section, the op erating system will use th is default locale for users. Also,the installation software w ill use the d efault locale for all futu re installations.

Choose from the following tw o procedures, depending on w hether your siteuses the NIS or N IS+ nam e service.

w How to Preconfigure Default Locale Using NIS

Overview The p rocedure to p reconfigure the d efault locale at sites using theNIS nam e service involves:

Using the vi or text editor to ed it files in th e /var/yp/Makefile file

Creating a locale file in th e /etc directory

Upd ating the NIS maps

Follow th ese instructions to set up a d efault locale for the system beinginstalled over the network.


53/229


3

1. On the name server, log in and become root and edit the

/var/yp/Makefile file.

Add the following text after the other *.time entries.

2. 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.

locale.time: $(DIR)/locale

-@if [ -f $(DIR)/locale ]; then \

sed -e "/^#/d" -e s/#.*$$// $(DIR)/locale \

| awk '{for (i = 2; i


54/229


3

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

The entry sp ecifies the d efault locale for the d omain. For examp le, thefollowing line sp ecifies French to be the d efault locale for the worknet.com

domain:

worknet.com fr

You can also use a host name instead of the domain name to specify thedefault locale for a p articular host. For examp le, the following line sp ecifiesKorean to be the d efault locale for system n amed sherlock:

sherlock ko

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

Note Not all locales are available on all Solaris CDs. The locale you selectwill be used for installation if it is present on th e Solaris CD.

4. Make the maps.

Systems in the name service are now set up to use the default locale. Thedefault language you have specified will be used during the installation andwill also be the language provided to system users.

domain_name locale

# cd /var/yp; make

TaskComplete


55/229


3

w How to Preconfigure Default Locale Using NIS+

Overview The p rocedure to p reconfigure the d efault locale at sites using theNIS+ name service involves:

Using the nistbladm command to create a locale table and addinformation to it

Updating the NIS+ tables

Note The installation software is not translated to the A sian locales, so thisprocedure will not work for any of the Asian locales.

Follow th ese instructions to set up a d efault locale for a system being installedover the network. (This procedure assumes the NIS+ domain is set up. Settingup the NIS+ domain is documented in theN IS+ and FNS Administration Guide.)

1. Log in to a name server as root or as a user in the NIS+ admin group.

2. 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'


56/229


3

3. Add an entry to the locale.org_dir table by typing the following

nistbladm command.

In this command ,

Note Not all locales are available on all Solaris CDs. The locale you selectwill be used for installation if it is present on th e Solaris CD.

# nistbladm -a name=domain_name locale=locale comment=comment

locale.org_dir.'nisdefaults -d'

domain_name Is either the domain name or a specific host namefor w hich you wan t to preconfigure a d efaultlocale.

locale Is the locale you w ant to u se to install the systemand the locale you w ant to come up on userssystems. The following table show s valid valu esfor locale.

Language Valid locale Values

Chinese zhEnglish (Solaris default) CFrench frGerman deItalian itJapanese jaKorean koLatin American esSwedish svTaiw anese zh_TW

comment Is the comment field. Use double quotation marksto begin and end comments that are longer than

one word.


57/229


3

Systems in the name service are now set up to use the default locale. Thedefault language you have specified will be used during the installation andwill also be the language provided to system users.

TaskComplete


58/229


3


59/229

47

Preparing Custom JumpStartInstallations 4

Definition: Custom JumpStart Installation

A custom Jum pStart installation is a typ e of installation in w hich the Solarissoftware is autom atically installed on a system ba sed on a u ser-defin ed p rofile.You can create customized profiles for d ifferent typ es of users.

Note App endix D, Samp le Custom Jum pStart Installation provides anexample of how a fictitious site is prepared for custom Jump Start installations.

How to Create a JumpStart Directory on a Diskette for x 86 Syst ems page 53

How to Create a JumpStart Directory on a Diskette for S PARC Systems page 59

How to Create a JumpStart Directory on a Server page 63How to En able A ll Syst ems t o Access t he JumpStart D irectory page 65

How to Create a Profile page 67

How to Create the ru les File page 83

How to Use check t o Validate the rules File page 94


60/229


4

Note Instructions in this chap ter are v alid for either an x86 or SPARC serverthat is being u sed for custom Jum pStart installations. An x86 server canprovid e custom Jum pStart files for SPARC systems, and a SPARC system canprovid e custom Jum pStart files for x86 systems.

Reasons to Choose a Custom JumpStart InstallationYou should choose custom JumpStart installations when you have to installSolaris software on:

Many systems.

Particular groups of systems.

For example, the following scenario would be ideal for performing customJum pStart installations:

You need to install the Solaris software on 100 new systems.

The engineering group own s 70 out of the 100 new systems, and its systems

must be installed as standalone systems with the developer software group. The marketing group owns 30 out of the 100 new systems, and its systems

must be installed as standalone clients with the end user software group.

These installations would be time-consuming and tedious if you chose toperform a n interactive installation on each system .


61/229

Preparing Custom JumpStart Installations 49

4

Tasks to Prepare for Custom JumpStart Installations

Table 4-1 shows th e tasks that are requ ired to p repare for custom Jump Startinstallations.

Table 4-1 Tasks to Prepare for Custom JumpStart Installations

Task Description

Creating a Jump Startdirectory on a d iskette oron a server

You mu st create a Jump Start d irectory to h old th e customJumpStart files. If you are going to use a diskette forcustom Jump Start installations, see Creating a Jum pStartDirectory on a Diskette on p age 53. If you are going touse a server for custom JumpStart installations, seeCreating a Jump Start Directory on a Server on p age 62.

Enabling a ll clients toaccess the JumpStartdirectory

When you use a server to provid e the Jum pStart directory,you can enab le all clients to access the Jum pStart d irectory.See Enabling All Systems to A ccess the Jump StartDirectory on p age 65 for detailed information.

Creating profiles A profile is a text file used as a template by the customJumpStart installation software. It defines how to installthe Solaris software on a system (for example, initial orup grade installation op tion, system typ e, disk partitioning,software group), and it is named in the rules file. SeeCreating a Profile on p age 67 for detailed information.

Creating a rules file The rules file is a text file used to create the rules.okfile. The rules file is a look-up table consisting of one ormore ru les that define matches between system attributesand profiles. See Creating the ru les File on p age 82 fordetailed information.

Using check to validateth e rules file

The rules.ok file is a generated version of the rules file,and it is required b y the custom Jum pStart installationsoftware to match a system to a profile. You mustuse thecheck script to create the rules.ok file. See Using checkto Validate th e ru les File on page 93 for d etailedinformation.

Or

Profile

keyword

keyword

keyword

rules File

rule 1

rule 2

rule 3

rules.ok Filerules File

rule 1

rule 2

rule 3

rule 1

rule 2

rule 3

check


62/229


4

What Happens During a Custom JumpStart Installation

Figure 4-1 describes w hat hap pens after you boot a system to p erform acustom Jump Start installation.

Figure 4-1 What Happens During a Custom JumpStart Installation

BEGIN

The system proceeds with a

custom JumpStart installa-

tion. The profile specified in

the matched rule is used to

install the system.

Yes

END

Does the system find a dis-

kette in the systems diskette

drive?

Does the system find

a rules.ok file on the

diskette?

YesDoes the system match any

rules in the rules.ok file?Does the system find a

rules.ok file on a designated

server?

No No

Yes

The system proceeds with

an interactive installation.

END

NoNo

The system mounts

the diskette.Yes


63/229


4

Figure 4-2 is an example of how a custom Jump Start installation w orks on astandalone, non-networked system using the systems diskette drive.

Figure 4-2 How a Custom Jump Start Installation Works: Non-Networked Examp le

rules.ok File

rule 1

rule 2

rule 3

EngineeringGroupsProfile

MarketingGroupsProfile

PetesProfile

JumpStart Directory

Pete's System

After the system boots,

the Solaris installation

program finds a rules.ok

file on the diskette in the

systems diskette drive.

The Solaris installation pro-

gram finds a matching rule

for Petes system.

The matched rule specifies a

profile to use for installing

Solaris on Petes system.

The Solaris installation pro-

gram uses the selected profile

to automatically install the

Solaris software on Petes sys-

tem.


64/229


4

Figure 4-3 is an examp le of how a custom Jump Start installation w orks formultiple systems on a network where different profiles are accessed from asingle server.

Figure 4-3 How a Custom Jum pStart Installation Works: Networ ked Example

rules.ok

File

rule 1

rule 2

rule 3

EngineeringGroupsProfile

MarketingGroupsProfile

PetesProfile

JumpStart Directory

Engineerings Systems

Marketings Systems

Petes System

The Solaris installation program

uses the selected profile to auto-

matically install the Solaris soft-

ware on the system.

The matched rule speci-

fies a profile to use for

installing the Solaris soft-

ware on a that system.

Solaris installation pro-

gram finds a matching rule

for the specific system.

After a system boots, the

Solaris installation pro-

gram finds a rules.ok fileon designated server.


65/229


4

Creating a JumpStart Directory on a Diskette

You sh ould use a d iskette for a custom Jum pStart installation if the system:

Has a diskette drive H as a local CD-ROM d rive Is not connected to a network

When you use a diskette for custom JumpStart installations, the JumpStartdirectory must be the root directory on the diskette that contains all theessential custom Jum pStart installation fi les (for example, the rules file,rules.ok file, and profiles). The Jum pStart directory should be ow ned by rootand have permissions equal to 755.

The diskette requ irements for the Jum pStart d irectory are d ifferent for x86 andSPARC systems. So, the following pag es describe how to create a Jump Startdirectory on a diskette for an x86 system and for a SPARC system.

w How to Create a JumpStart Directory on a Diskette for x86 Systems

Overview The procedu re to create a Jum pStart d irectory on a d iskette for x86systems involves:

Making a copy of the Solaris boot diskette (the copied Solaris boot d iskettehas a PCFS file system)

Copying samp le custom Jum pStart installation files into th e diskettes rootdirectory

Follow th is procedu re to create a Jum pStart d irectory on a d iskette for x86systems.

1. Log in as root on an x86 or SPARC system that has a diske tte drive and a

CD-ROM drive.

2. Insert the Solaris boot diske tte into the diskette drive.


66/229


4

3. Choose the appropriate steps, depending on w hether or not the system is

running Volume Management:

4. Make sure Volume Management know s about the diskette:

5. Copy the Solaris boot diske tte image to the systems hard disk:

In this command ,

For example, the following command would copy a Solaris boot diskette toth e boot_save file.

dd if=/vol/dev/aliases/floppy0 of=boot_save

If the System Is ... Then ...


Go to Step 4.

Note: Volume Man agement is run ning if the /voldirectory on the system contains files. Systems ru nningSolaris 2.0 or 2.1 do not have Volume Management.

Not running VolumeManagement

Go to Step 12.

# volcheck

# dd if=/vol/dev/aliases/floppy0 of=boot_image

boot_image Is the file name w here the Solaris boot d isketteimage is copied. You can specify an absolute p athname.


67/229


4

6. Eject the Solaris boot diskette:

Note The following command is not required for x86 systems; you mustman ually eject the d iskette on an x86 system.

7. Insert a blank diskette into the diske tte drive.


9. Format the diskette:

10. Copy the Solaris boo t diskette image from the sy stems hard disk to the

formatted di skette:

The boot_image variable should be the same as in Step 5.

11. Go to Step 17.Step 12 through Step 16 are used if the system is not running VolumeManagement.

# eject floppy

# volcheck

# fdformat -d -U

# dd if=boot_image of=/vol/dev/aliases/floppy0

Caution This step will overwrite any data on the diskette.

!


68/229


4

12. Copy the Solaris boot diske tte image to the systems hard disk:

In this command ,

For example, the following command would copy a Solaris boot diskette toth e boot_save file.

dd if=/dev/rdiskette of=boot_save

13. Eject the Solaris boot disk ette:

Note The following command is not required for x86 systems; you must

man ually eject the d iskette on an x86 system.

14. Insert a blank diskette into the diske tte drive.


# dd if=/dev/rdiskette of=boot_image

boot_image Is the file name w here the Solaris boot d isketteimage is copied. You can specify an absolute p athname.

# eject fd

# fdformat -d


!


69/229


4

16. Copy the Solaris boo t diskette image from the sy stems hard disk to the

formatted di skette:

The boot_image variable should be the same as in Step 12.

17. Mount the diskette:

18. Determine your next step based on w here the Solaris CD is located.

# dd if=boot_image of=/dev/rdiskette



1) Eject the copied Solaris boot diskette.2) Insert the copied Solaris boot diskette back into thediskette drive.3) Make sure Volume Management knows about thediskette:volcheck


mount -F pcfs /dev/diskettejump_dir_path

Note: jump_dir_path is the absolute d irectory path wh erethe diskette is mounted.

If You Want to Use The ... Then ...

Solaris CD in the localCD-ROM drive

1) Insert the Solaris CD into the CD-ROM drive.2) Go to Step 19.

Solaris CD image on localdisk

1) Change the d irectory to the Solaris CD image on thelocal disk. For example:cd /export/install

2) Go to Step 20.


70/229


4


mounted CD:

20. Copy the JumpStart installation files from the auto_install_sample

directory on the Solaris CD in to the Jump Start directory (root directory) of

the diskette:

Note The custom Jump Start installation files mu st be in the root directory ofthe diskette.

You have com pleted creating a Jum pStart d irectory on the d iskette. Tocontinue, see How to Create a Profile on page 67.

If th e S ys te m Is ... Th en ...


cd /cdrom/cdrom0/s0


Not run ning VolumeManagement

1)mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom


2)cd /cdrom


Running Volume

Management

cp -r auto_install_sample/* /floppy/floppy0/.


cp -r auto_install_sample/*jumpstart_dir_path

Note: jump_dir_path is the absolute d irectory path wh ere thediskette is mounted.

Caution File names on PCFS file systems can be only 11 characters long (an8-character file name and a 3-character extension). When copying Jump Startinstallation files to a d iskette for x86 systems, be aw are that the file tran sfermay truncate file names.

!

TaskComplete


71/229


4

w How to Create a JumpStart Directory on a Diskette for SPARC Systems

Overview The procedure to create a Jump Start d irectory on a d iskette forSPARC systems involves:

Formatting a d iskette (if needed).

Creating a U FS file system on the d iskette (if needed).

Copying samp le custom Jum pStart installation files into th e diskettes rootdirectory.

Follow th is procedu re to create a Jum pStart d irectory on a d iskette for SPARCSystems.

1. Log in as root on a SPARC system that has a diskette drive and a

CD-ROM drive.

2. Insert a diskette into the diskette drive.

3. Choose the appropriate steps, depending on w hether or not the system isrunning Volume Management:


If the Sys te m Is ... Then ...


Go to Step 4.

Note: Volume Man agement is run ning if the /voldirectory on the system contains files. Systems ru nningSolaris 2.0 or 2.1 do not have Volume Management.


Go to Step 12.

# volcheck


72/229


4

5. If the diskette already has a UFS file system on it, go to Step 16.

To find out if the diskette has a UFS file system on it, check the/etc/mnttab file for an entry similar to this:

/floppy/unnamed_floppy ufs


7. Create a UFS file sy stem on the diskette:

8. Eject the diskette:

9. Insert the formatted diskette back into the d iskette drive.

10. Make sure Volume Management knows about the diskette:

11. Go to Step 16.

Step 12 through Step 15 are used if the system is not running VolumeManagement.

12. If the diskette already has a UFS file system on it, go to Step 15.

If the mount comm and fails in Step 15, the diskette does not have a UFS filesystem on it.

# fdformat -U

# newfs /vol/dev/aliases/floppy0

# eject floppy

# volcheck


!


73/229


4


14. Create a file system on the diskette:

15. Mount the diskette:

In this command ,

jumpstart_dir_path Is the absolute directory path where the diskette ismounted.

For examp le, the following comm and wou ld mou nt a SPARC diskette on the/mnt directory:

mount -F ufs /dev/rdiskette /mnt

Note If the mount command fails, go back to Step 13 to format the d iskette.


# fdformat /dev/rdiskette

# newfs /dev/rdiskette

#mount -F ufs /dev/diskette jumpstart_dir_path

If You Want to Use The .. . Then ...



Solaris CD image on thelocal disk

1) Change th e directory to th e Solaris CD image on thelocal disk. For example:cd /export/install

2) Go to Step 18.


!


74/229


4


mounted CD:

18. Copy the custom JumpStart installation files from the

auto_install_sample directory on the So laris CD i nto the JumpStart

directory (root directory) of the diskette:

Note The custom Jump Start installation files mu st be in the root directory ofthe diskette.

You have com pleted creating a Jum pStart d irectory on the d iskette. Tocontinue, see How to Create a Profile on page 67.

Creating a JumpStart Directory on a Server

If you w ant to perform custom Jum pStart installations by using a server on thenetwork, you must create a JumpStart directory on the server. When you use aserver for custom Jump Start installations, the Jum pStart d irectory is a d irectory

If the Sys tem Is ... Th en ...


cd /cdrom/cdrom0/s0



1)mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom


2)cd /cdrom



cp -r auto_install_sample/* /floppy/floppy0/.


cp -r auto_install_sample/*jumpstart_dir_path

Note: jump_dir_path is the absolute d irectory path wh ere thediskette is mounted.

TaskComplete


75/229


4

on th e server tha t contains all the essential custom Jum pStart files (forexample, the rules file, rules.ok file, and profiles). The Jump Start d irectoryshould be ow ned by root and have p ermissions equal to 755.

w How to Create a JumpStart Directory on a Server

Overview The procedu re to create a Jum pStart directory on a serv er involves:

Creating a directory on the server

Editing the /etc/dfs/dfstab file

Copying sam ple custom Jump Start installation files into the d irectory on theserver

Follow th is procedure to create a Jum pStart directory on a server.

1. Log in as root on the s erver wh ere you w ant the JumpS tart directory to

reside.

2. Create the JumpStart directory anyw here on the s erver:

In this command ,

For example, the following command would create the directory calledjumpstart in the root file system:

mkdir /jumpstart

3. Edit the /etc/dfs/dfstab file. Add the follow ing entry:

For examp le, the following entry w ould be correct for the examp le shown inStep 2:

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

#mkdir jumpstart_dir_path

jumpstart_dir_path Is the absolute p ath of th e Jum pStart d irectory.

share -F nfs -o ro,anon=0 jumpstart_dir_path


76/229


4

4. Type unshareall and p ress Return.

5. Type shareall and press Return.



mounted CD:

8. Copy the contents of the auto_install_sample directory from the

Solaris CD-ROM into the JumpStart directory:

For example, the following command wou ld copy theauto_install_sample directory into the Jump Start d irectory created inStep 2:

If You Want to Use The .. . Then ...



Solaris CD image on thelocal disk

1) Change the d irectory to the Solaris image on th elocal disk. For example:cd /export/install

2) Go to Step 8.


Running Volume

Management

cd /cdrom/cdrom0/s0


Note: Volume Man agement is run ning if the /vol directory onthe system contains files. Systems r un ning Solaris 2.0 or 2.1 donot have Volume Man agement.


1)mount -F hsfs -o ro /dev/dsk/c0t6d0s0

installing solaris on sparc

Documents