Solaris SA 1 & 2 - Training Material
SOLARIS - OPERATING ENVIRONMENT SYSTEM ADMINISTRATION – I & II
Training Material
Solaris Operating Environment System Administration I & II
Page 1 of 563
Solaris SA 1 & 2 - Training Material
SOLARIS - OPERATING ENVIRONMENT SYSTEM ADMINISTRATION - 1 INDEX
Chap. No
Chapter Name
Starting Page No
1
Introducing the Solaris Operating System Installing the Solaris Operating Environment on a Standalone System
4
2
Administration of Software Packages Managing Software Patches
19
3
Systems Security
52
4
The Boot PROM
97
5
Adding Users
125
6
Device Configuration
150
7
Disks, Slices, and Format
170
8
The Solaris Operating Environment UFS File System
193
9
Mounting File System
208
10
Directory Hierarchy
232
11
Maintaining File Systems
248
12
Scheduling Process Control
263
13
System Boot Process
274
14
Backup and Recovery
300
Solaris Operating Environment System Administration I & II
Page 2 of 563
Solaris SA 1 & 2 - Training Material
SOLARIS - OPERATING ENVIRONMENT SYSTEM ADMINISTRATION - II INDEX
Chap. No
Chapter Name
Starting Page No
15
Introducing Disk Management.
320
16
Introducing the Solaris Network Environment.
329
17
Solaris Operating Environment syslog.
350
18
Solaris Pseudo File Systems and Swap Space.
369
19
NFS.
392
20
AutoFS.
422
21
Cache FS.
438
22
Naming Services Overview.
454
23
NIS.
474
24
JumpStart™-Automatic Installation.
517
*****
Solaris Operating Environment System Administration I & II
Page 3 of 563
Solaris SA 1 & 2 - Training Material
CHAPTER - 1 INTRODUCING THE SOLARIS OPERATING SYSTEM ENVIRONMENT SYSTEM ADMINISTRATION
Roles of the system Administrator
The system administrator is responsible for the smooth operation of day-to-day, activities on each system. The scope and variety of tasks that a Solaris Operating Environment system administrator performs have been placed into the following two course categories:
The first category encompasses all the major skills and activities required to administer a standalone system and are covered in this course: SA-238 Solaris Operating Environment System Administration I
The second category includes those skills and activities required to successfully administer a basic client/server configuration and are covered in the course: SA-288 Solaris Operating Environment System Administration II
Solaris Operating Environment System Administration I & II
Page 4 of 563
Solaris SA 1 & 2 - Training Material
System Administration Terms The following list defines some common system administration terms
Host – Another word for a computer system
Host Name – A unique name given to a computer system by the system administrator to distinguish from other hosts on the network. The command uname – displays the assigned host name.
Internet (IP) address - A number that represents the host address and the network address, for example: 192.134.117.25. A host's IP address identifies where a host is on the Internet, which allows network traffic to be directed to that host. This software address is placed in the /etc/inet/hosts file.
Ethernet address -A host's unique hardware address. A number displayed as 12 hexadecimal digits. For example, 08:00:20:1c:54:7e. This address is stored in the NVRAM (nonvolatile random access memory) chip.
Server - A host that provides one or more services to hosts on a network.
Client - A host that uses services, provided by the
Note - Servers and clients are two types of hosts in a distributed computing environment.
Solaris Operating Environment System Administration I & II
Page 5 of 563
Solaris SA 1 & 2 - Training Material
INSTALLING THE SOLARIS OPERATING ENVIRONMENT ON A STANDALONE SYSTEM
Objectives Upon completion of this module, you should be able to: •
State the different installation methods available for the Solaris Operating Environment software
•
Explain the hardware requirements for a Solaris Operating Environment installation
•
Identify the different Solaris Operating Environment soft-ware CD-ROM editions
•
List the five Solaris Software Groups
•
Demonstrate how to install the Solaris Operating Environment software on a networked, standalone system, using Solaris™ Web Start
Solaris Operating Environment System Administration I & II
Page 6 of 563
Solaris SA 1 & 2 - Training Material
The Solaris Operating Environment Software Installation Options You can install the Solaris software on a system using one of the following installation options •
Solaris Web Start 3.0 Installation - Provides a graphical user interfacebased, Java technology-powered software application that guides you through the installation of the Solaris Operating Environment and other software on a single system from a local or remote CD-ROM drive.
•
Solaris Interactive Installation Program-Provides a graphical user Interface that guides you step-by-step through installing the Solaris Operating Environment software, 'this installation program does not enable you to install all the additional software, as with Solaris Web Start, it installs only the Solaris Operating Environment software.
•
Solaris Installation Over the Network - Provides the capability to install the Solaris Operating environment software on a large number of systems that do not have -a local CD-ROM drive. This eliminates the need to insert the Solaris Operating Environment software CD-ROM on every system. You can install these systems from the remote Solaris Operating Environment software CD images, which have been copied to an install server system's hard drive.
•
Solaris JumpStart Installation - Provides the capability to automatically install the Solaris Operating Environment software on a new system only, by inserting the CD labeled Solaris •Software 1 of 2 SPARC Platform Edition or Intel Platform Edition into the CD-ROM drive and turning on the system. The software components installed are specified by a default profile that is selected based on the model and disk size of the system.
Solaris Operating Environment System Administration I & II
Page 7 of 563
Solaris SA 1 & 2 - Training Material
•
Solaris Custom JumpStart Installation - A type of installation in which the Solaris Operating Environment software is automatically installed on a system based on a user-defined profile. You can customize profiles for different types of users and systems, and this is the most cost-effective option for installing the Solaris Operating Environment software in a large enterprise. Provides hands off installation across the network based on a central configured server. .
Note - This module describes how to install the Solaris Operating Environment software on a single system with Solaris Web Start, Sun's graphical wizard, Java technology-powered software installation application.
Solaris Operating Environment System Administration I & II
Page 8 of 563
Solaris SA 1 & 2 - Training Material
Hardware Requirements of a Solaris Operating Environment Installation A desktop Solaris Operating Environment installation requires: •
A SPARC-based or an Intel-based system
•
64 Mbytes of memory
•
2.3 Gbytes of disk space
•
Access to a CD-ROM drive
Solaris Operating Environment System Administration I & II
Page 9 of 563
Solaris SA 1 & 2 - Training Material
The Solaris Operating Environment installation CD-ROM The content of each CD-ROM in the Solaris Operating Environment Media kit is as follows: The Solaris Operating Environment SPARC Platform Edition CD-ROM
•
Solaris Installation English SPARC Platform Edition
•
Solaris Software CD 1 of 2 SPARC Platform Edition
•
Solaris Software CD 2 of 2 SPARC Platform Edition
•
Solaris Documentation CD (English SPARC/Intel Platform Edition)
International Versions of the Solaris Operating Environment International versions of Solaris contain: •
Solaris Installation Multilingual CD SPARC Platform Edition
•
Solaris Software CD 1 of 2 SPARC Platform Edition
•
Solaris Software CD 2 of 2 SPARC Platform Edition
•
Solaris Languages CD - SPARC Platform Edition or Intel Platform Edition
International versions also include a two CD-ROM set labeled: •
Solaris -Documentation European SPARC/Intel Platform Edition, which contains English, French, German, Italian, Spanish, and Swedish documentation.
•
Solaris Documentation Asian SPARC/Intel Platform Edition, which contains Simplified and Traditional Chinese, Japanese, and Korean documentation.
Solaris Operating Environment System Administration I & II
Page 10 of 563
Solaris SA 1 & 2 - Training Material
Intel Versions of the Solaris. Operating Environment An equivalent CD-ROM set is included with the Solaris Intel Platform Edition, plus a diskette labeled Solaris Device Configuration Assistant Intel Platform Edition.
Choosing the Correct CD for Your Installation Requirements
The following describes which CD-ROM is required when installing Solaris using the different installation methods: •
Solaris Web Start uses the following CD-ROM set: ¾ Solaris Installation ¾ Solaris Software 1 of 2 ¾ Solaris. Software 2 of 2
All the other installation methods described earlier use the Solaris Software 1 of 2 and-Solaris Software 2 of 2 CD-ROM set.
Solaris Operating Environment System Administration I & II
Page 11 of 563
Solaris SA 1 & 2 - Training Material
The Solaris Operating Environment Software Arrangement The Solaris Operating Environment software delivered on the Solaris Software CD-ROM set 1 of 2 and 2 of 2 are organized into three types of components: •
Software Packages
•
Software Clusters
•
Cluster Configurations
Cluster Configuration
Figure 14-1
Software Cluster
Software Packages
Solaris Operating Environment Software Components
Software Packages A software package contains a group of files and directories in a category of related software (for example, system or application) and software installation scripts
Solaris Operating Environment System Administration I & II
Page 12 of 563
Solaris SA 1 & 2 - Training Material
Software Clusters During the software installation process, logical collections of software packages are grouped into software clusters, For example, the CDE software cluster includes the following packages: SUNWdtbas SUNWdtbas SUNWdtdem SUNWdtdm SUNWdtdst SUNWdthe
SUNWdthed SUNWdthev SUNWdticn SUNWdtim SUNWdtinc SUNWdtma
SUNWdtmad SUNWdtrme SUNWdtwn SUNWeudba SUNWudbd SUNWeudda
SUNWeudhr SUNWeudhs SUNWeudis SUNWeudlg SUNWmfman
Some software clusters can contain only one software package.
Cluster Configuration The cluster configurations are referred to during the installation process as the Solaris Software Groups. There are currently five software groups available, which include: •
Entire Solaris Software Group Plus OEM -SUNWCXall
•
Entire Solaris Software Group – SUNWCall
•
Developer Solaris Software Group - SUNWCprog
•
End User Solaris Software Group - SUNWCusr
•
Core Solaris Software Group - SUNWCreq
Solaris Operating Environment System Administration I & II
Page 13 of 563
Solaris SA 1 & 2 - Training Material
The Solaris Operating Environment Software Groups
Figure 14-2
Solaris Operating Environment Software Groups
Core Core is a software group that contains the minimum software required to boot and run the Solaris Operating Environment on a system. It includes some networking software and the drivers required to run the Common Desktop Environment (CDE) or Open Windows desktop. It does not include the CDE or Open Windows software.
End User System Support The End User System Support is a software group that contains the Core software group plus the recommended software for an end user, including Open Windows or CDE and DeskSet software.
Note - Approximate disk space requirement for End User is 1.6 Gbytes.
Solaris Operating Environment System Administration I & II
Page 14 of 563
Solaris SA 1 & 2 - Training Material
Developer System Support The Developer System Support is a software group that contains the End User System Support software group plus the libraries, Include files, man pages, and programming, tools for developing software.
Note - Approximate disk space requirement for Developer is 1.9 Gbytes.
Entire Distribution The Entire Distribution is a. software group that contains the entire Solaris Operating Environment software release.
Note — approximate disk space requirement for Entire Distribution is 2.3 Gbytes.
Entire Distribution Plus OEM Support The Entire Distribution plus OEM Support is a software group that contains the entire Solaris Operating Environment software release, plus additional hardware support for Original Equipment Manufactures (OEMs). This software group is recommended when, installing the Solaris Operating Environment software on SPARC-based servers.
Note - Approximate disk space requirement for Entire Distribution plus OEM is 2.4 Gbytes.
Solaris Operating Environment System Administration I & II
Page 15 of 563
Solaris SA 1 & 2 - Training Material
Planning an Installation on a Standalone System The following installation procedures describe how to run Solaris Web Start to install the Solaris Operating Environment software on a networked, standalone system from a local CD-ROM drive.
You can run Solaris Web Start in either of two ways: •
Graphical User Interface (GUI) - This requires a local or remote CD-ROM drive or network connection, frame buffer, keyboard, and monitor.
•
Command Line Interface (CLI) - This requires a local or remote CD-ROM drive or network connection, keyboard, and monitor.
If Solaris Web Start detects a frame buffer for the system, it uses the GUI, if it does not it uses the CLI. The content and sequence of instructions in both are generally the same.
Note - You can select the Solaris Web Start's upgrade option during installation if the system is currently running Solaris Operating Environment software. However, if the system is currently running the Solaris 2.5.1 or Solaris 2.6 Operating Environments, you must run an Interactive Installation to perform a Solaris Operating Environment upgrade.
Solaris Operating Environment System Administration I & II
Page 16 of 563
Solaris SA 1 & 2 - Training Material
Pre-Installation Information Before installing the Solaris Operating Environment software on a networked standalone system, you must provide the following information: •
Host name - A unique, commonly short name for the system. You can use the command uname –n command to determine the host name on an existing system.
•
Host IP address - A software address representing the host address and network address.
•
Name service type - Determine if the networked system is to be included in one of the following types of name service domains: NIS, NIS+, other, or none.
•
Subnet mask - Determine if the networked system is to be included in a particular subnet. The subnets mask is stored in the /etc/netmask file.
Note - A subnet is used to partition network traffic. Segmenting network traffic over many different subnets increases bandwidth to each host. •
Geographic location and time zone - A specific region where the system physically resides.
•
Root password - A password assigned to root to gain access and root privileges on the system.
•
Language - Determine the language to be used to install the Solaris Operating Environment. Use the CD labeled: *
Solaris Installation English SPARC Platform Edition - All prompts, messages, and other installation information is displayed in English only.
Solaris Operating Environment System Administration I & II
Page 17 of 563
Solaris SA 1 & 2 - Training Material
*
Solaris Installation Multilingual SPARC Platform Edition - Select a language in which to display prompts, messages, and other installation information: • • • • • • • • • •
Simplified Chinese Traditional Chinese English French German Italian Japanese Korean Spanish Swedish
The last step in the pre-installation process is to make sure the following Solaris CD-ROM, set is available: •
Solaris Installation English SPARC Platform Edition or Solaris Installation Multilingual SPARC Platform Edition.
•
Solaris Software 1 of 2 SPARC Platform Editions and Solaris Software 2 of 2 SPARC Platform Editions.
•
Solaris Languages SPARC Platform Edition (if using the Multilingual CD).
Note - Before a software installation, always back up any modifications or data that exist in the previous version of the Solaris Operating Environment, and restore them after the installation is complete.
Solaris Operating Environment System Administration I & II
Page 18 of 563
Solaris SA 1 & 2 - Training Material
CHAPTER - 2
ADMINISTRATION OF SOFTWARE PACKAGES Objectives Upon completion, of this module, you should be able to: •
Describe a software package
•
View software package information, using the pkginfo command
•
Add a software package from the Solaris Software CD-ROM using the pkgadd. Command
•
Verify the attributes and content of a software package using the pkgchk command
•
Remove a software package installed on the disk using the pkgrm command
•
View, add, and remove software packages using the admintool
•
Add and remove a software package from a spool directory using the pkgadd and pkgrm
Solaris Operating Environment System Administration I & II
Page 19 of 563
Solaris SA 1 & 2 - Training Material
Software Packages Software administration involves adding and removing software from systems. Sun and its third-party vendors deliver products in a form called a software package. The term package to the method for distributing and installing software products to systems where the products, will be used. In its simplest form, a package is a collection of files and directories
Note - All the required software packages are installed automatically during the Solaris Software installation process.
Software packages contain: •
Files that describe the package and the amount of disk space required.
•
The actual software files to be installed on the system.
•
Scripts that are run when the package is added and removed.
The tools for viewing, adding and removing software from a workstation after the Solaris software is installed on a system include: •
Package administration commands - pkgadd, pkgrm, pkginfo, and pkgchk
•
The admintool utility - A graphical front-end to the pkgadd and pkgrm commands
Solaris Operating Environment System Administration I & II
Page 20 of 563
Solaris SA 1 & 2 - Training Material
The pkginfo Command You use the pkginfo command to display information about the software packages that have been installed on the local systems disk.
Command format
pkginfo [ -d [ device | pathname ] ] [ -1 ] pkg_name
For example:
# pkginfo | more <some output omitted> application SUNWAxg application SUNWaadm system SUNWab2m system SUNWab2r system SUNWab2s system SUNWab2u application SUNWabda application SUNWabe application SUNWabsdk
Solaris XGL 3 .3 Answer Book Solaris System Administrator Collection Solaris Documentation Server Lookup Solaris Documentation Server Solaris Documentation Server Solaris Documentation Server Sun ultra 5/10 Hardware AnswerBook Solaris User Collection Solaris Software Developer Collection
The columns of information that are displayed are described below.
CATEGORY
Is the package category, such as application, system, ALE, or CTL.
PKGINST
Is the software package name; if it begins with SUNW, it is a Sun Microsystems product; otherwise, it represents a third-party package.
NAME
Is a brief description of the software product.
Displaying Detailed Information for All Packages.
To view all the available information about the software packages, use the pkginfo command with the option: # pkginfo -l | more Solaris Operating Environment System Administration I & II
Page 21 of 563
Solaris SA 1 & 2 - Training Material
Displaying Detailed Information for a Specific Package To view information for a specific software package, specify us name on the command line, for example:
# pkginfo -1 SUNman PKGINST: NAME: CATEGORY: ARCH VERSION: BASEDIR: VENDOR: DESC: PSTAMP: INSTRELEASE: HOTLINE: STATUS FILES:
SUNWman On-line Manual Pages system sparc 41.0,REV=31 /usr Sun Microsystems, Inc. System Reference Manual Pages tinkertoymOS133331 May 19 2000 16:50 Please contact your local service provider completely Installed 6420 installed pathnames 3 shared pathnames 74 directories 73925 blocks used (approx)
The last line (73925 blocks used (approx), identifies the size of the package. A block is a 512-byte disk block. The blocks used number defines how much space is needed on the disk to install this package. To determine how many packages are currently installed on disk, use the following command: # pkginfo | wc -1
Displaying Information for Software Packages on CD-ROM By default, the pkginfo command is used to access information about packages that have been installed on disk.
Solaris Operating Environment System Administration I & II
Page 22 of 563
Solaris SA 1 & 2 - Training Material
Displaying Detailed Information for All Packages on CD-ROM To display information about software packages that resides on the Solaris Software CD-ROM (or other release media), use the pkginfo command with the -d option. This option defines the device on which the software packages reside.
# pkginfo -d /cdrom/ 0/s0/Solaris_x/Product | more
Displaying Detailed Information for Selected Package on CD-ROM # pkginfo -d /cdrom/cdrom0/s0/Solaris_10/Product -1 SUNWaudio PKGINST: SUNWaudio NAKE: Audio applications CATEGORY: system ARCH: spare VERSION: 3.6.20.REV=1.1999.12.03 BASEDIR: / VENDOR: Sun Microsystems, Inc. DESC: Audio binaries PSTAMP: dtbuild38sl9991204142646 INSTDATE: May 19 2000 16:35 HOTLINE: Please contact your local service provider. STATUS: spooled FILES: 5 spooled pathnames 2 directories 3 executables 4 package information files 681 blocks used (approx)
Solaris Operating Environment System Administration I & II
Page 23 of 563
Solaris SA 1 & 2 - Training Material
The pkgrm Command When a software package is removed from the system, the pkgrm command and deletes all files associated with that package unless those files are also shared with other packages. The command asks for confirmation to continue and might warn about possible package dependencies. If package dependencies do exist, it will again ask for confirmation to continue with the package removal process.
Command Format Pkgrm pkg__name For example: # pkgrm SUSWaudio The following package is currently installed: SUNWaudio
Audio applications (spare) 3.6.4,REV=1.98.12.03
Do you want to remove this package? y ## Removing installed package instance <SUNWaudio> ## Verifying package dependencies. WARNING: The <SUNWolrte> package depends on the package Currently being removed. WARNING: The <SUNWolaud> package depends on the package Currently being removed. WARNING: The <SUNWoldcv> package depends on the package Currently being removed. WARNING: The <SUNWxwkey> package depends on the package Currently being removed. Dependency checking failed. Do you want to continue with the removal of this package [y,n,?,q] y
Solaris Operating Environment System Administration I & II
Page 24 of 563
Solaris SA 1 & 2 - Training Material
Note - The message filename <shared pathname not removed> is displayed if a file is shared by two or more packages. It is removed only when the last package it is shared with removed
Solaris Operating Environment System Administration I & II
Page 25 of 563
Solaris SA 1 & 2 - Training Material
The pkgadd Command When a software package is added, the pkadd command uncompresses and copies files from the installation media to the local system’s disk. This command will ask for confirmation to continue with package add process.
Command Format Pkgadd [-d [device | pathname ] ] pkg_name For example: # pkgadd –d /cdrom/cdrom0/s0/solaris_10/Product SUNWaudio processing packages instance <SUNWaudio> from Audio applications (sparc) 3.6.4, REV=1. 98.12.03 copyright 1999 Sun Microsystems, INC. All rights reserved. Using as the package base director. ## processing package information. ## Processing system information. 2 package pathnames are already properly installed ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts, which will be executed with super-user permission during the process of installing these packages.
Do you want to continue with the installation of <SUNWaudio> [ y, n, ?] y
Installing Audio applications as <SUNWaudio>
## Installing part 1 of 1.
Solaris Operating Environment System Administration I & II
Page 26 of 563
Solaris SA 1 & 2 - Training Material
Installation of <SUNWaudio> was successful.
Solaris Operating Environment System Administration I & II
Page 27 of 563
Solaris SA 1 & 2 - Training Material
The pkgchk Command
The pkgchk command checks installation completeness pathname, file contents, and file attributes of a package.
Command Format
Pakgchk [ options ] [-p path …] [pkg_name]
The following example checks the contents and attributes of a software package currently installed on the system.
# pkgchk SUNWaudio
Note – If the pkgchk command does not display a message, it indicates that the package was installed successfully.
To list the file contained in a software package, type # pkgchk –v SUNWaudio To check any file to determine if its content and attributes have changed since it was installed with its software package, type: # pkgchk –p /etc/ passwd ERROR: /etc/passwd File size <414> expected <3391> actual File cksum <3439> expected <17254> actual The original /etc/passwd file has changed in size since the initial Solaris Operating Environment software installation. This is indicated by the Solaris Operating Environment System Administration I & II
Page 28 of 563
Solaris SA 1 & 2 - Training Material
differences in file size and checksum. The checksum is used to validate transported data.
Solaris Operating Environment System Administration I & II
Page 29 of 563
Solaris SA 1 & 2 - Training Material
The /var/sadm/Install/contents File The /var/sadm/install/contents file is a complete record of all the software packages installed on the local system disk. It references every file belonging to every software package, and the configuration of products installed can be viewed.
# more /var/sadm/install/contents The pkgadd command update the contents file whenever new packages are installed. The pkgrm command uses the contents file to determine where files for a software package are located on the system. Once a package is removed, pkgrm updates the contents file. This file can be queried to determine if a particular file has been installed on the system disk:
Solaris Operating Environment System Administration I & II
Page 30 of 563
Solaris SA 1 & 2 - Training Material
Identifying the Directory Location of a Command Use the grep command to search the /var/sadm/install/contents file to determine if a particular file was installed, and the directory where it is located. For or example, verify that the command showrev is installed on the system disk.
# grep showrev /var/sadm/install/contents /usr/bin/showrev f none 0755 root sys 30116 42078 943863705 SUNWadmc /usr/share/man/smanlm/showrev.lm f none 0444 bin bin 6398 62569 943312114 SUNWman Search the Solaris Operating Environment CD-ROM for Command Information
Use the grep command to search for the showrev command on the distribution media. Instead of searching the contents file on the system disk, in this example the information for the showrev command is contained in the pkgmap file. Every software package contained, on the distribution media has its own pkgmap, which contains a content list of each package. # grep showrev /cdrom/cdrom0/s0/Solaris_10/Product/*/pkgmap /cdrom/sol_10_sparc/s0/Solaris_10/Product/SUNWadmc/pkgmap:l f none usr/bin/showrev 0755 root sys 31276 44676 938676470
Solaris Operating Environment System Administration I & II
Page 31 of 563
Solaris SA 1 & 2 - Training Material
Using a Spool Directory For convenience, frequently installed software packages can be copied from the Solaris Software CD-ROM to a spool directory on the system. The pkgadd command, by default, looks in the /var/spool/pkg directory for any packages specified on the command line. Copying packages from the CD-ROM into spool directory is not the same as installing the packages on disk. To copy a package into the /var/spool/pkg directory: # pkgadd -d /cdrom/cdrom0/s0/Solaris 10/Product -s spool SUNWaudio Transferring <SUNWaudio> package instance The -s option with the keyword spool copies the package into the /var/spool/pkg directory by default.
Spooling Packages You can specify a different directory location using the -s option. In this example, a new directory is created, and then pkgadd is instructed to copy the package into the new spool directory.
# mkdir /export/pkgs # pkgadd -d /cdrom/cdrom0/s0/Solaris_10/Product -s /export/pkgs SUNWaudio Transferring <SUNWaudio> package instance # ls /export/pkgs SUNWaudio
Removing Packages from the Spool Directory You remove software packages from a spool directory using the pkgrm command with the -s option. # pkgrm -s spool SUNWaudio # pkgrm -s /export/pkgs SUNWaudio
Solaris Operating Environment System Administration I & II
Page 32 of 563
Solaris SA 1 & 2 - Training Material
Package Administration Summary The following section summarizes the tasks involved in package administration.
Package Command Summary Table 15-1 summarizes the commands used for package administration. Table 15-1 Package Administration Command Name
Description
Pkginfo
Lists packages installed on the system or available on distribution media. Installs packages, Removes packages. Verifies the attributes and contents of the path names belonging to packages.
pkgadd pkgrm pkgchk
Package Administration File and Directory Summary Table 15-2 describes a list of the files and directories used with package administration. Table 15-2 Files and Directories File or Directory
Description
/var/sadm/install/contents
Software package/map of the entire system.
/opt/pkgname
Preferred location for the installation of unbundled packages.
/opt/pkgname/bin or /opt/bin
Preferred location for the executable files of unbundled packages.
/var/opt/pkgname or /etc/opt/pkgname
Preferred location for log files of unbundled package.
Solaris Operating Environment System Administration I & II
Page 33 of 563
Solaris SA 1 & 2 - Training Material
MANAGING SOFTWARE PATCHES
Objective Upon completion of this module, you should be able to: •
List the locations to access patches
•
Explain how to access patches from the World Wide Web and anonymous ftp
•
Describe the different patch formats
•
Prepare a patch for installation
•
Install a patch using the patchadd command
•
Demonstrate how to verify what patches are currently installed
•
Remove a patch-using the patchrm command
Solaris Operating Environment System Administration I & II
Page 34 of 563
Solaris SA 1 & 2 - Training Material
Patch Administration The administration of patches involves installing or removing Solaris Operating environment patches from a running Solaris Operating Environment. A patch contains a collection of files and directories that replace existing files and directories that are preventing proper execution of the software. Some patches contain product enhancements. A patch is distributed as a directory that is identified by a unique number. The number assigned to a patch includes the patch base code first, a hyphen, and a number that represents the patch revision number. For example, a patch directory named 101945-02, indicates that 101945 is the base code, and 02 is the revision number.
Solaris Operating Environment System Administration I & II
Page 35 of 563
Solaris SA 1 & 2 - Training Material
Patch Distribution Sub customers have access to a general set of security patches and other recommended patches through the World Wide Web or anonymous ftp. Sun customers who have a Sun Services SM contract, have access to the Sunsolve database of patches and patch information, such as technical white papers, the Symptom and Resolution database, and more. These are available using the World Wide Web or anonymous ftp. A SunService customer can request to receive the Patch Update CD-ROMs, winch are released every six to eight weeks.
Solaris Operating Environment System Administration I & II
Page 36 of 563
Solaris SA 1 & 2 - Training Material
World Wide Web Patch Access To access patches on the World Wide Web site, the workstation has to be: •
Able to access the Internet
•
Capable of running Web browsing software, such as Netscape
To access patches using the World Wide Web, use the following URLs: http://sunsolve.sun.com http://sunsolve.sun,com.au http://sunsolve.sun.fr http://sunsolve.sun.de http://sunsolve.sun.co.jp http://sunsolve.sun.se http://sunsolve.sun.ch http://sunsolve.sun.co.uk
United States Australia France Germany Japan Sweden Switzerland United Kingdom
Or use the following URL, and navigate to the SunSolve patch database from the Support entry. http://www.sun.com From the Sun Microsystems home page, click on the Sales and Service button and navigate to the SunSolve patch database. The patch databases for publicly available patches are labeled "Public patch access." The patch database for the comprehensive set of patches and patch information available to contract customers is labeled "Contract customer patch access." The customer's assigned Sun Service password is required to access this database.
Solaris Operating Environment System Administration I & II
Page 37 of 563
Solaris SA 1 & 2 - Training Material
An Additional URL for patch Access The University of North (Carolina maintains a public patch site, as a cooperative venture between Sun Microsystems. Inc and the university. Publicly available patches can be accessed by using the URL: http://metalab.unc.edu/pub/sun-info/sun-patches/
Solaris Operating Environment System Administration I & II
Page 38 of 563
Solaris SA 1 & 2 - Training Material
Anonymous ftp Patch Access To access patches using anonymous ftp, the workstation must be: •
Able to access the Internet
•
Capable of running the ftp program
To access patches using ftp, use the ftp command to connect to: sunsolve.sun.com When ftp prompts for a login, enter anonymous as the login name. When prompted for the password, enter your complete email address
After the connection is complete, the publicly available patches are located in the /pub/patches directory.
An Additional ftp Site for Patch Access Publicly available patches can also be accessed by connecting to: http://metalab.unc.edu/pub/sun-info/sun-patches/ This site is also maintained by the University of North Carolina.
The ftp Patch Access Procedure The ftp utility has many commands; however, only a few are necessary for moving files from system to system. You can locate and copy patches to the local system with a few basic ftp commands. The following example shows the procedure for changing to the /tmp directory on the local system, connecting to the remote ftp site, locating a patch and its README file in the /pub/patches directory, and transferring (copying) both files to the local systems directory.
Note - To transfer patches, change the ftp transfer mode to binary, by typing bin at the ftp prompt.
Solaris Operating Environment System Administration I & II
Page 39 of 563
Solaris SA 1 & 2 - Training Material
For example: # cd /tmp # ftp sunsolve. sun.com Name (sunsolve.sun. com: root): anonymous 331 331 Welcome to the SunSolve Online FTP server. 331331-Public users .may log in as anonymous. 331331 Contract customers should use the following 2-tier login procedure: 331 331-At the first login prompt sunsolve 331 passwd: sunmicro 331331-At the second login prompt: <sunsolve login name> /<sunsolve passwd> 331 example: myssID/mypasswd 331 331 Public users may log in as anonymous; contract customers 331- Should use the standard sunsolve login and password, 331- Followed by their susolve account/password when prompted. 331331- Sunsolve6 FTP serve (Version wu-2.6.0(3) Wed Jan 5 15:02: 27 MST 2000) ready. 331- Guest login ok, send your complete e-mail address as password. Password:
