Solaris Admin

INTRODUCTION TO UNIX
Solaris System Administration
Primarly influenced by Multics First version of UNIX developed by Ken Thompson in 1969 on DEC PDP for business, scientific and industrial users Originally written in Assembly language for PDP-7 Transportability facilitated by Thompson in B Language B modified by Richie as C Language Thompson and others wrote Unix in C in 1980 to be able to port on any computer
FEATURES OF UNIX
Multitasking Multiuser On line help Communication and Electronic mail
FEATURES OF UNIX CONTINUES...

Available on micros, minis and mainframes Hierarchical file system Library of application software
SYSTEM CONCEPTS
UNIX
KERNEL
SHELL
Kernel Shell
APPLICATION SOFTWARE
Applications
KERNEL is the heart of the UNIX operating system. It is next to the hardware. It is responsible for scheluing tasks and managing data storage SHELL is the command interpreter. It is an interfacce between the user and the kernel. APPLICATION SOFTWARE are the specific capabilities added on to the operating system
SHELLS BOURNE prompt - ($) -> DEFAULT SHELL C prompt - (%) -> HAS SYNTAX SIMILAR TO C LANGUAGE KORN prompt - ($) -> BOURNE + ALIASING, HISTORY, ETC.
FILE SYSTEM STRUCTURE

(Hierarchical Inverted-Tree Structure)
/ (ROOT)
USR
OPT
DEV
ETC
EXPORT
KERNEL
VAR
lib
sbin
bin
dsk
tty
home
genunix
ssa1
ssa2
COMMON TERMS USED
HOST
HOST NAME IP ADDRESS SERVER CLIENT
NETWORK
DAEMON MULTITASKING MULTIUSER DISTIBUTED PROCESSING
10
SYSTEM RUN LEVELS

Objectives :
Change Run Levels
Shutdown & Booting Commands Reboot

Solaris System Administration 11
Changing Run Levels
Init Command e.g. init 6 will reboot the System to default run level
Boot Command
boot <devicename> -[options] devicenames cdrom

disk net Options -a for interactive boot -r to reconfigure system -s for booting to single user
Shutdown Command
shutdown [-y] [-g seconds] (-init state)[message]

yes Grace period(60 sec) Init levels (0,1,5,6) e.g. shutdown -y -g 0 -I 0 warning
will immediately shutdown the system to level 0
14
Other Boot/Reboot Commands
halt
poweroff
reboot
Not Recommended
15
OPEN BOOT PROM(OBP)
16
OPEN BOOT PROM
Resident firmware that provides basic hardware testing & initialization prior to booting. It is used for testing & initializing system hardware determines the configuration boots the operating system provides interactive debugging facilities
SYSTEM BOARD
Sbus
BOOT PROM
Custom Driver
ID - PROM
Third Party Sbus Card

BOOT PROM VERSIONS
1.x
(ORIGINAL SPARC BOOT PROM)
2.x
(FIRST OPEN BOOT PROM)
3.x
(OBP WITH DOWNLOADABLE FIRMWARE)
19
BASIC OBP COMMANDS
banner boot help printenv setenv set-defaults
devalias probe scsi probe - scsi - all probe - ide reset
20
CHANGING DEFAULT BOOT - DEVICE
ok
setenv boot - device = NET
ok
reset
ok
boot
CREATING CUSTOM DEVICE ALIASES
nvalias
nvunalias
22
EEPROM COMMAND
Lists eeprom settings
Changes need not be followed by reset
23
STOP KEY
stop - a key sequence
puts system into obp command mode. Use sync to synchronize file systems.
stop - n
starts/boots the system with default values.
24
SOLARIS INSTALLATION
25
SOFTWARE GROUPINGS
CONFIGURATION CLUSTERS SOFTWARE CLUSTERS PACKAGE CDE Demos CDE CDE developer s/w CDE DT BUILDER
CDE Man pages

O P T I O N S
ENTIRE DISTRIBUTION ENTIRE DEVELOPER END USER
CORE
DISTRIBUTION
PLUS OEM DRIVERS

27
HARDWARE REQUIREMENTS FOR SOLARIS 7 INSTALLATION

SPARC / INTEL SYSTEM
1.05 GB HDD SPACE 64 MB RAM CD-ROM DRIVE or INSTALL SERVER
SYSTEM INFORMATION
HOST NAME
IP ADDRESS
NAME SERVICE
SUBNET
GEOGRAPHIC LOCATION TIME ZONE INFORMATION ROOT PASSWORD
INSTALLATION TYPES
UPGRADE
Initial Precautions
Notify Users Backup Files Shutdown System
INITIAL
(Fresh Installation)
30
LOG OF INSTALLATION
/var/sadm/install_ data/install_log
31
SOLARIS BOOT PROCESS
32
BOOT PROCESS
PROM executes POST
BOOTS PROM Phase
Determines Boot device (eg. Disk,net,CD-ROM) Reads Boot Block ( Sector 1- 15) PROM loads Bootblk Program Bootblk loads (ufsboot) program
BOOT Program phase

Kernel Initialization phase
ufsboot loads 32-bit/64-bit kernel

Loads kernel Modes Reads \etc\system file Kernel initialized and starts init process
/sbin/init phase
Init process starts and run control scripts

KERNEL
consists of a two piece static core (unix & genunix) and loadable modules.
LOADABLE MODULES
is a device driver which is loaded when device is accessed.

KERNEL STRUCTURE
Resides in /platform/uname-m/kernel/unix
KERNEL misc drv
fs
exec genunix Sys
Sched
Strmod
/etc/system file
Can be customized to change kernel configuration process

moddir - modifies search path for kernel modules. rootdev - determines alternate root device. exclude - modules to be excluded even if referenced. forceload - modules loaded forcibly at boot time.
Overrides default value using
variable = value
eg. set -pt-cnt =100 set npty = 100 - sets pseudo-ttys to 100.
Take backup before editing .
SYSTEM RUN LEVELS & INITIALIZATION FILES
37
SYSTEM RUN LEVELS

0 1

PROM monitor Run level Single user mode
Used for performing Administrative tasks.
Multi-user mode (no resources shared).
3
4 5
Multi-user mode (resources shared).

Not used. Halt.
Reboot.
Single user mode with user logins disabled.
S,s
/etc/inittab
S3 : 3 : wait : |sbin|rc3 >/dev/console 2 < > |dev|console
id rstate action
Command to execute
39
init process and /etc/inittab

/etc/inittab
init process
Set initdefault to level 3.
Run entries with sysinit in Action field. Run entries with 3 in rstate field.
40
/etc/rc#.d
Contains scripts to start /stop
daemons/services.
Scripts starting with alphabet k. Scripts starting with alphabet s starts
process/services eg. S71 inetinit

