Home > Articles > Operating Systems, Server > Solaris

Minimizing Domains for Sun Fire V1280, 6800, 12K, and 15K Systems, Part II

This article is the second part of a two-part series and provides information and recommendations for minimizing domains for the Sun Fire V1280, Midframe, 12K and 15K systems. This part describes the package configurations needed for the various applications, describes the profiles produced for performing JumpStart installations of domains, and provides a case study as an example of applying the minimization methodology to an application. This article is targeted toward an advanced audience.
Like this article? We recommend

This article is the second part of a two-part series that provides information and recommendations for minimizing domains for Sun Fire™ V1280, 6800, 12K, and 15K systems. This part describes the package configurations needed for the various applications, describes the profiles produced for performing JumpStart installations of domains, and provides a case study as an example of applying the minimization methodology to an application. Part II provides background information, describes how to qualify a minimized Solaris™ configuration for an application, covers how to automate installations using JumpStart technology, and details a recommended methodology for minimizing a system.

This document contains the following topics:

  • "Application Package Configurations"

  • "Understanding Profiles and Application Dependencies"

  • "Case Study: Minimizing Sun Validation Test Suite 5.1"

  • "About the Authors"

  • "Related Resources"

  • "Ordering Sun Documents"

  • "Accessing Sun Documentation Online"

Application Package Configurations

This section contains a listing of all the packages that need to be installed to allow the applications discussed in Part I, "Qualifying a Solaris Configuration," to function on minimized domains. These are the results that were found by applying the minimization methodology.

The packages needed are structured into the areas for which they are required.

  • The smallest bootable set of packages to get a domain running, error free.

  • Device drivers needed for full functionality of add-in cards and hardware.

  • Commonly needed packages required by most applications.

  • Useful network tools that a user often needs.

  • Packages needed for Sun Fire V1280, 6800, 12K, and 15K functionality to be available.

  • Packages needed for support software to function.

  • Packages needed for additional applications to function.

NOTE

We focus on Solaris 9 Operating Environment (Solaris OE) for documenting the packages; only the differences for Solaris 8 OE are documented.

The packages detailed in this article are recommended always to be installed on a minimized domain to provide a consistent baseline, unless it mentions the packages are optional. For convenience, various JumpStart profiles have been produced as a baseline for adding packages that a customer's application would need. These profiles are detailed in the section "Understanding Profiles and Application Dependencies" on page 29.

For more information on supported configurations, see the section "What Software Is Supported?" in Part I of this article.

Solaris 9 OE

To get applications installed and working, a minimum baseline system is required to bring the system up in an operational state with configured hardware. This section describes the minimized set of packages to achieve this, and it is divided into the following subsections:

  • "Solaris 9 OE Booting" on page 3

  • "Hardware Device Drivers" on page 5

Solaris 9 OE Booting

The following packages define the smallest subset of 32- and 64-bit Solaris 9 OE packages that can be selected as a bootable install and that are supportable. These are all the packages that cannot be removed from metacluster SUNWCreq by specifying them with the delete keyword in a JumpStart profile.

The 32-bit packages cannot be deselected. The 64-bit versions of packages are included where available, because domains must be booted and run in 64-bit mode. The domains do not support 32-bit booting for the domain-specific software components.

Solaris 9 OE running in 64-bit mode requires the packages listed in TABLE 1.

TABLE 1 Required Packages for 64-Bit Mode Solaris 9 OE

Package Type

Description

SUNWadmr

System and network administration root

SUNWbzip

The bzip compression utility

SUNWcar

Core architecture (root)

SUNWcarx

Core architecture (root) (64-bit)

SUNWced

Sun GigaSwift Ethernet adapters (32-bit driver)

SUNWcedx

Sun GigaSwift Ethernet adapters (64-bit driver)

SUNWcsd

Core Solaris devices

SUNWcsl

Core Solaris (shared libs)

SUNWcslx

Core Solaris libraries (64-bit)

SUNWcsr

Core Solaris (root)

SUNWcsu

Core Solaris (usr)

SUNWcsxu

Core Solaris (usr) (64-bit)

SUNWesu

Extended system utilities

SUNWesxu

Extended system utilities (64-bit)

SUNWfcip

Sun FCIP IP/ARP over Fibre Channel device driver

SUNWfcipx

Sun FCIP IP/ARP over Fibre Channel device driver (64-bit)

SUNWfcp

Sun FCP SCSI device driver

SUNWfcpx

Sun FCP SCSI device driver (64-bit)

SUNWfctl

Sun Fibre Channel transport layer

SUNWfctlx

Sun Fibre Channel transport layer (64-bit)

SUNWhmd

SunSwift adapter drivers

SUNWhmdx

Core architecture (kvm) (64-bit)

SUNWi15cs

X11 ISO8859-15 codeset support

SUNWi1cs

X11 ISO8859-1 codeset support

SUNWkey

Keyboard configuration tables

SUNWkvm

Core Architecture (kvm)

SUNWkvmx

Core architecture (kvm) (64-bit)

SUNWlibms

Forte™ developer bundled shared libm

SUNWlmsx

Forte developer bundled 64-bit shared libm

SUNWloc

System localization

SUNWlocx

System localization (64-bit)

SUNWluxop

Sun Enterprise™ Network Array firmware and utilities

SUNWluxox

Sun Enterprise Network Array libraries (64-bit)

SUNWmdi

Sun Multipath I/O drivers

SUNWmdix

Sun Multipath I/O drivers (64-bit)

SUNWnamos

Northern America OS support

SUNWnamow

Northern America OW support

SUNWnamox

Northern America 64-bit OS support

SUNWpl5u

Perl 5.6.1 (core)

SUNWpl5v

Perl 5.6.1 (non-core)

SUNWsolnm

Solaris Naming Enabler

SUNWswmt

Install and patch utilities


In addition to the packages listed in TABLE 1, a Sun Fire 12K or 15K domain install adds the following packages automatically.

TABLE 2 Packages Installed Automatically With Sun Fire 12K and 15K Domains

Package Type

Description

SUNWnisr

Network information system (root)

SUNWnisu

Network information system (usr)


NOTE

Deselecting these packages from the suninstall profile will be ignored.

Hardware Device Drivers

Sun Fire V1280, 6800, 12K, and 15K domains support a wide variety of hardware. The most common hardware that is critical to the domain normally has the hardware device drivers stored in core Solaris packages, such as SUNWkvmx or SUNWcarx. However, add-on hardware normally has device drivers stored in separate packages that are part of the Solaris OE.

Add the packages listed in this section to a profile containing the Solaris 9 OE booting packages.

The audio device drivers are required to prevent console error messages when booting Solaris on the domain. TABLE 3 lists these packages.

TABLE 3 Required Audio Device Drivers

Package Type

Description

SUNWaudd

Audio drivers

SUNWauddx

Audio drivers (64-bit)


The packages listed in TABLE 4 are required for the Sun FCP SCSI Fibre Channel adapter.

TABLE 4 Required Packages for Sun FCP SCSI Fibre Channel Adaptor

Package Type

Description

SUNWses

SCSI Enclosure Services device driver

SUNWsesx

SCSI Enclosure Services device driver (64-bit)

SUNWssad

SPARCstorage_ Array drivers

SUNWssadx

SPARCstorage Array drivers (64-bit)


The packages listed in TABLE 5 are required for the Sun Gigabit Ethernet adapter.

TABLE 5 Required Packages for Sun Gigabit Ethernet Adaptor

Package Type

Description

SUNWged

Sun Gigabit Ethernet adapter driver

SUNWgedx

Sun Gigabit Ethernet adapter driver (64-bit)


NOTE

Sun GigaSwift Ethernet adapter packages are required to get Solaris booted. These are documented in "Solaris 9 OE Booting" on page 3.

The packages listed in TABLE 6 are required for the Sun Expert3D graphics card.

TABLE 6 Required Packages for Sun Expert3D Graphics Card

Package Type

Description

SUNWifb

Sun Expert3D (IFB) graphics system software/device driver

SUNWifbcf

Sun Expert3D (IFB) graphics configuration software

SUNWifbr

Sun Expert3D (IFB) graphics system software (root)

SUNWifbw

Sun Expert3D (IFB) graphics window system support

SUNWifbx

Sun Expert3D (IFB) graphics system software/device driver (64-bit)


NOTE

The Sun Expert3D graphics card packages are not included in any minimized profiles. Add them if this hardware is used. Additional graphic cards may be supported in the future. These are not documented in this article.

The packages listed in TABLE 7 are required for PCI cards.

TABLE 7 Required Packages for PCI Cards

Package Type

Description

SUNWpd

PCI drivers

SUNWpdx

PCI drivers (64-bit)


The packages listed in TABLE 8 are for Sun Quad FastEthernet adapters cards.

TABLE 8 Packages for Supporting Sun Quad FastEthernet Adaptor Cards

Package Type

Description

SUNWqfed

Sun Quad FastEthernet™ adapter driver

SUNWqfedx

Sun Quad FastEthernet adapter driver (64-bit)


The packages listed in TABLE 9 are for Sun WCI RSM.

TABLE 9 Required Packages for Sun Fire Link

Package Type

Description

SUNWrsm

Remote shared memory

SUNWrsmo

RSMPI operations registration module

SUNWrsmox

RSMPI operations registration module (64-bit)

SUNWrsmx

Remote shared memory (64-bit)

SUNWwrsax

WCI Remote Shared Memory API library (64-bit)

SUNWwrsdx

WCI RSM DLPI driver (64-bit)

SUNWwrsmx

WCI Remote Shared Memory drivers (64-bit)

SUNWwrsux

WCI RSM commands and libraries (64-bit)


NOTE

Installation of these packages is optional, however, they are required for the Sun Fire Link to operate. Uncomment them from the JumpStart™ profiles to install them during domain installation.

Commonly Needed Packages

