Q.1a What Are Different Linux Distribution? Explain Each in Brief
Q.1a What Are Different Linux Distribution? Explain Each in Brief
2. Debian:
This was used as a non-commercial O.S. Debian has been used as a platform for other
Linux distributions. Debian is an operating system composed only of free, open-source
software.
3. Slackware:
Slackware aims for design stability and simplicity and to be the most "Unix-like" Linux
distribution. The Official Release of Slackware Linux is an advanced Linux operating
system, designed with the twin goals of ease of use and stability as top priorities.
4. SUSE:
SUSE Linux is of German origin, an acronym of “Software und System-Entwicklung”. The
first version appeared in 1994, making SUSE one of the oldest existing commercial
distributions.
5. Turbolinux:
The Turbolinux distribution is a Japanese Linux distribution targeting Asian users.
6. Ubuntu:
It is a Debian-based Linux O.S. and distribution. It is based on free software. It’s developer
is Canonical Ltd.
7. Fedora:
It is a project with a strong focus on free software. Fedora is sponsored by Red Hat. It is the
foundation for Red Hat Enterprise Linux.
8. CentOS:
The CentOS Linux distribution is a reproducible platform derived from the sources of Red
Hat Enterprise Linux (RHEL). It aims to be functionally compatible with its upstream source,
Red Hat Enterprise Linux (RHEL).
9. Gentoo:
Gentoo is a free operating system based on either Linux or FreeBSD that can be
automatically optimized and customized for just about any application or need. It is
designed for advanced Linux users.
Q.1b Explain the duty of the Linux system administrator in backing up and restoring files.
Ans. 1) Until equipment becomes absolutely infallible, and until people lose their desire to
harm the property of others (and, truth be known, until system administrators
become perfect), there is a need to back up important files so that in the event of a
failure of hardware, security, or administration, the system can be up and running
again with minimal disruption.
2) Only the system administrator may do this.
3) Because of its built-in security features, Linux may not allow users to be able even
to back up their own files to floppy disks.
4) Again, knowing that file backup is our job is not enough. We need to formulate a
strategy for making sure our system is not vulnerable to catastrophic disruption and
it’s not always obvious.
5) If we have a high-capacity tape drive and several good sets of restore diskettes, we
might make a full system backup every few days.
6) Once we’ve decided what to back up, we need to decide how frequently we want to
perform backups and whether we wish to maintain a series of incremental backups
,adding only the files that have changed since the last backup or multiple full
backups, and when these backups are to be performed or, if we have input as to the
equipment used, do we want to use a redundant array of independent disks, or
RAID, which is to say multiple hard drives all containing the same data as insurance
against the failure of any one of them, in addition to other backup systems.
7) A RAID is not enough, because hard drive failure is not the only means by which a
system can be brought to a halt.
8) Part of our strategy should be the maintenance of perfect backups without ever
needing to resort to them.
9) This means encouraging users to keep multiple copies of their own important files,
all in their home directories, so that you are not being asked to mount a backup so as
to restore a file that a user has corrupted.
10) Backing up is only half the story, too. You need to formulate a plan for bringing the
system back up in the event of a failure.
Sometimes hardware failures are so severe that the only solution is replacing the hard
drive, replacing everything except the hard drive, or even restoring from backup to a whole
new machine.
1c Explain the booting process of the Linux operating system in detail.
Ans Have you ever wondered what happens behind the scenes from the time you press the
power button until the Linux login prompt appears?
The following are the 6 high level stages of a typical Linux boot process.
1. BIOS
2. MBR
• MBR stands for Master Boot Record.
• It is located in the 1st sector of the bootable disk. Typically /dev/hda, or /dev/sda
• MBR is less than 512 bytes in size. This has three components 1) primary boot
loader info in 1st 446 bytes 2) partition table info in next 64 bytes 3) mbr validation
check in last 2 bytes.
• It contains information about GRUB (or LILO in old systems).
• So, in simple terms MBR loads and executes the GRUB boot loader.
3. GRUB
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-194.el5PAE)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-194.el5PAE ro root=LABEL=/
initrd /boot/initrd-2.6.18-194.el5PAE.img
• As you notice from the above info, it contains kernel and initrd image.
• So, in simple terms GRUB just loads and executes Kernel and initrd images.
4. Kernel
5. Init
6. Runlevel programs
• When the Linux system is booting up, you might see various services getting
started. For example, it might say “starting sendmail …. OK”. Those are the
runlevel programs, executed from the run level directory as defined by your run
level.
• Depending on your default init level setting, the system will execute the programs
from one of the following directories.
o Run level 0 – /etc/rc.d/rc0.d/
o Run level 1 – /etc/rc.d/rc1.d/
o Run level 2 – /etc/rc.d/rc2.d/
o Run level 3 – /etc/rc.d/rc3.d/
o Run level 4 – /etc/rc.d/rc4.d/
o Run level 5 – /etc/rc.d/rc5.d/
o Run level 6 – /etc/rc.d/rc6.d/
• Please note that there are also symbolic links available for these directory under /etc
directly. So, /etc/rc0.d is linked to /etc/rc.d/rc0.d.
• Under the /etc/rc.d/rc*.d/ directories, you would see programs that start with S and
K.
• Programs starts with S are used during startup. S for startup.
• Programs starts with K are used during shutdown. K for kill.
• There are numbers right next to S and K in the program names. Those are the
sequence number in which the programs should be started or killed.
• For example, S12syslog is to start the syslog deamon, which has the sequence
number of 12. S80sendmail is to start the sendmail daemon, which has the sequence
number of 80. So, syslog program will be started before sendmail.