/etc/init.d
Contain run control scripts HARD
LINKED to start/ kill scripts in

eg. Sendmail nfs.server etc Services can be started/stopped in running system eg. /etc/init.d/nfs.server
/etc/rc#.d
start
42
DISK CONFIGURATION & PARTITIONING
43
LOGICAL DISK DEVICE NAMES

/dev /[r] dsk /c n tn dn sn
The /dev directory The rdsk or dsk subdirectory Controller number Target number
Disk number
Slice number
VTOC - Volume Table Of Contents

Slice 2 Slice 0 Slice 1 VTOC (sector 0)
Disk Geometry - Describes the no. of heads , sectors and cylinders. Partition Tables - Describes the slices on the disk.
Volume Names - Identifies the disk device (optionally assigned by the system administrator.) Slice Tags - name the standard mount points for each of the slices. Slice Flags - Label whether each slice is writeable and mountable.
Displaying a Disks VTOC

# prtvtoc /dev/rdsk/c0t0d0s0
* /dev/rdsk/c0t0d0s0 partition map ** Dimensions * 5 12 bytes/sector * 80 sectors/track * 9 tracks/cylijnder * 720 sectors/cylinder * 2500 cylinders * 1151 accessible cylinders * * Flags : * 1: unmountable * 10: readonly * * First Sector Last * Partition Tag Flags Sector Count Sector * 0 2 00 0 41040 41039 * 1 3 01 41040 205200 246239 * 2 5 00 0 828720 828719 * 5 6 00 246240 20880 267119 * 6 4 00 267120 561560 828719
Mount Directory / /opt /usr

46
PARTITIONING DISK
partition> 0 Part 0 Tag root Flag wm Cylinders 0 - 41 Size Blocks 14.77mb(42/0/0)
Enter Partition id tag[root] : <cr> Enter Partition Permission Flags[wm] : <cr> Enter new starting cylinder[0] : <cr> Enter Partition size[30132b, 42c, 14.77mb] : 16mb
Disk Blocks Cylinders Mbytes
What Makes a Partition Into a File System

CPU Memory
Super Block Super Block Updated Every 30 seconds
Loaded into memory at boot time Boot Blocks (15 sectors)
Slice 6 Super Blocks (16 sectors)

Slice 1 Slice 0
Disk label (1 sector)

48
Creating a New File System

# newfs /dev/rdsk /c0t1d0s0
newfs : construct a new file system /dev/rdsk/c0t1d0s0: (y.n) ? Y

/dev/rdsk/c0t1s0d0 : 28188 sectors in 87 cylinders of 9 tracks, 36
sectors
15.5MB in 3 cyl groups (16 c/g, 5.90MB/g, 2688 i/g ) super-blocks backups (for fsck -F ufs -o b= #) at : 32, 11632, 23232,
BACKGROUND STRUCTURES
VTOC Boot block
Super block Backup Superblock Cylinder group block Inode table
Data block(s)
Created by the newfs command
Backup super block Cylinder group block Inode table
Data block(s)
Backup Superblock Cylinder group block Inode table
Super Block & Cylinder Group Block

Super Block Super Block clean flag. Number of cylinder groups Number of data blocks. Number of fragments in data block. Size of data block. Size of a fragment. Number of tracks in a cylinder. Number of sectors in a track. Number of sectors per cylinder. Number of cylinders in the partition.
Cylinder Group Block Number of cylinders. Number of data blocks. Position of the last used data block. Number of free data blocks and their locations. Position of the last used fragment. Number of free fragments.
File inodes
inode Data blocks Permissions Links and other Information Indirect blocks
0 1 2 3 4 5 6 7 8 9 10 11 12
2048 data blocks
Double indirect block 2048 addresses
2048 data blocks Indirect block 2048 addresses

13
FILE SYSTEMS STRUCTURE
53
FILE SYSTEM
Collection of files & directories used to store & organize information Collection of control structures & data blocks of a partition File Systems
ufs
hsfs
Disk -based
pcfs
NFS
psuedo
Network based Cachefs etc.

Label
1-15
16-31 32
Boot Block
Superblock
Backup superblock
First Cylinder Group 47 Cylinder group block
Inode table
Data Blocks Second Cylinder group
CYLINDER GROUPS
Cylinder Group Blocks

Inode tables Data blocks
56
Inodes
Direct Pointers
Indirect Pointers
single indirect double indirect triple indirect

The fsck utility
The fsck program is run when a system

boots
The fsck program runs in two modes :
Non-Interactive mode interactive mode

checked by the fsck utility
Superblock summary information

cylinder group block
inode information
file system data block information
directory information
fsck Output
The following is the fsck program when no inconsistencies were discovered: # fsck /dev/rdsk/c0t3d0s7 **last mounted on /export/home **Phase 1 - check blocks and sizes **Phase2 - check pathnames **Phase3 - check connectivity **Phase4 - check Reference counts **Phase5 - check Cyl groups 2 files,9 used, 21606 free
60
MONITORING FILE SYSTEM

df df-k
capacity/usage of file system
du
display disk usage
quota
disk usage by a user
du -a /usr (in blocks)
quot [-af] filesystem all filesystems and no. of files
61
MOUNTING FILESYSTEM
format command
creates a slice out of a disk.
newfs command
creates a file system out of a
raw slice.
ALTERNATIVE SUPERBLOCKS
If superblock is corrupted, run fsck to use a

backup superblock
Locate the backup superblock at offset 32 of

file system
Use newfs -N to locate backup superblocks

MOUNTING FILES
The process by which separate file systems

are attached to the file-system hierarchy
(file tree structure)

/etc/vfstab Manual mounting(from the command line)

EXAMPLE MOUNT COMMANDS
to mount a file system manually # mount /dev/dsk/c0t3d0s7 /export/home to enable UFS logging # mount -o logging /dev/dsk/c0t3s6 /usr to mount a file system with largefiles disabled #mount -o nolargefiles /dev/dsk/c0t3d0s7 /export/home to mount a file system using the content of the /etc/vfstab file #mount /export/home
/etc/vfstab file
The /etc/vfstab virtual file system table provides default entries for mounting file system at boot time. The format of the file is one record per line,seven fields per record with a dash(-) indicating a null value for a field. #device device mount fs fsck mount mount #to mount to fsck point type pass at boot ops
#dev/dsk/c1d0s2 /proc fd
/dev/rdsk/c1d0s2 -
/usr /proc
ufs proc
1 -
yes no no -
/dev/fd fd
swap
/tmp
/ /usr /export /opt -
tmpfs
ufs ufs ufs ufs -
1 1 5 8 swap
yes
no no yes
logging logging
/dev/dsk/c0t3d0s0 /dev/rdsk/c0t3d0s0 /dev/dsk/c0t3dos6 /dev/rdsk/c0t3d0s6 /dev/dsk/c0t3d0s3 /dev/rdsk/c0t3d0s3
/dev/dsk/c0t3d0s7
/dev/dsk/c0t3d0s5 /dev/dsk/c0t3d0s1 -
/dev/rdsk/c0t3d0s7
/dev/rdsk/c0t3d0s5 -
/export/home ufs 5
yes
yes -
logging
logging no
66
mountall commands
mountall -l
Mounts all local filesystems
mountall -r
Mounts all remote filesystems
67
umountall commands
umountall -l
Unmounts all local filesystems
umountall -r Unmounts all remote filesystems
68
MOUNTING DIFFERENT TYPES OF FILESYSTEMS
Create a mount point

#mkdir /pcfs
specify the file system tape # mount -F pcfs /dev/diskette /pcfs
#mount -F hsfs -o ro /dev/dsk/c0t6d0s0/cdrom

HOW FILE SYSTEM TYPE IS DETERMINED
/etc/vfstab file
/etc/default/fs and /etc/dfs/fstypes files
70
NFS CLIENT ACCESS

Using the dfshares and mount commands
determine NFS file system availability from a server #dfshares sun mount a remote resource # mount -f nfs -o ro sun:/usr/share/man /usr/share/man unmount a remote resource # umount /usr/share/man
71
BASIC UTILITIES (EDITORS)
72
ed (Line Editor)
vi (Visual Editor)
73
PACKAGE ADMINISTRATION
74
Objectives
Information of Installed Packages
Adding New Packages
Deleting Packages
Checking Consistencies
Spooling Packages
PACKAGE CONTENTS
Description Of Package
Description Of Relationships To Target System
e.g. Disk space required
Files To Be Installed Pre & Post Installation Scripts

PACKAGE ADMINISTRATION
COMMANDS
pkginfo
ADMINTOOL
pkgrm
pkgchk pkgadd
77
PKGINFO
Display Software Package Information Command Format pkginfo [-d [device | pathname]]
Device where S/W resides
[-l]
pkg_name
Name Of Package
Displays Detailed Information
78
EXAMPLE
a) pkginfo | more
Application SUNWAxg System
Category
Solaris XGL 3.3 AnswerBook