Solaris has some common commands and libraries that are prerequisites for many of the applications discussed in this article. These are as follows:

  • "Miscellaneous Commands" on page 8

  • "Library Packages" on page 8

  • "Platform Information and Control Library (PICL)" on page 9

  • "Java Runtime Environment" on page 10

Miscellaneous Commands

The showrev command is called whenever patches already installed need to be examined. This process occurs during the install process of Solaris Patch Manager and Sun Remote Services Net Connect 3.0.

Sun Management Center 3.5 requires the /usr/ucb/whoami command to check if the user is root during install. SRS Net Connect 3.0 requires /usr/ucb/ps for its install process to run properly.

The packages containing miscellaneous executables and dynamic libraries are listed in TABLE 10.

TABLE 10 Miscellaneous Executables and Dynamic Libraries

Package Type

Description

SUNWadmc

System administration core libraries

SUNWadmfw

System and network administration framework

SUNWscpu

Source Compatibility (usr)

SUNWscpux

Source Compatibility (usr, 64-bit)


Library Packages

Several packages contain dynamic libraries that are typically mandatory for executing applications.

The major one is the standard C runtime library, needed by Sun Explorer 4.1, Sun Remote Services Net Connect 3.0, Sun Validation Test Suite 5.1, ORACLE 9i, and Sun ONE Application Server 7.0.

Another important library is the mathematical library, libm, needed by Sun Validation Test Suite 5.1, ORACLE 9i, and Sun ONE Application Server 7.0.

The zlib is a compression library that is required by Solaris Secure Shell and Sun Validation Test 5.1.

The packages listed in TABLE 11 contain these libraries.

TABLE 11 Dynamic Library Packages Typically Required

Package Type

Description

SUNWlibC

Sun Workshop™ compilers bundled libC

SUNWlibCx

Sun WorkShop bundled 64-bit libC

SUNWlibms

Forte Developer bundled shared libm

SUNWlmsx

Forte Developer bundled 64-bit shared libm

SUNWzlib

The Zip compression library

SUNWzlibx

The Zip compression library (64-bit)


Platform Information and Control Library (PICL)

The picld is a root running daemon process that is a database repository for system configuration information.

The Sun Fire V1280 relies on picld running on its domain for allowing Sun Management Center 3.5 agent software to be installed. Sun Explorer 4.1 software also has a need for picld to be running, for information to be gathered properly on the Sun Fire range.

Sun Validation Test Suite 5.1 software requires dynamic libraries in SUNWpiclu to function correctly.

PICL makes use of FRU information for a domain. Each platform has its own libraries for accessing this information. These are contained in the three SUNWfru* packages and need to be installed.

PICL provides limited information on the Sun Fire V1280, but this might change in the future, so it is recommended that it be installed.

Add the packages listed in TABLE 12 to allow picld to run on a domain.

TABLE 12 Packages Necessary for picld to Run on a Domain

Package Type

Description

SUNWfruid

FRU ID Utility and Library (usr)

SUNWfruip

FRU ID Platform Modules (usr)

SUNWfruix

FRU ID Library (64-bit)

SUNWpiclr

PICL framework (root)

SUNWpiclu

PICL libraries, and plugin modules (usr)

SUNWpiclx

PICL libraries (64-bit)


Java Runtime Environment

Many Solaris programs use the Java™ Runtime Environment (JRE) for carrying out operations. Often processes open libjvm.so to carry out FRU diagnostics.

Sun Explorer 4.1 is one application that does this. The program rprtfru.sparc requires libjvm.so or it fails.

Sun Remote Services Net Connect 3.0 has a similar requirement for it when the install process tries to install package SUNWfrunc. If libjvm.so is missing, then the install fails.

The JRE has dependencies on the packages listed in TABLE 13.

TABLE 13 JRE Package Dependencies

Package Type

Description

SUNWctpls

Portable layout services for Complex Text Layout support

SUNWdtcor

Solaris Desktop /usr/dt file system anchor

SUNWj2rt

JDK 1.2 run time environment

SUNWj3rt

JDK 1.3 runtime environment (Solaris 8 OE)

 

J2SDK 1.4 runtime environment (Solaris 9 OE)

SUNWj3rxt

J2SDK 1.4 runtime environment (64-bit) (Solaris 9 OE only)

SUNWmfrun

Motif RunTime Kit


Sun Validation Test Suite 5.1 requires these dependencies to be installed, because it needs SUNWmfrun.

NOTE

The package SUNWj3rxt is in Solaris 9 OE only.

Network Tools

This section describes the following important and useful network access tools for file transfers, secure communication, application configuration tracing, and X-Window application export over the network:

  • "NFS Client" on page 11

  • "ping and ftp Client" on page 12

  • "sendmail" on page 12

  • "truss" on page 12

  • "X-Windows Basic Applications" on page 13

  • "Solaris Secure Shell" on page 13

NFS Client

It is often useful to NFS mount remote server directories to a domain. TABLE 14 lists the packages required.

