Server Administration - System Component
Server Administration - System Component
Server Administration
-System Component-
Lecture 2 System Component
In System Administration:
Word System is used to refer both the operating system of a
computer and often, collectively the set of all computers that
cooperate in a network.
Human-computer system ?
An Organized Colaboration between humans and Computers
to solve a problem or provide service.
Network Infrastructure:
Human
Host Computer
Network Hardware
Layer 1,2,3 Devices
Human Computer System (depedencies)
Hardware Handling
Memory
Different sizes, Different Speed
When Purchasing a Memory Please remember :
Physical Size of the Memory Plugins ( Choose the appropriate socket)
Capacities & Data Rates
ECC RAM Tolerant from external noises
RAM Slots Particulary Order
Another Aspect of Hardware
Lightning
Fuse ? Transistor & CMOS Chips burn out much faster than any fuse
Electronic Spike/ Surge Protectors
Power
UPS
Heat
Metals Expand the Heat Significantly
Increased Temperature Increased Noise Level Reduce Network
Capacities
Cold
Sudden change from hot to cold Chip Damage
Humidity
Static Electricity builds up
Operating Systems
OS Key Element
Technical Layer of Software
Driving Hardware in Computers
Filesystem
Provides a way for organizing files logically
User Interface
Enables users to run their own programs and manipulate their files in a
simple way
Operating Systems
Multiuser OS
Allow multiple users to share the resource in a single host
Protected by Unique Identity
Username
Private Login Area
Simulate Virtual Workstations for each users
Operating System
Securable OS
Unix and NT secure ?
By Its Nature security is not an achievable goal
Aspiration that includes accepted level of risk
Mechanism basic level preventive security possible
Why Windows, DOS, Macintosh are so susceptible to virus
attacks?
Properly configured and bug free Unix/NT (ownership,
permissions)
Operating Systems
Privileged accounts
Unix : root / super user
Windows : Administrator (doesnt have automatic access to
everything such does root)
Administrator & root accounts should never be used for normal
work (Too Much Power)
Behind every great powers, come a great responsibility
Unix Like and Windows Computer
Unix Like and Windows Computer
Filesystem
Symbolic link
Alias to another file
(ex:unix ln -s fromfile /other/directory/tolink )
Hard link
Duplicate directory from an inode in filesystems
ex: unix
% date > hardfile ( create the file )
% ls -l -rwx-xr-x 1 john users 605 Nov 18 12:25 hardfile
% ln hardfile project/hardfile2
% ls -l projects/hardfile2 -rwx-xr-x 2 john users 605 Nov 18 12:25
hardfile
Ignored by filesystem designers
22
A. User A then decides whether or not other u ser s can r ead, wr ite or execu te the
le by setting the protection bits or the permission of the le u sing the command
chmod.
File access control
In addition to u ser identities, ther e ar e gr ou ps of u ser s. The idea of a gr ou p is
that sever al named u ser s might want to be able to r ead and wor k on a le, withou t
other u ser s being able to access it. Ever y u ser is a member of at least one gr ou p,
called the login group and each gr ou p has both a textu al name and a nu mber
Restrict
(group privilege
id). The uid and to gid
filesofoneach ser is r ecor ded in the le /etc/passwd (see
the usystem
chapter
Unix 6). Member
records ship of other
information ( whogr ou ps is &
create r ecor ded intothe
allowed le /etc/group or on
access)
some systems /etc/logingroup.
The
Username (uid),
following login
ou tpu name
t is fr om the(text string) ls -lag execu ted on a Su nOS type
command
machine.
23
File access control
24
File access control (cont)
25
Access Control List
27
Network Filesystem Models
The nal & at the end of this line means that the job will be ru n in the back grou nd.
Note that this will not be confu sed with the redirection operator >& since it mu st
be the last non-whitespace character of the command. The command above look s
for any les in the system containing the string lib and writes the list of les to a
le called output.
If we want to see what processes are ru nning, we can u se the ps com-
mand. ps withou t any argu ments lists you r cu rrent processes, i.e. all processes
owned by the u ser identity you logged in with that are connected to the shell
you are cu rrently u sing. ps tak es many options, for instance ps auxg will
list all u ser processes in detail on BSD-lik e systems, while ps -efl will pro-
vide a similar, if not entirely compatible, listing on System V-lik e systems.
Some Unix-lik e systems su pport both the BSD and System V ags to the ps
command.
Processes can be stopped and started, or k illed once and for all. The kill
command does this and more. In fact, it sends generalized signals to ru nning
processes, not only the k ill signal. There are two versions of the kill command.
One of them is bu ilt into the C-shell and the other is not. If you u se the C-shell
then you will never care abou t the difference u nless the process table is fu ll. We
shall nonetheless mention the special featu res of the C-shell bu ilt-ins below. The
k ill command tak es a nu mber called a signal as an argu ment and another nu mber
Network Environment
OSI Layer
IP Address
Subnet & Broadcast
Interface Settings
ARP
NAT
IPv6
2001:0700:0700:0004:0290:27ff:fe93:6723
2001:700:700:4:290:27ff:fe93:6723
Assignment