INSTALLING
SHELLS
Bourne C Korn
Aliases No Yes Yes
Command line editing No Yes Yes
History capability/editing No Yes/Yes Yes/No
History execution No !n r n
Prompt* $ hostname% $
Repeat last command No !!
Initialization file:
- login .profile .login .profile
- shell startup No .cshrc user defined
Interactive: SUNInstall à does not support copackaged software install, can use to upgrade
Web Start à supports copackaged software, cannot use to upgrade
Automatic: JumpStart à cannot use to upgrade
Custom JumpStart à can use to upgrade
Preconfiguring System Configuration: 1. Name Service Method – NIS or NIS+ has system config info
2. Sysidcfg method – sysidcfg file contains config info
Network Installation: 1. Install server – has contents of Solaris 7 CD
2. Boot server – for installs on clients on different subnet than install server
pkgadd [arg] package_name install a software package, default spool directory = /var/spool/pkg
-d path identifies spool directory other than the default -s path spools package into a spool directory
Examples:
pkgadd –d /cdrom/cdrom0 SUNWast installs package SUNWast from cdrom
pkgadd –s /tmp –d /cdrom/cdrom0 SUNWast spools SUNWast to /tmp from cdrom
pkgadd –s spool –d /cdrom/cdrom0 SUNWast spools to default spool directory from cdrom
pkginfo [package_name] provides information on installed packages
-l package_name view info on a particular package
Examples:
pkginfo displays a list of installed packages
pkginfo SUNWast views info on SUNWast package
pkginfo –l SUNWast also views info on SUNWast package
pkgrm package_name removes named packages, more than one can be listed
admintool GUI that can add, remove and obtain information on installed packages
Identified by an 8-digit number, the first 6 digits identify the base patch and the last two are the revision.
Because patches have no default spool directory, the full pathname of the patch must be provided.
patchadd [args] patch_full_pathname installs patch, default backup directory is /var/sadm/pkg
-d files are not backed up and patch cannot be removed
-M directory install multiple patches from this directory
-R client_root_image appply patch to diskless client
-S OS_service apply patch to ooperating system service
-C install_server_image apply patch to install server configuration
-p lists installed patches (can include witth –R, -S or –C to show those)
-B directory changes the default bacckup directory from /var/sadm/pkg
Examples:
patchadd /var/spool/patch/107588-01 installs patch
patchadd –d /var/spool/patch/107588-01 installs but makes no backup, cannot remove patch
patchadd –R /export/root/client /var/spool/patch/107588-01 patch to diskless client’s root image
patchadd –S Solaris_7x86 /var/spool/patch/107588-01 applies to x86 Solaris 7 image named Solaris_7x86
patchadd –M /var/spool/patch 106542-05 106794-01 applies multiple patches from specified directory
patchadd –B /var/spool/backup /var/spool/patch/107588-01 uses different backup directory for install
FAILURE: patchadd fails if any of the following occur:
- A package being patched is not installed or only partially installed.
- The patch requires another patch that is not installed.
- The patch is not compatible with another patch already installed.
- The current version or a higher version of the patch is already installed.
- The architecture of the patch and the system do not match
pkgparam package_name PATCHLIST Displays patches applied to a particular package.
patchrm [args] patch_name Removes patch, returns system to the state it was before patch was installed
-B directory identifies backupp directory if different from default
-R client_root_image removes patch from diskless client
-S OS_service removes patch from operating system service
-C install_server_image removes patch from install server configuration
Examples:
patchrm 106961-01 removes patch
patchrm –R /export/root/client5 106961-01 removes patch from bootable root image of diskless client
patchrm –B /var/spool/backup 107588-01 removes patch, identifies backup directory other than default
FAILURE: patchrm fails if any of the following occur:
- The patch is required by another patch.
- The patch is obsoleted by a later patch.
- The patch was installed using patchadd –d which makes no backup.