TABLE 14 Packages for NFS Mounting of Remote Server Directories

Package Type

Description

SUNWnfscr

Network file system (NFS) client support (Root)

SUNWnfscu

Network file system (NFS) client support (Usr)

SUNWnfscx

Network file system (NFS) client support (Root) (64-bit)


ping and ftp Client

For the ability to be able to ping and ftp from domain calls, the SUNWbip package (basic IP commands) is required.

NOTE

The FTP client is just that. It is not an FTP server and does not run an ftp daemon on the domain. Communication must be initiated from the domain to an external host.

sendmail

Often it is a requirement for an application to be able to send email. Add the packages listed in TABLE 15 for this functionality.

TABLE 15 Packages for sendmail Functionality

Package Type

Description

SUNWsndmr

Sendmail root

SUNWsndmu

Sendmail user


truss

The truss is an important tool for troubleshooting system configurations by analyzing system calls. The packages listed in TABLE 16 install truss.

TABLE 16 Packages for Installing truss

Package Type

Description

SUNWtoo

Programming tools

SUNWtoox

Programming tools (64-bit)


X-Windows Basic Applications

To run X-based applications, such as xterm, add the packages listed in TABLE 17.

TABLE 17 Packages for Running X-Windows Applications

Package Type

Description

SUNWcpp

Solaris cpp

SUNWlccom

Localization common files

SUNWxwdv

X-Windows system window drivers

SUNWxwfnt

X-Windows system platform required fonts

SUNWxwice

X-Windows system inter-client exchange (ICE) components

SUNWxwopt

X-Windows system optional clients

SUNWxwplt

X-Windows system platform software


Common Desktop Environment (CDE) based packages, such as dtterm, are not supported in minimized profiles.

Solaris Secure Shell

Starting with Solaris 9 OE, Secure Shell is included with the software distribution. The packages listed in TABLE 18 allow Secure Shell client and server to operate in a domain.

TABLE 18 Packages for Operating Secure Shell in a Domain

Package Type

Description

SUNWsshcu

SSH Common (usr)

SUNWsshdr

SSH Server (root)

SUNWsshdu

SSH Server (usr)

SUNWsshr

SSH Client and utilities (root)

SUNWsshu

SSH Client and utilities (usr)


Secure Shell can tunnel X-applications over a secure channel. This action allows insecure commands like xterm to be run with confidence over an unsecured network. To do this requires X-application packages to be installed.

Domain-Specific Components

The following are specialized domain-dependent components that are needed to allow a domain to be fully operational and to allow full domain functionality, such as dynamic reconfiguration (DR) and remote monitoring.

  • "Common Dynamic Reconfiguration Components" on page 14

  • "Sun Fire 12K and 15K Dynamic Reconfiguration" on page 15

  • "Sun Fire 12K and 15K Network Console" on page 15

  • "Sun Fire 6800 Packages" on page 16

  • "Sun Fire V1280 Packages" on page 16

  • "Capacity On Demand 2.0" on page 16

  • "Sun Management Services 1.3" on page 16

  • "Sun Management Center 3.5" on page 17

Common Dynamic Reconfiguration Components

The packages listed in TABLE 19 must be installed on Sun Fire V1280, 6800, 12K, and 15K domains for remote DR requests to succeed.

TABLE 19 Packages Required for Dynamic Reconfiguration Requests (All Platforms)

Package Type

Description

SUNWdcsr

Domain configuration server (root)

SUNWdcsu

Domain configuration server

SUNWefclx

Embedded FCode libraries (64-bit)

SUNWefcr

Embedded FCode interpreter (root)

SUNWefcux

Embedded FCode interpreter (64-bit)

SUNWefcx

Embedded FCode interpreter drivers (64-bit)


Sun Fire 12K and 15K Dynamic Reconfiguration

Infrastructure services for the Sun Fire 12K and 15K domains, such as DR, have core drivers and daemons that are part of Solaris OS core.

The packages listed in TABLE 20 are not required for minimized Sun Fire V1280 and 6800 domains.

TABLE 20 Additional Packages Required for Sun Fire 12K and 15K Dynamic Reconfiguration

Package Type

Description

SUNWsckmr

init script and links for Sun Fire 15K key management daemon

SUNWsckmu

Key management daemon for Sun Fire 15K

SUNWsckmx

Key management modules for Sun Fire 15K (64-Bit)

SUNWdrcrx

Dynamic reconfiguration modules for Sun Fire 15K (64-bit)


Sun Fire 12K and 15K Network Console

The packages listed in TABLE 21 are required for the network console.

TABLE 21 Packages Required for the Network Console

Package Type

Description

SUNWcvcr

Network Console daemon and rc script

SUNWcvcx

Network Console (64-bit)


NOTE

SUNWcvc (network console) contains drivers for Sun Enterprise 10000 only; therefore, it is not required for Sun Fire 12K and 15K systems.

Sun Fire 6800 Packages

There are no Sun Fire 6800 specific packages in Solaris OE version 8 or 9.

Sun Fire V1280 Packages

