Solaris 10 System Administration Essentials Engineers Solaris Systemcreator

Solaris 10 System Administration Essentials
Engineers Solaris Systemcreator download
https://ebookbell.com/product/solaris-10-system-administration-
essentials-engineers-solaris-systemcreator-22123632
Explore and download more ebooks at ebookbell.com

Here are some recommended products that we believe you will be
interested in. You can click the link to download.
Solaris 10 System Administration Your Complete Certification Solution
Pt 1 Exam Cx310200 2 Ed Calkins
https://ebookbell.com/product/solaris-10-system-administration-your-
complete-certification-solution-pt-1-exam-cx310200-2-ed-
calkins-21983800
Solaris 10 System Administration Exam Cx310200 Exam Cx310202 With
Cdrom Calkins
https://ebookbell.com/product/solaris-10-system-administration-exam-
cx310200-exam-cx310202-with-cdrom-calkins-22123634
Sun Certified System Administrator For Solaris 10 Study Guide Exams
Cx310200 And Cx310202 1st Edition Paul Sanghera
https://ebookbell.com/product/sun-certified-system-administrator-for-
solaris-10-study-guide-exams-cx310200-and-cx310202-1st-edition-paul-
sanghera-1279440
Oracle Solaris 10 System Virtualization Essentials Jeff Victor
https://ebookbell.com/product/oracle-solaris-10-system-virtualization-
essentials-jeff-victor-2309916

Solaris 10 Zfs Essentials Watanabe Scott
https://ebookbell.com/product/solaris-10-zfs-essentials-watanabe-
scott-21995790
Solaris 10 Security Essentials Press Sun Microsystemscreator
https://ebookbell.com/product/solaris-10-security-essentials-press-
sun-microsystemscreator-22123630
Solaris 10 The Complete Reference 1st Edition Paul Watters
https://ebookbell.com/product/solaris-10-the-complete-reference-1st-
edition-paul-watters-984016
Solaris 10 The Complete Reference Watters
https://ebookbell.com/product/solaris-10-the-complete-reference-
watters-1020868
Solaris 10 Zfs Essentials Scott Watanabe
https://ebookbell.com/product/solaris-10-zfs-essentials-scott-
watanabe-56659384

Solaris™
10 System
Administration Essentials

This page intentionally left blank

Solaris™
10 System
Administration Essentials
Solaris System Engineers
Sun Microsystems Press
Upper Saddle River, NJ • Boston • Indianapolis • San Francisco
New York • Toronto • Montreal • London • Munich • Paris • Madrid
Capetown • Sydney • Tokyo • Singapore • Mexico City

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as
trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim,
the designations have been printed with initial capital letters or in all capitals.
The authors and publisher have taken care in the preparation of this book, but make no expressed or implied
warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental
or consequential damages in connection with or arising out of the use of the information or programs contained
herein.
Sun Microsystems, Inc., has intellectual property rights relating to implementations of the technology
described in this publication. In particular, and without limitation, these intellectual property rights may
include one or more U.S. patents, foreign patents, or pending applications. Sun, Sun Microsystems, the Sun
logo, J2ME, J2EE, Solaris, Java, Javadoc, Java Card, NetBeans, and all Sun and Java based trademarks and
logos are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other
countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed
through X/Open Company, Ltd.
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 A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD
INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY
ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDI-
TIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC., MAY MAKE IMPROVEMENTS AND/OR
CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT
ANY TIME.
The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special
sales, which may include electronic versions and/or custom covers and content particular to your business,
training goals, marketing focus, and branding interests. For more information, please contact:
U.S. Corporate and Government Sales
(800) 382-3419
corpsales@pearsontechgroup.com
For sales outside the United States please contact:
International Sales, international@pearsoned.com
Visit us on the Web: informit.com/ph
Library of Congress Cataloging-in-Publication Data
Solaris 10 system administration essentials / Solaris system engineers.
p. cm.
Includes index.
ISBN 978-0-13-700009-8 (pbk. : alk. paper)
1. Electronic data processing—Management. 2. Systems software. 3.
Solaris (Computer ﬁle) I. Sun Microsystems.
QA76.9.M3S65 2009
005.4’3—dc22
2009034498
Copyright © 2010 Sun Microsystems, Inc.
4150 Network Circle, Santa Clara, California 95054 U.S.A.
All rights reserved.
Printed in the United States of America. This publication is protected by copyright, and permission must be
obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmis-
sion in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For informa-
tion regarding permissions, write to:
Pearson Education, Inc.
Rights and Contracts Department
501 Boylston Street, Suite 900
Boston, MA 02116
Fax: (617) 671-3447
ISBN-13: 978-0-13-700009-8
ISBN-10: 0-13-700009-X
Text printed in the United States on recycled paper at RR Donnelley in Crawfordsville, Indiana.
First printing, November 2009

v
Contents
Preface xvii
About the Authors xxi
Chapter 1 Installing the Solaris 10 Operating System 1
1.1 Methods to Meet Your Needs 1
1.2 The Basics of Solaris Installation 2
1.2.1 Installing Solaris on a SPARC System 6
1.2.2 Installing Solaris on an x86 System 9
1.3 Solaris JumpStart Installation 13
1.3.1 Setting up a JumpStart Server 13
1.3.2 Creating a Proﬁle Server for Networked Systems 14
1.3.3 Performing a Custom JumpStart Installation 22
1.4 Upgrading a Solaris System 25
1.5 Solaris Live Upgrade 26
Chapter 2 Boot, Service Management, and Shutdown 33
2.1 Boot 33
2.1.1 The Bootloader 33
2.1.2 The Kernel 34
2.1.3 User-Mode Programs 34
2.1.4 GRUB Extensions 35

vi Contents
2.1.5 Modifying Boot Behavior 36
2.1.6 Run Levels 37
2.1.7 Troubleshooting 37
2.2 Service Management Facility 39
2.2.1 enabled 40
2.2.2 state, next_state, and state_time 40
2.2.3 logfile 41
2.2.4 dependency 41
2.2.5 How SMF Interacts with Service Implementations 42
2.2.6 The Service Conﬁguration Facility 44
2.2.7 Health and Troubleshooting 44
2.2.8 Service Manifests 45
2.2.9 Backup and Restore of SCF Data 45
2.3 Shutdown 46
2.3.1 Application-Speciﬁc Shutdown 46
2.3.2 Application-Independent Shutdown 46
Chapter 3 Software Management: Packages 47
3.1 Managing Software Packages 47
3.2 What Is a Package? 47
3.2.1 SVR4 Package Content 48
3.2.2 Package Naming Conventions 49
3.3 Tools for Managing Software Packages 49
3.4 Installing or Removing a Software Package with the
pkgadd or pkgrm Command 50
3.5 Using Package Commands to Manage Software Packages 51
3.5.1 How to Install Packages with the pkgadd
Command 51
3.5.2 Adding Frequently Installed Packages to a Spool
Directory 54
3.5.3 Removing Software Packages 56
Chapter 4 Software Management: Patches 59
4.1 Managing Software with Patches 59
4.2 What Is a Patch? 59
4.2.1 Patch Content 60
4.2.2 Patch Numbering 61

Contents vii
4.3 Patch Management Best Practices 61
4.3.1 Proactive Patch Management Strategy 62
4.3.2 Reactive Patch Management Strategy 68
4.3.3 Security Patch Management Strategy 70
4.3.4 Proactive Patching When Installing a New System 71
4.3.5 Identifying Patches for Proactive Patching and
Accessing Patches 73
4.4 Example of Using Solaris Live Upgrade to
Install Patches 75
4.4.1 Overview of Patching with Solaris Live Upgrade 75
4.4.2 Planning for Using Solaris Live Upgrade 77
4.4.3 How to Apply a Patch When Using Solaris Live
Upgrade for the Solaris 10 8/07 Release 79
4.5 Patch Automation Tools 86
4.6 Overview of Patch Types 88
4.7 Patch README Special Instructions 93
4.7.1 When to Patch in Single-User Mode 93
4.7.2 When to Reboot After Applying or Removing a Patch 94
4.7.3 Patch Metadata for Non-Global Zones 95
4.8 Patch Dependencies (Interrelationships) 96
4.8.1 SUNW_REQUIRES Field for Patch Dependencies 96
4.8.2 SUNW_OBSOLETES Field for Patch Accumulation
and Obsolescence 97
4.8.3 SUNW_INCOMPAT Field for Incompatibility 97
Chapter 5 Solaris File Systems 99
5.1 Solaris File System Overview 99
5.1.1 Mounting File Systems 100
5.1.2 Unmounting File Systems 102
5.1.3 Using the /etc/vfstab File 103
5.1.4 Determining a File System Type 104
5.1.5 Monitoring File Systems 105
5.2 UFS File Systems 105
5.2.1 Creating a UFS File System 106
5.2.2 Backing Up and Restoring UFS File Systems 107
5.2.3 Using Quotas to Manage Disk Space 108
5.2.4 Checking File System Integrity 110

viii Contents
5.2.5 Using Access Control Lists 112
5.2.6 Using UFS Logging 113
5.2.7 Using Extended File Attributes 115
5.2.8 Using Multiterabyte UFS File Systems 115
5.2.9 Creating UFS Snapshots 115
5.3 ZFS File System Administration 117
5.3.1 Using Pools and File Systems 118
5.3.2 Backing Up a ZFS File System 120
5.3.3 Using Mirroring and Striping 121
5.3.4 Using RAID-Z 122
5.3.5 Using Copy-on-Write and Snapshots 122
5.3.6 Using File Compression 124
5.3.7 Measuring Performance 124
5.3.8 Expanding a Pool 125
5.3.9 Checking a Pool 126
5.3.10 Replacing a Disk 127
5.4 NFS File System Administration 127
5.4.1 Finding Available NFS File Systems 128
5.4.2 Mounting an NFS File System 129
5.4.3 Unmounting an NFS File System 129
5.4.4 Conﬁguring Automatic File System Sharing 130
5.4.5 Automounting File Systems 130
5.5 Removable Media 133
5.5.1 Using the PCFS File System 135
5.5.2 Using the HSFS File System 136
5.6 Pseudo File System Administration 136
5.6.1 Using Swap Space 136
5.6.2 Using the TMPFS File System 138
5.6.3 Using the Loopback File System 139
Chapter 6 Managing System Processes 141
6.1 Overview 141
6.1.1 State of a Process 143
6.1.2 Process Context 143
6.2 Monitoring the Processes 145
6.2.1 Process Status: ps 146

Contents ix
6.2.2 Grepping for Process: pgrep 149
6.2.3 Process Statistics Summary: prstat 149
6.2.4 Reap a Zombie Process: preap 151
6.2.5 Temporarily Stop a Process: pstop 152
6.2.6 Resuming a Suspended Process: prun 152
6.2.7 Wait for Process Completion: pwait 152
6.2.8 Process Working Directory: pwdx 152
6.2.9 Process Arguments: pargs 152
6.2.10 Process File Table: pfiles 153
6.2.11 Process Libraries: pldd 154
6.2.12 Process Tree: ptree 154
6.2.13 Process Stack: pstack 155
6.2.14 Tracing Process: truss 156
6.3 Controlling the Processes 158
6.3.1 The nice and renice Commands 158
6.3.2 Signals 159
6.4 Process Manager 164
6.5 Scheduling Processes 170
6.5.1 cron Utility 171
6.5.2 The at Command 175
Chapter 7 Fault Management 179
7.1 Overview 179
7.2 Fault Notiﬁcation 181
7.3 Displaying Faults 182
7.4 Repairing Faults 184
7.5 Managing Fault Management Log Files 184
7.5.1 Automatic Log Rotation 185
7.5.2 Manual Log Rotation 186
7.5.3 Log Rotation Failures 187
7.5.4 Examining Historical Log Files 188
7.6 Managing fmd and fmd Modules 188
7.6.1 Loading and Unloading Modules 189
7.6.2 fmd Statistics 191
7.6.3 Conﬁguration Files 192

x Contents
7.7 Fault Management Directories 193
7.8 Solaris Fault Management Downloadable Resources 193
7.8.1 Solaris FMA Demo Kit 193
7.8.2 Events Registry 194
Chapter 8 Managing Disks 197
8.1 Hard Disk Drive 197
8.2 Disk Terminology 199
8.3 Disk Device Naming Conventions 200
8.3.1 Specifying the Disk Subdirectory in Commands 202
8.4 Overview of Disk Management 202
8.4.1 Device Driver 202
8.4.2 Disk Labels (VTOC or EFI) 203
8.4.3 Disk Slices 205
8.4.4 Slice Arrangements on Multiple Disks 207
8.4.5 Partition Table 208
8.4.6 format Utility 210
8.4.7 format Menu and Command Descriptions 211
8.4.8 Partition Menu 213
8.4.9 x86: fdisk Menu 214
8.4.10 Analyze Menu 215
8.4.11 Defect Menu 217
8.5 Disk Management Procedures 217
8.5.1 How to Identify the Disks on a System 218
8.5.2 How to Determine If a Disk Is Formatted 218
8.5.3 How to Format a Disk 219
8.5.4 How to Identify a Defective Sector by Performing a
Surface Analysis 221
8.5.5 How to Repair a Defective Sector 222
8.5.6 How to Display the Partition Table or Slice
Information 223
8.5.7 Creating Disk Slices (Partitioning a Disk) and
Labeling a Disk 224
8.5.8 Creating a File System On a Disk 228
8.5.9 Additional Commands to Manage Disks 229

Contents xi
Chapter 9 Managing Devices 235
9.1 Solaris Device Driver Introduction 235
9.2 Analyzing Lack of Device Support 236
9.2.1 Device Does Not Work 236
9.2.2 Obtaining Information About Devices 236
9.2.3 Obtaining Information About Drivers 241
9.2.4 Does the Device Have a Driver? 248
9.2.5 Current Driver Does Not Work 250
9.2.6 Can a Driver for a Similar Device Work? 250
9.3 Installing and Updating Drivers 251
9.3.1 Backing Up Current Functioning Driver Binaries 251
9.3.2 Package Installations 252
9.3.3 Install Time Updates 252
9.3.4 Manual Driver Binary Installation 253
9.3.5 Adding a Device Driver to a Net Installation Image 256
9.3.6 Adding a Device Driver to a CD/DVD
Installation Image 262
9.3.7 Swapping Disks 263
9.4 When Drivers Hang or Panic the System 266
9.4.1 Device Driver Causes the System to Hang 266
9.4.2 Device Driver Causes the System to Panic 268
9.4.3 Device Driver Degrades System Performance 269
9.5 Driver Administration Commands and Files 270
9.5.1 Driver Administration Command Summary 270
9.5.2 Driver Administration File Summary 272
Chapter 10 Solaris Networking 275
10.1 Introduction to Network Configuration 275
10.1.1 Overview of the TCP/IP Networking Stack 275
10.1.2 Configuring the Network as Superuser 277
10.2 Setting Up a Network 277
10.2.1 Components of the XYZ, Inc. Network 277
10.2.2 Configuring the Sales Domain 280
10.2.3 Configuring the Accounting Domain 283
10.2.4 Configuring the Multihomed Host 288

xii Contents
10.2.5 Setting Up a System for Static Routing 296
10.2.6 Configuring the Corporate Domain 300
10.2.7 Testing the Network Configuration 302
10.3 Monitoring Network Performance 304
10.3.1 dladm Command 304
10.3.2 ifconfig Command 305
10.3.3 netstat Command 305
10.3.4 snoop Command 307
10.3.5 traceroute Command 308
Chapter 11 Solaris User Management 309
11.1 Solaris Users, Groups, and Roles 309
11.1.1 File System Object Permissions 310
11.1.2 User Account Components 312
11.1.3 User Management Tools 313
11.1.4 User Management Files 313
11.2 Managing Users and Groups 314
11.2.1 Starting the Solaris Management Console 314
11.2.2 Adding a Group and a User to Local Files 315
11.2.3 Adding a Group and a User to an NIS Domain 317
11.3 Managing Roles 318
11.3.1 Changing root from a User to a Role 318
11.3.2 Viewing the List of Roles 319
11.3.3 Assigning a Role to a Local User 319
Chapter 12 Solaris Zones 321
12.1 Overview 321
12.2 How Zones Work 323
12.3 Branded Zones 324
12.4 Network Interfaces in Zones 324
12.5 Devices in Zones 325
12.6 Packages and Patches in a Zones Environment 325
12.7 Administering Zones 326
12.7.1 Zone Configuration 327
12.7.2 Viewing a Zone Configuration 331
12.7.3 Zone Installation and Booting 331
12.7.4 Zone Login Using the zlogin Command 332

Contents xiii
12.8 Halting, Uninstalling, Moving, and Cloning Zones 333
12.9 Migrating a Zone to a New System 334
12.10 Deleting a Zone 336
12.11 Listing the Zones on a System 336
12.12 Zones Usage Examples 337
12.12.1 Adding a Dedicated Device to a Non-Global Zone 337
12.12.2 How to Export Home Directories in the Global Zone
into a Non-Global Zone 337
12.12.3 Altering Privileges in a Non-Global Zone 337
12.12.4 Checking the Status of SMF Services 338
12.12.5 Modifying CPU, Swap, and Locked Memory Caps
in Zones 338
12.12.6 Using the Dtrace Program in a Non-Global Zone 339
Chapter 13 Using Naming Services 341
13.1 Using Naming Services (DNS, NIS, AND LDAP) 341
13.1.1 Naming Service Cache Daemon (nscd) 342
13.1.2 DNS Naming Services 342
13.1.3 NIS Naming Services 342
13.1.4 LDAP Naming Services 343
13.1.5 Organizational Use of Naming Services 343
13.1.6 Network Database Sources 344
13.2 Name Service Switch File 347
13.2.1 Configuring the Name Service Switch File 347
13.2.2 Database Status and Actions 349
13.3 DNS Setup and Configuration 350
13.3.1 Resolver Files 350
13.3.2 Steps DNS Clients Use to Resolve Names 350
13.4 NIS Setup and Configuration 351
13.4.1 Setting Up NIS Clients 351
13.4.2 Working with NIS Maps 352
13.5 LDAP Setup and Configuration 356
13.5.1 Initializing a Client Using Per-User Credentials 357
13.5.2 Configuring an LDAP Client 359
13.5.3 Using Profiles to Initialize an LDAP Client 362
13.5.4 Using Proxy Credentials to Initialize an LDAP Client 362
13.5.5 Initializing an LDAP Client Manually 363

xiv Contents
13.5.6 Modifying a Manual LDAP Client Configuration 363
13.5.7 Troubleshooting LDAP Client Configuration 364
13.5.8 Uninitializing an LDAP Client 364
13.5.9 Initializing the Native LDAP Client 364
13.5.10 LDAP API Entry Listings 368
13.5.11 Troubleshooting Name Service Information 368
Chapter 14 Solaris Print Administration 369
14.1 Overview of the Solaris Printing Architecture 369
14.2 Key Concepts 370
14.2.1 Printer Categories (Local and Remote Printers) 370
14.2.2 Printer Connections (Directly Attached and
Network Attached) 370
14.2.3 Description of a Print Server and a Print Client 371
14.3 Solaris Printing Tools and Services 371
14.3.1 Solaris Print Manager 371
14.3.2 LP Print Service 371
14.3.3 PostScript Printer Definitions File Manager 372
14.4 Network Protocols 372
14.4.1 Berkeley Software Distribution Protocol 372
14.4.2 Transmission Control Protocol 372
14.4.3 Internet Printing Protocol 373
14.4.4 Server Message Block Protocol 373
14. 5 Planning for Printer Setup 373
14. 5.1 Print Server Requirements 373
14. 5.2 Locating Information About Supported Printers 374
14. 5.3 Locating Information About Available PPD Files 375
14. 5.4 Adding a New PPD File to the System 375
14. 5.5 Adding Printers in a Naming Service 377
14. 5.6 Printer Support in the Naming Service Switch 377
14. 5.7 Enabling Network Listening Services 378
14.6 Setting Up Printers with Solaris Printer Manager 379
14.6.1 Assigning Printer Definitions 379
14.6.2 Starting Solaris Print Manager 380
14.6.3 Setting Up a New Directly Attached Printer With
Solaris Print Manager 381

Contents xv
14.6.4 Setting Up a New Network-Attached Printer with
Solaris Print Manager 381
14.7 Setting Up a Printer on a Print Client with Solaris
Print Manager 385
14.7.1 Adding Printer Access With Solaris
Print Manager 385
14.8 Administering Printers by Using LP Print
Commands 385
14.8.1 Frequently Used LP Print Commands 386
14.8.2 Using the lpstat Command 386
14.8.3 Disabling and Enabling Printers 387
14.8.4 Accepting or Rejecting Print Requests 387
14.8.5 Canceling a Print Request 388
14.8.6 Moving Print Requests from One Printer to
Another Printer 389
14.8.7 Deleting a Printer 390
14.9 Troubleshooting Printing Problems 392
14.9.1 Troubleshooting No Output (Nothing Prints) 392
14.9.2 Checking That the Print Scheduler Is Running 393
14.9.3 Debugging Printing Problems 393
14.9.4 Checking the Printer Network Connections 394
Index 395

xvii
Preface
Solaris™ 10 System Administration Essentials
Solaris™ 10 System Administration Essentials is the centerpiece of the new series
on Solaris system administration. It covers all of the breakthrough features of
the Solaris 10 operating system in one place. Other books in the series, such as
Solaris™ 10 Security Essentials and Solaris™ 10 ZFS Essentials, cover specific
features and aspects of the Solaris OS in detail.
Solaris™ 10 System Administration Essentials is the most comprehensive book
about Solaris 10 on the market. It covers the significant features introduced with
the initial release of Solaris 10 and the features, like ZFS, introduced in subse-
quent updates.
The Solaris OS has a long history of innovation. The Solaris 10 OS is a water-
shed release that includes features such as:
Zones/Containers, which provide application isolation and facilitate server
consolidation
ZFS, the file system that provides a new approach to managing your data
with an easy administration interface
The Fault Management Architecture, which automates fault detection
and resolution

xviii Preface
The Service Management Facility, a unified model for services and service
management on every Solaris system
Dynamic Tracing (DTrace), for troubleshooting OS and application prob-
lems on production systems in real time
The Solaris 10 OS fully supports 32-bit and 64-bit x86 platforms as well as the
SPARC architecture.
This book is the work of the engineers, architects, and writers who conceptual-
ized the services, wrote the procedures, and coded the rich set of Solaris features.
These authors bring a wide range of industry and academic experience to the busi-
ness of creating and deploying operating systems. These are the people who know
Solaris 10 best. They have collaborated to write a book that speaks to readers who
want to learn Solaris or who want to use Solaris for the first time in their com-
pany’s or their own environment. Readers do not have to be experienced Solaris
users or operating system developers to take advantage of this book.
The book’s key topics include:
Installing, booting, and shutting down a system
Managing packages and patches (software updates)
Controlling system processes
Managing disks and devices
Managing users
Configuring networks
Using printing services
Books in the Solaris System Administration Series
Solaris™ 10 Security Essentials
Solaris™ 10 Security Essentials describes how to make Solaris installations secure
and configure the operating system to the particular needs of an environment,
whether the systems are on the edge of the Internet or running a data center. It
does so in a straightforward way that makes a seemingly arcane subject accessible
to system administrators at all levels.
Solaris™ 10 Security Essentials begins with two stories that highlight the
evolution of security in UNIX systems and the particular strengths that Sun
Microsystems has added to the Solaris operating system that make it the best
choice for meeting the present-day challenges to robust and secure computing.