Solaris Documentation Server
Name of Package
SUNWab 2u
System Name
b) Checking S/W packages on CD

pkginfo -d /cdrom/cdrom0/s0/solaris_2.7/product |more
pkgrm
pkgrm <package_name>
warns about possible package dependencies a shared file is removed only when last of sharing package is removed
pkgadd
Adds packages Spooling Packages
pkgadd -d <device path name> package name
Stages in Package addition

Checks Package & System Information Verifies Package Requirements Verifies Disk Space Requirements Checks For Package Conflicts Starts the Installation
PACKAGE SPOOLING

Copying Package Without Installing it Package -d <device name> -s spool <package name> Default Spool Directory is /var/spool/pkg
e.g. pkgadd -d /cdrom/cdrom0/s0/solaris_2.7/product -s spool SUNWaudio OR pkgadd -d /cdrom/cdrom0/s0/solaris_2.7/product -s /export/spool_dir SUNWaudio

PKGCHK
Compares various attributes & contents of package
pkgchk [ -p [path1] [path2] ]
<package name>
e.g. pkgchk SUNWaudio
83
Important Files/Directories
/opt/pkgname - Preferred location for unbundled Packages /opt/pkgname/bin OR Preferred location for /opt/bin executables /var/opt/pkgname OR log files of packages /etc/opt/pkgname /var/sadm/install/contents - package map of entire system
PATCH ADMINISTRATION
85
OBJECTIVES
Obtain Patch Information

Verify Current Patches Installed Install Patches Remove Patches
86
PATCH NUMBERING
1011945-34
PATCH DISTRIBUTION
(revision number)
WWW

FTP Server
CDROM for SunService Customer
www.sunsolve.com www.sun.com metalab.unc.edu

87
PATCH FORMATS
zip Files (.z)

# Extracted using
zcat path.z | tar xvf
compressed tar
# Extracted using
tar xvf <patchfile>
gzip files
# Extracted using
gzip utility (www.gzip.org)
88
IMPORTANT
Never modify/edit contents of files in /var/sadm/patch /var/sadm/patch has historical information of patches installed on system.
89
PATCH VERIFICATION
showrev -p or patchadd -p
displays complete patch information like

incompatibles , packages etc.
PATCH REMOVAL
patchrm <patchnumber>
USER ADMINISTRATION
91
OBJECTIVES
Use admintool to create new groups & users

setup password aging/locking useradd/usermod/userdel commands
92
ADMINTOOL
GUI utility to maintain system databases for
users groups hosts printers serial ports software

useradd command

Creates new user account new login remains locked until password command is used Options:
-comment -d <dir> -e -f -g -u -s -o e.g -c trainee e.g -d /home/trainee e.g -e 10/6/99 e.g -f 10 e.g -g other e.g -u 100 e.g -s /bin/sh allows duplication of uid
usermod command
Modifies a existing user account e.g
usermod -g other -d /export/home/trainee -m -l guest trainee
group
New loginname New directory moves users directory to new location
95
userdel command
Deletes user account userdel [-r] login

removes users home directory
96
System initialization files for users
Initialization files
contains a series of commands that are executed when a shell is started Customize the environment for that shell
System (Read first) /etc/profile User (Read second/third) $HOME/.profile Template /etc/ skel Local.profile
Shell
Bourne
Korn
/etc/profile
/etc/profile
$HOME/.profile then $HOME/.login $HOME/ .cshrc then $HOME/.login

Local.profile
Local.profile
97
.dtprofile File

is used by CDE users resides in users home directory is created the first time a user logs in
98
/etc/profile Script
exports environment variables

exports PATH sets TERM displays /etc/motd sets default permissions checks for mail
/etc/skel directory
skel
Local .cshrc
Local .profile
.profile
Local .login
100
Rereading the initializing files

Bourne and korn shells $ cd $ . ./.profile $ . ./.kshrc C shell % source ~/.login % source ~/.cshrc
SYSTEM SECURITY
102
OBJECTIVES
Security Overview of files

Superuser Account
Effective user ids & group ids

