SA226 - Transitioning To Solaris 2.6 - SG - 0997

Transitioning to Solaris 2.
SA-226
Seminar Handbook
Sun Educational Services

SunService Division
Sun Microsystems, Inc.
901 San Antonio Road
UMIL02-105
Palo Alto, CA 94303
U.S.A.
Part Number 805-2890-01

Revision A, September 1997
Copyright © 1997 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303, U.S.A. All rights reserved.
This product or document is protected by copyright and distributed under licenses restricting its use, copying,
distribution, and decompilation. No part of this product or document may be reproduced in any form by any means
without prior written authorization of Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a
registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, and the Sun Logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S.
and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun
Microsystems, Inc.
RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-
14(g) (2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015 (b)(6/95) and DFAR 227.7202-3(a).
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS,
AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLAY INVALID.
Seminar Developers: John Accardi, Patrick Born, Rich Gilbertson, Matt Gomes, Jerald Josephs, Bill Norton, Don Roach,
Debra Scott, and Mark Wright
Please
Recycle
Contents
About This Seminar .................................................................................. vii
Seminar Overview ........................................................................... viii
Seminar Map........................................................................................ ix
Module-by-Module Overview ........................................................... x
Seminar Objectives........................................................................... xiii
Seminar Icons and Typographical Conventions .......................... xiv
Icons ............................................................................................xiv
Typographical Conventions .....................................................xv
Java................................................................................................................1-1
Java ...................................................................................................... 1-2
Context........................................................................................1-2
Features ......................................................................................1-3
Java Virtual Machine .........................................................1-3
HotJava Browser ................................................................1-6
Intranet/Internet Servers ..........................................................................2-1
Intranet/Internet Servers................................................................. 2-2
Context........................................................................................2-2
Features ......................................................................................2-3
WebNFS ...............................................................................2-3
Sun WebServer ...................................................................2-7
Performance Improvements.....................................................................3-1
Performance Improvements ............................................................ 3-2
Context........................................................................................3-2
Features ......................................................................................3-3
Database Performance .......................................................3-3
UFS Direct I/O ...................................................................3-6
Raw I/O ...............................................................................3-7
Network/Web Server Performance ................................3-7
Kernel Sockets ....................................................................3-9
TCP Large Windows .......................................................3-10
Zero Copy TCP/Hardware checksum ..........................3-11
iii
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved. SunService September 1997
Ease-of-Use and Management Improvements .....................................4-1
Ease-of-Use and Management Improvements ............................. 4-2
Context........................................................................................4-2
Features ......................................................................................4-3
Solaris Web Start Browser-based Installation ................4-3
New Installation Documentation ....................................4-6
Solaris 2.x Compatibility ...................................................4-8
Changed Solaris CD-ROM Layout ..................................4-8
Disk Space Reallocation Upgrade Options ..................4-10
Upgrade Profile Testing ..................................................4-12
System Boot Device Modifications ................................4-16
Preconfiguration of System Configuration
Information ....................................................................4-18
Disabling Stop A ..............................................................4-19
Documentation .................................................................4-21
Desktop ........................................................................................................5-1
Desktop............................................................................................... 5-2
Context........................................................................................5-2
Features ......................................................................................5-3
Common Desktop Environment ......................................5-3
Power Management for SPARC Desktop Systems .......5-8
Solaris User Registration .................................................5-15
Standards .....................................................................................................6-1
Standards............................................................................................ 6-2
Context........................................................................................6-2
Features ......................................................................................6-3
Year 2000 Ready .................................................................6-3
Robust Software Developer Environment............................................7-1
Robust Software Developer Environment .................................... 7-2
Context........................................................................................7-2
Features ......................................................................................7-3
Versioning and Scoped Libraries .....................................7-3
Scheduler Activation .........................................................7-5
Preemption Control ...........................................................7-5
/proc File System and Watchpoints ...............................7-6
Federated Naming Service (FNS) ....................................7-7
Asynchronous I/O for Tapes ...........................................7-8
Solaris Developer Kit (SDK) .............................................7-8
Graphics ...............................................................................7-9
X Server Configuration ...................................................7-17
Large Files Support....................................................................................8-1
Large Files Support........................................................................... 8-2
Context........................................................................................8-2
Features ......................................................................................8-3
iv Transitioning to Solaris 2.6

Large Files ...........................................................................8-3
64-bit Asynchronous Input/Output (AIO) ....................8-6
Network Security .......................................................................................9-1
Network Security .............................................................................. 9-2
Context........................................................................................9-2
Features ......................................................................................9-3
NFS Kerberos ......................................................................9-3
RPCSEC_GSS ......................................................................9-5
Pluggable Authentication Modules (PAM)
Framework .......................................................................9-6
BIND 4.9.4-P1 ....................................................................9-12
Network Management and System Administration.........................10-1
Network Management and System Administration ................. 10-2
Context......................................................................................10-2
Features ....................................................................................10-3
Network Time Protocol (NTP) .......................................10-3
Solstice Enterprise Agents (SEA) ...................................10-6
Dynamic Host Configuration Protocol (DHCP) ..........10-7
NFS Client Failover ........................................................10-11
Variable Length Subnet Mask (VLSM) .......................10-12
Routing Sockets ..............................................................10-13
Processor Sets .................................................................10-14
Autofs ..............................................................................10-15
NIS+ Backup and Fast Restore .....................................10-17
NIS+ Over a Wide Area Network (WAN) .................10-18
NIS Server .......................................................................10-20
CFS Boot ..........................................................................10-21
Patch Tools ......................................................................10-22
Printing ......................................................................................................11-1
Printing ............................................................................................. 11-2
Context......................................................................................11-2
Features ....................................................................................11-3
Redesign of Print Packages .............................................11-3
Print Protocol Adaptor ....................................................11-6
SunSoft Print Client .........................................................11-7
Enhanced Network Printer Support .............................11-9
Other Minor Differences .........................................................................A-1
Ease-of-Use and Management Improvements ....................A-2
Configuration Assistant and Booting Software
for x86 Platforms ............................................................A-2
x86 Configuring Peripherals ...........................................A-2
Optional 8-bit Locales .......................................................A-4
v
Desktop.............................................................................................. A-5
New User Locales in the Solaris 2.6 CD-ROM ..............A-5
Unicode 2.0 Support .........................................................A-5
Font Administration .........................................................A-6
Asian Language Enhancements ......................................A-6
Standards........................................................................................... A-7
The X/Open UNIX 95 (Spec 1170) ..................................A-7
X/Open XFN CAE ............................................................A-7
POSIX 1003.1b ....................................................................A-8
ISO 10646 ............................................................................A-9
PCMCIA PC Card ...........................................................A-10
Nomadic Support: File Synchronization .................................... A-11
filesync ..........................................................................A-11
Where To Go For Help ............................................................................. B-1
Sun Educational Services Courses................................................. B-2
vi Transitioning to Solaris 2.6

About This Seminar
Seminar Goal
The goal of this seminar is to present the major new features
in the Solaris 2.6 operating environment, as well as discuss
major features of the previous release that have been
updated.
vii
Seminar Overview
In this seminar, you will learn the major new features added to the
Solaris environment in the 2.6 release and key areas that have been
updated. These features apply to topic areas such as servers,
performance, network security, developer support, large files, printing,
and desktop environments.
Note – This course does not present details on how to administer, use,
or customize the features discussed. These details are provided in the
materials referred to in each module and in the system administration
courses offered by Sun Educational Services.
viii Transitioning to Solaris 2.6

Seminar Map
Each module begins with a seminar map that enables you to see what
you have accomplished and where you are going in reference to the
seminar goal. A complete map of this seminar is shown below.
Topics Covered
Java Intranet/Internet
Servers
Performance Ease-of-Use & Desktop

Improvements Mgmt. Improvements
Standards Robust Software Large Files

Developer Environment Support
Network Network Management & Printing

Security System Administration
About This Seminar ix

Module-by-Module Overview
● Module 1 – Java
This module discusses how parts of the Java platform are not part
of the Solaris environment.
● Module 2– Intranet/Internet Servers
The major new features relevant to servers is discussed in this

module.
● Module 3 – Performance Improvements
This module examines the features that were added to improve

system and application performance.
● Module 4 – Ease-of-Use and Management Improvements
In this module, the features that enable easier installation and

provide end-users with a new easy-to-use desktop are discussed.
x Transitioning to Solaris 2.6

● Module 5 – Desktop
This module discusses the features of the new default desktop, the
Common Desktop Environment.
● Module 6 – Standards
This module looks at the year 2000 ready issue.
● Module 7 – Robust Software Developer Environment
The features added to the Solaris environment that make software

development easier and more robust are presented in this module.
● Module 8 – Large Files Support
Features that support file sizes of up to 2 Gbytes are examined.
● Module 9 – Network Security
In this module, the changes and new features that support or

enhance network security are presented.
About This Seminar xi

● Module 10 – Network Management and System Administration
The new features and updates relevant to network management

and system administration are presented in this module.
● Module 11 – Printing
This module discusses the new printing features in the Solaris

environment.
xii Transitioning to Solaris 2.6

Seminar Objectives
Upon completion of this seminar, you will be able to:
● List the key features in the Solaris 2.6 release
● Describe the importance of these key features to your work

environment
● Identify where to find more detailed information on other Sun

Educational Services courses
About This Seminar xiii

Seminar Icons and Typographical Conventions
The following icons and typographical conventions are used in this

seminar to represent various training elements and alternative
learning resources.
Icons
Indicates additional reference materials are available.
Indicates Sun Educational Services courses that cover the current

topic.
Indicates a new feature.

New
Indicates a feature that has been updated.

Update
Note – Additional important, reinforcing, interesting, or special

information.
Caution – A potential hazard to data or machinery.
!
Warning – Anything that poses personal danger or irreversible
damage to data or the operating system.
xiv Transitioning to Solaris 2.6

Seminar Icons and Typographical Conventions
Typographical Conventions
Courier is used for the names of commands, files, and directories, as
well as on-screen computer output. For example:
Use ls -al to list all files.

system% You have mail.
Courier bold is used for characters and numbers that you type. For
example:
system% su
Password:
Courier italic is used for variables and command-line

placeholders that are replaced with a real name or value. For example:
To delete a file, type rm filename.
Palatino italics is used for book titles, new words or terms, or words
that are emphasized. For example:
Read Chapter 6 in User’s Guide.

These are called class options
You must be root to do this.
About This Seminar xv

Java 1
Seminar Map
This module discusses how the Java™ platform has been
made an integral part of the Solaris 2.6 operating
environment.
Topics Covered
Servers



1-1
1
Java
Context
The Solaris™ 2.6 operating environment lays the foundation for Java™
computing by bundling the Java Virtual Machine™, the interpreter for
the Java language, with Solaris. The HotJava™ browser is also
conveniently bundled with Solaris. It is an easy-to-use Internet
browser for exploring the World Wide Web (WWW) and is
recommended for viewing and installing Sun™ online documentation.
1-2 Transitioning to Solaris 2.6

1
Java
Features
New Java Virtual Machine

The Java Virtual Machine (JVM) 1.1 provides access to the Java
platform for the Solaris operating environment. It is compatible
with the 1.1 Java Developer Kit (JDK™) from JavaSoft™. It
includes the standard Java compiler (javac), the Java interpreter
(java), the Java class file disassembler (javap), and the C-header
and stub file generator (javah). The Solaris JVM also includes a
just in time (JIT) compiler, which improves performance.
The JVM uses Solaris native threads, which provide

multiprocessor support for Java threads. Use of Solaris native
threads improves Java application scalability and integration with
native methods.
In addition, the Solaris JVM includes the appletviewer

application. The appletviewer is used by Java developers to test
applets outside of the context of a WWW browser.
Java 1-3
1
Java
Features
Java Virtual Machine (Continued)
javald(1), another enhancement, is used to manage Java

applications and generate wrappers which execute Java programs.
The wrapper ensures that a Java program is executed with
JAVA_HOME, CLASSPATH, and LD_LIBRARY_PATH environment
variables that are set correctly for the program.
What This Means to You: Your users will now have the software
they need to run their favorite Java applications. It is a great step
towards the implementation of Java as a platform-independent
environment.
Solaris 2.6 Reviewer’s Guide
Network Interfaces Programmer’s Guide

1
Notes
Java 1-5
1
Java
Features (Continued)
New HotJava Browser

The HotJava browser (Figure 1-1) provides an easy-to-use,
customizable user interface for exploring the Internet. HotJava
features include:
● Java applet support
Applets are small programs that can be included on a Web

page, much like images are.
● Network security
The HotJava browser provides a secure environment for

running applets. It supports signed applets, which enables you
to fine tune the desired level of security.

1
Java
Features
HotJava Browser (Continued)
Figure 1-1 The HotJava Browser
● Full HTML support
HTML (hypertext markup language) is the language used to create

Web pages. The HotJava browser supports the latest HTML
standard, which is currently HTML 3.2.
Java 1-7
1
Java
Features
HotJava (Continued)
● HTML verification
Whenever you display a page with HTML errors, the HotJava

HTML Errors button is activated. Click on this button for a list
of the errors. This is useful if you are developing your own
HTML page or if you are having trouble displaying a page.
● Multithreaded applications support
Because the HotJava browser is written in the Java

multithreaded language, several actions can take place
simultaneously. For example, the browser can fetch multiple
images at the same time, or it can clone HotJava pages,
allowing you to have several HotJava windows open at one
time.
● External viewer applications
There are a multitude of file types on the WWW. When

HotJava encounters a file that it cannot display in a web page,
it starts up the appropriate external viewer application and
uses it to display the file. A graphical user interface (GUI) is
provided to enable you to specify your own content or
application viewer.

1
Java
Features
HotJava (Continued)
● Fully configurable user interface
You can easily customize the HotJava browser to look and

work the way you want. For example, one area of
customization is security. With the HotJava browser, the user
can specify different levels for signed applets and for unsigned
applets.
Much of this customization can be done without any

programming.
● Extensible support for content and protocol handlers
The HotJava browser provides extensible support for new data

types and protocols. A Java programmer can define new
content and protocol handlers to use with HotJava.
The HotJava browser is also used in the new Web Start

installation process.
What This Means to You: The Sun HotJava browser is the

cornerstone of the user’s view of the Java computing environment.
The Solaris 2.6 operating environment includes many new features
which are based on Java technologies.
SA-235: Solaris 2.x System Administration I
Java 1-9
Intranet/Internet Servers 2
Seminar Map
This module discusses the changes in the Solaris 2.6 operating
environment that are relative to intranet and Internet servers.
Topics Covered
Servers



2-1
2
Intranet/Internet Servers
Context
The Solaris operating environment is the intranet and Internet leader,
and a powerful and reliable Web platform. The Solaris software is the
premier operating environment for building a robust Web-based
network infrastructure. As companies move toward using the Web,
both internally and externally, powerful Solaris features, such as
WebNFS™ that provide speedy access to Web files, become crucial.

2
Features
New WebNFS
WebNFS software enables file systems to be accessed through the
Web using the NFS (network file system) protocol. This protocol is
very reliable and provides greater throughput under a heavy load.
Also, files can be made publicly accessible without the overhead
associated with an anonymous ftp site.
WebNFS is a standard part of Solaris 2.6.
Intranet/Internet Servers 2-3

2
Features
When to Enable WebNFS Access
In the 2.6 release, all file systems that are available for NFS
mounting are automatically available for WebNFS access by
default. However, this may result in excessively long URL strings.
To shorten the string, you can follow the procedure shown under
‘‘How to Enable WebNFS Access’’ on page 2-5. This procedure can
also be used if the -index option is required.
The -public option allows URLs (uniform resource locators) to be

relative to the shared file system rather than to the server’s root
file system. By default, the public file handle points to the root file
system. This file handle does not allow Web access unless the root
file system is shared, however.
Use the -public option of the share command to associate the

public file handle with a specific exported directory. Use the
-index option to load the index.html file rather than list the
directory which is referenced by the NFS URL.

2
Features
How to Enable WebNFS Access
1. Become superuser.
# su
2. Edit the /etc/dfs/dfstab file.
Add one entry for each file system that you want to have shared
automatically to the file. The -index tag is optional.
share -F nfs -o ro,public,index=index.html
/export/ftp
3. Check that the NFS service is running on the server.
If this is the first share command or set of share commands that

you have initiated, it is likely that the NFS daemons are not
running. The following commands will kill and restart the
daemons:
# /etc/init.d/nfs.server stop
# /etc/init.d/nfs.server start
4. Share the file system.
Once the entry is in /etc/dfs/dfstab, the file system can be

shared by either rebooting the system or by using the shareall
command. If the NFS daemons were restarted in step 2, then this
command does not need to be run because the script runs the
command.
# shareall
5. Verify that the information is correct.
Run the share command to check that the correct options are
listed:
# share
- /usr/src rw=eng ""
- /export/ftp ro,public,index=index.html ""

2
Features
How to Enable WebNFS Access (Continued)
6. Access the NFS directory with a browser using a URL which

matches the format below. Note that the default port is 2049.
nfs://server_hostname<:port>/path_to_file
What This Means to You: WebNFS brings the tested NFS

technology to the WWW. Internet/Intranet application
implementators can now leverage the proven functionality and
performance of NFS to file system access through Web service.
Most importantly, the use of WebNFS minimizes the efforts of

system administrators who access NFS exported files as clients.
SA-286: Solaris 2.x System Administration II
NFS Administration Guide

2
Features
New Sun WebServer

The Solaris 2.6 operating environment offers Web server
performance enhancements that improve the speed of response to
user requests, increase the number of users able to connect to a
single server, and reduces client administration costs.
What This Means to You: The Sun WebServer has better server
performance which results in a reduction of client administration
costs not associated with additional service capacity.

Performance Improvements 3
Seminar Map
This module discusses the performance improvements made to the
operating environment in the Solaris 2.6 release.
Topics Covered
Servers



3-1
3
Performance Improvements
Context
Solaris 2.6 performance enhancements focused on improving database
and Web performance while maintaining the already high levels of file
server and time-share performance seen in the Solaris 2.5.1 operating
environment.

3
Features
Update Database Performance
Significant efforts were made to improve the performance of
database engines system. Work focused on two areas:
● Virtual memory (VM) improvements
VM changes focused on reducing overhead by using larger

pages for the shared memory area used by database engines to
share and store data. Instead of using the default system page
size for pages in this area, a larger page size of 4 Mbytes was
used. This reduces the amount of internal work the system has
to do when managing the page descriptions attached to each
process. When coupled with existing mechanisms for sharing
these descriptions, a performance increase of about 12 percent
was achieved on various industry standard tests.
Performance Improvements 3-3

3
Features
Database Performance (Continued)
● I/O throughput improvements
I/O (input/output) throughput jumped as the result of low-

level changes that minimized the overhead associated with
processing large lists of pages for I/O. These modifications
reduced the overhead associated with converting the virtual
address used by the system to the physical address needed by
the device drivers to execute I/O requests. With these
improvements, the cost of doing I/O to physical devices
dropped dramatically.
Throughput improvements have been demonstrated in a recent

Informix TPC-C benchmark that:
• Produced 15,461 tpmC at $134/tpmC

• Employed 13,000 users
• Used an SMCC (Sun Microsystems Computer, Corporation)
E4000 with 14 * 250-Mhz CPUs and 5 Gbytes of memory

3
Features
Database Performance (Continued)
This produced the highest Informix TPC-C number ever produced

and reflects the best price/performance in the mid-range class.
TPC-C is a benchmark conducted under the auspices of the

Transaction Performance Processing Council (TPC). It simulates a
warehouse distribution system. Data is contained in nine tables;
five transactions are executed against this data in pre-specified
mixes. The figure of merit is tpmC, which is shorthand for
transactions per minute in the TPC-C benchmark.

3
Features
New UFS Direct I/O

Many customers are interested in placing data directly on disk
without buffering it in memory. The Solaris 2.6 release provides
direct I/O to do this. Bulk I/O operations use large buffer sizes to
transfer large files (files larger than physical memory). An example
of a bulk I/O operation is downloading satellite data that writes
large amounts of data to a file.
Direct I/O data is read or written into a process' address space

without incurring the overhead of the operating system's page
caching mechanism.
What This Means to You: The performance demands of modern

commercial database applications require special data handling.
The direct I/O enhancements to UFS (UNIX® file system) result in
better data transfer rates between the database server process and
the disk. Data is read directly into the process’ address space.
Large buffer sizes speed up data being written to the disk.
directio(3C) man page

3
Features
Update Raw I/O
Improvements were made to low-level I/O support routines that
dramatically improved throughput for I/O to disk devices
without a file system (raw devices). (Raw devices are often used
for database files.) The driver for the SPARCstorage™ Array was
rewritten to improve its throughput.
Update Network/Web Server Performance

Previous efforts in improving network throughput had focused on
long-lived connections. These efforts resulted in the highest NFS
server numbers in the industry. The Web server area represents an
entirely different paradigm since it emphasizes short-lived
connections with little bandwidth demand during the connection.
Some of the work for the Solaris 2.6 release which greatly
improved that aspect of performance was packaged and released
as the Solaris Internet Server Supplement (SISS) for the Solaris
2.5.1 release. The SISS is now part of the new OS (operating
system) environment.
Web server performance improvements were achieved in several

areas, ranging from the socket interface layer and the TCP/IP
(Transmission Control Protocol/Internet Protocol) stack, to the
STREAMS framework.
The socket interface layer was redesigned as a file system

(sockfs), thereby removing the need to duplicate socket code in
the socket library as well as the STREAMS socket module. This
significantly improved the performance for the short-lived
connections that are common on the Web.

3
Features
Network/Web Server Performance (Continued)
The TCP/IP changes consisted of improvements which enabled

efficient handling of large numbers of connections and better
multithreading of the opening and closing of connections and
sockets. The STREAMS framework was restructured to allow more
efficient opening and closing of TCP/IP sockets.
The Standard Performance Evaluation Corporation (SPEC) has

released SPECweb96, a standardized benchmark for comparing
Web server performance. The benchmark is designed to provide
comparable measures of how well systems can handle HTTP
(Hypertext Transfer Protocol) GET requests. SPEC based the
workload upon analysis of server logs from Web sites ranging
from a small personal server up through some of the Internet's
most popular servers. Built upon the framework of the popular
SPEC SFS (System: File Server) benchmark, SPECweb96 can
coordinate the driving of HTTP requests from single- or multiple-
client systems. For the latest Solaris 2.6 SPECweb96 submissions
and more information on SPECweb96 benchmarks, please visit the
SPEC Web site at http://www.specbench.org.

3
Features
Update Kernel Sockets
The kernel sockets implementation provides improved
compatibility with SunOS™ 4.x and BSD (Berkeley Software
Distribution) sockets which enables higher socket performance.
These enhancements are transparent to the user and the
administrator.
SA-380: Solaris 2.x Network Administration

3
Features
New TCP Large Windows

TCP Large Windows provide the support described in RFC
(Request for Comments) 1323. They are designed to improve
performance over large bandwidth networks such as ATM
(Asynchronous Transfer Mode), or high-delay networks such as
satellite links, by expanding the amount of data that can be
outstanding in a TCP session from 65,535 bytes to approximately
1 Gbyte.

3
Features
New Zero Copy TCP/Hardware checksum

Zero copy TCP/hardware checksum functionality can be used to
increase TCP throughput in certain situations. It does so by
avoiding the copying of data and by using hardware checksum
logic in the network interface when available. Currently, the only
network interface that contains the hardware checksum logic is the
SunATM™ 622 interface.
Transport Interface Guide

Ease-of-Use and Management
Improvements 4
Seminar Map
This module discusses the new features that enable easier installation
of the Solaris environment and provide end-users with a new easy-to-
use desktop.
Topics Covered
Servers



4-1
4
Ease-of-Use and Management Improvements
Context
The Solaris operating environment is large and complex; its structure
gives customers the flexibility to meet their needs. Some of the new
features that enable customers to easily install and manage the Solaris
environment are:
● Solaris Web Start, a Web-browser installation tool
● An installation card which leads customers through the

installation
● A device Configuration Assistant for x86 machines
● A new, easy-to-use desktop called the Common Desktop

Environment (CDE)

4
Features
New Solaris Web Start Browser-based Installation

The Solaris software is the industry's first operating system that
can be installed using a Web browser. Solaris Web Start
(Figure 4-1) is a browser-based utility that guides users through
the selection and installation of both Solaris and co-packaged
application software. Its graphical user interface facilitates file
system configuration.
The utility's built-in suite of online information answers questions

about the product itself, the software it installs, and the hardware
platforms it supports. Use of the utility is optional; users can exit
at any point and proceed with the traditional SunInstall™ Solaris
installation method.
Ease-of-Use and Management Improvements 4-3

4
Features
Solaris Web Start Browser-based Installation (Continued)
Figure 4-1 Web Start Browser

4
Features
Solaris Web Start Browser-based Installation (Continued)
What This Means to You: Using the Web Start browser installation
package makes installation of software easy and convenient even
if your system is not capable of using a graphical user interface.
Web Start Information Library, the “Using Web Start” module

4
Features
New New Installation Documentation

A documentation reorganization (Figure 4-2) makes finding
information on how to install Solaris software easier. The desktop
product contains a small, step-by-step guide that describes how to
install the Solaris software from a local CD-ROM. The server
product contains an advanced guide for setting up servers and
clients, and descriptions of included software.

4
Features
New Installation Documentation (Continued)
Figure 4-2 Installation Documentation

4
Features
Update Solaris 2.x Compatibility
Moving to Solaris 2.6 is made as seamless as possible. System Test
places a significant focus on binary compatibility and extensive
testing is done during Beta with Sun Catalyst™ customers and
ISVs (independent service vendors).
This means that other 2.x binary files will work in Solaris 2.6.
Update Changed Solaris CD-ROM Layout

The Solaris CD-ROM layout has been changed in the Solaris 2.6
release (Figure 4-3). Slice 0 has been reorganized to make it more
intuitive and extensible. It contains only control files and the
Solaris_2.6 directory at the top level. The control files at the top
level on slice 0 are the same control files found on previous Solaris
CD-ROMs. The control files are .cdtoc, .slicemapfile, and
.install_config.

4
Changed Solaris CD Layout (Continued)
Slice 0
Control files Solaris_2.6
Docs Misc Patches Product Tools
Boot
Solaris boot image
Figure 4-3 Solaris CD-ROM Layout
Solaris Advanced Installation Guide

4
Features
New Disk Space Reallocation Upgrade Options

The upgrade option for the Solaris 2.6 release provides an auto-
layout feature which reallocates disk space if the current file
systems do not have enough space for the upgrade. This new
feature is provided in the interactive Solaris installation program
and by a new set of custom JumpStart™ profile keywords.

4
Features
A Sample Upgrade
# profile keywords profile values

# ---------------- -------------------
[ This profile upgrades a system by reallocating disk space. In this
example, disk space must be reallocated because some file systems on the
system did not have enough room for the upgrade.]
install_type upgrade
[ The root file system on c0t3d0s2 is upgraded.]

root_device c0t3d0s2
[ A remote system named timber will be used to back up data during the
disk space reallocation.]
backup_media remote_filesystem timber:/export/scratch
[ The layout_constraint keywords designate that auto-layout can change

slice 2 and 5 (the slices can be moved to another location and their
size can be changed) and it can move slice 5 (the slice can be moved to
another location but its size stays the same) when it tries to
reallocate disk space for the upgrade.]
layout_constraint c0t3d0s2 changeable 100
layout_constraint c0t3d0s4 changeable
layout_constraint c0t3d0s5 movable
[ The binary compatibility package (SUNWbcp) will not be installed on

the system after the upgrade.]
package SUNWbcp delete
[ This code ensures that the OpenLook and X Windows man pages and the
universal multiplexor software are selected to be installed if they are
not installed on the system. (All packages already on the system are
automatically upgraded.)]
package SUNWolman add
package SUNWxwman add
cluster SUNWCumux add
[ The German localization packages are selected to be installed on the

system.]
locale de

4

Features
Update Upgrade Profile Testing
In previous Solaris releases, the system administrator could only
test profiles that used the initial option. The Solaris 2.6 release
enables the pfinstall command to test profiles that use the
upgrade option, so an administrator can see if a profile will do
what is wanted before using it to upgrade a system. This is
especially useful with the new disk space reallocation feature.
To test an upgrade profile, you must run the pfinstall -D

command (against the system's disk configuration) on the system
that you are going to upgrade. You cannot test an upgrade profile
using a disk configuration file.
Testing a Profile
1. Test the profile on a system that has the platform type (x86 or
SPARC™) for that profile.
If you are testing an upgrade profile, you must use the system that
you are going to upgrade.

4
Features
Testing Upgrade Profiles (Continued)
2. The next step is dependent on your situation. If you:
a. Need to test an initial installation profile and have a system

running Solaris 2.6, then become superuser on the system and
go to step 9.
b. Need to test an upgrade profile or you need to test an initial

installation profile and you do not have a system running
Solaris 2.6, then go to step 3.
3. Boot the system from the system's local Solaris 2.6 CD-ROM or
from an Solaris 2.6 install server.
Note – If you are testing an upgrade profile, boot the system that you
are going to upgrade.
4. Answer the system identification questions, if prompted.
5. If you are presented with a choice of installation options, choose

the Solaris Interactive Installation program.
6. Exit from the first screen of the Solaris Interactive Installation

program.
After the Solaris Interactive Installation program exits, a shell

prompt is displayed.
7. Create a temporary mount point.

# mkdir /tmp/mnt

4
Features
8. Mount the directory that contains the profile(s) you want to test.
If you want to
a. Mount the JumpServer system (for systems on the network), to

the directory containing the install software, then type
# mount -F nfs jumpserver:/export/install /tmp/mnt
b. Mount a UFS-formatted diskette, then type:

# mount -F ufs /dev/diskette /tmp/mnt
c. Mount a PCFS-formatted diskette, the type:

# mount -F pcfs /dev/diskette /tmp/mnt
9. To test the profile with a specific system memory size, set

SYS_MEMSIZE to the specific memory size in Mbytes.
# SYS_MEMSIZE=memory_size
# export SYS_MEMSIZE
10. Change directory to where the profile resides, which is usually the
JumpStart directory.
# cd /tmp/mnt/Solaris_2.6/Misc/jumpstart_sample

4
Features
11. Test the profile with the pfinstall -d or pfinstall -D

command and state the mount path where the JumpServer
software resides followed by the profile name.
# pf -D -c /tmp/mnt any_machine
Warning – Without the -d or -D option, pfinstall will perform an

actual installation of the Solaris software on the system by using the
specified profile, and the data on the system will be overwritten.

4

Features
New System Boot Device Modifications

The Solaris 2.6 release now enables you to change a system's boot
device during the installation. A system's boot device is the disk
slice where the root file system is installed and consequently
where the installed system will boot from. On x86 systems, the
boot device is the active fdisk partition where the root file system
is installed.
You can also have the installation program update the system's
EEPROM (electronically erasable programmable read-only
memory) if you change the new boot device so the system can
automatically boot from it (SPARC systems only). In previous
releases, changing the system's boot device during an installation
meant that you had to manually change the system's EEPROM so
it could automatically boot from the new boot device.
This new feature is provided in the interactive Solaris installation

program and by the new custom JumpStart boot_device profile
keyword.

4
Features
System Boot Device Modifications (Continued)

4
Features
New Preconfiguration of System Configuration Information

In previous releases, the first part of the Solaris installation
program tried to obtain system configuration information about a
system (such as the system's peripheral devices, host name, IP
address, and name service) from the name service databases. The
installation program prompted you if it could not find the
information. If you did not want to be prompted, you had to
preconfigure the system configuration information in the name
service database.
Using the Solaris 2.6 sysidcfg file, you can now preconfigure
system configuration information through a set of keywords. You
can choose to provide one or more of the keywords to
preconfigure varying levels of system configuration information.

4
Features
Preconfiguring System Configuration Information (Continued)
The sysidcfg file can reside on a remote system or on a UFS or

PCFS diskette in the system's local diskette drive. If you choose to
put the sysidcfg file on a remote system, you have to use the -p
option of the add_install_client command to specify where
the system being installed can find the sysidcfg file.
When installing the English Solaris 2.6 CD-ROM, you will be

prompted to select an English locale because a new, 8-bit English
locale (en_US) has been added to Solaris 2.6. If you do not want to
be prompted for the locale, you must preconfigure the locale
information.
SA-350: Solaris 2.x Server Administration
New Disabling Stop A
Procedure to Disable the Stop A Key
1. Issue the following command:
vi /etc/default/kbd
#pragma ident "@(#)kbd.dfl 1.2 96/06/07 SMI"
#
# Copyright 1996, Sun Microsystems, Inc.
# All Rights Reserved.
#

4
Features
Disabling Stop A (Continued)

# /etc/default/kbd
#
# kbd default settings processed via kbd(1).
#
# KEYBOARD_ABORT affects the default behavior of the
keyboard abort
# sequence, see kbd(1) for details. The default
value is "enable".
# The optional value is "disable". Any other value
is ignored.
#
# KEYCLICK affects the default keyclick behavior.
Possible values are
# 'on' and 'off'. Any other value is ignored. The
default behavior is
# to leave the current keyclick setting unchanged.
#
# Uncomment the following lines to change the
default values.
#
KEYBOARD_ABORT=disable
#KEYCLICK=off

4
Features
Update Documentation
The AnswerBook2™ documentation system (Figure 4-4) uses a
Web-browser-based interface that enables you to view and print a
variety of Solaris information, including existing AnswerBook™
documents and man pages. AnswerBook2 provides a robust
search engine that enables you to easily find information
throughout the documentation library. You can install the
AnswerBook2 document collections locally or on a centralized
documentation server, and you can customize the AnswerBook2
documentation library.
What This Means to You: The popularity and convenience of Web

access to information now applies to Solaris documentation. The
convenience of a new browser interface enables and unifies access
to existing AnswerBook documents and man pages.
Solaris 2.6 Information Library, the “Accessing Online

Documentation” module

Features
Documentation (Continued)
Figure 4-4 AnswerBook2

Desktop 5
Seminar Map
This module discusses the features of the Common Desktop
Environment (CDE).
Topics Covered
Servers



5-1
5
Desktop
Context
The Solaris 2.6 release uses the Common Desktop Environment (CDE)
as the default desktop. It continues to support the OpenWindows™
desktop.

5
Desktop
Features
New Common Desktop Environment

The Solaris CDE is an advanced Motif-based desktop package
with an easy-to-use interface that provides a consistent look and
feel across UNIX platforms. Sun, Hewlett-Packard Company, IBM
Corporation, and Novell, Inc. each contributed technologies to
establish a new cross-platform standard for user and application
interfaces based on the X Window System and Motif.
While maintaining compliance with the CDE standards, Solaris

CDE offers additional benefits to its users and developers,
including performance improvements and significant defect fixes,
thus providing a higher quality product. Existing OpenWindows
utilities were integrated with CDE using a special folder in the
Application Manager. New features include a spell checker and an
image viewer which can display, rotate, scale, and convert graphic
images and PostScript™ files.
Desktop 5-3
5
Desktop
Features
Common Desktop Environment (Continued)
With Solaris CDE, you can run OpenWindows applications

without modification, and with drag-and-drop interaction from
OpenWindows applications to CDE applications. All
OpenWindows and OPEN LOOK applications run without any
need for modification, recompilation, or unwieldy compatibility
libraries. If you are used to the OpenWindows environment, you
have access to familiar backdrops, color palettes, and pop-up
workspace menus.
CDE User Environment
The CDE front panel is illustrated in Figure 5-1.
Calendar Trash Can

File Manager Workspace Help
Switch
Text Editor Stye Manager
Mailer Printer
Front Panel Lock Exit Application Manager

Figure 5-1 The CDE Front Panel

5
Desktop
Features
CDE User Environment (Continued)
The CDE user environment consists of the following features:
● A Login Manager for logging into the desktop, which is

available automatically when your workstation is booted.
Choose the Options menu and then the Remote Login menu
item if you want to run your desktop on any system on your
network.
● An integrated Motif environment that contains a Front Panel

from which you can launch desktop applications. You can
customize your desktop look by choosing such things as font
size, color, and backdrop.
● A workspace menu, which is a pop-up menu that contains

items for managing the desktop workspace.
● An online help information system that provides information

on the various desktop applications.
Desktop 5-5
5
Desktop
Features
CDE Development Environment
The CDE 1.2 Development Environment is included in optional

packages for users who develop software in CDE. These packages
contain:
● Utility applications, man pages, libraries, and header files to

help you develop CDE applications
● Widgets (a re-usable windows component used by

programmers to create GUIs) to ease porting OPEN LOOK and
Microsoft Windows applications to CDE, as well as terminal
emulator, text editor, and file selection box widgets
● Application Builder, a tool for creating graphical user interfaces

that use CDE application program interfaces (APIs)
● Desktop Korn Shell (dtksh), a scripting language
● Demonstration programs in source form for Motif, ToolTalk™

messaging, and other CDE services

5
Desktop
Features
Significant CDE Application Features
The following application features are also included in the CDE 1.2
Development Environment:
● Web- and Internet-aware features in File Manager and

Enterprise Mailer
● A spell checker integrated into Text Editor and Enterprise

Mailer
● Basic IMAP4 support in Enterprise Mailer
● Removable media support for CD-ROMs and diskettes
● Access Control List (ACL) support
● Multimedia image and audio support
● An auto-lock screen
● Federated Naming Space (FNS) support in Calendar (for NIS+

(Network Information Service) only)
Solaris Common Desktop Environment: Advanced User’s and

System Administrator’s Guide
Desktop 5-7
5
Desktop
Features
New Power Management for SPARC Desktop Systems

Power Management software enables users to be more frugal with
power consumption on desktop systems when they are not being
used. By default, UltraSPARC™ desktop systems power off when
not used for 30 minutes. The system can later be restored to
exactly the state it was in before it was powered off by Power
Management software. Users can modify or turn off Power
Management if needed.
Note – The goal of Power Management is to conserve electricity.

However, you should also take into account how an increase in power
cycling will affect the overall reliability of the hardware.
Power Management reduces the amount of power that your

system consumes. Reduction of power use is accomplished in two
levels:
● Reducing the power consumed by the display monitor
● Removing power to a system completely in a way that allows a

quick restoration of the system at the next power on

5
Desktop
Features
Power Management for SPARC Desktop Systems (Continued)
The Power Management software uses the feature of Suspend-

Resume, which allows for the power cycling of the system without
losing the state of some current activities. Certain functions that
require a fully operational system, such as mail and cron, will not
operate in a Suspended state.
Activating a Power Off
Two methods for activating a power off are:
● Manual operation by user:
a. Depress the Power Off key on a Sun 5 keyboard (top right

corner) or
b. Within a pop-up workspace menu, choose Suspend System.
● Automated operation based on idle system
Desktop 5-9
5
Desktop
Methods to Configure Auto-Power Off
You can use the Power Management program (Figure 5-2) either
from the command line with the command
/usr/openwin/bin/dtpower, or the pop-up workspace menu
option Programs ➤ Power Manager to do the following tasks for
your system:
● Check current Power Management settings
● Activate or deactivate AutoShutdown and AutoWakeup

features
● Set the idle time for the AutoShutdown feature
● Set the time of day when AutoShutdown can take place
● Set the time AutoWakeup will start up your system each day
(only for sun4u architecture)

5
Desktop
Features
Methods to Configure Auto-Power Off (Continued)
Figure 5-2 Power Management
Desktop 5-11
5
Desktop
Features
Command-Line Entry (Continued)
By configuring the /etc/power.conf file, the times of auto

shutdown can be defined as well as the parameters for what
indicates an idle system.
# more /etc/power.conf#
Note – The keyboard and mouse are considered idle when not used
for 1800 seconds.
Name Threshold(s) Logical Dependent(s)

/dev/kbd 1800
/dev/mouse 1800
Note – The frame buffer is considered idle when both the keyboard
and the mouse are idle.
/dev/fb 0 0 /dev/kbd /dev/mouse
Note – The above items apply only when windows is not running;
windows has its own screensaver program. When idle time is
exceeded, the frame buffer is powered off.

5
Desktop
Features
Command Line Entry (Continued)
If the system is idle for 30 minutes between 21:00 and 7:00, it will
automatically shut down.
Auto-Shutdown Idle(min) Start/Finish(hh:mm) Behavior
autoshutdown 30 21:00 7:00 shutdown
Note – The file that contains the information to bring the system back
to its pre-shutdown state is /export/home/.CPR.
statefile /export/home/.CPR
You can set the AutoShutdown feature to activate “always” by

entering identical Start and Finish time values in the
/etc/power.conf file. This means your system will power off at
any time of day after a 30-minute period of inactivity.
Refer to the power.conf man pages for instructions on how to set

idle threshold values on other devices and other behavior actions.
Desktop 5-13
5
Desktop
Features
Configuring the Automatic Shutdown Time
You should use the Power Management menu to change the

autoshutdown parameter.
Use the following steps to configure the system such that the screen
turns black after 10 minutes (600 seconds) of inactivity, if you are not
running windows:
1. As superuser, edit the following AutoShutdown entry in

/etc/power.conf file if it is not already available:
# vi /etc/power.conf
Name Threshold(s) Logical Dependent(s)

/dev/kbd 600
/dev/mouse 600
/dev/fb 00 /dev/kbd /dev/mouse
2. Inform the Power Management framework of the new settings by

entering:
# /usr/sbin/pmconfig
Using Power Management

5
Desktop
Features
New Solaris User Registration

Solaris User Registration is a registration mechanism invoked
when the user first brings up the Solaris 2.6 desktop environment.
By registering, customers can take advantage of the Sun

commitment to providing superior service and support.
Registered users will be regularly informed about new Solaris
releases, upgrade offers, and promotions that they can use to
enhance their systems.
Desktop 5-15
Standards 6
Seminar Map
The topic of this module is “year 2000 ready.”
Topics Covered
Servers



6-1
6
Standards
Context
Many customers rely on the Solaris operating environment as the
foundation for mission-critical applications. New standards in Solaris
(which are discussed in the next few pages) show how Sun
Microsystems continuous improvements support the standards and its
commitment to providing a stable operating environment.

6
Standards
Features
Update Year 2000 Ready
The Solaris 2.6 operating environment is “year 2000 ready”; that is,
it uses unambiguous dates and follows the X/Open guidelines
where appropriate.
For further information, including the definition of year 2000

compliance, see the Year 2000 Web page at
http://www.sun.com/y2000.
Standards 6-3
Robust Software Developer
Environment 7
Seminar Map
New features of the Solaris 2.6 operating environment that are of
interest to software developers are discussed in this module.
Topics Covered
Servers



7-1
7
Robust Software Developer Environment
Context
The Solaris operating environment provides developers with the
documentation, development software libraries, productivity tools,
sample code, and testing tools needed to develop software
applications for the Solaris runtime environments. This module
describes new features which help developers deal with large files
(over 2 Gbytes), multithreaded applications, and X servers and
libraries.

7
Features
Update Versioning and Scoped Libraries
Versioning and scoping are related enhancements to the link editor
in the Solaris operating environment. Developers of dynamic
objects can use these technologies to define sequential versions of
a dynamic object’s binary interface within the object and reduce
global symbols to local scope. These capabilities provide the
means to control interface evolution across software releases,
inherit global symbols from previous versions, record version
dependencies, and describe internal implementation changes.
Versioning and scoping make it possible to provide stable

interfaces for program development, achieve standards
compliance, and protect implementation changes (such as bug
fixes) from the object’s public interface. An added benefit can be
reduced object size and runtime relocation cost, which can
improve an application’s runtime performance.
Robust Software Developer Environment 7-3

7
Features
Versioning and Scoped Libraries (Continued)
In the Solaris 2.6 operating environment, the system libraries take

advantage of this technology and have been both scoped and
versioned.
Linkers and Libraries Guide

7
Features
New Scheduler Activation

Scheduler activations provide additional kernel scheduling
support for multithreaded applications. This is implemented as a
private interface between the kernel and the libthread library
(or libpthread), without changing the libthread
(libpthread) interface. Among other things, this enables the
thread library to implement adaptive mutex locks. With adaptive
mutex locks, a thread trying to acquire a lock spins if the thread
holding the lock is currently running on a processor, otherwise the
thread is blocked.
libsched(3X) man page
New Preemption Control

Preemption control enables applications to give scheduling hints
to the kernel to prevent preemption for short periods of time. This
can improve the performance of some classes of applications such
as database servers.

7
Features
Update /proc File System and Watchpoints
The previously flat /proc file system has been restructured into a
directory hierarchy that contains additional subdirectories for state
information and control functions. It also provides a watchpoint
facility to monitor access to and modifications of data in the
process address space. The new /proc file structure provides
complete binary compatibility with the old /proc interface.
The adb(1) command has been modified to use the new /proc
watchpoint facility. It now provides data breakpoints which cause
the subject processes to stop access to specified variables.
adb(1) man page

7
Features
Update Federated Naming Service (FNS)
FNS is now compliant with the X/Open XFN CAE definition. FNS
has also been enhanced to include support for Lightweight
Directory Access Protocol (LDAP). It also provides improved
support for files and NIS back ends.
Federated Naming Services Guide
Solaris Naming Administration Guide
Solaris Naming Setup and Configuration Guide

7
Features
Update Asynchronous I/O for Tapes
Asynchronous I/O for tapes provides an interface which improves
performance on high-performance tape devices. With the ability to
queue up requests, this feature significantly improves the I/O
throughput.
Update Solaris Developer Kit (SDK)

The SDK software is now built into the Solaris environment and is
no longer an unbundled product. All the information a developer
needs to produce applications and graphics handlers for end-user
Solaris runtime environments is now available in the Solaris
operating environment.

7
Features
Update Graphics
Solaris VISUALTM software includes several graphics and
multimedia software foundation libraries. Foundation libraries are
the lowest-level device-independent layer of the Solaris software.
This level of interface is designed to support a wide variety of
common functions. You can build higher-level libraries on top of
the foundation libraries, or the foundation libraries can be used
directly by a software application. These foundation libraries
create applications that incorporate two-dimensional and three-
dimensional graphics, imaging, and digital video. The libraries are
the XGL™ graphics library (which serves as a foundation library
for Solaris PEX™) and the XIL™ imaging library.

7
Features
XGL 3.3 Runtime Environment
The XGL library is a two-dimensional and three-dimensional

immediate-mode API that provides application portability across
hardware platforms and enables graphics applications to get
optimal performance from graphics accelerators. The XGL version
3.3 release enables applications to determine transparency support
level and includes a new attribute which enables user s to control
edge offset.
The XGL 3.3 runtime environment (RTE) is included with the

Solaris 2.6 release and should be installed if users at your site are
running graphics applications. It is not always obvious whether an
application requires the XGL RTE; therefore, you should install the
XGL RTE if you are installing CDE or OpenWindows software,
since an application may reference the XGL libraries.
XGL Programmer’s Guide
XGL Reference Manual

7
Features
XIL 1.3 Runtime Environment
The XIL library is an imaging API that provides a broad set of

functions for imaging and video applications. The library is part of
a strategy for low-level software interfaces (foundation libraries)
and enables imaging library and imaging application developers
to port their code to these foundation libraries.
The XIL 1.3 runtime environment (RTE) is included with the

Solaris 2.6 release and should be installed if users at your site are
running imaging applications. It is not always obvious whether an
application requires the XIL RTE; therefore, you should install the
XIL RTE if you are installing either OpenWindows or CDE
software, since an application may reference the XIL libraries.
Backward Compatibility
The XIL 1.3 library API is fully backwards compatible. This means
that existing applications can be run without modification or
recompilation.

7
Features
MT-Hot
The XIL 1.3 library is MT-hot. This means developers can write
multithreaded applications without putting locks around XIL
functions. Multiple threads from the API will execute correctly as
long as they do not require data from the same image. The library
itself also is MT-hot. It takes advantage of multiprocessor systems
without applications having to be rewritten.
Tiled Storage
The XIL 1.3 library stores very large images in buffers of memory
called tiles. If a region of an image within a tile boundary is
needed, only that tile is loaded into memory, thereby increasing
performance.
The library also includes a new storage object, which supports

conventional contiguous storage as well as tiled or stripped
storage for XIL images. The storage object serves as a container for
the image’s attributes, such as its scanline and pixel stride, and its
data pointer. Storage is not allocated for the image until you
export the image and modify it directly. This saves memory until it
is needed.

7
Features
New Data Type
The XIL 1.3 library now supports the 32-bit, single-precision, IEEE
(Institute of Electrical and Electronics Engineers) floating point
data type. Using this data type enables you to develop highly
sophisticated, scientific imaging applications.
Temporary Images
The XIL 1.3 library supports temporary images which are images
that are used as an intermediate step in the creation of a
subsequent image. They may only be written to and read from
once. Temporary images are particularly advantageous for large
images, because XIL can release the storage associated with them
when it is no longer needed.

7
Features
XIL_GENERAL Storage Format
The XIL 1.3 library supports the new XIL_GENERAL storage

format. This format provides the flexibility of specifying each band
of a multiband image as a separate memory buffer. Furthermore,
each band can have its own scanline and pixel stride.
XIL_BAND_SEQUENTIAL Storage Format
The XIL 1.3 library now supports the XIL_BAND_SEQUENTIAL

format for all data types, not just XIL_BIT images.

7
Features
KCMS Integration
The XIL 1.3 library includes Kodak Color Management System

(KCMS) support. The KCMS software product is a color-
management solution that ensures color consistency from input
devices to output devices. It is technology licensed from Eastman
Kodak that was developed in conjunction with SunSoft™.
Now you can achieve very close color matching between a display
image and the actual stored image.
KCMS Application Developer’s Guide
KCMS Multithreaded Programming
KCMS now supports multithreaded programs; it is multithread

safe (MT-safe). If your KCMS application uses multithread
capabilities, you do not need to put locks around KCMS library
calls.
PEX 3.0.2 Runtime Environment
The PEX API provides application portability across platforms and

three-dimensional graphics on local and remote displays.
Solaris PEX Implementation Specification
Solaris PEXlib Reference Manual
CGE PEX 5.1 Portability Guide

7
Features
OpenGL Framework
Solaris OpenGL™ 1.1 is a fully functional and conformant release

of the OpenGL 1.1 specification (as defined by the OpenGL®
Architecture Review Board). New support increases performance
and provides greater device support. Sun also supports the
following extensions:
● Three-dimensional texture mapping
● Texture color table
● SGI (Silicon Graphics, Inc.) color table

7
Features
Update X Server Configuration
The X server configuration provides a user program and a set of
interfaces that enable changing of device attributes in a platform-
independent way. This is the equivalent of the display properties
section of a “windows setup” for an X server. The framework
allows independent hardware vendors (IHV) to deliver
configuration modules and add their X server devices to the list of
Solaris-supported devices. The program allows changing of device
attributes, creation of new configurations, changing of Device
Type attributes, and configuration of the placement of screens (as
understood by the X server).

7
Features
X11R6 Base Window System
The X11R6 base windowing system includes the latest fixes and
patches from the X consortium.
X11 Double Buffer Extension
The Double Buffer Extension (DBE) provides a standard way to

utilize double-buffering within the framework of the X Window
system. Double-buffering uses two buffers, called front and back,
which hold images. The front buffer is visible to the user; the
back buffer is not. Using an Internet browser, you can access a
detailed specification from
ftp://ftp.x.org/pub/DOCS/DBE/.

Large Files Support 8
Seminar Map
The features that enable the support for files larger than 2 Gbytes is the
focus of this module.
Topics Covered
Servers



8-1
8
Large Files Support
Context
Solaris now supports files larger than 2 Gbytes. New interfaces are
provided, which operate on large files, for developers who want to do
asynchronous I/O to large files.

8
Large Files Support
Features
Update Large Files
The large files project supports files that are larger than or equal to
2 Gbytes. Large file semantics are supported on UFS, NFS, and
CacheFS file systems. Applications are able to create and access
files up to:
● One Tbyte on a UFS-mounted file systems.
● The limit of the NFS server for NFS and CacheFS mounted file
systems. Since NFS mounts a disk-based file system
somewhere else on the network, like a UFS file system, then
whatever the limit imposed on that UFS file system is honored
by the NFS mounting subsystem. For example, a UFS file
system can be mounted with the largefiles option (the
default). It also can be mounted with the nolargefile option.
NFS follows the option set.
Large Files Support 8-3

8
Large Files Support
Features
Large Files and Applications
Existing file I/O interfaces have been modified to detect an error

when they are used with a large file. New data types (most with
suffixes of 64 or 64_t) and new interfaces (most with suffixes of
64) are provided to operate on large files.
An existing application running on Solaris 2.x software should be

checked for the following points:
● To make the application large-file compatible (for example,

“large file safe in Solaris 2.6”), examine the application’s source
code to ensure that use of existing interfaces is appropriate and
that it has the correct error-handling characteristics for when a
large file is encountered.
● For your application to work with large files (for example,

“large file aware”), you must examine and modify your source
code. Areas to modify include:
•Output and in-memory formatting strings such as ld to %lld
•Any variable for temporary storage of sizes or offset
information
•Function parameters and return values

8
Large Files Support
Features
New mount Option
A new mount option is available to disable the large file support

on UFS file systems. This gives the system administrator a way to
ensure that older applications that are not able to safely handle
large files will continue to work.
The default mount option is largefiles. The largefiles option

means that a file system mounted with this option allows creation
of files larger than or equal to 2 Gbytes.
Note – A file system mounted with this option does not have to
contain files larger than 2 Gbytes.
Once a file system has been mounted with the largefiles

option, if a large file has been created in that file system, it cannot
be remounted with the nolargefiles option until the fsck
command is run and the absence of large files is confirmed.
System Administration Guide
Large Files Support 8-5

8
Large Files Support
Features
New 64-bit Asynchronous Input/Output (AIO)

Solaris provides a new set of interfaces for developers who want
to do asynchronous I/O to large files. The following interfaces
accept 64-bit AIO:
● aio_read64
● aio_write64
● lio_listio64
● aio_suspend64
● aio_error64
● aio_return64
The following interfaces exist, but are not supported:
● aio_fsync64
● aio_cancel64
These interfaces also work with KAIO. KAIO is the optimized

path for doing I/O to raw files. Using the interfaces with KAIO to
work with raw files results in a significant performance
improvement.
The Solaris operating environment supports another set of AIO

interfaces that predates POSIX (the IEEE Portable Operating
System Interface for Computer Environments). The following
interfaces also have been updated for large file support:
● aioread64
● aiowrite64

Network Security 9
Seminar Map
In this module, the new security features that have been added to the
Solaris environment are examined.
Topics Covered
Servers



9-1
9
Network Security
Context
The Solaris operating environment provides a sophisticated security
system that controls the way users access files, protect system
databases, and use system resources. Solaris security is network-wide
security, providing security over several different systems, not just
one. The Solaris security system is designed to accommodate different
security models, giving users the flexibility to choose the model that
best fits their needs now and in the future. Here are a number of new
features that add to the Solaris security system in the areas of access
control, encryption, and authentication.

9
Network Security
Features
New NFS Kerberos

Kerberos authentication uses DES (data encryption standard)
encryption to improve security over the network. The kernel
implementations of NFS and RPC (remote procedure call) network
services have been modified to add support for a new RPC
authentication standard that is based on the Generalized Security
Services API (GSS-API). This support contains the hooks to add
stronger security to the NFS environment.
The share and mount commands have been altered to provide

NFS support for Kerberos. Also, the share command now allows
for multiple authentication types from different clients.
Network Security 9-3

9
Network Security
Features
Setting Up a Secure NFS Environment Using Kerberos
1. Edit the /etc/dfs/dfstab file and add the -sec=krb4 option to

the appropriate entries.
# share -F nfs -o sec=krb4 /export/home
2. Edit the auto_master data to include -sec=krb4 as a mount

option.
/home auto_home -nosuid,sec=krb4
For Diffie-Hellman secure NFS, set sec=dh.
Note – With Solaris 2.5 and earlier releases, if a client did not mount as
a shared secure client, users could access it as user nobody, rather than
as themselves. With Version 2 on the Solaris 2.6 release, the NFS server
will refuse access if the security modes do not match, unless -
sec=none is included on the share command line. With version 3, the
mode will be inherited from the NFS server, so there is no need for the
clients to specify -sec=krb4 or -sec=dh. The users will have access to
the files as themselves.

9
Network Security
Features
Update RPCSEC_GSS
The user-level RPC implementation has been modified to add
support for a new authentication type. It is based on the GSS-API
and provides stronger authentication, privacy, and integrity for
RPC-based services.

9
Network Security
Features
New Pluggable Authentication Modules (PAM) Framework

The PAM framework enables you to “plug in” new authentication
technologies without changing the login, ftp, or telnet
commands. You can also use PAM to integrate UNIX logins with
other security mechanisms like DCE or Kerberos.
Mechanisms for account, session, and password management can

also be plugged in using this framework.
Some of the benefits PAM provides are:
● Flexible configuration policy

•Per application authentication policy
•The ability to choose a default authentication mechanism
•Multiple passwords on high-security systems
● Ease-of-use for the end-user

•No retyping of passwords if they are the same for different
mechanisms
•Single password for multiple authentication methods
The ability to use a single password for multiple

authentication methods is provided with the password
mapping feature, even if the passwords associated with each
authentication method are different.

9
Network Security
Features
Pluggable Authentication Modules (PAM) Framework (Continued)
•Single prompt for multiple authentication methods
The ability to prompt the user for passwords for multiple

authentication methods without having the user enter
multiple commands is provided.
● The ability to pass optional parameters to the user

authentication services
PAM Module Types
It is important to understand the PAM module types because the

module type defines the interface to the module. The four types of
runtime PAM modules are:
● The authentication modules provide authentication for the

users and allow for credentials to be set, refreshed, or
destroyed. They provide a valuable administration tool for user
identification.
● The account modules check for password aging, account

expiration, and access-hour restrictions. After the user is
identified through the authentication modules, the account
modules determine if the user should be given access.
● The session modules manage the opening and closing of an

authentication session. They can log activity or provide for
clean-up after the session is over.
● The password modules allow for changes to the actual

password.
Figure 9-1 illustrates how PAM works.

9
Network Security
Features
PAM Module Types (Continued)
ftp telnet login
Applications
PAM library
pam.conf file
PAM modules
pam_unix.so.1 pam_dial_auth.so.1 pam_dcs.so.1
Figure 9-1 How PAM Works

9
Network Security
Features
The pam.conf File
The syntax of for the pam.conf file is

service_name module_type control_flag module_path module_options
where
● service_name – Name of the service (for example, ftp,

login, or telnet).
● module_type – Module type for the service.
● control_flag – The continuation or failure semantics

(required, requisite, optional, or sufficient) for the
module.
● module_path – Path to the library object that implements the

service functionality.
● module_options – Specific options that are passed to the

service modules. Options are dependent on PAM; debug is the
typical option.
Example of an /etc/pam.conf Entry
login auth required /usr/lib/security/pam_unix.so.1
PAM Modules New to Solaris 2.6
Shown below are the newly added PAM modules.
● pam_sample.so.1
● pam_dial_auth.so.1
● pam_rhosts_auth.so.1

9
Network Security
Features
Limiting the Impact of .rhosts With PAM
The sample pam.conf file below enables a superuser to copy files to a

remote system. The remote login operation will require a password,
however.
Disable the use of the .rhosts file in the /etc/pam.conf by

commenting out the pam_rhosts_auth.so.1 object.
# vi /etc/pam.conf
# Authentication management
#
login auth required pam_unix.so.1
login auth required pam_dial_auth.so.1
#rlogin auth sufficient pam_rhosts.so.1
rlogin auth required pam_unix.so.1
rsh auth sufficient pam_rhosts.so.1
...

9
Network Security
Features
Adding a PAM Module
1. Become superuser.
2. Determine which control flags and other options should be used.
3. Copy the new module to /usr/lib/security.
4. Set the permissions so that the module file is owned by root and
permissions are 555.
5. Edit the PAM configuration file, /etc/pam.conf, and add this

module to the appropriate services.
Verification
It is very important to do some testing before the system is

rebooted, in case the configuration file is misconfigured. Run
rlogin, su, and telnet before rebooting the system. If a service
daemon is spawned only once when the system is booted, it may
be necessary to reboot the system before you can verify that the
module has been added.

9
Network Security
Features
New BIND 4.9.4-P1

Solaris now supports and includes Domain Name System (DNS)
Berkeley Internet Name Daemon (BIND) version 4.9.4 patch level
one. BIND is the most popular implementation of DNS. BIND is
critical for Internet connectivity because it provides an Internet
naming service that stores host (IP) addresses, mail information,
and similar data for lookup purposes. BIND always includes a
number of programs and the resolver library. The main program is
named, the daemon that provides DNS information. Applications
such as telnet communicate with named using the resolver
library.
BIND 4.9.4-P1 provides new security over the Internet. The older
version of BIND did little to prevent DNS spoofing. Intruders
could cause BIND to provide incorrect name data. Services that
use this (some of which do not verify data) could be tricked into
allowing remote access to unauthorized users. The 4.9.4 version
fixes many security holes.

Network Management and System
Administration 10
Seminar Map
The new network management and system administration features are
discussed in this module.
Topics Covered
Servers



10-1
10
Network Management and System Administration
Context
The Solaris operating environment provides a stable and reliable
networking environment. New network management and system
administration features in this release expand tools for managing
this environment.

10
Features
New Network Time Protocol (NTP)

The Solaris 2.6 release supports NTP, which provides both precise
time and network clock synchronization for use in distributed
computing environments. In the past, Solaris customers could use
a publicly available version of NTP. The new support provides
increased time precision.
Network Management and System Administration 10-3

10
Procedure for Network Clock Synchronization
1. A. On the NTP Server, issue the commands:

cd /etc/inet
cp ntp.server ntp.conf
vi ntp.conf
# @(#)ntp.server 1.4 97/05/05 SMI

#
# /etc/inet/ntp.server
#
# An example file that could be copied over to /etc/inet/ntp.conf and
# edited; it provides a configuration template for a server that
# listens to an external hardware clock, synchronizes the local clock,
# and announces itself on the NTP multicast net.
#
# This is the external clock device. The following devices are

# recognized by xntpd 3.4y:
#
# XType Device Name Description
# -------------------------------------------------------
# 1 (none) LOCAL Undisciplined Local Clock
# 2 trak GPS_TRAK TRAK 8820 GPS Receiver
# 3 pst WWV_PST PSTI/Traconex WWV/WWVH Receiver
# 4 wwvb WWVB_SPEC Spectracom WWVB Receiver
# 5 goes GPS_GOES_TRUE TrueTime GPS/GOES Receivers
# 6 irig IRIG_AUDIO IRIG Audio Decoder
# 7 chu CHU Scratchbuilt CHU Receiver
# 8 refclock- GENERIC Generic Reference Clock Driver
# 9 gps GPS_MX4200 Magnavox MX4200 GPS Receiver
# 10 gps GPS_AS2201 Austron 2201A GPS Receiver
# 11 omega OMEGA_TRUE TrueTime OM-DC OMEGA Receiver
# 12 tpro IRIG_TPRO KSI/Odetics TPRO/S IRIG Interface
# 13 leitch ATOM_LEITCH Leitch CSD 5300 Master Clock Controller
# 14 ees MSF_EES EES M201 MSF Receiver
# 15 gpstm GPS_TRUE TrueTime GPS/TM-TMD Receiver
# 17 datum GPS_DATUM Datum Precision Time System
# 18 acts NIST_ACTS NIST Automated Computer Time Service

10
Procedure for Network Clock Synchronization
# 19 heath WWV_HEATH Heath WWV/WWVH Receiver

# 20 nmea GPS_NMEA Generic NMEA GPS Receiver
# 22 pps ATOM_PPS PPS Clock Discipline
# 23 ptbacts PTB_ACTS PTB Automated Computer Time Service
#
# Some of the devices benefit from "fudge" factors. See the xntpd
# documentation.
# Either a peer or server. Replace "XType" with a value from the

# table above.
#server 127.127.XType.0 prefer
fudge 127.127.XType.0 stratum 0
#Set ntp server to be an Undisciplined Local Clock.
server 127.127.0.0 prefer

fudge 127.127.0.0 stratum 0
broadcast 224.0.1.1 ttl 4

enable auth monitor
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
(Start up ntp server process)
server# /etc/init.d/xntpd start
2. On the client, issue the command

client# ntpdate server
11 Sep 15:31:15 ntpdate[322]: adjust time server 128.50.30.1 offset
0.286216 sec

10
Features
New Solstice Enterprise Agents (SEA)

The SunSoft Solstice Enterprise Agents (SEA) technology is based
on the new extensible agent technology or master/subagent
technology. The agents consist of a master agent and subagents.
The Master Agent receives and responds to Simple Network
Management Protocol (SNMP) or Desktop Management Interface
(DMI) requests. The responses are sent after retrieving the
appropriate values from the respective subagents. The subagents
manage information bases (MIB [management information base]
or MIFs [management information file]) designed for specific
components and applications. Enterprise agents also enable users
to integrate and use SNMP-based legacy agents.
SEA is used by component developers and system and network

managers who want to develop custom SNMP or DMI subagents
which enable device management from an SNMP management
console.
SA-340: Managing Your Network Using SunNet Manager

10
Features
New Dynamic Host Configuration Protocol (DHCP)

DHCP (Figure 10-1) enables a host to get an Internet protocol (IP)
address and other system configuration parameters preconfigured
by the administrator on the DHCP server.
Remote network (129.144.8.0) DHCP service

architectural diagram
DHCP Client BOOTP Client
Legend:
BOOTP relay agent Unicast
(could be a router or a SunOS Broadcast
machine running in.dchpd)
in.dhcpd DHCP client
DHCP client
dhcptab
DHCP network tables BOOTP client
129_148_5_0 129_144_8_0
DHCP service datastore interface

in.dhcpd dhcpconfig
NIS+ lib.dhcp.so.datastore
switch is dhtadm
/etc/default/dhcp
UFS Files pntadm
Figure 10-1 Dynamic Host Configuration Protocol Overview

10
Features
DHCP (Continued)
DHCP also enables the host to give up an IP address when it is no

longer required, or when the designated period for its use ends.
This protocol improves on the IP address allocation where the
system administrator must assign or change each IP address
individually. Both the DHCP server and client side support are
provided.
Procedure for Setting Up DHCP
1. On the DHCP server, create the dhcp configuration.
server# dhcpconfig
Would you like to:
1) Configure DHCP Service
2) Configure BOOTP Relay Agent