Preface xix
Solaris™ 10 ZFS Essentials
Solaris™ 10 ZFS Essentials presents the revolutionary Zettabyte File System
introduced in Solaris 10. It is a file system that is elegant in its simplicity and the
ease with which it allows system administrators to manage data and storage.
ZFS is an all-purpose file system that is built on top of a pool of storage devices.
File systems that are created from a storage pool share space with the other file
systems in the pool. Administrators do not have to allocate storage space based on
the intended size of a file system because file systems grow automatically within
the space that is allocated to the storage pool. When new storage devices are
added, all file systems in the pool can immediately use the additional space.
Intended Audience
The books in the Solaris System Administration Series can benefit anyone who
wants to learn more about the Solaris 10 operating system. They are written to be
particularly accessible to system administrators who are new to Solaris, and
people who are perhaps already serving as administrators in companies running
Linux, Windows, and/or other UNIX systems.
If you are not presently a practicing system administrator but want to become
one, then this series, starting with the Solaris™ 10 System Administration Essen-
tials, provides an excellent introduction. In fact, most of the examples used in the
books are suited to or can be adapted to small learning environments like a home
setup. Even before you venture into corporate system administration or deploy
Solaris 10 in your existing IT installation, these books will help you experiment in
a small test environment.
OpenSolaris
In June 2005, Sun Microsystems introduced OpenSolaris, a fully functional Solaris
operating system release built from open source. While the books in this series
focus on Solaris 10, they often incorporate aspects of OpenSolaris. Now that
Solaris has been open-sourced, its evolution has accelerated even beyond its nor-
mally rapid pace. The authors of this series have often found it interesting to intro-
duce features or nuances that are new in OpenSolaris. At the same time, many of
the enhancements introduced into OpenSolaris are finding their way into Solaris
10. Whether you are learning Solaris 10 or already have an eye on OpenSolaris,
the books in this series are for you.

xxi
About the Authors
This book benefits from the contributions of numerous experts in Solaris technolo-
gies. Below are brief biographies of each of the contributing authors.
David Bustos is a Senior Engineer in the Solaris SMF team. During seven years
at Sun, he implemented a number of pieces of the SMF system for Solaris 10 and
is now designing and implementing enhanced SMF profiles, which is a major revi-
sion of the SMF configuration subsystem. David graduated from the California
Institute of Technology with a Bachelor of Science degree in 2002.
Stephanie Brucker is a Senior Technical Writer who enjoys documenting net-
working features for system administrators and end users. Stephanie worked for
Sun Microsystems for over twenty years, writing tasks and conceptual informa-
tion for the Solaris operating system. She has written Wikipedia and print articles
on computer networking topics, as well as articles on ethnic dance for specialty
magazines. Stephanie lives in San Francisco, California. She has a Bachelor of
Fine Arts degree in Technical Theater from Ohio University.
Raoul Carag is a Technical Writer at Sun. He belongs to the System Administra-
tion writers group and documents networking features of the Solaris OS. He has
been involved in projects that enhance network administration such as IP observ-
ability, rearchitected multipathing, and network virtualization.
Penelope Cotten is a Technical Writer at Sun Microsystems, working on Solaris
Zones/Containers and the Sun xVM hypervisor.