The Sun Fire V1280 uses Sun Advanced Lights Out Management 2.0 software, and there are several packages that need to be installed to use this software on the domain. These are installed from the Solaris install supplemental CD and consist of the packages listed in TABLE 22.

TABLE 22 Packages for Sun Advanced Lights Out Management 2.0 Software

Package Type

Description

SUNWlomr

LOMlite driver (root)

SUNWlomu

LOMlite utilities (usr)


Sun Fire 6800, 12K, and 15K do not support Sun Advanced Lights Out Management 2.0 software.

NOTE

The Sun Advanced Lights Out Management 2.0 software can either be manually installed with pkgadd or installed via the installer script. If installed by the installer script, then the X-applications profile must be used.

Capacity On Demand 2.0

There are no package requirements on the domain.

Sun Fire 12K and 15K Capacity On Demand 2.0 commands, for example, showcodusage, showcodlicense, and addcodlicense, are executed from the SC and installed as part of Sun Management Services 1.3 software.

Sun Fire Capacity On Demand 2.0 software is built into the SC firmware.

Sun Management Services 1.3

Sun Management Services 1.3 is installed on Sun Fire 12K and 15K system controllers only. It is not needed on Sun Fire V1280, 6800, 12K, or 15K domains, therefore, it should not be installed on domains.

Sun Management Center 3.5

The Sun Management Center 3.5 domain agent software is installed by executing the command es-inst -a from the Sun Management Center 3.5 install CD.

Sun Management Center 3.5 is made up of domain, server, and console software. Domain agent software is the only software that should be installed on the domain. All components of the agent software were installed during software qualification.

The Sun Management Center 3.5 server software should be installed and configured on another Solaris system to allow Sun Management Center 3.5 console to be invoked and to allow the domain configuration to be manipulated.

The Sun Management Center 3.5 agent software installation process installs a domain-specific component. This component is unique for a Sun Fire V1280, 6800, 12K, and 15K chassis.

The packages listed in TABLE 23 are required for Sun Management Center 3.5 agent software.

TABLE 23 Packages for Sun Management Center Software

Package Type

Description

SUNWdtdst

CDE Desktop Applications

SUNWwrsux

WCI RSM Commands and Libraries (64-bit)


NOTE

SUNWdtdst has substantial dependencies that include dependencies on X packages and all the dt packages. The X and dt packages are unneeded because only the shared library /usr/dt/lib/libcsa.so.0 in SUNWdtdst is needed by libcalendarservice.so and pkgcalendar.so.1.

Support Software Components

This section lists packages for the following reliability, availability, and scalability RAS-D (Diagnostics) software.

  • "Solaris Patch Manager 1.0" on page 18

  • "Sun Explorer 4.1" on page 18

  • "Sun Remote Services Net Connect 3.0" on page 18

  • "Sun Validation Test Suite 5.1" on page 19

Solaris Patch Manager 1.0

Patch utilities patchadd, patchrm, and unzip are needed by Solaris Patch Manager 1.0. The Solaris Patch Manager 1.0 software installs the JRE only if it is not already installed; it does not try to display any GUI windows.

NOTE

The install process for Solaris Patch Manager 1.0 software flags SUNWmfrun as a prerequisite and the install aborts if it is not present.

The packages list installed by Solaris Patch Manager 1.0 on a full system is much less than that installed on a minimized system, because Solaris Patch Manager 1.0 requires a JRE. If one is not found, then Solaris Patch Manager 1.0 installs it with dependent packages.

Sun Explorer 4.1

There are no domain-specific packages required for Sun Explorer 4.1 to work correctly other than those detailed in "Commonly Needed Packages" on page 8. To make use of the sendmail capability, then the sendmail packages must be installed.

NOTE

The shared library libfrufileaccess.so.1 is in the package SUNWSMSop. This package is installed on the SC when Sun Management Services 1.3 is installed. It is not needed on a minimized domain.

Sun Remote Services Net Connect 3.0

Sun Remote Services Net Connect 3.0 installs a specific version of Sun Explorer data collector software, if it is not already installed. If a different version is installed, then it asks to replace it. Otherwise, installation of Sun Remote Services Net Connect 3.0 aborts.

NOTE

Sun Remote Services Net Connect 3.0 currently does not work on the Sun Fire V1280. Check for software patches or updates after the release of this article.

Installing Sun Remote Services Net Connect 3.0 software requires SUNWstade (storage automated diagnostic environment) or else the SUNWsrssp (part of Sun Remote Services Net Connect 3.0) will fail to be installed.

NOTE

Download the latest SUNWstade package from the Sun Download Center.

Sun Validation Test Suite 5.1

Sun Validation Test Suite 5.1 installs many kernel modules that perform diagnostic operations. These operations touch every part of the system hardware; for this reason, the package requirements for Sun Validation Test Suite 5.1 are substantial.

The packages listed in TABLE 24 are required for Sun Validation Test Suite 5.1

TABLE 24 Required Packages for Sun Validation Test Suite 5.1

