SOLARIS INSTALLATION

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

Entire Distribution System

Disk Selection
Identification
Developer Support c0t0d0
Networked
End User Support c0t1d0 IP Address & subnet
Core System Host Name

Reduced N/W Support Naming Services for client

DNS/NIS/NIS+/LDAP /NONE

2
SOLARIS 10 INSTALLATION

There are a number of ways to install the Solaris 10 OE on your system.

They include:
 Solaris sun install program
 Custom JumpStart™ procedure
 Standard upgrade
1. Solaris sun install program:-
This is the basic mode of installing the Solaris 10 OE in the
Graphical Mode of installation from the local CD-ROM.
2. Custom JumpStart procedure
The Solaris JumpStart procedure installs Solaris OE software on
a system by referencing a user-defined profile. You can customize profiles
for differenttypes of systems.
A JumpStart installation provides a hands-off installation across
the network and is based on a central-configured server.
BACK
3
1 3
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.

The Solaris OE software is organized into three components:

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

Software groups are collections of Solaris OE software packages. Each

software group includes support for different functions and hardware drivers.
The Solaris OE is made up of six software groups:

 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

 Developer System Support :-The Developer System Support software

group contains the End User System Support software group. It also
contains the libraries, the include files, the online manual pages, and the
programming tools for developing software
 Entire Distribution it contains the Developer System Support software
group. It also contains additional software needed for servers.

 Entire Distribution Plus OEM Support Software Group

The Entire Distribution Plus OEM Support software group contains
the entire Solaris OE software release. It also contains additional
hardware support for OEMs.

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

File type Owner Group Others

- | --- | --- | ---
Platform
Independent
chown FAP e.g.. Notepad,
(change ownership) vi
#chown scott *.c
ASCII
Platform
chmod
Cmds. Regular Data dependent
(change FAP) Files e.g. DBF’s
#chmod 755 file1
Binary
chgrp
Platform
(change group
Special dependent
Ownership)
(executables)
#chgrp group1 *.sh
e.g. abc.doc
Default Character Special
permissions
umask (022) Block Special

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

File System Types

Disk Based Network Based Pseudo

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

Disk Based File systems:-

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.

Network-Based File Systems:-

1. NFS – The network file system allows users to share files among many types
of systems on the network.

Pseudo File Systems:-

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

The main components that we will be dealing with are :-

 Disk Architecture
 Disk Convention
Disk Architecture:-
 Sector:- The smallest addressable unit on a platter. One sector can hold 512
bytes of data. Sectors are also known as disk blocks.
 Track:- A series of sectors positioned end-to-end in a circular path.
 Cylinder:- A stack of tracks.
Disks are logically divided into individual partitions known as disk slices.
Disk slices are groupings of cylinders that are commonly used to organize data by
function.
A disk under the Solaris OE can be divided into eight slices that are labeled Slice 0
through 7.
Slice 2 represents the entire disk. Slice 2 maintains important data about the entire
disk
BACK
15
1 4
MANAGING FILE SYSTEM

SECTOR TRACK

CYLINDER

BACK
16
1 4
MANAGING FILE SYSTEM

Disk Convention:-

An eight-character string typically represents the full name of a slice.

The string includes the controller number, the target number, the disk
number, and the slice number.

• Controller number:- Identifies the host bus adapter (HBA), which

controls communications between the system and disk unit.

• Target number:- correspond to a unique hardware address that is

assigned to each disk, tape, or CD-ROM.

• 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.

• Slice number:- A slice number ranging from 0 to 7.

The overall representation will be:- c#t#d#s#

17
MANAGING FILE SYSTEM

Unix 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.

2. Primary Super Block :-

The superblock resides in the 16 disk sectors (Sectors 16–31) that
follow the boot block. This Consists of

19
MANAGING FILE SYSTEM

1. The number of data blocks

2. The number of cylinder groups
3. The size of a data block and fragment
4. The name of the mount point
5.Filesystemstate flag: clean, stable, active, logging, or
unknown
3. Backup Super Block:-
The replication of the primary super block that starts from the sector-32.

4. Cylinder Group Block:-

This contains the information about
1. the number of data blocks in the cylinder group
2. the number of directories
3. free blocks, free inodes, and free fragments in the cylinder group
4. the used inode

BACK
20
1 4
 END OF CONCEPT
MANAGING FILE SYSTEMS

BACK
21
1 4
 SOLARIS 10
STARTUP & SHUTDOWN

BACK
22
1 5
STARTUP & SHUTDOWN

Startup and Shutdown

Boot Process
PROM runs POST

Boot PROM Phase Boot locates boot device

Boot reads & loads primary bootblk

Primary bootblk loads secondary boot

block i.e. ufsboot
Boot Program Phase
ufsboot loads kernel (32-bit or 64bit,
platform independent, platform dependent)

Kernel Initialization Kernel initialize itself and loads modules,

Phase reads /etc/system

Kernel reads /etc/inittab