Administrating File Ownerships Monitoring System Access
SECURITY IN SOLARIS
Password authentication
File access permissions
ACLs
SECURITY FILES
/etc/password
/etc/shadow
105
/etc/password

Contains entry for each system user Contains the following information: login ID username x placeholder for password UID number used by system to recognize the user GID number representing users primary group comment home directory
login shell
/etc/shadow
Contains encrypted password

login ID
password(Encrypted form)
lastchg - no. of days between last password change and 1 Jan 1970
min- minimum no of days between password change

max warn
inactive
expire
/etc/group
Defines all system groups a user belongs to fields :

groupname password GID userlist
108
SUPERUSER ACCOUNT
Performs administrative tasks
shutting down system backing up & restoring file systems mounting & unmounting file resources user management etc.
password aging should be enabled password should be changed frequently
id command
Identifies user id -a
displays uid ; name ; gids of groups.
110
su command

Used to change to other users A/C su - <username>
provides the environment of user
all su attempts are logged in /var/adm/sulog

Administrating File Ownership

chown (changes file ownership) chgrp (changes group name of file)
e.g. e.g. chown user1<files> chgrp grp1 file1 or chown -R dir1 or chown -R user:grp1 dir1
/etc/default directory
passwd
controls system-wide password aging variables: - MAXWEEKS
-MINWEEKS -PASSLENGTH
login
restricting super user access variables:
-PASSREQ -CONSOLE
su
logging su attempts
113
Monitoring System Access
who
who -u
finger
displays detailed user a/c information
last
login & logout information
sulog
/var/adm/sulog
114
PROCESS CONTROL
115
OBJECTIVES
ps command
kill command & options
pgrep & pkill

at / crontab commands
structure of crontab file & process scheduling

Process Status
ps Lists processes currently running on system
options
-e :- information of all processes -f :- full listing
-u :- processes of particular users
117
The kill command

Command format kill [-signal] PID(s) Signals
44 signals SIGTERM,signal 15,is default signal sent
Process termination # kill 1400

pgrep
displays process id of process matching pattern
pkill
kills the process matching pattern
Usage
pgrep [-options] pattern pkill [-options] pattern
Options
-u :- matching UID -f :- a regular expression -t :- matching the terminal -G :- matching GID number e.g pkill -U user1 mails
Process Manager
Tools( CDE option)

find process
proctool
120
at command
Executes a command or script at a specified time /etc/cron.d/at.deny:-identifies users who cannot use at command
USAGE:
at [-m] [-r job]

send mail to user on completion
time [date]
removes a previously scheduled jobs

Running commands at specified time
Displaying the crontab file :

crontab -l
using root crontab file

/etc/cron.d/logchecker
/usr/lib/newsyslog
controlling crontab access

/etc/cron.d/cron.allow /etc/cron.d/cron.deny
User access to CRON
By default the cron.deny file prohibits crontab use from the following system users:

daemon bin smtp nuucp listen nobody noaccess
The cron.allow file does not exist by default

The crontab file format

The crontab file consists of entries with six fields in each entry. The fields are separated by spaces or tabs. 10 3 * * 0 /usr/lib/newsyslog The command field
The day of week field,values 0-6 .0 is sunday
The month field,values 1-12 The hour field,values between 0-23

The day of month field,values 1-31 The minute field,values between 0 and 59
124
How to edit a users crontab file
Set the editor variable to specify the editor to use

Edit the crontab file using crontab -e View the current crontab file using crontab -l
125
ADVANCED FILE PERMISSIONS
126
FILE PERMISSIONS REVIEWED

The Octal Mode
Octal mode is based on the base eight numbering system(07 are the available numerals). Each permission has an octal value as follows:
Octal Values 4 Permissions Read
2
1
Write
Execute
The octal values for the permissions set are :

Octal Value 7 6 5 4 3 2 1 0 Permissions rwx rwr -x r --wx -w- -x - --
128
umask filter
Determine the default permissions for files and directories Assigns permissions during the creation of new files and directories Displays your umask $ umask 022 Enables users to set their own umask value
Changing the umask value

In the current shell $ umask 027 $ umask 027 PERMANENTLY CHANGING umask $ vi .profile # @(#)local.profile 1.4 93/09/15 SMI # stty istrip Path=.:/usr/bin:/usr/usb:/etc export PATH umask 027
ACCESS CONTROL LISTS(ACLS)
Provides greater control over file permissions

Provides traditional UNIX file protection and more
131
setfacl command
Syntax
setfacl [options] acl_entry filename1 [filename2...] Options -m Creates or modifies an ACL -s Replaces the entire ACL with new ACL -d Deletes ACL entries -r Recalculates ACL permissions acl_entry Is an ACL entry filename Is a file or directory which contains the ACL entries
EXAMPLES
Adding read/write permissions for ssa20

$ setfacl -m user:ssa20:6 ch3.doc
Checking if a file has an ACL

$ ls -l ch3.doc -rwxr-----+ 1 william sysadmin 163 Nov 11 11:12
Deleting an ACL entry

$ setfacl -d user:ssa20:6 ch3.doc
getfacl command
Used to verify that an ACL was set on the file
SYNTAX getfacl [options] filename1 [filename2] OPTIONS

-a
-d displays the file name,owner,group, and ACL entries for the specified file or directory displays the file name,owner,group and default ACL entries for the specified directory
setuid and setgid

These special permissions enable you to control the modification of files and create shared directories
executable programs directories setuid and setgid permissions
e.g.
$ ls -l /bin/passwd /etc/shadow -r-sr-sr-x 3 root sys 99640 sep 1 1998 /bin/passwd -r-------- 1 root sys 493 Apr 12 16:13 /etc/shadow
135
Using setuid and setgid permissions

Setting setuid and getuid permissions
numeric or symbolic notation
controlling modification of files e.g. #chmod 4755 setuid_program #chmod 2755 setgid_program creating shared directories #chmod g+s some-directory
The STICKY bit

Determining the characteristics of a directory with set sticky bit identifying sticky permission $ ls -ld /var/tmp drwxrwxrwxt 2 sys sys 512 may 26 11:02 /var/tmp setting the sticky permission # chmod 1777 project # ls -ld project drwxrwxrwxt 2 root other 512 nov 15 14:30 project #chmod a=rwxt project $ ls -ld project drwxrwxrwxt 2 root other 512 nov 15 4:30 project
DEVICE ADMINISTRATION
138
Logical device Name
Used by system administrator to reference devices These names are symbolically linked to their corresponding physical device name The logical names are located in the /dev directory and are created at the time when the physical names are created
System board SCSI host adapter c0 fas0
t1
t6
t0
scsi ctlr
scsi ctlr
scsi ctlr
DEVICE NAMING CONVENTIONS s0
d0 s5
d1 s0 s6
d2
s6
/dev/dsk/c0t0d0s0
/dev/dsk/c0t0d0s0
/dev/dsk/c0t0d0s1
s1
/dev/dsk/c0t0d0s5 /dev/dsk/c0t0d0s6 /dev/dsk/c0t0d0s6