Package Type

Description

SUNWcpc

CPU performance counter driver

SUNWcpcu

CPU performance counter libraries and utilities

SUNWcpcux

CPU performance counter libraries and utilities (64-bit)

SUNWcpcx

CPU performance counter driver (64-bit)

SUNWcpp

Solaris cpp

SUNWdtbas

CDE application basic runtime environment

SUNWfns

Federated Naming System

SUNWgss

GSSAPI V2

SUNWgssc

GSSAPI CONFIG V2

SUNWlxml

The XML library

SUNWlxmlx

The XML library (64-bit)

SUNWmdb

Modular Debugger

SUNWmdbx

Modular Debugger (64-bit)

SUNWrsg

RPCSEC_GSS

SUNWtltk

ToolTalk runtime

SUNWwrsux

WCI RSM commands and libraries (64-bit)

SUNWxwcft

X-Windows system common (not required) fonts

SUNWxwdv

X-Windows system window drivers

SUNWxwfnt

X-Windows system platform required fonts

SUNWxwice

X-Windows system inter-client exchange (ICE) component

SUNWxwicx

X-Windows system ICE library (64-bit)

SUNWxwopt

X-Windows system optional clients

SUNWxwplt

X-Windows system platform software

SUNWxwplx

X-Windows system library software (64-bit)

SUNWxwrtl

X-Windows system and graphics runtime library links in /usr/lib

SUNWxwrtx

X-Windows system runtime compatibility package (64-bit)


Sun Validation Test Suite 5.1 is installed without Kerberos. If Kerberos is enabled during installation of Sun Validation Test Suite 5.1, then the packages listed in TABLE 25 are required.

TABLE 25 Packages Required for Kerberos

Package Type

Description

SUNWkrbr

Kerberos version 5 support (root)

SUNWkrbu

Kerberos version 5 support (usr)

SUNWkrbux

Kerberos version 5 support (usr), (64-bit)


NOTE

The Kerberos packages are not included in the minimized profiles.

Additional Applications

The following are the package requirements for additional applications that customers typically want installed.

  • "ORACLE 9i" on page 20

  • "Sun ONE Application Server" on page 21

ORACLE 9i

ORACLE9i requires the linker to be available during install. It needs make, ar, ld, and nm to be available for this purpose.

ORACLE9i does not have a client-only install, other than by supplying a configured response file. This is not supported in this article.

So, to do an interactive install, it requires a few X-packages be installed to allow the Java GUI to be displayed. ORACLE9i installs its own JRE in preference to any system-wide version.

The packages listed in TABLE 26 are required for ORACLE9i to install and work correctly.

TABLE 26 Packages Required for ORACLE9i

Package Type

Description

SUNWarc

Archive libraries

SUNWbtool

CCS tools bundled with SunOS

SUNWcpp

Solaris cpp

SUNWhea

SunOS header files

SUNWlibm

Forte Developer bundled libm

SUNWlmx

Forte Developer bundled miscellaneous 64-bit libm files

SUNWsprot

Solaris bundled tools

SUNWtoo

Programming tools

SUNWxwice

X-Windows system inter-client exchange (ICE) components

SUNWxwplt

X-Windows system platform software

SUNWxwrtl

X-Windows system and graphics runtime library links in /usr/lib


Sun ONE Application Server

The packages listed in TABLE 27 are required for a Sun ONE Application Server to function.

TABLE 27 Packages Required for Sun ONE Application Server

Package Type

Description

SUNWscpu

Source compatibility (usr)

SUNWxcu4

XCU4 utilities

SUNWxwfnt

X-Windows system platform required fonts

SUNWxwice

X-Windows system inter-client exchange (ICE) components

SUNWxwplt

X-Windows system platform software

SUNWxwrtl

X-Windows system and graphics runtime library links in /usr/lib


Solaris 8 OE

Solaris 8 has limited support for minimization through package deletion from a defined package metacluster. It does not allow any packages to be deselected from metacluster SUNWCreq. This whole metacluster is the minimal set of packages that can be installed via suninstall. Due to this restriction in suninstall, all packages must be included in this set for it to be supported.

NOTE

The following sections detail only the differences between Solaris OE versions 8 and 9. Where package requirements are the same, see the equivalent section "Solaris 9 OE" on page 3.

This section describes the differences between the Solaris OE version 8 and 9 for the following topics:

  • "Solaris 8 OE Booting" on page 22

  • "Hardware Device Drivers" on page 26

  • "NFS, ping, and FTP Client" on page 26

  • "X-Windows Basic Applications" on page 27

  • "Secure Shell" on page 27

  • "Sun Validation Test Suite 5.1" on page 28

Solaris 8 OE Booting

Although the package clusters SUNWCcs and SUNWCnis can be deselected successfully from suninstall, when the system is rebooted, the packages that make up those clusters are installed regardless.

Additionally, packages such as SUNWftpr (FTP server root files) cannot be deselected via suninstall. These packages should by default not be installed on a minimized system; however, there is no option for not installing them.

