Académique Documents
Professionnel Documents
Culture Documents
Minimal Requirements
SPARC
1. Memory to install/upgrade 256MB recommended
2. Swap Area 512MB Default Size
3. Processor Speed 200MHz or Faster
INTEL
1. Memory to install/upgrade 256MB recommended
2. Swap Area 512MB Default Size
3. Processor Speed 120MHz or Faster
BACK
1
1 3
SOLARIS INSTALLATION
CD Disk Net
Solaris Interactive
Custom
File System Source Custom Jump Start
Installation
Default Layout
Type Flash
Device Configuration of
Solaris X86
Software
Selection Installation
Key board Display Mouse
Entire Distribution + OEM
2
SOLARIS 10 INSTALLATION
3. Standard Upgrade
A standard upgrade merges the new version of the Solaris OE with the existing files
on the system’s disk. The methods available for a standard upgrade are Solaris sun
install program, custom JumpStart procedure.
Software packages
Software clusters
Software groups
Software Packages
A software package contains a group of software files and directories. The
package also contains the related software installation scripts.
Software Clusters
During the software installation process, software clusters group logical
collections of software packages together.
Ex:- CDE
BACK
4
1 3
SOLARIS 10 INSTALLATION
Reduced Network:- This group Consists of minimal O/S to run and utilize
the network interfaces but cannot start the interface.
Core:- The Core software group contains the minimum software required to
boot and run the Solaris OE in a minimum configuration, without the support
to run many server applications.
End User System Support:- The End User System Support software group
contains the Core software group and also contains the recommended
software for an end user plus
the CDE.
BACK
5
1 3
SOLARIS 10 INSTALLATION
BACK
6
1 3
END OF CONCEPT
SOALRIS 10 - INSTALLATION
BACK
7
1 3
SOLARIS 10
MANAGING FILE SYSTEMS
BACK
8
1 4
MANAGING FILE SYSTEM
Shared
BACK
9
1 4
MANAGING FILE SYSTEM
Create
Add new hard Select the
respective Login as root # format
disk. boot -r new drive.
device files.
Partition
option.
Maximum
File System
7 slices
Slice Raw device Starting
Create Slice
Cylinder
Swap Specify
size
Save changes
by using “label”
command.
Inode table (7%) Reserved space (10%)
100mb
format>verify
partition> quit
format> quit
BACK
10
1 4
MANAGING FILE SYSTEM
PROCFS
NFS
UFS PCFS UDFS TMPFS
Or
HSFS CTFS
LOFS
FDFS
MNTFS
BACK
11
1 4
MANAGING FILE SYSTEM
/etc/vfstab
Device Mount
Device Mount FS fsck Mount
to at
to fsck. point. type. pass options.
mount. boot
df du
Commands
Maintenance Mount
File System
# fsck # mount /dev/dsk/c0d0s6 /junk
BACK
12
1 4
MANAGING FILE SYSTEM
1. UFS:- The UNIX file system in the Solaris OE is based on the Berkeley fast file
system.
2. HSFS – The High Sierra file system is a special-purpose file system developed
for use on CD-ROM media.
3. PCFS – The PC file system is a UNIX implementation of the disk operating
system (DOS) file allocation table (FAT32) file system. The pcfs file system
allows the Solaris OE to access PC-DOS formatted file systems.
4. UDFS – The Universal Disk Format file system is used for optical storage
targeted at DVD and CD-ROM media.
1. NFS – The network file system allows users to share files among many types
of systems on the network.
1. TMPFS – The temporary file system stores files in memory, which avoids the
overhead of writing to a disk-based file system.
2. SWAPFS – The swap file system is used by the kernel to manage swap space
BACK
on disks. 13
1 4
MANAGING FILE SYSTEM
3. PROCFS – The process file system contains a list of active processes in the /proc
directory.
4. MNTFS – The mount file system provides read-only information from the kernel about
locally mounted file systems.
5. FDFS – The file descriptor file system provides explicit names for opening files by using
file descriptors (for example, /dev/fd/0, /dev/fd/1, /dev/fd/2) in the /dev/fd directory.
6. LOFS - The loopback file system (LOFS) lets you create a new virtual file system so that
you can access files by using an alternative path name. For example, you can create
a loopback mount of the root (/) directory on /tmp/newroot
7. CTFS - The contract file system) is the interface for creating, controlling, and observing
contracts. A contract enhances the relationship between a process and the system
resources it depends on.
14
MANAGING FILE SYSTEM
SECTOR TRACK
CYLINDER
BACK
16
1 4
MANAGING FILE SYSTEM
Disk Convention:-
• Disk number:- The disk number is also known as the logical unit
number (LUN). This number reflects the number of disks at the target
location.
17
MANAGING FILE SYSTEM
BACK
18
1 4
MANAGING FILE SYSTEM
The data structures that are present in the UFS file systems are:-
Bootblk
Primary super Block
Backup super Block
Cylinder Group Block
1. Bootblk :-
The bootstrap program (bootblk) resides in the 15 disk sectors (Sectors
1–15) that follow the VTOC. Only the / (root) file system has an
active boot block.
19
MANAGING FILE SYSTEM
BACK
20
1 4
END OF CONCEPT
MANAGING FILE SYSTEMS
BACK
21
1 4
SOLARIS 10
STARTUP & SHUTDOWN
BACK
22
1 5
STARTUP & SHUTDOWN
The boot PROM performs the following steps during the first part of the boot sequence
The PROM runs the POST. The boot PROM firmware runs the POST to verify the system’s
hardware and memory. It then begins its boot sequence upon successful completion of the
self-test diagnostics.
The boot PROM determines the boot device by reading the PROM parameter boot-device.
The boot PROM reads the disk label located at Sector 0 on the default boot device.
The boot PROM finds the boot program from the default boot device programmed into the
PROM.
The boot PROM program reads a system’s primary boot program called bootblk (located at
Sectors 1 through 15) that contains a UNIX file system (ufs) file system reader. (The bootblk
program is
placed on the disk by the installboot program during system installation.)
The boot command loads the bootblk program from its location on the boot device into
memory.
BACK
24
1 6
STARTUP & SHUTDOWN
The bootblk program loads the secondary boot program, ufsboot, from the boot device into memory.
The path to ufsboot is recorded in the bootblk program, which is installed by the Solaris OE utility
installboot.
The ufsboot program locates and loads the appropriate two-part kernel.
The core of the kernel is two pieces of static code called genunix and unix, where genunix is the
platform-independent generic kernel file and unix is the platform-specific kernel file.
25
STARTUP & SHUTDOWN
The kernel initializes itself and begins loading modules.The kernel uses the ufsboot
command to load the files. When it has loaded enough modules to mount the root file system,
it unmaps the ufsboot program and continues.
When you boot a system or change run levels with the init or shutdown command, the init
daemon stops process, starts processes, or does both by reading information from the
/etc/inittab file.
A run level is a system state, represented by a digit or letter, that defines what services and
resources are currently available to users. The system is always running in a single run level.
Run levels are sometimes referred to as init states because the init process transitions
between run levels.
26
STARTUP & SHUTDOWN
SMF provides an infrastruction that arguments the traditional UNIX start-up scripts, init
run levels and configuration files. SMF provides the following function.
Makes services objects that can be viewed, with the new svcs command and managed
with svcadm and svccfg commands and makes it easy to backup, restore, and undo changes
to services by providing an explanation of why a service isn’t running by using svcs –x.
Also for services to be enabled and disabled using svcadm. These changes can persist
through upgrades and reboots. If the –t option is used the changes are temporary.
SMF defines a set of actions that can be invoked on a service by an administrator .These
actions includes enable, disable, refresh, restart, and maintain. Each service is managed by
a service restarter which carries out the administrative actions.
27
STARTUP & SHUTDOWN
All of the information that was provided by the boot messages is in /var/svc/log.
SMF Concepts:
Services:
Service Identifier:
Each service instance is named with a Fault Management Resource Identifier or FMRI.
The FMRI includes the service name and the instance name.
For example the FMRI for the rlogin service is svc:/network/login:rlogin
The service names usually includes a general functional category.
The categories include the following: application, device, milestone, network,
platform
Legacy init.d scripts are also represent with FRMIs that start with lrc instead of svc,
for example: lrc:/etc/rcS_d/s35cacheos_sh.
28
STARTUP & SHUTDOWN
Service States:
The svcs command displays the state, start time, and FMRI of service instances. The state of each
service is one of the following:
29
STARTUP & SHUTDOWN
SMF automatically takes the following backups of the repository. The boot backup is
taken immediately before the first change to the repository is made during each system
startup.
The manifest_import backup occurs after svc:/system/manifest-import: default
completes, if it imported any new manifest or ran any upgrades scripts.
The backups are stored as /etc/svc/repository-type-YYYYMMDD_HHMMSS. Note
that the hour format is 24 –hours. You can restore the repository from these backups, if
an error occurs. To do use the /lib/svc/bin/restore repository command.
SMF Snapshots:
The data in the service configuration repository includes snapshots, as well as a configuration
that can be edited. Data about each service instance is stored in the snapshots. The standard
snapshots are as follows.
30
STARTUP & SHUTDOWN
Run levels
0 - Shutdown
4 - Not Defined
5 - Power Off
6 - Reboot
BACK
31
1 5
STARTUP & SHUTDOWN
BACK
32
1 5
STARTUP & SHUTDOWN
Where to go
0 1 2 3 6
Where u are
boot -s boot -s
0 (login as DRL
#init 2
root)
# init 0
# init 6
1 or # init 2 # init 3
# reboot
halt
# init 0 # init 6
2 #shutdown # init 3 #shutdown
#init 1
-g 300 -i 0 -g -i
# init 0
3 #shutdown -do- # init 2 -do-
-g 300 -i 0
BACK
33
1 5
STARTUP & SHUTDOWN
Finally CDE
X-windows Loads all
login appears. DD
Starts the SMF service and
SMF takes care of starting Starts “ init ”
Starts scheduler
all the services /etc/inittab
with pid “ 0 ”
[ in dependency order ] svc.startd
34
END OF CONCEPT
STARTUP & SHUTDOWN
BACK
35
1 5
SOLARIS 10
USER ADMINISTRATION
BACK
36
1 6
USER ADMINISTRATION
Accounts Management
/etc/passwd
users groups /etc/group
/etc/shadow
1. Solaris
useradd groupadd
Management
usermod users groups groupmod
Console
userdel groupdel
2. Cmd Line
3. Shell Script
BACK
37
1 6
USER ADMINISTRATION
Password user2:x:100:4:/usr/user2:/bin/ksh:Hyd
aging info.
(16 default groups) sales: :4:user1 User Name Comment
Password
Group Name
UID
Password
GID
GID
HD
Users belongs to
Shell
secondary groups
as “sales”.
BACK
39
1 6
USER ADMINISTRATION
Profile
User logging
40
END OF CONCEPT
USER ADMINISTRATION
BACK
41
1 6
SOLARIS 10
PACKAGE MANAGEMENT
BACK
42
2 1
PACKAGE MANAGEMENT
/var/sadm/install/contents
/var/sadm/pkg
Files
Collection of Files
Package and
Spooling Concepts Definition
Management Directories
Components
1. Package Installation
2. Package Information
3. Package Verification
4. Package Removal
BACK
43
2 1
PACKAGE MANAGEMENT
Package Administration:-
Software package administration adds software to systems and removes software from
systems.
In its simplest form, a package is a collection of files and directories.
Files that describe the package and the amount of disk space required for installation
The pkgchk command also checks the path name, the file size and checksum,
and the file attributes of a package.
BACK
45
2 1
PACKAGE MANAGEMENT
Patch Administration:-
A patch contains a collection of files and directories. This collection replaces existing
files and directories that prevent proper execution of the software.
The Solaris 10 OE patches are in zip format, for example, 105050-01.zip
The showrev command and the patchadd command provide useful information
about currently installed patches.
Historical information about all patches that are currently installed on a system and
that can be uninstalled using the patchrm command is stored in the /var/sadm/patch
directory.
One of the common reasons for patch installation failure is directory permission or
ownership problems. The /var/tmp directory is open to all and eliminates any of these
types of problems.
BACK
46
2 1
PACKAGE MANAGEMENT
The patchrm command calls the pkgadd utility to restore packages that were
saved during the initial patch installation.
When you remove a patch, the patchrm command restores all files that were
modified or replaced by that patch, unless:
The patch was installed with the patchadd -d option (which instructs the
patchadd command not to save copies of files being updated or replaced)
The patch cluster provides a selected set of patches for a designated Solaris
OE level and is conveniently wrapped for one-step installation.
BACK
47
2 1
END OF CONCEPT
PACKAGE MANAGEMENT
BACK
48
2 1
SOLARIS 10
PRINTERS
BACK
49
3 2
PRINTERS
1. Parallel Port
1. Speed (ppm) 2. Serial Port
2. (dpi) 3. USB Port
3. Color Option 4. MPSC (ISA or PCI)
Local
4. RAM 5. AB Switch Box
5. Disk Based Spooling (Manual or Electronic)
6. Duplex Option 6. Laptops I-R Port
7. Optional Printer Tray
8. Network Connectivity 1. Between same OS.
Interfaces Remote 2. Between different OS.
Types Printers (PCNFS / SAMBA)
Plotters
1.lp
logs lp 2.cancel
1.lpadmin model interface
2.lpmove
3.reject
network
Request tmp
(root) (users) standard
Local Net Standard
51
Print administration
52
Diagrammatic representation – Local Printers
CONNECTOR
SERVER LOCAL PRINTER
53
Network Printers
• Network Printers can work in two ways:
54
Network Printers – Without a Print Server
VLAN 1
SERVER A1 VLAN3
IP: 10.0.0.2
N/w SWITCH PRINTER
VLAN2 IP: 10.0.0.1 IP: 10.0.0.4
•The servers communicate to the printer via the Network
switch.
•The switch, based upon the IP address from which print
request in sent, forwards the request to the printer.
SERVER A2 •The devices can either be a part of the same VLAN of a
different VLAN.
IP: 10.0.0.3 55
Network printers – With Print Server
N/w Switch
IP: 10.0.0.1
56
Stages in Printing
Initiating
Queuing
Tracking
Fault Notification
Filtering
57
STAGES IN PRINTING
Queuing – Once the printer is initialized and ready to print, the Print
service, queues the print requests and schedules their printing.
Tracking – The Print service also tracks the status of various print
requests. The ‘Super User’ can track these requests and manage
them. Individual users can also manage their requests.
58
59
Daemons involved in LP printing
60
Configuring Local Printers
61
Adding a printer
# /usr/sbin/lpadmin -p <printer-name> –v /dev/printers/0
This command adds the printer to the server on the device
/dev/printers/0.
All the configuration of the printers is stored in the /etc/printers.conf file. Any
changes in the configuration would be updated in this file.
62
Setting a printer as the default printer
# lpadmin -d printername
Checking the default destination path:
# lpstat –d
Starting the Print service:
# /usr/lib/lpsched
# /etc/init.d/lp start
Deleting a printer’s configuration
# reject <printer name>
# disable <printer name>
# lpadmin –x <printer name>
The reject command stops all currently queued jobs.
63
lpshut
This command kills the lpsched and the in.lpd daemons thereby
stopping the print services.
# lp <filename>
This command prints the file via the default printer.
64
END OF CONCEPT
PRINTERS
65
SOLARIS 10
SECURITY SERVICES
BACK
66
3 4
SECURITY SERVICES
F.A.P F.A.C.L
Service
Level System SecurityUtilities Switch User
ftp
/var/adm/loginlog Network
Level
/var/adm/utmpx
/etc/default/login IP-Filters
/etc/default/su
/var/adm/sulog
67
SECURITY SERVICES
68
END OF CONCEPT
SECURITY SERVICES
69
70
SOLARIS 10
BACKUPS
BACK
71
2 6
BACKUPS
72
BACKUPS:-
The most common method to schedule backups is to perform cumulative incremental backups
daily. This schedule is recommended for most situations. To set up a backup schedule,
determine:
The /etc/dumpdates file records backups if the -u option is used with the ufsdump
command.
Each line in the /etc/dumpdates file shows the file system that was backed up and
the level of the last backup.
73
To restore files or file systems, determine the following:
When you restore an entire file system from a backup tape, the system creates a
restoresymtable file
.
The ufsrestore command uses the restoresymtable file for check-pointing or passing
information between incremental restores. You can remove the restoresymtable file when the
restore is complete.
74