140
/dev/[r]dsk/c# t# d# s#
Controller number
Target number
Logical unit number
Slice number
141
PHYSICAL DEVICE NAMES

Devices PCI pci fdthree se dad psuedo
ide sd
Devices directory structure

Device Instances
Kernels abbreviation for a device

dmesg displays instance names Instance disk is an abbreviation for the physical device name
e.g. /dev/sd0 represents an instance of a HDD.

BSD NAMES
located in the /dev directory

used for backward compatibility
# ls -l /dev/sd0a lrwxrwxrwx 1 root root 12 oct 20 16:05 /dev/sd0a
dsk/c0t3d0s0
144
dmesg command
Identifies the devices connected to the system

uses instance names and physical device names stores output in a buffer(get overwritten)
145
The /etc/path_to_inst file

The following is from the /etc/path_to_inst file on an ultra 1 system using one SCSI controller :
/sbus@1f,0 0 sbus /sbus@1f,0/espdma@e,84000 0 dma /sbus@1f,0/espdma@e,84000/esp@e,88000 0 esp /sbus@1f,0/espdma@e,84000/esp@e,88000/sd@3,0 3 sd /sbus@1f,0/espdma@e,84000/esp@e,88000/sd@2,0 2 sd /sbus@1f,0/espdma@e,84000/esp@e,88000/sd@1,0 1 sd /sbus@1f,0/espdma@e,84000/esp@e,88000/st@3,0 3 st /sbus@1f,0/espdma@e,84000/esp@e,88000/st@5,0 5 st /sbus@1f,0/espdma@e,84000/esp@e,88000/st@4,0 4 st /sbus@1f,0/espdma@e,84000/esp@e,88000/st@1,0 1 st ses /sbus@1f,0/espdma@e,84000/esp@e,88000/ses@0,0 0 ses
prtconf command
Displays systems configuration like memory & peripherals.
format command
Displays logical & physical device names.
147
RECONFIGURING DEVICES
To add new devices
1. Create a /reconfigure file.
2. Set the SCSI target number.

3. Connect the new disk to the system. 4. Turn on the power. 5. Boot the system.
SOLARIS NETWORKING
149
IP ADDRESSING
Class A
Class B
large networks
Class C
Small/Mid size Network
very large networks
(upto 16 million)
(upto 65000)
128-191
(upto 254)
192-223
1-127
150
NETWORKING FILES
/etc/inet/hosts or
/etc/nodename /etc/hostname.hme0
/etc/hosts
151
/etc/inet/hosts
Stores ip addresses for host names

linked to /etc/hosts network entry 127 is reserved for local host network number network entry with keyword loghost identifies IP address of host
/etc/hostname.hme0
identifies ethernet interface to be configured at boot up contains hostname or its ip address
/etc/nodename
contains system host name

REMOTE ACCESS
Files
Commands
rsh
rlogin
/etc/hosts.equiv $home/.rhosts
rcp
154
/etc/hosts.equiv

Identifies remote machines as trusted hosts does not exist by default
e.g. $ cat /etc/hosts.equiv

hostname1 userlist
hostname2 userlist
$HOME/. rhosts
Does not exist by default
e.g $ cat $HOME/.rhosts hostname1 -> all users of hostname1 hostname2 -> user1 of hostname2
rlogin
Logging in remotely
syntax :rlogin hostname [-l username]

Remote hostname
rsh
Running commands remotely
syntax :rsh [-l username] hostname <command> e.g. rsh -l ssa1 venus ls - al
/var/mail
158
rcp
Copying files across the network
rcp source-file hostname:destination file
159
NETWORK FILE SYSTEM & MOUNTING
160
THE NFS FILE SYSTEM
Some benefits of NFS file system are :
centralized files common software files appear to be local

NFS TERMINOLOGY
NFS SERVER -- An NFS file server designates local file resources to be shared with other systems on the network
NFS Client -- An NFS client machine mounts file resources that are shared over a network and treats the file systems if they were local
162
NFS server Daemons:

mountd,nfsd,statd and locked
NFS Client Daemons:

statd and lockd
Files:
/etc/dfs/dfstab /etc/dfs/sharetab /etc/rmtab
Files:
/etc/vfstab and /etc/mnttab
Commands:
share,unshare, shareall, unshareall, dfshares and dfmounts
Commands:
mount,umount, mountall, umountall, dfshares and dfmounts
163
NFS DAEMONS
mountd daemon
mountd : responds to a client mount request with a file handle nfsd : processes subsequent client file operation requests statd and lockd - provide crash and recovery functions
NFS server daemon
NFS daemons on the client and server
The /etc/dfstab file

The /etc/dfs/dfstab file is read when

the system enters run level 3 root executes the shareall command the /etc/init.d/nfs.server script runs
THE SHARE COMMAND
SYNTAX
OPTIONS
ro rw root = client ro = access - list rw = access - list
share [-F Fstype] [-o options] [-d description]pathname
unshare command
Command Format unshare [ -F nfs ] pathname

Options

-F nfs pathname
167
shareall and unshareall commands
Command format
shareall [-F nfs]
unshareall [-F nfs]
168
NFS File Server configuration
Edit the /etc/dfs/dfstab file. Start the server daemons verify the intended sharing
169
The dfshares command
Command format dfshares [-F nfs] [ host]
Examples
#dfshares
resource
venus:/usr/share/man
server
venus
access
-
transport
-
#dfshares mars
resource
mars:/export
server
mars
access
-
transport
170
The dfmounts command
Command format dfmounts [-F nfs]
Example
# dfmounts
Resource
-
Server
venus
Pathname
/usr/share/man
CLIENTS
earth,pluto
171
The mount command
Command format
Options
mount [ -F ][ -o options] server : pathname mount_point
-F nfs -o options server : pathname mount_point

#mount venus:/usr/share/man /usr/share/man
Entries in /etc/vfstab file
To mount remote file systems at boot

#device #to mount device mount to fsck point
-
FS fsck type pass

-
mount at boot
yes
mount options
soft.bg
venus:/usr/man
/usr/man nfs
173
The NFS Client Setup
Displays resources currently available from server

mounts the desired resources
setups automatic mounting of the resources