These packages could be removed manually using the command pkgrm after the JumpStart installation of the domain has occurred or via a finish script, but this practice is not supported. TABLE 28 provides a partial set of candidates that could be deleted this way.

TABLE 28 Solaris 8 OE: Candidate Packages for Removing After Installation

Package Type

Description

SUNWftpr

FTP server (root)

SUNWftpu

FTP server (usr)

SUNWwsr2

Solaris product registry and Web Start runtime support

SUNWxwdv

X-Windows system window drivers

SUNWxwdvx

X-Windows system window drivers (64-bit)

SUNWxwmod

OpenWindows™ kernel modules

SUNWxwmox

X-Windows system kernel modules (64-bit)


TABLE 29 lists packages installed on a domain as part of metacluster SUNWCreq.

TABLE 29 Solaris 8 OE: Packages Installed as Part of SUNWCreq

Package Type

Description

SUNWadmr

System and network administration root

SUNWatfsr

AutoFS (root)

SUNWatfsu

AutoFS (usr)

SUNWauda

Audio applications

SUNWaudd

Audio drivers

SUNWauddx

Audio drivers (64-bit)

SUNWbzip

The bzip compression utility

SUNWcar

Core architecture (root)

SUNWcarx

Core architecture (root) (64-bit)

SUNWced

Sun GigaSwift Ethernet Adapter (32-bit driver)

SUNWcedx

Sun GigaSwift Ethernet Adapter (64-bit driver)

SUNWcg6

GX (cg6) device driver

SUNWcg6x

GX (cg6) device driver (64-bit)

SUNWcsd

Core Solaris devices

SUNWcsl

Core Solaris (shared libs)

SUNWcslx

Core Solaris libraries (64-bit)

SUNWcsr

Core Solaris (root)

SUNWcsu

Core Solaris (usr)

SUNWcsxu

Core Solaris (usr), (64-bit)

SUNWdfb

Dumb frame buffer device drivers

SUNWdtcor

Solaris Desktop /usr/dt filesystem anchor

SUNWeridx

Sun RIO 10/100 Megabyte Ethernet drivers (64-bit)

SUNWesu

Extended system utilities

SUNWfcip

Sun FCIP IP/ARP over Fibre Channel device driver

SUNWfcipx

Sun FCIP IP/ARP over Fibre Channel device driver (64 bit)

SUNWfcp

Sun FCP SCSI device driver

SUNWfcpx

Sun FCP SCSI device driver (64-bit)

SUNWfctl

Sun Fibre Channel transport layer

SUNWfctlx

Sun Fibre Channel transport layer (64-bit)

SUNWftpr

FTP server (root)

SUNWftpu

FTP server (usr)

SUNWged

Sun Gigabit Ethernet Adapter driver

SUNWhmd

SunSwift SBus Adapter drivers

SUNWhmdx

SunSwift SBus Adapter drivers (64-bit)

SUNWi15cs

X11 ISO8859-15 codeset support

SUNWi1cs

X11 ISO8859-1 codeset support

SUNWkey

Keyboard configuration tables

SUNWkvm

Core architecture (kvm)

SUNWkvmx

Core architecture (kvm) (64-bit)

SUNWlibms

Sun WorkShop bundled shared libm

SUNWlmsx

Sun WorkShop bundled 64-bit shared libm

SUNWloc

System localization

SUNWlocx

System localization (64-bit)

SUNWluxdx

Sun Enterprise Network Array sf device driver (64-bit)

SUNWluxop

Sun Enterprise Network Array firmware and utilities

SUNWluxox

Sun Enterprise Network Array libraries (64-bit)

SUNWm64

M64 Graphics system software/device driver

SUNWm64x

M64 Graphics system software/device driver (64-bit)

SUNWmdi

Sun Multipath I/O drivers

SUNWmdix

Sun Multipath I/O drivers (64-bit)

SUNWnamos

Northern America OS support

SUNWnamow

Northern America OW support

SUNWnisr

Network information system (root)

SUNWnisu

Network information system (usr)

SUNWpd

PCI drivers

SUNWpdx

PCI drivers (64-bit)

SUNWpl5u

Perl 5.005_03

SUNWqfed

Sun Quad FastEthernet Adapter driver

SUNWqfedx

Sun Quad FastEthernet Adapter driver (64-bit)

SUNWqlc

Qlogic ISP 2200/2202 Fibre Channel device driver

SUNWqlcx

Qlogic ISP 2200/2202 Fibre Channel device driver (64 bit)

SUNWrmodu

Realmode modules, (usr)

SUNWses

SCSI Enclosure Services device driver

SUNWsesx

SCSI Enclosure Services device driver (64-bit)

SUNWsndmr

Sendmail root

SUNWsndmu

Sendmail user

SUNWsolnm

Solaris Naming Enabler

SUNWssad

SPARCstorage Array drivers

SUNWssadx

SPARCstorage Array drivers (64-bit)

SUNWswmt

Install and patch utilities

SUNWtleux