Init Phase
start the master daemon svc.startd
BACK
23
1 5
STARTUP & SHUTDOWN

Boot PROM Phase

 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

Boot Program Phase :-

The following describes the boot programs phase:

 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.

 Running in 32-bit mode, the two-part kernel is located in the directory

/platform/‘uname -m‘/kernel.
 Running in 32-bit mode, the two-part kernel is located in the directory
/platform/‘uname -m‘/kernel

25
STARTUP & SHUTDOWN

The kernel Initialization Phase

The kernel reads its configuration file, called /etc/system.

 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.

 The kernel starts the /etc/init process.

The init Phase

 The final phase of the boot process is the init phase.

 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 and the Boot Process:

 SMF provides an infrastruction that arguments the traditional UNIX start-up scripts, init
run levels and configuration files. SMF provides the following function.

 Automatically restarts failed services in dependency order

 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.

 Enhance the ability of administrators to securely delegate tasks to non-root users,

including the ability to modify properties and enable, disable, or restart services on the
system.

 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:

 The fundamental unit of administration in the SMF is the service instance.

 An instance is a specific configuration of a service. A web server is a service.
 A service is an entity that provides a list of capabilities to applications i.e,local and
remote.
 A service is dependent on an implicitly declared list of local 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:

 degrade - The service instance is enabled, but is running at a limited capacity.

 disabled - The service instance is not enabled and is not running.
 maintenance - The service instance has encountered an error that must resolved by the
administrator.
 offline - The service instance is enabled, but the service is not yet running or available to
run.
 online - The service instance is enabled and has successfully started.
 un-initialized:- This state is the initial state for all services before their configuration has
been read.
SMF Manifest:
An SMF manifest is an XML file that contains a complete set of properties that are associated
with a service or a service instance. The files are stored in /var/svc/manifest.
SMF Profile:
An SMF profile is an XML file that lists the set of service instances that are enabled when a
system is booted. The profiles are stored in /var/svc/profile.
Service Configuration Repository:
The service configuration repository stores persistent configuration information as well as SMF
runtime data for services.

29
STARTUP & SHUTDOWN

SMF Repository Backups:

 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.

 initial – Taken on the first import of the manifest

 running – Used when the service methods are executed
 start – Taken at the last successful start

The svccfg command is used to view or revert to instance configuration in a previous

snapshot.

30
STARTUP & SHUTDOWN

Run levels

0 - Shutdown

1 - Single User Mode

2 - Multi User Mode with out NFS Service

3 - Multi User Mode with NFS Service

4 - Not Defined

5 - Power Off

6 - Reboot

S s - Single User with some Services

BACK
31
1 5
STARTUP & SHUTDOWN

/etc/inittab Run Control

Scripts in /sbin

What action to Default

take when the Run Level
rc0 rc1 rc2 rc3 rc5 rc6 rcS
system enters into
new run level.
Run Control
Script Directories
in /etc

rc0.d rc1.d rc2.d rc3.d rcS.d

K#Scripts S#Scripts K#Scripts

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

Solaris Booting Process

Secondary Loads kernel
boot block
Booting POST Primary (ufsboot)
Process (power on self test) boot block
Platform Platform
dependent independent
H/W check modules modules

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

User & Group

Components
User Account Group
Main Components components
useradd
User Name Group Name
-u UID
Password Secondary
-g GID
Groups
Home -s Shell
Directory Group ID
-d Home Directory
Login Shell
-m Creating HD
User
Initialization Login Name
File /etc/skel
-c Comment
BACK
38
1 6
USER ADMINISTRATION

User and Group info.

/etc/shadow /etc/group (Default 12 Users) /etc/passwd

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

System wide /etc/profile Submit user name & password

User wide $HOME/.profile Check user name & password

in /etc/passwd & /etc/shadow
Env. PATH, MANPATH,
TERM, MAIL, Error No Looks for Shell
SHELL yes
Aliases Alias del=rm, Provides “ / ” No
Looks for HD
as HD
P=`ps -ef|more` yes
Cmds. Every time user logs in and wants Go to HD & execute /etc/profile,
to fire up certain cmds e.g. who etc. $HOME/.profile.“$” prompt is
displayed.
Menu
We can call menu scripts

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.

Software packages contain:

 Files that describe the package and the amount of disk space required for installation

 Compressed software files to be installed on the system

 Optional scripts that run when the package is added or removed

The /var/sadm/install/contents file is a complete record of all the software packages

installed on the local system disk. The command-line tools are:-

 pkgadd Installs software packages to the system

 pkgrm Removes a package from the system

 pkginfo Displays software package information

 pkgchk Checks package installation state

BACK
44
2 1
PACKAGE MANAGEMENT

The pkgadd command updates the /var/sadm/install/contents file each

time new packages are installed.

The pkgrm command uses the /var/sadm/install/contents file to determine

where the files for a software package are located on the system

By default, the pkgrm command requires confirmation to continue removing a

package and issues a message to warn about possible package dependencies

A file shared by two or more packages displays the message:-