10
Features
Procedure for Setting up DHCP (Continued)
3) Unconfigure DHCP or Relay Service
4) Exit
Choice: 1
Would you like to stop the DHCP service? (recommended) ([Y]/N):y
### DHCP Service Configuration ###

### Configure DHCP Database Type and Location ###
Enter datastore (files or nisplus) [files]:
Enter absolute path to datastore directory [/var/dhcp]:
### DHCP server daemon option setup ###
Would you like to specify nondefault daemon options (Y/[N]):
### Initialize dhcptab table ###
Enter default DHCP lease policy (in days) [3]:

Do you want to allow clients to renegotiate their leases? ([Y]/N):
### Select Networks For BOOTP/DHCP Support ###
Enable DHCP/BOOTP support of networks you select? ([Y]/N):
### Configure Local Networks ###
Configure BOOTP/DHCP on local LAN network: 128.50.0.0? ([Y]/N):

Do you want hostnames generated and inserted in the files hosts table?
(Y/[N]):y
What rootname do you want to use for generated names? [bigpopa-]: host-10
s Rootname host- correct? ([Y]/N):
What base number do you want to start with? [1]: 1
Enter starting IP address [128.50.0.0]: 128.50.30.1

10
Features
Enter the number of clients you want to add (x < 65535): 12

Disable (ping) verification of 128.50.0.0 address(es)? (Y/[N]):
- 66% Complete.Warning: 128.50.30.10 entry in 128.50.0.0 already exists.
Warning: 128.50.30.11 entry in 128.50.0.0 already exists.
Warning: 128.50.30.12 entry in 128.50.0.0 already exists.
Configured 9 entries for network: 128.50.0.0.

### Configure Remote Networks ###
Would you like to configure BOOTP/DHCP service on remote networks?

([Y]/N):n
Would you like to restart the DHCP service? (recommended) ([Y]/N):
Would you like to:
1) Configure DHCP Service
2) Configure BOOTP Relay Agent
3) Unconfigure DHCP or Relay Service
4) Exit
Choice: 4
2. On each client which will use DHCP, create a dhcp file for each
ethernet interface which requires a dhcp-generated IP address.
client# touch /etc/dhcp/dhcp.le0
(Upon reboot, the rc startup script will invoke the ifconfig

dhcp-auto command against each dhcp interface filename.)
client# init 6
(Confirm IP address and new hostname were applied)
host-1# ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000

10
Features
le0: flags=4863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,DHCP> mtu 1500

inet 128.50.30.1 netmask ffff0000 broadcast 128.50.255.255
ether 8:0:20:83:9e:f1
host-1# uname -n
host-1
TCP/IP Network Administration Guide
New NFS Client Failover

Client failover provides for a high level of availability of read-only
file systems by allowing the client to mount files from another
server as needed. The failover is transparent to the client, so work
is not disturbed if one server has problems, as long as there is a
replica available.

10
Features
Update Variable Length Subnet Mask (VLSM)
Previously, the Solaris operating environment supported the use of
a single netmask for each network number in use on a network.
The netmask determines which bits of an IP network number
represent the subnet, and which represent the host number. Using
variable length subnet masks (VLSM) enables more efficient use of
IP addresses in large networks. With VLSM, the TCP/IP
administrator can now use multiple netmasks for a given network
number, tailoring each mask according to the size of each
individual subnetwork. When determining how to route an IP
packet, Solaris automatically uses the longest matching netmask.
For example, in prior releases an administrator could subdivide

the network 192.168.1.0 into eight subnets by using a netmask of
255.255.255.224. By using VLSM, this network number can instead
be broken into the following:
● Two subnets with a netmask of 255.255.255.192 and
● Four subnets with a netmask of 255.255.255.224.
In addition, the use of VLSM allows supernetting or aggregation

of network numbers, which can result in substantial savings in the
sizes of routing tables carried by network routers. These two
techniques make it possible to implement Classless Inter-Domain
Routing (CIDR) as described in RFC 1519.
To fully utilize VLSM in a network, CIDR-aware protocols such as