xxii About the Authors
Scott Davenport has been at Sun for eleven years, the last five of which have
been focused on fault management. He is a leader of the OpenSolaris FM Commu-
nity (http://opensolaris.org/os/community/fm) and issues periodic mus-
ings about fault management via his blog (http://blogs.sun.com/sdaven).
Scott lives in San Diego, California.
Alta Elstad is a Technical Writer at Sun Microsystems, working on device drivers
and other Solaris and OpenSolaris operating system features.
Eric Erickson is a Technical Writer and a professor of English at Mt. San Antonio
College, Walnut, California. He has a Master of Fine Arts degree in English from
the University of Iowa.
Juanita Heieck is a Senior Technical Writer in the Sun Learning Services organi-
zation at Sun Microsystems. She writes basic and advanced system administra-
tion documentation for a wide range of Solaris features including booting,
networking, and printing.
Puneet Jain works as a developer at Sun Microsystems in the Diagnostics
Engineering Group. He works on design and development of system-level diag-
nostics using C on Solaris. These diagnostics are used across all the Sun hard-
ware products during engineering, manufacturing, and field usage. His major
responsibilities include developing new diagnostics and enhancing the existing
diagnostics in I/O space to ensure that Sun Systems shipped to the customers
are of the highest quality. For his academic and leadership excellence, he has
been awarded with the Gold Medal from his college and The Best Student of
State Award, 2006 from the Indian Society of Technical Education (ISTE), New
Delhi. Puneet lives in Bangalore with his parents, Mr. Surendra Kumar Jain
and Ms. Memo Jain. His father likes writing poems in his spare time and
Puneet enjoys listening to his father’s poems in his spare time.
Narendra Kumar.S.S earned his Bachelor of Science in Computer Science Engi-
neering and Master of Science in Software Systems. He has over ten years of experi-
ence and has worked in varied areas such as networking, telecom, embedded systems,
and Operating Systems. He has worked for Sun for the last four years. Initially he
joined the “Solaris Install” team and later was moved to the “Solaris Sustaining”
team. Currently he is responsible for sustaining the sysidtools part of the Solaris
Install. He is based in Bangalore and lives with his wife, Rukmini, and daughters,
Harshitha and Vijetha.
James Liu is a Senior Staff Engineer at Sun. He joined Sun in 1995 and has
helped countless ISVs and IHVs to develop Solaris and Java software. James has a
broad range of expertise in UNIX, Java, compilers, networking, security, systems
administration, and applications architecture. He holds multiple software patents
in performance tuning, bug management, multimedia distribution, and financial

About the Authors xxiii
derivatives risk management. Prior to coming to Sun, James did research in
inertial confinement fusion, and then worked as a consultant building trading- and
risk-management systems in the Tokyo financial markets. James holds a Bachelor
of Science and Doctorate of Philosophy from UC Berkeley in Nuclear Engineering,
specializing in Shockwave Analysis and Computational Physics. At present, James
is a kernel engineer helping IHVs write device drivers. In his spare time, he likes
to blog about how to build cheap Solaris x86 boxes.
Alan Maguire is a Software Engineer at Sun Microsystems. He has ten years of
experience in Solaris—covering both test and product development—primarily
focused on networking components in the Solaris Operating System. These include
the open-source Quagga routing protocol suite, the Network Auto-Magic technol-
ogy, and the Service Management Facility (SMF). He graduated with a Bachelor of
Science in Computer Science and obtained a Master of Science in Cognitive
Science from University College, Dublin, Ireland.
Cathleen Reiher is a Senior Technical Writer at Sun Microsystems. She has over
seventeen years of experience working with and writing about the Solaris operat-
ing system. Her work is primarily focused on helping system administrators and
developers to effectively use Sun technologies to support their endeavors. She
graduated with a Bachelor of Arts degree in Linguistics from the University of
California, Los Angeles.
Vidya Sakar is a Staff Engineer in the Data Technologies group of Solaris
Revenue Product Engineering. Vidya Sakar has about ten years of technical and
management experience in Solaris Sustaining and Engineering. During this period
he has worked on different file systems, volume managers, and various kernel sub-
systems. He was a part of the team that ported the ZFS file system to Solaris 10
and has delivered talks on Internals of file systems at various universities in India
and at technology conferences. He is a Kepner Tregoe certified Analytic Trouble
Shooting (ATS) program leader and has facilitated on-site trouble-shooting ses-
sions at customer sites.
Michael Schuster earned his degree (“Diplom-Ingenieur”) at the Technische
Universität in Vienna in 1994. Since the early 1990s, he has been working with
and on UNIX systems, mainly Solaris, but also HP-UX and AIX. After several
years of software engineering work in Austria, Michael moved to Munich to
join Sun Microsystems’ Services organization, where he specialized in kernel
internals-related work and performance analysis. He joined the Solaris Engineer-
ing group in late 2006, where he currently works in the networking team, and
moved to the San Francisco Bay Area in early 2007.
Lynne Thompson is a Senior Technical Writer who has written about the Solaris
operating system for more than fourteen years. She is a twenty-year veteran of

xxiv About the Authors
writing about UNIX and other technologies. To enhance the understanding of
Solaris for system administrators and developers, she has written extensively
about Solaris installation, upgrading, and patching, as well as many Solaris
features related to installing, such as ZFS, booting, Solaris Zones, and RAID-1
volumes. Lynne is a contributor to OpenSolaris. She has a Master of Arts in
English (Writing). When she’s not learning and writing about technology, Lynne
is traveling, designing art-jewelry, or tutoring reading for people with learning
disabilities.
Sowmini Varadhan is a Staff Engineer at Sun Microsystems in the Solaris
Networking group. For the last nine years, she has been participating in the imple-
mentation and improvements of routing and networking protocols in the Solaris
TCP/IP stack. Prior to working at Sun, Sowmini was at DEC/Compaq, working on
Routing and IPv6 protocols in the Tru64 kernel, and on Sun RPC interfaces at
Parametric Technology Corp.

1
1
Installing the Solaris 10
Operating System
The chapter explores the key methods for installing and updating the Solaris oper-
ating system. It takes the reader from simple installation on a single system
through the options for installing and upgrading systems in a networked environ-
ment where multiple machines can be managed automatically.
1.1 Methods to Meet Your Needs
The Solaris 10 operating system offers a rich installation experience with a num-
ber of options to meet the needs of a variety of users and environments. The
Solaris OS can be installed easily on a single system using a CD or DVD, it can be
installed over a network, update installations can be performed while the system
is running without interruption, and installation on multiple machines can be per-
formed hands-free with JumpStart. You can even clone a system for installation on
other machines using the Solaris Flash archive feature.
The ﬁrst thing a new Solaris user needs is the DVD or an image of the DVD
from which the Solaris OS can be installed. The DVD image can be downloaded
from http://www.sun.com/software/solaris/10/. Once you have down-
loaded that image, you can burn an ISO format disk image and then install that
image on one or more systems. This method provides a simple GUI installation
process, though you can always use the text-based installation interface.
It is not necessary to create a DVD, though. You can install the Solaris OS
directly from the image you downloaded. That can be done from the image stored

2 Chapter 1 Installing the Solaris 10 Operating System
on the machine you wish to install on or from another system in the network of
which your target system is a part.
When you get to installing multiple machines, you will want something more
versatile than a DVD, which must be carried to each machine. A network-based
installation is obviously a useful alternative. You can use all of the Solaris installa-
tion methods to install a system from the network. You can point each machine at
the installation image on the network and install almost as if you had inserted a
DVD. However, by installing systems from the network with the Solaris Flash
installation feature or with a custom JumpStart installation, you can centralize
and automate the installation process in a larger environment.
An upgrade installation overwrites the system’s disk with the new version of the
Solaris OS. If your system is not running the Solaris OS, then you must perform
an initial installation.
If the system is already running the Solaris OS, then you can choose to perform
an initial installation. If you want to preserve any local modifications, then you
must back up the local modifications before you install. After you complete the
installation, you can restore the local modifications.
You can use any of the Solaris installation methods to perform an initial
installation.
To upgrade the Solaris OS, there are three methods: standard installation, cus-
tom JumpStart, and Solaris Live Upgrade. When you upgrade using the standard
installation procedure or JumpStart, the system maintains as many existing con-
figuration parameters as possible of the current Solaris OS. Solaris Live Upgrade
creates a copy of the current system. This copy can be upgraded with a standard
upgrade. The upgraded Solaris OS can then be switched to become the current sys-
tem by a simple reboot. If a failure occurs, then you can switch back to the original
Solaris OS with a reboot. Solaris Live Upgrade enables you to keep your system
running while you upgrade and enables you to switch back and forth between
Solaris OS releases.
1.2 The Basics of Solaris Installation
Many terms and options make Solaris widely configurable for the large install-
base administrator; however, a basic understanding of these terms and options will
help an administrator installing even a single instance of Solaris get all that one
can from their system.
When you start off small with only a single system to install, the GUI and
console mode text installers are the simplest ways to install a single instance
of the Solaris OS. Because Solaris systems are optimized for networking, this
installation method focuses on setting up network parameters and file sharing

1.2 THE BASICS OF SOLARIS INSTALLATION 3
identification to accommodate user home directories on numerous Solaris systems
in the network.
The minimum memory requirement for installing Solaris is 128MB. The recom-
mended size is 256MB. If you install with the GUI installer, then you need 512MB.
If the system has less than 384MB, then the text installer will be used automati-
cally. These limits change slightly between the SPARC and x86 architectures (see
Table 1.1).
In a single-system install installation, the primary objective is to get the sys-
tem to boot up usably. This means specifying which of the system network inter-
faces should be used as the primary interface for network traffic, and nowadays
even which version of the Internet Protocol to use (IPv4 or IPv6) needs be speci-
fied. After figuring out which protocol to use, you need to specify how large the
machine’s network segment or subnet is and a default route for traffic destined
for another subnet. Solaris has support for Kerberos authentication and creden-
tial support; if you wish to set it up, then you can do that at install as well. One of
the last network services to set up is the naming service to be used for mapping
hostnames to Internet Protocol (IP) addresses. Solaris supports the Network
Information Service (NIS), the no longer recommended NIS+, the Lightweight
Directory Access Protocol (LDAP), and the Domain Name System (DNS). During
installation, only one service can be specified. Each service requires specific
information for setup (see Chapter 13, “Using Naming Services”). In the home or
small business case, DNS will be used because it requires only a DNS server IP
address. Lastly, for network configuration, NFS version 4 now supports domain
Table 1.1 Memory Requirements for “Solaris Install Display Options”
SPARC:
Memory
x86:
Memory
Type of
Installation
Description
128–383 MB 256–511 MB Text-based Contains no graphics, but provides a window and
the ability to open other windows.
If you install by using the text boot option and
the system has enough memory, you are install-
ing in a windowing environment. If you are
installing remotely through a tip line or using
the nowin boot option, you are limited to the
console-based installation.
384 MB or
greater
512 MB GUI-based Provides windows, pull-down menus, buttons,
scrollbars, and iconic images.

based identification, so you can configure which domain to use, if necessary
(see Section 5.4, “NFS File System Administration,” for more info).
After you specify the network settings, the installation program focuses on sys-
tem configuration. First, you specify the date and time, a root user password (also
known as an administrator password), and the last networking question about
whether the system should be “Secure by Default.” Solaris’ Secure by Default pro-
vides security for the system without requiring you to do a lot of configuration or
know a lot about security. See “Solaris Security Essentials” in the Solaris System
Administration series for more information about Secure by Default and the many
other security features of the Solaris OS.
Packaging and package metaclusters (also known as Software Groups) are a key
idea in a Solaris installation. You must specify the parts of Solaris to be installed
or specifically left off a system. Package metaclusters are designed as groups of
packages for designating a system’s intended use after installation. In this day of
big disks, it is recommended that you install the Entire Distribution plus OEM
support metacluster. However, you can use the customize feature in the GUI or
text installers to specify which metaclusters are to be installed. Table 1.2 describes
each Software Group and the disk space recommended for installing it.
Table 1.2 Disk Space Recommendations for Software Groups
Software Group Description Recommended
Disk Space
Reduced Network Sup-
port Software Group
Contains the packages that provide the
minimum code that is required to boot
and run a Solaris system with limited net-
work service support. The Reduced Net-
work Support Software Group provides a
multi-user text-based console and system
administration utilities. This software
group also enables the system to recog-
nize network interfaces, but does not acti-
vate network services.
2.0 GB
Core System Support
Software Group
and run a networked Solaris system.
2.0 GB
End User Solaris Soft-
ware Group
and run a networked Solaris system and a
Desktop Environment.
5.3 GB

When installing any software, the amount of space it takes up is always a ques-
tion. With an operating system another choice is available: the way you would like
to use your system’s disk space. Solaris supports several file systems. During
installation, you can choose UFS, the traditional file system for Solaris; or ZFS, the
new and future file system for Solaris. ZFS is usually the best option. See
Chapter 5, “Solaris File Systems,” for more information on file systems. Selecting
ZFS over UFS will change how much control you have during installation for lay-
ing out disks, but ZFS is more flexible after an install.
If ZFS is selected as the system’s boot file system, then you can choose the size
of the root pool (or storage space available) and the space set aside for system swap
and memory dump locations. Also, you may opt for separate root (/) and /var
datasets to make quota enforcement easier, or you can choose a monolithic dataset.
If UFS is selected as the system’s boot file system, then there are more choices
you need think about during installation. UFS is less flexible once the system is
installed. There is, however, an automatic layout option that enables you to pick
which directories should live on their own file systems versus which should reside
on the root file system. Where such large disks are available today, it is only recom-
mended to select swap to be separate unless the system will otherwise have spe-
cific security or application requirements.
Developer Solaris
Software Group
Contains the packages for the End User
Solaris Software Group plus additional
support for software development. The
additional software development support
includes libraries, “include files,” “man
pages,” and programming tools.
Compilers are not included.
6.6 GB
Entire Solaris Software
Group
Contains the packages for the Developer
Solaris Software Group and additional
software that is needed for servers.
6.7 GB
Entire Solaris Software
Group Plus OEM
Support
Contains the packages for the Entire
Solaris Software Group plus additional
hardware drivers, including drivers for
hardware that is not on the system at the
time of installation.
6.8 GB
Table 1.2 Disk Space Recommendations for Software Groups (continued )
Software Group Description Recommended
Disk Space

1.2.1 Installing Solaris on a SPARC System
These steps for SPARC and x86 differ slightly. We will ﬁrst see how Solaris is
installed on a SPARC system.
1. Insert the Solaris 10 operating system for SPARC platforms DVD.
2. Boot the system.
If the system is already running, execute init 0 to halt it.
If the system is new, then simply turn it on.
3. When the OK prompt is displayed, type boot cdrom.
4. When installation begins, you are asked to select a language. Select a lan-
guage and hit Enter.
After a few moments the Solaris Installation Program Welcome Screen
appears. Figures 1.1 and 1.2 show the graphical and text versions of those
screens.
5. Click Next to start entering the system conﬁguration information.
Figure 1.1 Solaris Installation Program Welcome Screen (GUI)

After getting all the conﬁguration information, the Solaris Installation Screen
appears (see Figure 1.3).
After this the actual installation related questions will be asked. What follows
are the questions that typically will be asked:
1. Decide if you want to reboot the system automatically and if you want to
automatically eject the disc.
2. The Specify Media screen appears. Specify the media you are using to
install.
3. The License panel appears. Accept the license agreement to continue the
installation.
4. The Select Upgrade or Initial Install screen appears. Decide if you want to
perform an initial installation or an upgrade.
5. When you are prompted to select initial installation or upgrade, choose Ini-
tial Install.
Figure 1.2 Solaris Text Installer Welcome Screen

6. Fill in the sequence of screens that ask for information about the system
configuration after installation. See Table 1.3 at the end of the chapter for a
checklist of information you need on these installation screens.
After you provide all the necessary information on the installation, the Ready to
Install screen appears as in Figure 1.4.
Click the Install Now button to start the installation.
When the Solaris installation program finishes installing the Solaris software,
the system reboots automatically or prompts you to reboot manually (this depends
on what you selected initially).
If you are installing additional products, then you are prompted to insert the
DVD or CD for those products. After the installation is finished, installation logs
are saved in a file. You can find the installation logs in the /var/sadm/system/
logs and /var/sadm/install/logs directories.
If you are performing an initial installation, then the installation is complete.
You can reboot the system.
If you are upgrading to a new version of Solaris operating system, then you
might need to correct some local modifications that were not preserved. Review the
contents of the upgrade_cleanup file located at /a/var/sadm/system/data to
determine whether you need to correct local modifications that the Solaris installa-
tion program could not preserve. Then you can reboot the system.
Figure 1.3 Welcome to Solaris Installation Screen

1.2.2 Installing Solaris on an x86 System
As mentioned, the installation for an x86 system differs slightly from a SPARC
Solaris installation.
On an x86 system, when the booting starts, go inside the BIOS (by selecting F2)
and change the booting sequence by selecting CD/DVD to boot ﬁrst. Check
your hardware documentations to learn how to enter BIOS and make changes.
After making the changes, save and come out. Now, the system will boot with the
x86 Solaris 10 Operating System media placed in the disk drive.
The ﬁrst screen to appear is the GRUB menu:
Figure 1.4 Solaris Installation Ready to Install Screen
GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-------------------------------------------------------------------------+
| Solaris |
| Solaris Serial Console ttya |
| Solaris Serial Console ttyb (for lx50, v60x and v65x) |
| |
| |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

1. Select the appropriate installation option.
If you want to install the Solaris OS from CD or DVD on your current
system, then select Solaris.
Select this option if you want to install the system using the default
values.
If you want to install the Solaris OS and send the screen output to serial
console ttya (COM1), then select Solaris Serial Console ttya.
Select this option if you want to change the system display to a device
that is connected to serial port COM1.
If you want to install the Solaris OS and send the screen output to serial
console ttyb (COM2), then select Solaris Serial Console ttyb.
Select this option if you want to change the system display to a device
that is connected to serial port COM2.
You might want to use specific boot arguments to customize the system
configuration during the installation.
On the GRUB menu, select the installation option you want to edit and
then press Enter.
Boot commands that are similar to the following text are displayed in
the GRUB menu.
2. Use the arrow keys to select the boot entry that you want to edit and again
press Enter.
The boot command that you want to edit is displayed in the GRUB edit window.
3. Edit the command by typing the boot arguments or options you want to use.
The command syntax for the Grub edit menu is as follows.
4. To go back to the GRUB menu, press Enter.
The GRUB menu is displayed. The edits you made to the boot command
are displayed.
5. To begin the installation, type b in the GRUB menu.
The Solaris installation program checks the default boot disk for the
requirements to install or upgrade the system. If the Solaris installation
cannot detect the system configuration, the program prompts you for any
missing information.
kernel /boot/multiboot kernel/unix -B install_media=cdrom
module /boot/x86.miniroot
grub editkernel /boot/multiboot kernel/unix/
install [url|ask] -B options install_media=media_type

When the check is completed, the installation selection screen is displayed.
Select an installation type.
The installation selection screen displays the following options:
To install the Solaris OS, choose from the following options.
To install with the Solaris interactive installation GUI, type 1, then press
Enter.
To install with the interactive text installer in a desktop session, type 3, then
press Enter. You can also type b - text at the prompt.
Select this installation type to override the default GUI installer and run
the text installer.
To install with the interactive text installer in a console session, type 4, then
press Enter. You can also type b - text at the prompt.
Select this installation type to override the default GUI installer and run
the text installer.
The system configures the devices and interfaces and searches for configuration
files. The kdmconfig utility detects the drivers that are necessary to configure the
keyboard, display, and mouse on your system. The installation program begins.
If you want to perform system administration tasks before your installation,
choose from the following options.
To update drivers or install an install time update (ITU), insert the update
media, type 5, and then press Enter.
You might need to update drivers or install an ITU to enable the Solaris
OS to run on your system. Follow the instructions for your driver update or
ITU to install the update.
To perform system administration tasks, type 6, then press Enter.
You might want to launch a single user shell if you need to perform any
system administration tasks on your system before you install.
Select the type of installation you want to perform:
1 Solaris Interactive
2 Custom JumpStart
3 Solaris Interactive Text (Desktop session)
4 Solaris Interactive Text (Console session)
5 Apply driver updates
6 Single user shell
Enter the number of your choice followed by the ENTER key.
Alternatively, enter custom boot arguments directly.
If you wait 30 seconds without typing anything,
an interactive installation will be started.

After you perform these system administration tasks, the previous list of
options is displayed. Select the appropriate option to continue the installation.
Decide if you need to modify the configuration settings.
If you do not need to modify the configuration settings, then let the Window Sys-
tem Configuration for Installation screen time out.
If you need to modify the configuration settings, then follow these steps.
1. Press the ESC key. (Note that you must press the ESC key within five sec-
onds to interrupt the installation and modify device settings.)
The kdmconfig – Introduction screen is displayed.
2. Examine the configuration information on the kdmconfig – View and Edit
Window System Configuration screen and determine which devices you need
to edit.
3. Select the device you want to change and press F2_Continue.
4. Select the appropriate driver for the device and press F2_Continue.
5. Repeat the steps for each device you need to change.
6. When you are finished, select No changes needed – Test/Save and Exit and
press F2_Continue.
7. The kdmconfig Window System Configuration Test screen appears. Press
F2_Continue.
The screen refreshes and the kdmconfig Window System Configuration
Test palette and pattern screen appears. Move the pointer and examine the
colors that are shown on the palette to ensure that they are displayed
accurately.
If the colors are not displayed accurately, click No. If possible, press
any key on the keyboard or wait until kdmconfig exits the kdmconfig
Window System Configuration Test screen automatically. Repeat the steps
Note
If the kdmconfig utility cannot detect the video driver for your system, the kdmconfig
utility selects the 640x480 VGA driver. The Solaris installation GUI cannot be displayed with
the 640x480 VGA driver. As a result, the Solaris installation text installer is displayed. To use
the Solaris installation GUI, use the kdmconfig utility to select the correct video driver for
your system.

1.3 SOLARIS JUMPSTART INSTALLATION 13
until the colors are displayed accurately and you can move the pointer as
expected.
If the colors are displayed accurately, then click Yes.
8. After a few seconds, the Select a Language screen is displayed. Select the lan-
guage you want to use during the installation, and press Enter.
After this, the screens and the steps are the same as those for the SPARC based
Solaris Installer.
1.3 Solaris JumpStart Installation
The custom JumpStart installation method is a command line interface that enables
you to automatically install or upgrade several systems based on profiles that you
create. The profiles define specific software installation requirements. You can also
incorporate shell scripts to include preinstallation and postinstallation tasks. You
choose which profile and scripts to use for installation or upgrade. The custom
JumpStart installation method installs or upgrades the system, based on the profile
and scripts that you select. Also, you can use a sysidcfg file to specify configura-
tion information so that the custom JumpStart installation is completely hands-off.
The key features of JumpStart install can be summarized as follows:
Useful for unattended installation of Solaris
Supports multiple OS releases
Supports both Sparc and Intel based processors
Supports multiple configurations for hosts based on a variety of criteria
Allows for customization via pre/postinstall Bourne shell scripts
1.3.1 Setting up a JumpStart Server
The JumpStart Server performs three separate functions, which can be performed
by a single machine or can be spread out across several machines, depending on
user requirements.
Boot Server
– Uses RARP BOOTP or DHCP to set the basic network parameters for
the machine.

– Uses tftp to load a boot kernel to perform the more complex task of mount-
ing the appropriate directories used to install the Solaris packages.
– Boot server must exist on the same network as client (in other words, they
should have the same netmask). Once client has loaded its boot kernel, it
can access an Install server across routers.
Install Server
– Contains Solaris packages, copied from the Solaris installation CDs or
DVD, to be installed.
– Contains a Solaris miniroot, which the client mounts via NFS. The OS
install is performed while running from this miniroot.
– Multiple Install servers can be used to distribute the load.
The items mentioned above are together called the Solaris Install
Image.
Configuration Server
– Contains site-specific information used for a custom JumpStart installation.
– sysidcfg file used to set basic network configuration; this is needed to
perform an unattended install. A different sysidcfg file is needed for
each architecture and OS release.
– Single configuration server can be used to install on multiple clients, which
will be easy to manage.
1.3.2 Creating a Profile Server for Networked Systems
When setting up custom JumpStart installations for systems on the network, you
will have to create a directory called a JumpStart directory on the server. The
JumpStart directory contains all of the essential custom JumpStart files, for exam-
ple, the rules file, profiles, and pre/postinstall scripts.
The server that contains a JumpStart directory is called a profile server. A pro-
file server can be on the same system as an install server or a boot server, or the
server can be on a completely different system. A profile server can provide custom
JumpStart files for different platforms. For example, an x86 server can provide
custom JumpStart files for both SPARC based systems and x86 based systems.
The sequence of commands to create a JumpStart directory follows:
1. mkdir -m 755 JumpStart directory
2. share -F nfs -o ro,anon=0 JumpStart directory

3. cp -r media_path/Solaris_10/Misc/JumpStart_sample/*
JumpStart directory
Where, media_path is the path to the Solaris Install CD/DVD or
Solaris Install Image on the local disk.
4. Copy the configuration and profile files to this directory.
The next step is to ensure that the systems on the network can have access
to the profile server. The command that comes in handy to get this done is
add_install_client. There are various options for this command. For this
reason, refer to the corresponding man pages to get all of the relevant details.
1.3.2.1 rules and profile file
The rules file is a text file that contains a rule for each group of systems on which
you will install the Solaris OS. Each rule distinguishes a group of systems that are
based on one or more system attributes. Each rule also links each group to a pro-
file. A profile is a text file that defines how the Solaris software is to be installed
on each system in the group. This rules file will be used to create a rules.ok file,
which will be used during JumpStart.
1.3.2.2 Syntax of the rules File
The rules file must have the following attributes:
The file must be assigned the name rules.
The file must contain at least one rule.
The rules file can contain any of the following:
Commented text
Any text that is included after the # symbol on a line is treated by Jump-
Start as a comment. If a line begins with the # symbol, then the entire line is
treated as a comment.
One or more blank lines
One or more multiline rules
To continue a single rule onto a new line, include a backslash character () just
before pressing Return.

1.3.2.3 Creating a rules File
To create a rules file, do the following:
1. Use a text editor to create a text file that is named rules or open the sample
rules file in the JumpStart directory that you created.
2. Add a rule in the rules file for each group of systems on which you want to
install the Solaris software.
A rule within a rules file must adhere to the following syntax:
The following list explains each element of the rules file syntax:
The exclamation point (!) is a symbol that is used before a keyword to indicate
negation.
rule_keyword: A predefined lexical unit or a word that describes a general
system attribute, such as host name (hostname) or memory size (memsize).
rule_keyword is used with the rule value to match a system with the same
attribute to a profile.
rule_value: A value that provides the specific system attribute for the
corresponding rule_keyword.
: A symbol (a logical AND) you must use to join rule keyword and rule
value pairs in the same rule. During a custom JumpStart installation, a sys-
tem must match every pair in the rule before the rule matches.
begin: The name of an optional Bourne shell script that can be executed before
the installation begins. If no begin script exists, you must type a minus sign (−)
in this field. All begin scripts must be located in the JumpStart directory.
Use a begin script to perform one of the following tasks:
Create derived profiles
Back up files before upgrading
Important information about begin scripts:
Do not specify something in the script that would prevent the mounting of file
systems during an initial or upgrade installation. If the JumpStart program
cannot mount the file systems, then an error occurs and installation fails.
!rule_keyword rule_value !rule_keyword rule_value
... begin profile finish

During the installation, output from the begin script is deposited in
/tmp/begin.log. After the installation is completed, the log file is
redirected to /var/sadm/system/logs/begin.log.
Ensure that root owns the begin script and that the permissions are set to 644.
You can use custom JumpStart environment variables in your begin scripts.
For a list of environment variables, see http://docs.sun.com/app/docs/
doc/819-2396/6n4mi6eth?a=view.
Save begin scripts in the JumpStart directory.
The name of a text file that defines how the Solaris software is to be installed on
the system when a system matches the rule is the profile. The information in a
profile consists of profile keywords and their corresponding profile values. All pro-
files must be located in the JumpStart directory. You can create different profiles
for every rule or the same profile can be used in more than one rule.
A profile consists of one or more profile keywords and their values. Each profile
keyword is a command that controls one aspect of how the JumpStart program is
to install the Solaris software on a system. For example, the following profile key-
word and value specify that the JumpStart program should install the system as a
server:
system_type server
1.3.2.4 Syntax of Profiles
A profile must contain the following:
The install_type profile keyword as the first entry
One keyword per line
The root_device keyword if the systems that are being upgraded by the
profile contain more than one root (/) file system that can be upgraded
A profile can contain the following:
Commented text.
Any text that is included after the # symbol on a line is treated by the
JumpStart program as commented text. If a line begins with the # symbol,
the entire line is treated as a comment.
One or more blank lines.

1.3.2.5 Creating a Profile
To create a profile, do the following:
1. Use a text editor to create a text file. Any name can be used as the filename
for a profile file. Sample profile files will be available in the JumpStart direc-
tory that you created.
2. Add profile keywords and values to the profile.
Profile keywords and their values are case sensitive.
3. Save the profile in the JumpStart directory.
4. Ensure that root owns the profile and that the permissions are set to 644.
5. The user can test the profile before using it.
1.3.2.6 Profile Examples
The following two examples show how to use different profile keywords and profile
values to control how the Solaris software is installed on a system.
Adding or Deleting Packages The following listing shows a profile that deletes
a package:
The variable names in the profile have the following meanings:
install_type: The install_type keyword is required in every profile.
system_type: The system_type keyword indicates that the system is to
be installed as a standalone system.
partitioning: The file system slices are determined by the software to be
installed with the value default. The size of swap is set to 512 MB and is
installed on any disk, value any.
cluster: The Developer Solaris Software Group, SUNWCprog, is installed
on the system.
# profile keywords profile values
# ---------------- --------------
install_type initial_install
system_type standalone
partitioning default
filesys any 512 swap # specify size of /swap
cluster SUNWCprog
package SUNWman delete
cluster SUNWCacc

package: If the standard man pages are mounted from the file server, s_ref,
on the network, the man page packages are not to be installed on the system.
The packages that contain the System Accounting utilities are selected to be
installed on the system.
Using the fdisk Keyword (for an x86 system) The following listing shows a
profile that uses the fdisk keyword:
The variable names in the profile have the following meanings:
fdisk: All fdisk partitions of type DOSOS16 (04 hexadecimal) are deleted
from the c0t0d0 disk.
fdisk: A Solaris fdisk partition is created on the largest contiguous free
space on the c0t0d0 disk.
cluster: The Entire Distribution Software Group, SUNWCall, is installed
on the system.
cluster: The system accounting utilities, SUNWCacc, are not to be installed
on the system.
1.3.2.7 Testing a Profile
After you create a profile, use the pfinstall(1M) command to test the profile. Test
the profile before using it to install or upgrade a system. Testing a profile is espe-
cially useful when it is being used for an upgrade with reallocation of disk space.
By looking at the output that is generated by pfinstall, one can quickly deter-
mine if a profile works as intended. For example, use the profile to determine if a
system has enough disk space to upgrade to a new release of the Solaris software
before performing an upgrade on that system.
1.3.2.8 Profile Test Examples
The following example shows how to use pfinstall to test a profile that is named
basic_prof. The profile is tested against the disk configuration on a system on
# profile keywords profile values
# ---------------- -------------------
install_type initial_install
system_type standalone
fdisk c0t0d0 0x04 delete
fdisk c0t0d0 solaris maxfree
cluster SUNWCall
cluster SUNWCacc delete

which the Solaris Express 5/07 software is installed. The basic_prof profile is
located in the /JumpStart directory, and the path to the Solaris Operating Sys-
tem DVD image is specified because removable media services are being used.
1.3.2.9 Validating the rules File
Before using a profile and rules file, the check script must be used to validate
that the files are set up correctly. If all rules and profiles are correctly set up, the
rules.ok file is created, which is required by the custom JumpStart installation
software to match a system to a profile.
The following steps describe what the check script does.
1. The rules file is checked for syntax.
check verifies that the rule keywords are legitimate and that the begin,
class, and finish fields are specified for each rule. The begin and finish
fields can consist of a minus sign (-) instead of a file name.
2. If no errors are found in the rules file, then each profile that is specified in
the rules is checked for syntax.
3. If no errors are found, then check creates the rules.ok file from the rules
file, removes all comments and blank lines, retains all rules, and adds the fol-
lowing comment line at the end:
# version=2 checksum=num
Follow these steps to validate a rules file:
1. Ensure that the check script is located in the JumpStart directory.
Note that the check script is in the Solaris_10/Misc/JumpStart_sample
directory on the Solaris Operating System DVD or on the Solaris
Software - 1 CD.
2. Change the directory to the JumpStart directory.
3. Run the check script to validate the rules file:
# ./check -p path -r file_name
The -p path parameter validates the rules file by using the check script
from the Solaris software image instead of the check script from the system
you are using. path is the Solaris Install Image on a local disk or a mounted
Solaris Operating System DVD/CD.
# cd /JumpStart
# /usr/sbin/install.d/pfinstall -D -c /media/cdrom/pathname basic_prof

Use this option to run the most recent version of check if your system is
running a previous version of Solaris.
The -r file_name paremeter specifies a rules file other than the one
that is named rules. Using this option, you can test the validity of a rule
before you integrate the rule into the rules file.
As the check script runs, the script reports the checking of the validity of
the rules file and each profile.
If no errors are encountered, then the script displays the following o/p:
The custom JumpStart configuration is ok
4. Ensure that root owns the rules.ok file and that the permissions are set
to 644.
The finish script is an optional Bourne shell script that can be executed after
the installation is completed. If no finish script exists, then you must type a minus
sign (−) in this field. All finish scripts must be located in the JumpStart directory.
A finish script performs tasks after the Solaris software is installed on a system,
but before the system reboots. You can use finish scripts only when using custom
JumpStart to install Solaris.
Tasks that can be performed with a finish script include the following:
Adding files
Adding individual packages or patches in addition to the ones that are
installed in a particular software group
Customizing the root environment
Setting the system’s root password
Installing additional software
1.3.2.10 Important Information about Finish Scripts
The Solaris installation program mounts the system’s file systems
on /a. The file systems remain mounted on /a until the system reboots.
A finish script can be used to add, change, or remove files from the
newly installed file system hierarchy by modifying the file systems that
are respective to /a.
– During the installation, output from the finish script is deposited in /tmp/
finish.log. After the installation is completed, the log file is redirected
to /var/sadm/system/logs/finish.log.
Ensure that root owns the finish script and that the permissions are set
to 644.

Custom JumpStart environment variables can be used in finish scripts.
Save finish scripts in the JumpStart directory.
1.3.2.11 Example of Adding Packages or Patches with a Finish Script
A finish script can be used to automatically add packages or patches after
the Solaris software is installed on a system. Note that, when using the pkgadd(1M)
or patchadd(1M) commands in finish scripts, use the -R option (alternate root) to
specify /a as the alternate root.
1.3.3 Performing a Custom JumpStart Installation
This section describes how to perform a custom JumpStart installation on a
SPARC based or an x86 based system. There are some subtle differences between
the SPARC and x86 systems with regard to the steps to be followed during instal-
lation. So, we are providing all the steps for both the architectures separately. You
should follow the procedures based on the architecture on which the installation is
done.
During a custom JumpStart installation, the JumpStart program attempts to
match the system that is being installed to the rules in the rules.ok file. The
JumpStart program reads the rules from the first rule through the last. A match
occurs when the system that is being installed matches all the system attributes
that are defined in a rule. When a system matches a rule, the JumpStart program
stops reading the rules.ok file and begins to install the system based on the
matched rule’s profile.
1.3.3.1 SPARC: Performing an Installation or Upgrade With
the Custom JumpStart Program
To perform an installation or upgrade with the custom JumpStart program when
the system is part of a network, follow these steps.
1. Ensure that an Ethernet connector or similar network adapter is attached to
your system.
2. If the system is connected through a tip(1) line, ensure that the console
window display is at least 80 columns wide and 24 rows long. For more
information on tip lines, refer to refer to the tip(1) man page.
To find out the current dimensions of the tip window, use the stty(1)
command. For more information on the stty(1) command refer to the
stty(1) man page.

3. When using the system’s DVD-ROM or CD-ROM drive to install the Solaris
software, insert the Solaris Operating System for SPARC Platforms DVD
or the Solaris Software for SPARC Platforms - 1 CD in the drive.
4. When using a profile diskette, insert the profile diskette in the system’s
diskette drive.
5. Boot the system.
To perform an installation or upgrade with the custom JumpStart program on a
new system that is out of the box, follow these steps.
1. Turn on the system.
2. To install or upgrade an existing system, shut down the system. At the ok
prompt, type the appropriate options for the boot command. The syntax of
the boot command is the following.
ok boot [cd–dvd|net] - install [url|ask] options
For example, by typing the following command, the OS is installed over the
network by using a JumpStart profile.
If the system is not preconfigured by using information in the sysidcfg file,
then when prompted, answer the questions about system configuration. Follow the
instructions on the screen to install the software.
When the JumpStart program finishes installing the Solaris software, the sys-
tem reboots automatically.
After the installation is finished, installation logs are saved in the following
directories:
1.3.3.2 x86: Performing an Installation or Upgrade With
the Custom JumpStart Program
Use this procedure to install the Solaris OS for an x86 based system with the
GRUB menu. If the system is part of a network, then ensure that an Ethernet con-
nector or similar network adapter is attached to your system. To install a system
that is connected through a tip(1) line, ensure that your window display is at
least 80 columns wide and 24 rows long.
ok boot net - install
http://131.141.2.32/JumpStart/config.tar
/var/sadm/system/logs
/var/sadm/install/logs

To determine the current dimensions of your tip window, use the stty(1)
command.
1. When using a profile diskette, insert the profile diskette in the system’s dis-
kette drive.
2. Decide how to boot the system.
To boot from the Solaris Operating System DVD or the Solaris Software - 1
CD, insert the disk. Your system’s BIOS must support booting from a DVD
or CD.
To boot from the network, use Preboot Execution Environment (PXE)
network boot. The system must support PXE. Enable the system to use
PXE by using the system’s BIOS setup tool or the network adapter’s
configuration setup tool.
For booting from a DVD or CD, you have the option to change the boot
setting in your system’s BIOS and set to boot from DVD or CD media. See
your hardware documentation for instructions.
3. If the system is off, then turn the system on. If the system is on, then reboot
the system.
The GRUB menu is displayed. This menu provides a list of boot entries.
The image_directory is the name of the directory where the installa-
tion image is located. The path to the JumpStart files was defined with the
add_install_client command and the -c option.
GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-------------------------------------------------------------------+
|Solaris 10 10/08 image_directory |
|Solaris 10 5/08 Serial Console tty |
|Solaris 10 5/08 Serial Console ttyb (for lx50, v60x and v65) |
+-------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted. Press
enter to boot the selected OS, 'e' to edit the commands before
booting, or 'c' for a command-line.
Note
Instead of booting from the GRUB entry now, one can edit the boot entry. After edit-
ing the GRUB entry, then perform the JumpStart installation.

1.4 UPGRADING A SOLARIS SYSTEM 25
4. At the prompt, perform one of the following instructions:
5. To select the custom JumpStart method, type 2 and press Enter.
The JumpStart installation begins.
When the JumpStart program finishes installing the Solaris software, the sys-
tem reboots automatically. Also, the GRUB menu.lst file is automatically
updated. The instance of Solaris that you have installed appears in the next use of
the GRUB menu.
After the installation is finished, installation logs are saved in a file. You can
find the installation logs in the following directories:
/var/sadm/system/logs
/var/sadm/install/logs
1.4 Upgrading a Solaris System
As mentioned earlier in this chapter, there are three methods for upgrading the
Solaris OS: standard installation, custom JumpStart, and Solaris Live Upgrade.
For a UFS file system, you can upgrade a system by using any of these different
upgrade methods. For a ZFS root pool, you must use Solaris Live Upgrade. ZFS
will be the subject of the Live Upgrade section that follows.
Backing up your existing file systems before you upgrade to the Solaris OS is
highly recommended. If you copy file systems to removable media, such as tape,
you can safeguard against data loss, damage, or corruption.
For detailed instructions on backing up your system, refer to the Solaris 10
version of the System Administration Guide: Devices and Files Systems at
http://docs.sun.com.
Select the type of installation you want to perform:
1 Solaris Interactive
2 Custom JumpStart
3 Solaris Interactive Text (Desktop session)
4 Solaris Interactive Text (Console session)
5 Apply driver updates
6 Single User Shell
Enter the number of your choice.
Please make a selection (1-6).

Exploring the Variety of Random
Documents with Different Content

Thanks; I'm much obliged. This time I will not trouble you.
It was Mdlle. de Fontanes. When Mr Davison appeared she was
standing in the centre of the room. A thick black veil was before her
face. That waiter must have had keen eyes to detect the prettiness
beneath it. A little packet was in her hand. Opening it, she turned
out its contents on the table. There was a little heap of notes and
gold.
That is the money which my father has won from you.
This was her greeting as the young gentleman entered the room.
Mdlle. de Fontanes!
There was a pause. Mr Davison looked from the lady to the
money, and from the money to the lady. With a little movement she
lifted her veil.
He saw her face; it was pale, with the look upon it which follows a
sleepless night.
Did you think that we would keep it? She put out her hand and
touched his sleeve. Did you think so badly of us, then, as that?
He thought that he had never seen her look so pretty. There was
something in her voice which caused a choking in his throat.
But I cannot take the money. Especially--if you will forgive me,
Mdlle. de Fontanes--especially from you.
She sat down. For a moment she covered her face with her
hands. Suddenly she rose.
Do not make my burden heavier than it is already. Mr Davison,
my father cannot help but cheat. It is a disease. In the common
things of life he is the most honourable of men--the best of fathers.

But with the cards, night after night, since he must play, I play with
him, and he cheats me.
She fell on her knees by the side of the table. Burying her face in
her hands, she cried as though her heart would break. Mr Davison
could only whisper--
Mdlle. de Fontanes.
She looked up at him.
Say you forgive me, she cried.
Forgive you! I! What have I to forgive?
For taking you home that night; for letting you know my father;
for letting you know me.
Mr Davison fumbled with a compliment.
That--that is an honour for which I--I ought to thank you.
She rose. She regarded him intently, the tears still stealing from
her eyes. Never had he felt so uncomfortable before a woman's
gaze. It seemed to him that he was passing through all the colour
phases of the rainbow.
So you forgive me, truly?
If--if there is forgiveness needed.
If you forgive me--she came close to him, he felt her hand steal
into his--kiss me, Harry.
He kissed her as though she were a red-hot coal. Never did a
travelled young man of the world so kiss a pretty woman yet! And
when he had kissed her there was silence. Then, slipping her hand

into the bosom of her dress, she drew out a locket, to which was
attached a narrow black ribbon.
Keep this in memory of a chance acquaintance. Look at it
sometimes, and, in looking, think of me. And, in thinking of me, do
not think of me as one who plundered you, but as one who--
She paused. She looked down. But he was the most awkward of
men. When she looked up again her face was fiery red. She drew
herself away from him, and when she spoke her tone was changed.
So, Mr Davison, you quite perceive that you owe my father
nothing. You two are quits. But there is one thing you must promise
me--you will not fight him.
I do not understand.
Oh, it is simple. He will challenge you. After what passed last
night he is sure to challenge you. But, however that may be, you
must say 'No.'
If you wish me to, I promise. But in England we don't fight duels.
No? Not even at the 'Varsity?
She nodded to him and smiled. And in a moment she was gone.
Mr Davison found Mr Lintorn still engaged in putting the finishing
touches to his costume. The expression of his countenance was a
vivid note of interrogation.
Well, was it she?
Mr Davison said Yes.
I should have won that guinea.
Mr Davison narrated the interview. When he had finished, Mr
Lintorn reflected.

Odd! Something of the same sort happened to me. It was at
Mentone I first encountered the de Fontanes. On two or three
evenings I played écarté. I lost; but not five hundred pounds. Two or
three days afterwards the sum which I had lost came to me
enclosed in an envelope. Not a scrap of writing was with it, but the
address was in a feminine hand; I always suspected it came from
the lady. When I again inquired for the de Fontanes they were gone.
But my curiosity was piqued. I did not forget them. So I renewed the
acquaintance when I saw them here.
If he challenges me, what shall I do? I promised not to fight him.
Besides, the thing would be a rank absurdity.
Stand to your promise. I tell you what to do. There's a boat
leaves for Folkestone in an hour. Let's go by it together.
But wouldn't that look like running away?
It would be running away.
Mr Davison did not quite like this way of putting it, but he went.
They travelled together. On the boat Mr Davison remembered the
locket. He opened it. It contained a portrait of the giver. As he eyed
it, he observed in that curious vernacular which is an attribute of
some examples of modern youth,--
By Jingo! aren't those French girls goers?
But Mr Lintorn was an older man. His range was wider.
Don't judge of a nation by an individual. Mdlle. de Fontanes is
unique; the product, I should say, of a very singular experience.
Actually, Mr Davison kissed the portrait.
I will always keep it, he said.

THE GIRL AND THE BOY
I
Archie Ferguson's smoking-room. He and I its only occupants. We
had been to a meeting of the Primrose League which had been held
at the neighbouring county town. Knocking off the ash from his
cigar, he broke an interval of silence by asking me a question.
Did you notice a woman who, just as we were leaving the hall,
came up and shook hands with me in rather an effusive way?
A good-looking, well-dressed woman, with rather an effusive
smile? I wondered who she was.
She's a Mrs Bennett-Lamb. The weight-carrying man who was
standing at her side was Mr Bennett-Lamb. Perhaps you know the
name. She and her husband have been the owners of a good deal of
the public-house property in London which is worth owning. They're
the proud possessors of some of it still. They've made a heap of
money. Some of it they've spent in buying a place near here--
Oakdene. It's on the cards that their daughter--they've only one, and
she's an uncommonly pretty girl--will make a first-rate match. In
which case, no doubt, they'll try to graduate for county honours.
He flicked off another scrap of ash before he spoke again.

It was Mrs Bennett-Lamb who found the money with which to
start the firm. The way in which she found it was curious. It's a
queer story. I'll tell it you, if you like. It's a rather good one.
I lit another cigar; and smoked it while Ferguson told his story.
* * * * *
At that time Mrs Bennett-Lamb was a chorus girl at the Frivolity
Theatre. In those days only pretty girls were allowed to appear on
the Frivolity stage. The management's standard of beauty was a
high one. It drew all London. And the prettiest of the whole crowd
was Ailsa Lorraine. Whether Ailsa Lorraine was or was not her real
name I am unable to tell you; I have reason to know that nowadays
her husband calls her Peggy; but that was the name by which she
was known on the programme. Miss Lorraine was engaged to be
married--to Joe Lamb. Where the Bennett comes from Mr and Mrs
Bennett-Lamb only know. It is certain that then the present J.
Bennett-Lamb, Esquire, was plain Joe Lamb. Not to put too fine a
point upon it, Joe Lamb was a grocer's assistant--and not a
flourishing specimen of his kind. In fact, the more he considered his
position and future prospects the more despondent he became.
One Sunday afternoon he went to tea at Miss Lorraine's. While
they were enjoying the meal he gave utterance to the feelings which
filled his bosom.
We've been engaged for more than two years, he began.
Two years! the tone in which she echoed his words were
intended to indicate surprise. It doesn't seem anything like so long
as that, does it, Joe?
It does to me. It seems every bit as long. In fact, I don't mind
telling you that it seems longer.

Neither the words nor the manner in which they were spoken
suggested a compliment, as the lady appeared to think. There was a
rueful look upon her pretty face and a mist dimmed her eyes as she
asked him a question in return.
Does that mean that it has seemed so long because you're tired
of being engaged to me?
It does; that's just exactly what it does mean.
Joe!
Now don't jump up like that! You nearly upset the tray, and I've
hardly touched my third cup of tea. What are you up to? Crying?
I'm sure, Mr Lamb, if you wish to release me you're perfectly at
liberty to do so at once; and you need never see nor speak to me
again. There's no fear of my bringing an action against you for
breach of promise of marriage.
Whatever are you talking about?
I'm sure if you'd even dropped so much as the slightest hint
you'd have seen the last of me long enough ago; and I certainly
wouldn't have worried you to come to tea.
What have I said or done to start you off like this?--just as I was
beginning on a fresh round of toast!
How dare you say you were tired of being engaged to me!
So I am.
Joe--Joe Lamb!
It's gospel truth. I want you for my wife; that's what I want.

The lady's face perceptibly brightened. The tone of her voice was
altered also.
Joe! What extraordinary ways you have of expressing yourself.
Will you kindly explain exactly what it is you mean?
I've been engaged to you more than two years, and you're no
nearer being my wife than you were at the beginning. If anything,
you're further off. And I'm sick and tired of waiting; that's what I
mean.
If you'd only said so at first.
I did; didn't I?
I thought you meant something quite different.
I can't help what you thought. I know what I meant.
Poor Joe! So you want us to be quick and get married, do you?
Of course I do; what else do you suppose I got engaged for? But
we can't marry on ten bob a week.
Hardly.
And that's all I get, living in. I asked the governor yesterday to
give me thirty bob and let me live out. He said all he'd give me was
a week's notice.
The wretch!
As for bettering myself; I dare say I've spent five shillings on
paper, stamps and envelopes, and nothing's come of it. We don't
want to get married and have you keep on the stage.
We certainly don't. I have a voice in that matter. When I marry I
leave the stage for good; I don't marry until I do. I hate the theatre;

that is, I don't mind being in front of the curtain, looking on; but I
hate being behind. I only go there because I don't know any other
way of earning two pounds a week. I've no delusions about the
stage like some of the girls have. But, tell me, Joe, can't you think of
any way of earning more?
There's one way.
What's that?
Emigrating.
As she repeated the word again the expression on the lady's face
grew rueful.
Emigrating!
Going to Africa or Canada or one of those places where a fellow
has a chance.
But you'd have to leave me behind.
That's the worst of it.
We mightn't see each other again for years.
We mightn't.
There was a pause. The lady had seated herself on the arm of the
chair on which her lover sat, and was smoothing his hair with her
dainty little hand.
Joe, would you like to do that?
I'd sooner do anything--anything! I'd sooner sweep a crossing;
I'd sooner be a shoeblack. I hear that some of them shoeblacks earn
six and seven shillings a day when there's plenty of mud about.

I don't think I should care for you to be a shoeblack, even when
there's plenty of mud about. I'd almost rather you did anything than
that.
But there's nothing I can do.
Another pause; this time a longer one. Joe Lamb sat with his
hands thrust deeply into the pockets of his Sunday trousers; a frown
upon his brow. The lady continued to smooth his well-brushed hair.
Joe, suppose I were to see my way to earn some money.
You! Are they going to raise you to fifty shillings, and give you a
line to speak: 'The carriage waits,' or something of that sort?
She suffered his ungraciousness to pass unheeded.
Suppose I were to see my way to earn, say, five thousand
pounds.
Mr Lamb, withdrawing his head from the neighbourhood of the
lady's caressing hand, sat bolt upright in his chair with a start.
Five--what?
I know a public-house which is to be bought cheap, if bought at
once. Never mind how I know, but I do. We could get it for five
thousand pounds and have plenty over to go on with. You and I
might work the business up and in two years sell it for twice as
much as we gave for it. Joe, what do you think?
I think--it's no use my telling you what I think, because you
wouldn't like it. You might as well talk about buying the moon.
I'm not so sure of that. I believe I could earn the money if I
liked.

You earn five thousand pounds! Well! I don't want to say
anything--not a word; but might I just ask how you propose to set
about it?
By bringing an action for breach of promise of marriage.
What!
I shouldn't be surprised if I got at least five thousand pounds by
way of damages.
Joe Lamb, who had risen from his seat, was staring at her with,
on his countenance, an expression of increasing stupefaction.
From whom?--from me?
The idea! She laughed, as if the notion tickled her. In the first
place, I shouldn't dream of suing you, even if you were to prove
false; and you know very well that you're not worth half as many
farthings if I did. No; I propose to obtain my five thousand pounds
from Sir Frank Pickard.
Who's Sir Frank Pickard?
He's a young gentleman--a very young gentleman, just turned
twenty-one, who's fallen head over heels in love with me.
The lady was looking down at her skirt, as she smoothed it with
the tips of her fingers, with an air of the most extreme demureness.
Mr Lamb's face, as he regarded her, was rapidly assuming the hue of
a boiled lobster.
So you've been encouraging him, have you?
I have been doing nothing of the kind. So far, I haven't spoken to
him a single word. I've declined to receive his presents--even his
flowers.

So he's been sending you presents, has he!--and flowers.
The lady sighed, as if she found the gentleman a little trying.
My dear Joe, all sorts of people fall in love with me to whom I
have never spoken in my life, or they say they do. They send me
flowers and presents, and all kinds of things, which I always refuse
to accept, although some of the other girls call me a goose for my
pains. I can't help their falling in love with me, can I?
She looked up at him with an air of innocence which was almost
too perfect to be real. So far from it appeasing him, he began
stamping up and down the room, clenching and unclenching his fists
as he moved.
A nice sort of thing for a man to be told by his young woman!
You shall leave that confounded theatre this week!
To do so is part of my plan. I shall hand in my notice to-morrow-
-that is, if I am engaged to Sir Frank Pickard by then.
What?
Joe! don't be silly! Why are you glaring at me like that? Won't
you understand? Already, in three separate and distinct letters Sir
Frank has asked me to marry him.
Has he?
Though, of course, I've paid no sort of attention to his insane
request.
I should think it was insane!
I don't fancy I use the word in quite the same sense in which
you do. However, I've been making inquiries about him. I find he's of
a very old family, and tremendously rich. His father is dead. He's the

only child of his mother; she can't prevent his doing anything he
chooses to do, and she wouldn't if she could. She idolises him.
During his minority the income has accumulated, until now he has at
his command a perfectly enormous sum of ready money. Five
thousand pounds is nothing to him, or ten either. My idea is to ask
him to call on me to-morrow, and then to get him to repeat in
person the proposal which he has already made by letter. Having
accepted him, I shall see that he puts it all down in black and white,
so that everything is quite ship-shape. And then I shall hand in my
notice at the theatre.
During the lady's remarks Mr Lamb's countenance was a
panorama of disagreeable emotions.
And where do you suppose I shall be while all this is going on?
You'll be at the shop.
Not much I sha'n't. I'll keep on hanging about your front door
until I catch sight of your fine gentleman; and then I'll break his
neck.
Don't be silly. After we're engaged and everything is signed and
sealed and settled I shall begin to behave in a fashion which will
soon make him as anxious to break his promise as he was to make
it.
I bet he will! You wait till I get within reach of him, that's all.
You will not appear upon the scene. You would spoil all if you
did. I shall manage everything.
I fancy I see myself letting you do it! You've got some pretty
ideas of your own!
You'll find by the time I've finished that I've some very pretty
ones indeed. You don't know what a treasure you possess. When Sir

Frank begins to show signs of wanting to back out of his promise I
shall begin to talk about my injured feelings; to which, however, he'll
find it possible to apply a soothing plaster in the shape of--well, say
five thousand pounds.
You're a nice piece of goods, upon my word! I ask you again
where do you suppose I shall be while all this is going on?
And I tell you again, you'll be at the shop. You open so early and
close so late, and get out so little on week-days, that you never get
a chance of seeing me even after I leave the theatre. Possibly by
next Sunday, when we shall have a chance of seeing each other
again, it will all be settled.
By next Sunday?
Exactly. I mean to keep things moving. Possibly by next Sunday I
shall be within reach of the money which will enable us to marry and
ensure our future happiness. Think how delightful that will be! We
can't marry on ten shillings a week; after we're married I don't mean
to stay on at the theatre, and so keep up a home for us both; and as
for your emigrating--the chances are that we might never see each
other again. And, anyhow, it might be years before you earned even
a tenth part of five thousand pounds. So do be reasonable. I'm sure
if you think it over you'll see perfectly well that my way is by far the
best.
It was some time before Mr Lamb was reasonable--from the lady's
point of view. It is doubtful if to the end he saw as plainly as she
would have liked him to, that her way was the best. But at that
period of her career she had a way about her to which few men
were capable of offering a prolonged resistance. Joe Lamb was
distinctly not one of those few. By the time they parted she wrung
from him what she told him plainly she intended to regard as his
approbation of her nefarious schemes. So soon as his back was
turned she wrote a stiff, formal note, in the third person, in which

she informed Sir Frank Pickard that Miss Ailsa Lorraine would be at
home to-morrow--Monday--afternoon at three o'clock and might be
disposed to see him if he desired to call.
It's not exactly a nice sort of thing to do, she admitted to
herself, as she secured this epistle in an envelope. But it's the sort
of opportunity which never may occur again; it seems wicked to
throw it away. Especially as poor dear Joe never will be able to get
the money by himself. I am convinced that he's just the sort of man
to take advantage of a chance if he has one. And I love him well
enough to get him one. And that's the whole truth in a nutshell.
II
On the Monday afternoon a hansom drew up at the door of the
by no means pretentious house in which Miss Lorraine had her
quarters. Out of it stepped Sir Frank Pickard. He bore with him
upstairs what seemed to be a by no means insignificant portion of
the contents of a fair-sized shop. In one hand he carried a
magnificent bouquet, a large basket of splendid fruit, a big box of
bonbons and a mysterious case which, as a matter of fact, was filled
with various kinds of gloves. In the other were unconsidered trifles
in the shape of bottles of perfume, silver knickknacks, a writing case,
and other odds and ends. His arms were filled with parcels of
different shapes and sizes which contained he alone knew what.
Under the circumstances it was not surprising that he found it a little
difficult to know what to do with his hat. As he entered Miss
Lorraine's sitting-room he was in a state of some confusion.
Plumping the contents of one of his arms on the nearest chair,
whence they mostly proceeded to tumble on to the floor, he
removed his hat in a fashion which was rather dexterous than

elegant. As if conscious that he was not making his first appearance
under the most propitious conditions, his cheeks were a beautiful
peony red.
Miss Lorraine had risen to receive him. She had on her best frock-
-a frock which she specially reserved for high-days and holidays.
Although she had made it herself, it could not have become--or
fitted--her better had it been the creation of one of the world's great
dressmakers. At least, such was the instant and unhesitating opinion
of Sir Frank Pickard. He felt that he had never seen a more perfect
example of feminine beauty--of all that was desirable in woman; he
was convinced that he never should. He was trembling from head to
foot; as some boys still do tremble when, for the first time in their
lives, they are head over heels in love. Miss Lorraine, on the other
hand, was both cool and calm--an accident which enabled her to
perceive that her visitor was very much the reverse. She looked him
up and down, inclining to the opinion, as the result of her inspection,
that he was not an ill-looking boy. He was fairly tall, broad-
shouldered, carried himself well, and looked a gentleman. She told
herself that, had her affections not been pre-engaged, it was
extremely possible that she might have regarded him in quite a
different kind of way. But her heart really was Joe Lamb's; and she
never for a moment contemplated the feasibility of transferring it to
anybody else.
The lady was the first to speak.
You are Sir Frank Pickard?
The visitor had been afforded an opportunity to disencumber
himself of his parcels, and therefore ought to have become more at
his ease. But the simple truth was that the sight of the lady
embarrassed him more than the parcels had done. His heart was
thumping against his ribs; he seemed to be giving way at the knees;
his tongue clave to the roof of his mouth. However, he managed to

stammer out something; though it was only with difficulty that he
could articulate at all.
It's awfully good of you to let me come and see you.
The lady smiled--a smile which might have been described as of
the glacial kind.
Will you sit down, Sir Frank?
He sat down, on the extreme edge of a chair, as if fearful of
occupying too much of it at once. He looked--and no doubt was--
excessively uncomfortable. Placing herself in the only arm-chair the
room contained, she observed him with an air which was at once
both cruel and condescending.
You have written me one or two notes, Sir Frank?
He stammered worse than ever. Not only did he find the question
an awkward one, but it seemed to him that the lady was even more
bewitching in the arm-chair than she had been when standing up. As
he realised--or thought he realised--her charms still more clearly, his
few remaining senses were rapidly deserting him.
I--I'm afraid I did.
In which you asked me, a perfect stranger, to be your wife?
I--I'm awfully sorry.
You are sorry? Indeed. Do you mean that you are sorry you
asked me to be your wife?
He gasped. There was something in her tone, something in the
way in which she peeped at him from under the long lashes which
shaded her violet eyes, something in her attitude, in the quality of
the smile which parted her pretty lips, which set every fibre in his

body palpitating. What did she mean? What could she mean? Was it
possible that she meant--what he had scarcely dared to hope she
ever would mean?
In his stuttering eagerness his words tumbled headforemost over
each other.
Of course what I meant was that I know perfectly well that I
never ought to have written to you like that. It was frightful cheek,
and--and the sort of thing I ought to be kicked for. But as for being
sorry that I asked you to be my wife--! The boy's feelings were so
intense that for the moment his breath entirely failed him. When he
continued, tears were actually standing in his eyes. Oh, Miss
Lorraine, if you only knew what I have felt since I first saw you. I
have been to the theatre every night; I have waited at the stage
door to see you come out--
So I understand. It was very wrong of you.
I had to do something--I couldn't help it. I didn't know anyone
who'd introduce me; you wouldn't answer my letters; you refused
my presents--
Certainly; under the circumstances they were so many insults.
I didn't mean them for insults--I swear I didn't. I wouldn't have
insulted you, or allowed anyone else to insult you, not--not for all
the gold of the Indies.
Sir Frank, the question I put to you was, are you sorry that you
asked me to be your wife? That is, did you really wish me to be your
wife, and do you wish it still?
Wish it! I'd give all I have if you'd be my wife; you'd make me
the happiest fellow in the world!
If you truly mean that--

Put me to the test and see if I mean it!--say yes!
I do believe that you mean it; so I will say yes. One moment, Sir
Frank! Rising from his chair the young gentleman showed
symptoms of a desire to express his feelings in a style which the lady
might have found slightly inconvenient. A girl in my position cannot
be too careful. If you care for me as you say, you will see that even
better than I do. That was rather a bold stroke of Miss Lorraine's,
and a clever one. For it made an irresistible appeal to the boy's
quixotic nature. Remember, you and I are still almost strangers.
Nevertheless, you have asked me to be your wife; and I have
consented. Will you write a few lines, setting forth the exact position
of affairs, on this sheet of paper?
She pointed to paper, pens and ink, which were on the centre
table. The youngster did hesitate. There was a matter-of-fact air
about the fashion in which the lady made her suggestion which,
even to his eyes, rather blurred the romance of the situation. But his
hesitation did not endure. He was like wax in her hands. Presently
he sat down and wrote on a sheet of paper the words which--
without his being altogether conscious of the fact--she had put at
the point of his pen.
You understand, Sir Frank, she remarked, as she folded up
what, from her point of view, was an invaluable document, and
slipped it in the bodice of her dress, this engagement of ours must
be no hole-and-corner affair. You must not conceal it from your
mother!
Of course not. I never have concealed anything from her in my
life, and I certainly don't mean to start concealing from her that I'm
engaged to be married.
You must introduce me to her.
Rather! I shall be only too delighted, if you'll let me. She already
has some idea of how it is with me. I wrote to her that I'd fallen

Welcome to our website – the perfect destination for book lovers and
knowledge seekers. We believe that every book holds a new world,
offering opportunities for learning, discovery, and personal growth.
That’s why we are dedicated to bringing you a diverse collection of
books, ranging from classic literature and specialized publications to
self-development guides and children's books.
More than just a book-buying platform, we strive to be a bridge
connecting you with timeless cultural and intellectual values. With an
elegant, user-friendly interface and a smart search system, you can
quickly find the books that best suit your interests. Additionally,
our special promotions and home delivery services help you save time
and fully enjoy the joy of reading.
Join us on a journey of knowledge exploration, passion nurturing, and
personal growth every day!
ebookbell.com

Solaris 10 System Administration Essentials Engineers Solaris Systemcreator

More Related Content

Similar to Solaris 10 System Administration Essentials Engineers Solaris Systemcreator (20)

Recently uploaded (20)

Solaris 10 System Administration Essentials Engineers Solaris Systemcreator