Thai Language Environment user files (64-bit)

SUNWuaud

USB audio drivers

SUNWuaudx

USB audio drivers (64-bit)

SUNWudf

Universal disk format 1.50, (usr)

SUNWudfr

Universal disk format 1.50

SUNWudfrx

Universal disk format 1.50 (64-bit)

SUNWusb

USB device drivers

SUNWusbx

USB device drivers (64-bit)

SUNWwsr2

Solaris product registry and Web Start runtime support

SUNWxwdv

X-Windows system window drivers

SUNWxwdvx

X-Windows system window drivers (64-bit)

SUNWxwmod

OpenWindows kernel modules

SUNWxwmox

X-Windows system kernel modules (64-bit)


Hardware Device Drivers

Hardware device driver packages for Solaris 8 OE match those of Solaris 9 OE. For a list, see "Hardware Device Drivers" on page 5.

Additional Packages Needed by Solaris 8 OE

SUNWter is required by applications that manipulate the terminal. SUNWesxu is the 64-bit version of SUNWesu, and it is not included by default in SUNWCreq for Solaris 8 OE. TABLE 30 lists the additional packages.

TABLE 30 Solaris 8 OE: Additional Packages Needed

Package Type

Description

SUNWesxu

Extended system utilities (64-bit)

SUNWter

Terminal information


NFS, ping, and FTP Client

The NFS client software, ping, and FTP are mandatory for installation in Solaris 8 OE. They are installed as part of the Solaris core package SUNWcsu.

X-Windows Basic Applications

To use X-based applications such as xterm, add the packages listed in TABLE 31.

TABLE 31 Solaris 8 OE: Packages Required for running X-Windows Applications

Package Type

Description

SUNWtltk

ToolTalk runtime

SUNWxi18n

X-Windows system internationalization common package

SUNWxildh

XIL loadable pipeline libraries

SUNWxilow

XIL deskset loadable pipeline libraries

SUNWxilrl

XIL Runtime Environment

SUNWxwdv

X-Windows system window drivers

SUNWxwfnt

X-Windows system platform required fonts

SUNWxwice

ICE components

SUNWxwopt

Nonessential MIT core clients and server extensions

SUNWxwplt

X-Windows system platform software


Common Desktop Environment (CDE) based packages, such as dtterm, are not supported in minimized profiles.

Secure Shell

Secure Shell is not part of Solaris 8 OE; however, a mechanism for logging into domains remotely is required. This mechanism is achieved with the open source version of SSH, OpenSSH. The open source version that we tested consists of OpenSSH v3.5p1 and OpenSSL v0.9.6g. Because these are third-party products, they are unsupported by Sun.

NOTE

OpenSSH for Solaris 8 OE can be downloaded from http://www.sunfreeware.com. For more information about OpenSSH, go to http://www.openssh.org and to the Sun BluePrints book titled Secure Shell in the Enterprise.

Sun Validation Test Suite 5.1

The packages listed in TABLE 32 are required for Sun Validation Test Suite 5.1.

TABLE 32 Solaris 8 OE: Packages Required for Sun Validation Test Suite

Package Type

Description

SUNWcpc

CPU performance counter driver

SUNWcpcu

CPU performance counter libraries and utilities

SUNWcpcux

CPU performance counter libraries and utilities (64-bit)

SUNWcpcx

CPU performance counter driver (64-bit)

SUNWdtbas

CDE application basic runtime environment

SUNWfns

Federated naming system

SUNWgss

GSSAPI V2

SUNWgssc

GSSAPI CONFIG V2

SUNWlxml

The XML library

SUNWlxmlx

The XML library (64-bit)

SUNWrsg

RPCSEC_GSS

SUNWtltk

ToolTalk runtime

SUNWwrsux

WCI RSM commands and libraries (64-bit)

SUNWxwcft

X-Windows system common (not required) fonts

SUNWxwice

X-Windows system inter-client exchange (ICE) component

SUNWxwicx

X-Windows system ICE library (64-bit)

SUNWxwplt

X-Windows system platform software

SUNWxwplx

X-Windows system library software (64-bit)

SUNWxwrtl

X-Windows system and graphics runtime library links in /usr/lib

SUNWxwrtx

X-Windows system runtime compatibility package (64-bit)


NOTE

SUNWlxml and SUNWlxmlx can be installed from the Solaris 8 OE Supplement CD or downloaded from http://www.sun.com/oem/products/vts at the same time as Sun Validation Test Suite 5.1 is downloaded.

As with Solaris 9 OE, Sun Validation Test Suite 5.1 is installed without Kerberos. If Kerberos is enabled during installation of Sun Validation Test Suite 5.1, then the packages listed in TABLE 33 are required.

TABLE 33 Solaris 8 OE: Packages Required for Kerberos

Package Type

Description

SUNWkrbr

Kerberos version 5 support (root)

SUNWkrbu

Kerberos version 5 support (usr)

SUNWkrbux

Kerberos version 5 support (usr), (64-bit)


InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020