OSPF, BGP-4, or RIPv2 must be used.
TCP/IP and Data Communications Administration Guide

10
Update Routing Sockets
The Solaris operating environment now conforms to the defacto
routing socket interface as implemented by 4.4 BSD. This interface
enables netmask information to be shared between routing
protocol implementations and the kernel. It can also be used by
implementations of CIDR-aware routing protocols.
Although the Solaris software does not deliver a routing daemon

that implements these protocols, TCP/IP administrators are
advised to contact the Merit GateD Consortium (see
http://www.gated.org/) for information on Gated. Gated is a
program that implements these and other routing protocols and
uses the routing socket interface.

10
Features
Update Processor Sets
Processor sets allow a group of processors to be allocated for the
exclusive use of one or more applications. The /usr/sbin/psrset
command gives a system administrator control over the creation,
management, and binding of processes into processor sets.
psrset(1M) man page

10
Features
New Autofs
Autofs is a file system that automatically mounts file systems as
needed and unmounts them when they are not being used. The
new automount daemon is now fully multithreaded. This enables
concurrent servicing of multiple mount requests. The new
functionality makes the service more reliable.
The autofs service also supports the browsing of indirect aufofs

maps. All mountable entries under an autofs mount point can be
visible without the overhead of mounting them first. By default,
the /home and /net autofs mount points will have browsing
disabled, but all other indirect mount points can be browsed. The
ability to browse can be administered at the host level with the
automount command and at a name-space level through the
autofs maps.

10
Features
Autofs (Continued)
In addition, better on-demand mounting of hierarchically related

file systems is included. Previous releases automounted an entire
set of file systems if they were hierarchically related, even if only
one file system was referenced. Now, the file system that is
referenced is dynamically mounted without the other file systems
in the hierarchy.
Starting the Automounter
1. To enable the daemon without rebooting, become superuser and

type the following command:
# /etc/init.d/autofs start
This starts the daemon.
Stopping the Automounter
1. To disable the daemon without rebooting, become superuser and

type the following command:
# /etc/init.d/autofs stop

10
Features
New NIS+ Backup and Fast Restore

NIS+ backup and restore commands provide a quick and
efficient method of backing up and restoring NIS+ name spaces.
nisbackup Syntax
The nisbackup command uses the following syntax:

nisbackup [-v][-a] backupdir objects
Where:
● backupdir – The target directory where the backup files are

to be stored; for example, /var/master1_backup.
● objects – The NIS+ directory objects that you want to back

up; for example, org_dir.doc.com. Multiple NIS+ directory
objects can be listed if they are separated by spaces.
The nisbackup command takes the following options:
● -v – Verbose mode. This mode provides additional information
● -a – All. Backs up all NIS+ directory objects that the server is

master of. This includes any subdomain directory objects that
this server is the master for. Note that directory objects of
subdomains that have their own master servers will not be
backed up.

10
Features
nisbackup Syntax (Continued)
The nisbackup command must be run on the master server for

the NIS+ directory objects you are backing up.
When specifying NIS+ directory objects to be backed up, you can

use full or partially qualified directory names.
When you back up multi-level directories, the backup files for

lower level directories are automatically placed in subdirectories
of the target backup directory.
Update NIS+ Over a Wide Area Network (WAN)

NIS+ administrators can now specify NIS+ server search order for
clients that need naming services. Server use can be balanced
among various clients by designating different servers for different
clients as “preferred” (primary). The order in which the client
seeks out other servers when it cannot obtain information from its
preferred server can be specified. This feature is particularly useful
when a NIS+ domain spans a wide area network (WAN) link.

10
Features
NIS+ Over a Wide Area Network (WAN) (Continued)

Administrators can reduce network traffic over the WAN link by
specifying that clients first try to obtain the naming service from
servers on the client’s side of the link. NIS+ administrators can
also specify what a client does when no preferred server is
available.

Features
Update NIS Server
The Solaris operating environment now natively supports the NIS
server. In previous Solaris releases, the NIS server was supported
under emulation mode by the NIS+ server or by an unbundled
product named NSkit. Bundling the NIS server is intended to aid
the transition from the SunOS 4.x to the Solaris 2.6 release.

10
Features
Update CFS Boot
CFS boot enables AutoClient systems to boot more quickly with
less network traffic by booting from a local CacheFS disk cache.
The first system boot populates the cache, and the system boots
that follow are satisfied from the cache.

10
Features
Update Patch Tools
In previous releases, patch installation and removal tools and their
corresponding documentation were delivered as part of each patch
shipped. These tools are now part of the Solaris software, which
provides the following benefits:
● There is less wasted space on user systems. (Tools are installed

once instead of with each patch.)
● Multiple patch handling is easier.

10
Features
New Patch Commands
The patchadd and patchrm commands are used to add and

remove patches from a Solaris 2.x system. They cannot be used to
manage patches on a Solaris 1.x system.
You can add one or more patches to a system, client, service, or a

net install image.
The following is an example of how a patch is added by a

superuser to the local system:
# patchadd /var/spool/patch/104946-02

superuser to a client by specifying the client’s root directory on a
server:
# patchadd -R /export/root/client1 \
/var/spool/patch/104946-02

superuser to a service area by specifying the service area on the
server:
# patchadd -S Solaris_2.3 \
/var/spool/patch/104946-02
Note – A service area is a usr file system from any Solaris release set
up on a server. It is usually mounted as read-only by the clients the
server serves.

Features
New Patch Commands
If a patch contains both root and usr packages in the patch, the
patchadd command must be issued twice: once with the -R
option to apply the patch’s root package, and once with the -S
option to apply the patch’s usr package.
SA-235: System Administration I
patchadd(1M) man pages
patchrm(1M) man pages

10
Features
Isalist Utilities
Isalist is a set of utilities for SPARC systems that enables users

to find out which instruction sets are supported on their machines
and determine which one will perform the best for them. The set
of utilities include:
● The isalist command, which prints out an ordered list of

supported instruction sets. The list is sorted by which set
performs the best on the current system. That is, a program
that is compiled for an earlier-named instruction set will most
likely run faster on the system than the same program
compiled for a later-named instruction set.
● The optisa command, which prints out the best instruction

set.
● The SI_ISALIST command in the sysinfo command, which

returns an ordered list of the supported instruction sets. The
list is in descending order according to performance.
Currently there are many variations of the SPARC processor, some

of which can be treated as separate instruction sets. An application
binary that is compiled for one variation may not run, may run
with performance degradation, or may run normally on a machine
implementing a different variation. The Isalist utilities provide
a standard interface so users can choose their application binary
correctly to obtain maximum performance. For example, a system
administrator can write a wrapper script and use the output of
isalist and optisa to choose the appropriate binary for a given
application.

Printing 11
Seminar Map
New and updated printing features of the Solaris 2.6 environment are
presented in this module.
Topics Covered
Servers



11-1
11
Printing
Context
The Solaris 2.6 print software offers a better solution than the LP
print software in previous Solaris releases. System administrators
can easily set up and manage print clients using the NIS or NIS+
name services. This means you can centralize print administration
for a network of systems and printers.
Solaris 2.6 print software features include:
● Redesign of print packages
● Print protocol adapter
● SunSoft Print Client
● Network printer support

11
Printing
Features
Update Redesign of Print Packages
The Solaris 2.6 print packages have been redesigned to provide
greater flexibility and modularity of print software installation and
to allow installation of a smaller client footprint.
Redesign features include:
● It is possible, with a custom installation, to install only the

client software on the print client, allowing for a smaller client
footprint.
All packages, client and server, are installed by default on all

machines. You can choose to install client software only on
print client machines by customizing your installation.
● PostScript filter software is contained in the print package

SUNWpsf.
Printing 11-3
11
Printing
Features
Redesign of Print Packages (Continued)
The new set of print packages is:
Package Title Directory
SUNWpcr SunSoft Print - Client / (root)
SUNWpcu SunSoft Print - Client /usr

SUNWpsr SunSoft Print - LP Server / (root)
SUNWpsu SunSoft Print - LP Server /usr

SUNWpsf PostScript Filters /usr
SUNWscplp SunSoft Print - Source /usr
Compatibility

11
The removed print packages are:
Package Title Directory
SUNWlpr LP Print Service / (root)
SUNWlpu LP Print Service - Client /usr

SUNWlps LP Print Service - Server /usr
Print commands contained in SUNWscpu have been moved into

SUNWsclplp (SunSoft Print - Source Compatibility).
Printing 11-5
11
Printing
Features
Update Print Protocol Adaptor
The Solaris 2.6 print protocol adaptor replaces the Service Access
Facility (SAF), the network listener, and lpNet on the inbound side
of the LP spooler with a more modular, modern design.
This replacement provides the following features:
● Has complete BSD print protocol implementation plus

extended Solaris functionality
● Allows multiple spooling systems to coexist on the same host

and have access to the BSD print protocol
● Can be extended by third-party application developers (such as

Apple, Novell, and so on) to support other printing protocols
The new print protocol adaptor is compatible with print clients set
up in previous Solaris 2.x releases if the BSD protocol was used to
configure these clients. If not, you have to modify the previous
Solaris 2.x print client configuration to the BSD protocol using the
Solstice AdminTools™ utility, AdminSuite Printer Manager, or the
lpsystem command.

11
Printing
Features
Update SunSoft Print Client
The SunSoft Print Client software was previously released as an
unbundled product. It was available on the Solaris Migration
CD-ROM and as part of the Solstice AdminSuite™ 2.x suite of
administration products. It is now bundled with the Solaris 2.6
release.
The SunSoft Print Client software is
● Substantially smaller (183 Kbytes total) than the previous

Solaris release.
● Interoperable with BSD protocol as described in RFC 1179. This

includes SunOS 4.x, Solaris 2.x, HP-UX, and other operating
environments.
The SunSoft Print Client software uses a NIS map, NIS+ table, or a
single file to provide centralized client administration in the
Solaris 2.6 release.
Printing 11-7
11
Printing
Features
SunSoft Print Client (Continued)
● On client systems, the /etc/lp directory structure is replaced

with a configuration database that can be stored in a:
•Printer not in the client database (server:printer)
•User file ($HOME/.printers)
•System file (/etc/printers.conf)
•NIS map (printers.conf.byname)
•NIS+ FNS context
● The client software uses a more streamlined implementation,

thus providing reduced client overhead and generally quicker
and more accurate responses to print status requests.
● The printers.conf file is administered like a standard NIS

map or NIS+ table.
The lpset(1M) command is used to create the printers.conf

file.
The print client software packages are SUNWpcr and SUNWpcu.

11
Printing
Features
Update Enhanced Network Printer Support
The Solaris 2.6 print software provides better support for network
printers than in previous Solaris releases.
Features are:
● A new interface script, /usr/lib/lp/model/netstandard, is

specifically designed to support network printers. This script
collects the spooler and print database information needed to
perform network printing and passes it to the print output
module.
● A new print output module, netpr, is called from the

netstandard interface script to print the print job by opening a
network connection to the printer, creating the correct protocol
instructions, and sending the data to the printer.
The netpr binary currently supports two protocols: BSD print

protocol and TCP pass-through.
Printing 11-9
11
Printing
Features
Adding a Network Printer Using LP Commands
This section describes the steps necessary to set up a network printer

using the SunSoft Network Printer support software. The use of this
software is intended for those printers that do not come with vendor-
supplied software.
1. Connect the printer to the network and turn on the power to the
printer.
Consult the printer vendor's installation documentation for

information about the hardware switches and cabling
requirements. Get an IP address and select a name for the printer
node. This is equivalent to adding a node to the network.
2. Collect the information required to configure a network printer:
● Printer name
● Printer server
● Network printer access name
● Protocol
● Timeout
3. Define the printer name, the device, the printer type, and the
content type by using the lpadmin command.
a. As superuser, define the printer name and the port device the
printer will use.
# lpadmin -p printer-name -v /dev/null
The device to use is /dev/null.

11
Printing
Features
Adding a Network Printer Using LP Commands (Continued)
b. Identify the interface script the printer will use.

# lpadmin -p printer-name -i \ /usr/lib/lp/model/netstandard
The interface script that is supplied with the SunSoft network

printer support software is
/usr/lib/lp/model/netstandard.
c. Set the printer destination, protocol, and timeout values.

# lpadmin -p printer-name -o dest=access-name:port -o \ protocol=protocol -o
timeout=value
Where
-p printer-name Specifies the network printer

name.
-o dest=access-name:port Sets the printer destination to the

network printer access name and
a designated printer vendor port,
if it is defined in the printer
vendor documentation.
Printing 11-11
11
Printing
Features
-o protocol:protocol Sets the over-the-wire protocol

used to communicate with the
printer. Both BSD and raw TCP
are supported.
-o timeout:value Sets a retry timeout value that

represents the number of seconds
to wait between attempting
connections to the printer.
d. Specify the file content types of the printer and the printer
type.
# lpadmin -p printer-name -I content-type -T printer-type
4. Add filters to the print server by using the lpfilter command.

# cd /etc/lp/fd
# for filter in *.fd;do
> name=`basename $filter .fd`
> lpfilter -f $name -F $filter
> done
5. Enable the printer to accept printer requests and to print the

requests.
# accept printer-name
# enable printer-name
6. Verify the printer is correctly configured by using the lpstat

command.
# lpstat -p printer-name

11
Printing
Features
7. Add client access to the new printer.
Now that the printer has been added, you can create access to the
printer for the clients.
Solaris System Administration Guide
Solstice AdminSuite 2.3 Administration Guide
Printing 11-13
Other Minor Differences A
This appendix contains a list of the other minor differences between
previous releases of Solaris and Solaris 2.6.
A-1
A
Nomadic Support: File Synchronization

Update Configuration Assistant and Booting Software for x86
Platforms
The Configuration Assistant interface is part of the new booting
system for the Solaris (x86 platform edition) software. It
determines which hardware devices are in the machine, accounts
for the resources each device uses, and enables you to choose
which device to boot from. The booting software, including the
Configuration Assistant, is installed on the system's hard disk
along with the Solaris operating environment. A file that contains
the hardware configuration information for the system being
installed is also installed on the hard disk. Each time the system is
booted, the configuration information is passed to the Solaris
kernel. The Configuration Assistant must be rerun any time the
hardware configuration is changed.
Update x86 Configuring Peripherals

The kdmconfig program is used to configure the mouse, graphics
adapter, and monitor on an x86 system. If an OWconfig file already
exists, kdmconfig will extract any usable information from it. In
addition, this updated version of kdmconfig will also retrieve
information left in the devinfo tree by the devconf program, and
use that information to automatically identify devices. Any
attribute values, such as manufacturer or model information,
returned by probes for a given device (unless it is "Unknown")
take precedence over the value received for the same attribute
from the OWconfig file.
A-2 Transitioning to Solaris 2.6

A
x86 Configuring Peripherals (Continued)
If all attribute values in the Confirm Configuration screen are

obtained (none are "Unknown"), the default choice is Save and
Exit Configuration. If information is needed, the program selects
the first Unknown device as the default configuration selection.
You can override the default selection by either selecting another
device you want to configure or by selecting Save and Exit
Configuration. When you exit, kdmconfig checks for Unknown
devices and warns you about potential problems with the X
Window system if values are missing. After reading the warnings,
you can either continue with the configuration or exit the program
and configure the devices later.
The changes regarding the sequence of screens for configuring

individual devices are:
● You can now choose one of the ports (COM1 to COM4,

/dev/tty00 to /dev/tty03, respectively) when configuring a
serial mouse.
● When configuring a graphics card/monitor, users are now

always presented with a choice of monitors following the
selection of the graphics card. The choices on screens that
follow (such as resolution, and the like) depend on both card
and monitor selections.
The program is similar to the previous version with regard to

the character user interface and the function keys used to
navigate within the program.
Other Minor Differences A-3

A

Update Optional 8-bit Locales
The installation window in the base Solaris 2.6 CD-ROM offers
several English language locales. To use 8-bit characters, install
one of the en_XX options. The locale used in the installation
becomes the default system locale. Selection of an 8-bit locale
provides users the ability to input and display all of the European
languages in their English version of Solaris. Table A-1 lists the
new locales that are now available.
Note – The C locale was installed by default in the base English

releases prior to the Solaris 2.6 release.
Table A-1 New Locales Offered in Installation
Locale Name Language/Territory Code Set
C American English 7-bit

en_AU Australian English 8-bit
en_CA Canadian English 8-bit
en_UK UK English 8-bit
en_US American English 8-bit

A
Desktop
Update New User Locales in the Solaris 2.6 CD-ROM

All localized versions of Solaris, including English, includes the
new local support listed in Table A-2.
Table A-2 New User Locales Included in Solaris 2.6
Country Locale Name ISO Code Set

Austria de_AT (German Partial Locale) 8859-1
Estonia et 8859-1
Czech cz 8859-2
Hungary hu 8859-2
Poland pl 8859-2
Latvia lv 8859-4
Lithuania lt 8859-4
Russia ru 8859-5
Greece el 8859-7
Turkey tr 8859-9
These locales are supported through the SUNWploc1, SUNWplow1,

and SUNWpldte packages, which are part of the entire cluster.
Two locales, Greek and Russian, are based on non-Latin scripts

and require an optional SMCC keyboard for text input.
Update Unicode 2.0 Support

Two locales, which are Unicode 2.0 and ISO 10646 compliant, have
been added. These locales enable multiscript input and output and
are the first locales provided in the Solaris environment with this
capability. These locales support the CDE environment only,
including the Motif and CDE libraries.

A
Desktop
Update Font Administration

Font Administration enables easy installation and usage of fonts
for the X Window system. It supports TrueType, Type0, Type1, and
CID fonts for multibyte languages, and provides comparative font
preview capability. It is fully integrated into the CDE desktop.
TrueType fonts are supported through X and DPS software. Font

Administration allows for easy installation and integration of
third-party fonts into the Solaris environment.
Update Asian Language Enhancements

Solaris 2.6 software has been restructured to the historical
dependency on the Extended UNIX Codeset (EUC). Additional
codeset support and locales for popular Asian PC encoding
standards, ShiftJIS (PCK) in Japan, Big5 in PRC, and Johap in
Korea are also provided. These locales support the CDE
environment only, including the Motif and CDE libraries.

A
Standards
Update The X/Open UNIX 95 (Spec 1170)

The previous release of Solaris was compliant with much of
Spec 1170. Solaris 2.6 software now meets all of the requirements.
Areas changed in Solaris 2.6 to meet the Spec 1170 requirements
are:
● System interfaces and headers
System headers were updated to bring them up to compliance

with Spec 1170.
● X/Open curses
A new library has been added to support the interfaces defined

by this specification. Significant support for internationalized
curses capabilities, pads, terminfo database access, and color
manipulation has been added.
● Networking services
New X/Open standardized socket and IP address resolution

interfaces are available.
The X/Open Transport Interface (XTI) is the evolved

standardization of the set of interfaces that were supported by
the Transport Layer Interface (TLI) in System V Release 4. TLI
continues to be available for compatibility, but new
development should use XTI.
Update X/Open XFN CAE

Federated Naming Service (FNS) is now compliant with the
X/Open XFN common applications environment (CVE) definition.

A
Standards
Update POSIX 1003.1b

POSIX 1003.1b support is complete. The Solaris software provides
all of the interfaces for POSIX 1003.1b since the Solaris 2.3 release.
A subset of those interfaces was functional in that they provided
services instead of returning “Not Supported” messages. This
release finishes support for POSIX 1003.1b (with the exception of
the PRIORITIZED IO option).
This standards feature is of interest to developers interested in

writing portable, standards-compliant code. It is also of interest to
developers interested in higher performance message passing or
semaphore code who otherwise would use System V messages or
semaphores and who can accept the more limited functionality
offered by POSIX.
As of the Solaris 2.6 release, POSIX 1003.1b support is provided for
● Asynchronous I/O (except prioritized I/O)
● Mapped files
● Memory locking
● Memory protection
● Message passing
● Priority scheduling
● Real-time signals
● Semaphores
● File synchronization
● Shared memory objects
● Synchronized I/O
● Timers
Support for many of these features has been available in the

Solaris operating environment for several releases in a non-
standards conformable way.

A
Standards
Update ISO 10646

The International Organization of Standardization 10646 standard
defines Unicode 2.0, including UCS-2 and UTF-8 (the standard
UNIX implementation). All implementations specified in this
standard are Unicode 2.0 compliant.

A
Hardware Support
New PCMCIA PC Card

The PC Card Standard defines a 68-pin interface between a credit-
card-sized peripheral and the PC Card socket in the computer. It
also defines a software architecture that enables the computer’s
operating system to configure and control the PC Card peripheral
dynamically, upon insertion.
The Solaris 2.6 release provides a UNIX implementation of the PC

Card Standard, bundled with a number of drivers for common PC
Cards. Solaris Card Services provides PC Card driver interfaces
with ANSI C language bindings, enabling users to write drivers
that are independent of platform and host architecture.

A
New filesync
The new filesync feature ensures that data is moved
automatically between the portable computer and the server.
filesync is primarily intended for use on nomadic systems,
although it may also be useful for backup and file replication on
more permanently connected systems. Its purpose is to keep
copies of files in sync between multiple systems, typically a server
and a portable computer.
filesync can be used to maintain lists of files and directories to

be kept in sync between multiple systems. Each time it is invoked,
it examines all the files on both systems, determines which files
have changed, and propagates the changes (creations, deletions,
edits). It can deal with changes in both directions, and with
conflicting changes.

Where To Go For Help B
This appendix contains a summary of the information that was
presented in this seminar.
The complete titles of the courses referenced in the following tables

are:
SC-380: Securing Networked Environments
SA-350: Solaris 2.x Server Administration
SA-340: Managing Your Network Using SunNet Manager
B-1
B
Sun Educational Services Courses
Java
SA-235
SA-286
SA-350
SA-340
SC-380
HotJava browser X
SA-235
SA-286
SA-380
SA-350
SA-340
WebNFS X
SA-235
SA-286
SA-380
SA-350
SA-340
Kernel sockets X
TCP large windows X
Zero copy TCP/hardware checksum X
Ease-of-use and Management

SA-235
SA-286
SA-380
SA-350
SA-340
Improvements
Solaris Web Start browser-based X

installation
New installation documentation X
Changed Solaris CD-ROM layout X
Changing a system’s boot device X
Preconfiguring system configuration X
information
B-2 Transitioning to Solaris 2.6

B
Desktop
SA-235
SA-286
SA-380
SA-350
SA-340
Common Desktop Environment X
Power management for SPARC X
desktop systems
Network Management and
SA-235
SA-286
SA-380
SA-350
SA-340
System Administration
Solstice Enterprise Agents (SEA) X

Variable Length Subnet Mask (VLSM) X
NIS+ backup and fast restore X
CFS boot X
Patch tools X
Printing
SA-235
SA-286
SA-380
SA-350
SA-340
Redesign of print packages X

Print Protocol adaptor X
SunSoft Print Client X
Enhanced network printer support X
Where To Go For Help B-3

Copyright © 1997 Sun Microsystems Inc., 901 San Antonio Road, Palo Alto, Californie 94303, U.S.A. Tous droits réservés.
Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la
copie, la distribution, et la décompilation. Aucune partie de ce produit ou de sa documentation associée ne peut être
reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses
bailleurs de licence, s’il y en a.
Des parties de ce produit pourront être dérivées du système UNIX® licencié par Novell, Inc. et du système Berkeley 4.3
BSD licencié par l’Université de Californie. UNIX est une marque enregistrée aux Etats-Unis et dans d’autres pays et
licenciée exclusivement par X/Open Company Ltd. Le logiciel détenu par des tiers, et qui comprend la technologie
relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.
Sun, Sun Microsystems, le logo Sun sont des marques déposées ou enregistrées de Sun Microsystems, Inc. aux Etats-Unis et
dans d’autres pays. Toutes les marques SPARC, utilisées sous licence, sont des marques déposées ou enregistrées de SPARC
International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une
architecture développée par Sun Microsystems, Inc.
Les interfaces d’utilisation graphique OPEN LOOK® et Sun™ ont été développées par Sun Microsystems, Inc. pour ses
utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept
des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive
de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant aussi les licenciés de Sun qui mettent en
place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.
Le système X Window est un produit de X Consortium, Inc.
CETTE PUBLICATION EST FOURNIE “EN L’ETAT” SANS GARANTIE D’AUCUNE SORTE, NI EXPRESSE NI
IMPLICITE, Y COMPRIS, ET SANS QUE CETTE LISTE NE SOIT LIMITATIVE, DES GARANTIES CONCERNANT LA
VALEUR MARCHANDE, L’APTITUDE DES PRODUITS A RÉPONDRE A UNE UTILISATION PARTICULIERE, OU LE
FAIT QU’ILS NE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS.
Please
Recycle

SA226 - Transitioning To Solaris 2.6 - SG - 0997

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SA226 - Transitioning To Solaris 2.6 - SG - 0997

Uploaded by

Copyright:

Available Formats

Transitioning to Solaris 2.

Sun Educational Services

Part Number 805-2890-01

iv Transitioning to Solaris 2.6

vi Transitioning to Solaris 2.6

viii Transitioning to Solaris 2.6

Performance Ease-of-Use & Desktop

Standards Robust Software Large Files

Network Network Management & Printing

About This Seminar ix

● Module 2– Intranet/Internet Servers

The major new features relevant to servers is discussed in this

● Module 3 – Performance Improvements

This module examines the features that were added to improve

● Module 4 – Ease-of-Use and Management Improvements

In this module, the features that enable easier installation and

x Transitioning to Solaris 2.6

This module looks at the year 2000 ready issue.

● Module 7 – Robust Software Developer Environment

The features added to the Solaris environment that make software

● Module 8 – Large Files Support

Features that support file sizes of up to 2 Gbytes are examined.

● Module 9 – Network Security

In this module, the changes and new features that support or

About This Seminar xi

● Module 10 – Network Management and System Administration

The new features and updates relevant to network management

This module discusses the new printing features in the Solaris

xii Transitioning to Solaris 2.6

Upon completion of this seminar, you will be able to:

● List the key features in the Solaris 2.6 release

● Describe the importance of these key features to your work

● Identify where to find more detailed information on other Sun

About This Seminar xiii

The following icons and typographical conventions are used in this

Indicates Sun Educational Services courses that cover the current

Indicates a new feature.

Indicates a feature that has been updated.

Note – Additional important, reinforcing, interesting, or special

Caution – A potential hazard to data or machinery.

xiv Transitioning to Solaris 2.6

Use ls -al to list all files.

Courier italic is used for variables and command-line

To delete a file, type rm filename.

Read Chapter 6 in User’s Guide.

About This Seminar xv

Performance Ease-of-Use & Desktop

Standards Robust Software Large Files

Network Network Management & Printing

1-2 Transitioning to Solaris 2.6

New Java Virtual Machine

The JVM uses Solaris native threads, which provide

In addition, the Solaris JVM includes the appletviewer

Java Virtual Machine (Continued)

javald(1), another enhancement, is used to manage Java

Solaris 2.6 Reviewer’s Guide

Network Interfaces Programmer’s Guide

1-4 Transitioning to Solaris 2.6

New HotJava Browser

● Java applet support

Applets are small programs that can be included on a Web

The HotJava browser provides a secure environment for

1-6 Transitioning to Solaris 2.6