![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Home | SCJP | SCWCD | SCEA | SCSA | |||||||||||||||||||
Installation | |||||||||||||||||||
Describe the sequence of steps required to perform the Solaris 8 O.Env sw installation on a networked standalone system To install Solaris 8 onto a system the computer requeries a SPARC or Intel based system with 64 MB of RAM, 2.3 GB of HD space and access to a CD-ROM device. The Solaris 8 O.S comes on 2 CD-ROM disks. They are serveral default clusters that can be installed initially. Core - the base insall, containing drivers - SUNWCreq - 718 Mb End User - Core + OpenWindowns and CDE - SUNWCuser - 1.2 GB Developer - End User + Compiler tools and man pages - SUNCprog - 1.5 GB Entire Distribution - All of Solaris 8 - SUNWCall - 1.9 GB Entire Distribution plus OEM packages - SUNWCXall -2.1GB There are 2 different install methods for at standalone system: 1. Cmd Line (CLI) - Which defaults if there is no framebuffer installed 2. Graphical(GUI) - requeires a framebuffer and is a little slower An admin should have several pieces of info ready before performing an install: 1. HostName 2. IP Address 3. Name Service 4. Subnet Mask 5. Geographic Region 6. Root Password. 7. Lang. Support. An idea for a partitioning scheme for the disk: the default systems use: Root - Slice 0 Swap - Slice 1 /export/home - Slice 7 A good sample installation for a 4GB disk might look like: / 0 300MB /swap 1 2XRAM / 2 OVERLAY /var 3 500 MB /opt 4 500 MB /home 5 500 MB /usr 6 1400MB /export 7 300MB |
|||||||||||||||||||
Identify the fn of the following package admin cmds: 1. pkgadd 2. pkginfo 3. pkgchk and 4. pkgrm |
|||||||||||||||||||
Use the pkgrm cmd to remove an installed pkg. # pkgrm package_name Ex: #pkgrm SUNWaudio |
|||||||||||||||||||
The pkgadd cmd is used to install a pkg from an installation src. #pkgadd [-d [device | pathname ]] package_name Ex: #pkgadd -d /cdrom/cdrom0/s0/Solaris_8/Product SUNWaudio |
|||||||||||||||||||
The pkginfo cmd is used to check the installed packages on the system. #pkginfo [-d [device | pathname ] ] [-l ] package_name Ex:#pkginfo -d /cdrom/cdrom0/S0/Solaris_8/product #pkginfo -l SUNWman Shows useful info about the pkg. Use pkginfo | wc -l to determing how many pkgs are installed on the system. |
|||||||||||||||||||
![]() |
|||||||||||||||||||
The pkgchk cmd is used to check completeness of the installed pkg #pkgchk [options ] [ -p path ] [package_name ] Ex:#pkgchk SUNWaudio Note: pkgchk does NOT display any output if the pkg is OK Ex:#pkgchk -p /etc/shadow will check compare the shadow file to a checksum calc during initial install to tell the admin if the pkg (or file) has changed at all. |
|||||||||||||||||||
Identify the steps required to install a patch, verify which patches are currently installed, and remove a patch using the 1. patchadd 2. patchrm, and 3. showrev cmds On a Solaris 8 system, use the patchadd -p cmd to view installed patches. A legacy cmd, showrev -p will also display the same info. Intall a Patch 1.Copy the appropriate patch sw to /tmp. 2. Exec the cmd patchadd <patchname>. 3. Check the log file in /var/sadm/patch/<patchname>/log for details of the installation. Remove a Patch 1.Use the cmd patchrm <patchname> to remove an installed patch from the system. 2. All files modified by the patch are removed unless: - The patch was installed using patchadd -d - The patch was rendered obsolete by a later patch - The patch is required by another patch In Solaris 8 pkginfo, pkgadd and pkgrm are now part of the admintool utility. |