unmounts the resource when it is no longer needed
174
TROUBLESHOOTING NFS
Unknown host
rpcbind failure
server not responding

NFS client fails at reboot
stopped server error

BACKUP & RESTORATION
176
BACKUP PREPARATIONS
Preparing to back up file systems begins with planning and covers choosing :
A tape drive
Which file systems to back up

The type of backup (full or incremental)
A backup schedule
UFSDUMP
TO..
Do a full backup Do an incremental backup backup individual files Specify a cartidge tape
Argument 0 option 1-9 option

Specify a file or a directory
For Example
ufsdump 0ucf /dev/rmt/0 / ufsdump 9ucf /dev/rmt/0 / ufsdump ucf /dev/rmt/0/export/home/kryton ufsdump 9ucf /dev/rmt/0/export/home/
-c option
Backup local file system to a remote system tape drive
Remote system dump file
ufsdump oucf pluto : /dev/rmt/0 /export/home
178
FULL BACKUP of root( / )

The following example shows a full backup of root (/) file system to a QIC-150 tape(/dev/rmt/0)
# strudown -g30 -g
# ufsdump ucf /dev/rmt/0 Dump : Writing 63 Milobyte records Dump : Date of this level 0 dump : Tue Jun 09 10:13:44 1998 Dump : Date of last level 0 dump : the epoch Dump : Dumping /dev/rdsk/c0t3d0w0 (pluto:/) to /dev/rmt/0 Dump : Mapping (PANN I) [regular files] Dump : Mapping (PANN II) [directories] Dump : Estimated 73708 blocks (35.99 MB) Dump : Tape rewinding Dump : 73582 blocks(35.93 MB) on 1 volume at 100mb/sec Dump : Dump is done Dump : level 0 dump on Tue Jun 09 10:13:44 1998
tar & cpio

tar
It copies files and directorie subtresss to a single tape It is available on most UNIX operating systems Public domain versions are readily available It is not awrae of filesystems boundaries The full path name length can not exceed 255 characters It does not copy empty directories or special files such as device files
180
cpio
It copies special files or filesystems those require multiple tape volumes It packs data onto tape more efficiently than tar It skips over any bad sectors in atape while restoring It provides options for writing files with different header formats (tar, cdc, crc etc) for portability between different system tapes It creates multiple tape volumes
Copying All Files in Directory to a Tape (cpio)

The following example copies all the files in the directory /export/home/kryten to the tape in the tape drive 0. $ cd /export/home/kryten $ ls | cpio -oc > /dev/rmt/0 8 blocks $ cpio -civt < /dev/rmt/0 drwxr-xr-x 2 kryten users 0 Jun 9 15:56 1998, letters drwxr-xr-x 2 kryten users 0 Jun 9 15:56 1998, memos drwxr-xr-x 2 kryten users 0 Jun 9 15:56 1998, reports 8 blocks $
How to Retrieve All Files From a Tape (cpio)

1. Change to the directory where you want to put the files. 2. Insert the tape into the tape drive. 3. Copy all the files from the tape to the current directory using the cpio command. $ cpio -icvd < /dev/rmt/n Reads in the contents of the tape. specifies the cpio should read files in ASCII character -v Displays the files being retrieved in the format similar to the output from the ls command. -d Create directories as needed. < /dev/rmt/n Specifies the output file. 4. Verify the files copied by listing the contents of the current directory
-i -c
How to Copy Files to a Tape (tar)

1. Change to the directory that contains the files you want to copy. 2. Insert a write-enabled tape into the tape drive. 3. Copy the files to tape with the tar command. $ tar cvf /dev/rmt/n filename ... c Indicates you want to create an archive. v Displays the name of each file as it is archived. f/dev/rmt/n Indicates that the archive should be written to the specified device or file. filename ... Indicates the files and directories you want to copy. The file names you specify are copied to the tape, overwriting any existing files on the tape. 4. Remove the tape from the drive and write the names of the files on the tape label.
184
How to Retrieve Files From a Tape (tar)

1. Change to the directory where you want to put the files. 2. Insert the tape into the tape drive. 3. Retrieve files from the tape using the tar command. $ tar xvf /dev/rmt/n [filename ...] x Indicates that files should be extracted from the specified archive file. All of the files on the tape in the specified drive are copied to the current directory. v Displays the name of each file as it is archived. f /dev/rmt/n Indicates the tape device containing the archive. filename Specifies a file to retrieve. 4. Verify the files are copied by listing the contents of the current directory. $ ls -l
Retrieving Specified Files From the Tape(cpio)
The following example retrieves all the files with the suffix chapter from the tape in drive 0.
$ cd /home/smith/book $ cpio -icv *chapter < /dev/rmt/0 Boot.chapter Directory.chapter Install.chapter Intro.chapter 31 blocks $ ls-l
Media Storage Capacities

Media 1/2 inch reel tape 2.5-Gbyte 1/4 inch cartridge(QIC) tape DDS3 4-mm cartridge tape(DAT) 14-Gbytes 8-mm cartridge tape DLT 7000 1/2 inch cartridge tape Capacity 140 Mbytes (6250 bpi) 2.5Gbytes 12-24Gbytes 14 Gbytes 35-70 Gbytes
187
Device Naming
Berkeley(Sun OS 4.x) Compatibility
/dev/rmt/XAbn
Optional No-rewind n no-rewind omit for rewind Optional Density l low m medium h high u ultra c compressed
Drive 0 1 2 3 4 n
188
Displaying Tape Drive Status

$ mt -f /dev/rmt/0 status Archive QIC-150 tape drive: sense key (0x0) = No Additional Sense residual=0 retries=0 file no =0 block no=0 $ mt -f /dev/rmt/1 status Exabyte EXB-8200 8mm tape drive: sense key(0x0) = No Additional Sense residual=0 retries=0 file no =0 block no=0
Rewinding a Magnetic Tape Cartridge

$ mt -f /dev/rmt/1 rewind
NETWORK TROULESHOOTING
190
COMMANDS
snoop netstat ifconfig ping traceroute
191
netstat

Shows network status Syntax

netstat [-i][-p][-r] -I interface -P protocol Options

-i -p -r -I -P shows state of the interface. shows ARP tables Routing tables or static routes shows states of a particular interface statistics of a particular protocol
192
snoop
Used for capturing & inspecting network packets. Can only be run by supervisor. Displays contents of highest level protocol e.g. Examine Broadcast packets # snoop broadcast Using device -d (promiscous mode) mach 1 -- 128.50.255.255 RUSERS C mach 5 -- 128.50.255.255 RUSERS C -v verbose can be used for detailed information
ifconfig

Configure IP address to a network interface. Display status.
# ifconfig -a
Syntax :
ifconfig<interface_name><ipaddress> up/down
194
ping

Used to check network connectivity Uses Icmp Syntax : ping [-s] -I[internal] host -s -- continuously sends data packets.
195
traceroute
Prints the route taken by ICMP packets to reach a network host from another
Used to check fault on a network Syntax : #traceroute <ip address of the destination host)
LP PRINT SERVICES
197
PRINT SERVICE ARCHITECTURE
Client-server model
Print server Print client
Printing System

Print service software Sunsoft Print client software Print filters Hardware
SOLARIS 7 PRINT SOFTWARE

Print protocol adaptor SunSoft Print Client
Network printer support

LP administration and print commands
199
LP PRINT SERVICE DIRECTORIES

Directory
/usr/bin /etc/lp /usr/share/lib /usr/sbin
/usr/lib/lp
Contents
The LP print service user commands. LP server configuration files. The terminfo database directory. The LP print service administration commands. LP daemons, directories for binary files, and PostScriptfilters. LP daemon logs Spooling directory for pending requests.
/var/lp/logs /var/spool/lp
PRINT FUNCTIONS

Queuing Tracking
Fault notification
Initialization
Filtering
PRINTER TYPES AND INTERFACE PROGRAMS

Matching print requests to printers Determining printer types Checking for defined printer types # ls /user/share/lib/terminfo/e
ep2500+high ep2500+low ep40 ep400 ep4080 ergo4000 epson2500 epson2500-80 epson2500-hi epson2500-hi80
Using interface programs

PRINTING ENVIRONMENT

Local Printer Remote Printer
203
FINDING THE PRINTER
Determining the printer name
The command-line interface

The users PRINTER or LPDEST
environmental variables for a default printer
_default in $%HOME/.printer _default in /etc/printer.conf _default in a network name services database

LOCAL PRINT MODEL

lp/lpr
Lpsched schedules print request
lpsched
Selects printer /var/spool/lp/requests/system /var/spool/lp/tmp/system
Filter request
Interface Program
DOCUMENT
PRINTER
REMOTE PRINTING
inetd
In.lpd
lpsched
To printer
Spool area
206
CONFIGURING PRINT SERVICES
Setting up the printer

Setting up the print server Setting up the print client
PRINT SERVER REQUIREMENTS
Minimum of 20-25 Mbytes in spooling directory.
At least 32 Mbytes of RAM. Enough swap space to augment RAM and support print services.
208
lp command
Command Name lp lpstat cancel lpadmin accept reject lpmove enable disable Description Sends file to a printer Displays print service status Cancels print requests Performs various administration tasks Enables queuing of print requests Prevents queuing of further print requests Moves print requests Enables printer to print requests Disables printer from printing requests
lpstat command
Used to display a users print queue Syntax :
lpstat [-options]
-a -d -o -p Reports whether print destinations are accepting requests. Displays the name of the default printer. Displays the status of all output requests on printers. Displays the idle or busy status and availability of all printers. Determines what printers are configured for the system on which you are working. Displays all status information, the combined output of all other options, plus the list of queued print requests.
-s -t
PRINTER ADMINISTRATION COMMANDS
Designating a default destination
# lpadmin -d sparky
# lpstat -d system default destination: sparky
Setting a user default printer variable (Bourne shell)

$ LPDEST=spock; export LPDEST Setting a user default printer variable (C Shell)
venus % setenv LPDEST spock
211
TROBLESHOOTING A PRINTER
Check the status of the queues.
$ lpstat -o
Stop and restart daemons.
# /etc/init.d/lp stop
# /etc/init.d/lp start
Print services started.

JUMPSTART INSTALLATIONS
213
NETWORK INSTALLATION
Servers Required
Install Server
Boot Server
Name Server
214
INSTALL SERVER
Creating Install Server
Sun System with CD ROM as install Server

Mount CD ROM Drive
Run setup_install_server
eg ./setup_install_server /export/install
215
BOOT SERVER
Creating Boot Server

Sun System with CD ROM as Boot Server

Mount CD ROM Drive Run setup_install_server -b eg ./setup_install_server -b /export/install
Boot server is only required if the install server is on another subnet

ADDING CLIENTS
add_install_client
-c server:jumpstart_dir_path
-s install_server:install_dir_path -e ethernet address -p server:sysidcfg_path host_name
platform_group
217
TASKS

Create Jump start directory on the server
Enable all clients to access that directory

Creating Profiles
Creating a rules file

Using check to validate the rules file
218
Creating a jumpstart directory
Create Jump start directory on the server
eg mkdir /jmpstart
Share this directory
eg add share -F nfs -o ro,anon=0 /jmpstart in

/etc/dfs/dfstab file followed by unshareall and shareall
219
Creating a jumpstart directory
Copy the contents of auto_install_sample
directory from Solaris CD into the jumpstart

directory
eg cp -r auto_install_sample/* /jmpstart
220
Accessing jumpstart directory

Two ways of making client access the jumpstart directory
Using -c option of add_install_client command

everytime system is added for network installation
Editing the bootparams file and updating the name service if required
eg * install_config=server:jumpstart_dir_path
221
What is a profile?
Profile is a text file used as a template by the
custom jump start installation software
It defines how to install solaris software on a system
It consists of one or more profile keywords and their values
222
Requirements for profiles

The install_type profile keyword is required
Only one profile keyword can be on a line
223
Creating profile
Create a new file or edit one of the sample
profiles in the jumpstart directory
Profile keywords and their values are case sensitive
profile should be owned by root and have permissions equal to 644
224
Profile Examples
# Profile keywords profile values install_type system_type partitioning filesys cluster package initial_install standalone default any 60 swap SUNWCall SUNWman delete
Rules file
Rules file is a text file used to create the
rules.ok file
Rules file is a look-up table consisting of one or more rules that define matches between system attributes and profiles
226
Creating Rules file
Create a new file with name rules or edit the
existing rules file in jumpstart directory
Add a rule in the rules file for each group of systems that need to be installed
The rules file must have at least one rule Rule must have at least a rule keyword, a rule value, and a corresponding profile
Syntax
[!] rule_keyword rule_value [&& [!] rule_keyword rule_value] begin profile finish
! Symbol used to indicate negation
[] indicates an optional expression or field

rule_keyword - predefined keyword that
describes a general system attribute such as

host name or memory size
Syntax(Contd.)
Rule_value- Value that provides the specific system attribute for the corresponding rule keyword
&& Symbol used to logically AND
begin - name of an optional bourne shell script

that can be executed before the installation
begins. If no begin script exists, enter a minus

sign(-) in this field
Syntax(Contd.)
Profile- Name of text file used as a template that defines how to install solaris on a system
finish- Name of an optional bourne shell script that can be executed after the installation
completes
230
Rule Example
Rule keyword and value begin script profile finish script
hostname noida-1
prof1
memsize 16-32 &&

arch sparc any
prof2
genprof
231
Rules file

Rules file must have file name rules Rules.ok file is a generated version of the rules file and is required by the jumpstart installation software to match system to a profile
rule_value, begin and finish fields must have a

valid entry or a minus sign
232
Important rule keyword

Hostname karch memsize network
233
Check file
Check script is used to validate the rule and profile file. It does the following
Checks the rule file for syntax check the profile file for syntax If no errors are found, check creates the rule.ok file
./check -r file_name
Check file
Check script is used to validate the rule and profile file. It does the following
Checks the rule file for syntax check the profile file for syntax If no errors are found, check creates the rule.ok file
./check -r file_name
NIS+
236
What is NIS+?
Network name service that stores information such as workstation addresses, security information, mail information, ethernet interface information at a central location
where all workstations on a network can access

it
It uses client server model to store and

access information
What is NIS+?

Each domain is supported by a set of servers Prinicipal server is called the master server Backup server is called replica server Network information is stored in 16 standard NIS+ tables
Changes made to the NIS+ data on the master server are automatically propagated to the replicas
Name Service Switch
It controls how the client obtains network information
Switch is called nsswitch.conf and is stored in the /etc directory
239
Nsswitch.conf file
This file identifies a particular type of network information, such as host, password and group, followed by one or more sources, such as NIS+ tabkes, dns or local /etc
This file is loaded in every workstations

/etc directory along with three template
versions viz nsswitch.nisplus, nsswitch.nis

and nsswitch.files
NIS+ Scripts
Three NIS+ scripts are required to set up a NIS+ namespace
nisserver nispopulate nisclient
241
Configuring NIS+
242
Setting up Root Servers

Defaults used in root server Security level 2(DES) System information files(/etc) as the source of name service information
admin.domainname is the default NIS+ group
243
Setting up Root Servers(Contd.)
Set the superusers PATH variable to include /usr/lib/nis
If using DES authentication, specify the diffiehellman key length eg nisauthconf dh640-0 des
Run nisserver to configure a root master server
nisserver -r -d nis_domainname
244
Populating NIS+ tables

Check for no spurious entries in /etc files Remove all dots and underscores in host names Better make copies of /etc files and populate only the information you want to populate
Domain must have been configured and its

master server must be running
Run nispopulate -F -p /nis+files -d

domain_name
Setting up NIS+ Client
Domain must have been configured and master server must be running
Master server of the domains tables must be

populated
Log in as super user on the machine that is

going to become NIS client
246
Setting up NIS+ Client(Contd.)
Specify the Diffie-Hellman key length On the master server type nisauthconf. Use the output of this as an argument to nisauthconf on the client
Run nisclient on the client machine

nisclient -i -d domain_name -h root_server
247
Initializing NIS+ Client Users
The domain must have been configured and its master server must be running
The master server of the domains table must be

populated
Log in as a user on the client machine

If using DES authentication, the client machine
must use the same Diddie-Hellman key

configuration
Initializing NIS+ Client Users
Run the following command on the client machine
nisclient -u
249
NIS+ Servers
Client machines can be changed into NIS+ servers of the following types
Root Replicas- to contain copies of the NIS+

tables that reside on the root master server
To be master servers of subdomains of the root

domain
To be replicas of master servers of subdomains

of the root domain
NIS+ Servers
Run the following command on the client machine
rpc.nisd
251
Root Replica
The domain must have been configured and its master server must be running
The tables of master server must be populated

rpc.nisd must be started on the replica server
Log in as root on the root master server
252
Root Replica
Run the following command on the root master server
nisserver -R -d domain_name -h client_name
253
Creating Subdomain
The parent domain must have already been configured and its master server must be
running
The parents domains tables must be populated
New client machine must have been initialized

rpc.nisd must be running on the client
Log in as root on the parent master server

Creating Subdomain
Run the following command on the master server
nisserver -M -d new_domain -h client_name

where client_name is the name of the client
machine that will become the root domain
255
Populating Subdomains tables
Run the following command on the new subdomain server
nispopulate -F -p /nis+files -d new_domain
256

Solaris Admin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solaris Admin

Uploaded by

Copyright:

Available Formats

INTRODUCTION TO UNIX

Solaris System Administration

Solaris System Administration

Solaris System Administration

FEATURES OF UNIX CONTINUES...

Solaris System Administration

Solaris System Administration

Solaris System Administration

Solaris System Administration

Solaris System Administration

FILE SYSTEM STRUCTURE

Solaris System Administration

COMMON TERMS USED

Solaris System Administration

SYSTEM RUN LEVELS

Shutdown & Booting Commands Reboot

Changing Run Levels

boot <devicename> -[options] devicenames cdrom

shutdown [-y] [-g seconds] (-init state)[message]

will immediately shutdown the system to level 0

Solaris System Administration

Other Boot/Reboot Commands

Solaris System Administration

OPEN BOOT PROM(OBP)

Solaris System Administration

OPEN BOOT PROM

Third Party Sbus Card

BOOT PROM VERSIONS

Solaris System Administration

BASIC OBP COMMANDS

banner boot help printenv setenv set-defaults

devalias probe scsi probe - scsi - all probe - ide reset

Solaris System Administration

CHANGING DEFAULT BOOT - DEVICE

setenv boot - device = NET

CREATING CUSTOM DEVICE ALIASES

Solaris System Administration

Lists eeprom settings

Changes need not be followed by reset

Solaris System Administration

Solaris System Administration

Solaris System Administration

CDE Man pages

ENTIRE DISTRIBUTION ENTIRE DEVELOPER END USER

PLUS OEM DRIVERS

HARDWARE REQUIREMENTS FOR SOLARIS 7 INSTALLATION

Solaris System Administration

Solaris System Administration

SOLARIS BOOT PROCESS

Solaris System Administration

BOOTS PROM Phase

BOOT Program phase

ufsboot loads 32-bit/64-bit kernel

Init process starts and run control scripts

is a device driver which is loaded when device is accessed.

Overrides default value using

SYSTEM RUN LEVELS & INITIALIZATION FILES

Solaris System Administration

SYSTEM RUN LEVELS

PROM monitor Run level Single user mode

Used for performing Administrative tasks.

Multi-user mode (no resources shared).

Multi-user mode (resources shared).

Solaris System Administration