filename <shared pathname not removed>

The /var/sadm/pkg directory maintains a record of all installed packages.

The pkgchk command checks to determine if a package has been completely

installed on the system.

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.

The two most common commands for managing patches are:

 patchadd – Installs uncompressed patches to the Solaris OE

 patchrm – Removes patches installed on the Solaris OE

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 is required by another patch

 The patch has been obsoleted by a later patch

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)

The printer connected to

Laser Network LAN having an IP-
B/W or Color, Address.
size: 80 or 132

Dot Matrix Manufactures

Plotters

HP Canon Epson Samsung Okidata Xerox

Inkjet
50
 /

/var /usr /etc

lp spool bin sbin lib printer.conf lp

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

 Print administration can be broadly classified into 2 broad categories.

 Administering printers LOCAL to a particular server

 Network printers that can be SHARED across a network and can

be used by numerous servers.

52
 Diagrammatic representation – Local Printers

CONNECTOR
SERVER LOCAL PRINTER

•The printer is directly connected to the server through a parallel or a

USB cable.
•All print requests by the server are processed directly by the printer
and the print output is obtained.

53
 Network Printers
• Network Printers can work in two ways:

• With a print server

• Without a print server

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

Print Client 1 Print Server Printer

IP: 10.0.0.2 IP: 10.0.0.4 IP: 10.0.0.5

All printing requests forwarded by the

switch are authenticated by the print
server and then sent across to the
Print Client 2
printer.
IP: 10.0.03

56
 Stages in Printing

 Initiating

 Queuing

 Tracking

 Fault Notification

 Filtering

57
STAGES IN PRINTING

 Initiating – Prior to sending requests to the printer, the Solaris

Print Service initializes the printer, thereby ensuring that the printer
is in a state to process the print requests.

 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.

 Fault Notification – If there are any problems during printing, a

message is sent across to the console, or as a mail to the users
depending upon how the fault notification service has been setup.

 Filtering – The Solaris Print Service provides the option of filtering

the various print jobs and converting them into an appropriate file
type for the destination printer.

58
59
Daemons involved in LP printing

 in.lpd – A protocol adapter that receives print requests from the

‘inted’ service, translates the print requests and communicates it
to the spooler and returns the results to the requester.

 lpsched – A print scheduler which handles the various print

requests. If the lpsched daemon is not running on the server, print
requests are not accepted. The lpsched daemon is automatically
started by the ‘lpadmin’ command.

60
Configuring Local Printers

 Once the printer has been connected to the server as per

instructions mentioned in the manufacturer’s installation guide,
setting up of local printers involves the following steps.

 Adding the printer.

 Specifying the printer model.
 Specifying the content type.
 Providing the printer description.
 Enabling the printer to accept requests.
 Verify the configuration.

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.

 Specifying the printer Model

# lpadmin -p <printer-name> -m <model_type>
This command adds the printer along with the model type.
 Specifying the printer description
# lpadmin -p <printer-name> -D <printer-description>

 Enable the printer to accept print requests and to print those

requests.
# accept <printer-name>
# enable <printer-name>
 Verifying the configuration
# lpstat -p <printer-name> -l

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.

 Moving print jobs between printers.

# lpmove <source_destination> <target_destination>

63
lpshut
This command kills the lpsched and the in.lpd daemons thereby
stopping the print services.

Printing using the Local Printer

 Printing is usually done through the ‘lp’ command.

# lp <filename>
This command prints the file via the default printer.

 By using the –d option the destination can be changed.

 To set formatting options such as length, width and the characters

per inch (cpi), use the –o option.

64
END OF CONCEPT
PRINTERS

65
 SOLARIS 10
SECURITY SERVICES

BACK
66
3 4
SECURITY SERVICES

F.A.P F.A.C.L

File Level Telnet

Service
Level System SecurityUtilities Switch User

ftp
/var/adm/loginlog Network
Level
/var/adm/utmpx

/etc/default/login IP-Filters

/etc/ftpd/ftpusers NMAP Utility

/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

Veritas Net Backup Solastice Backup

Tivoli Backup Omni Backup Disk
Target Target Tape
Storage Tape Library
Onsite
Backups Utilities
Offsite

Levels Types Generic Flavour Specific

Full Backup Local tar ufsdump

Cumulative remote cpio ufsrestore
Network dd
Incremental
jar

72
BACKUPS:-

Performing backups on a regular basis to prevent loss of data due to:

 Accidental deletion of files

 Hardware failures
 Problems with re-installations or system upgrades
 System crashes
 System break-ins by unauthorized users, compromising data integrity

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 file systems to back up

 A backup device (for example, tape drive)
 The number of tapes to use for the backup
 The type of backup (for example, full or incremental)
 The time it takes to perform a backup

 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:

 The file system backup tapes that are needed

 The device name to which you will restore the file system
 The name of the temporary directory to which you will restore individual files
 The type of backup device to be used (local or remote)
 The backup device name (local or remote)

 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