Free Practice Questions for RedHat RH302 Exam

We know that every files/directories are owned by certain user and group. And Permissions are defines to owner user, owner group and other.

-rwxr-x---Full permission to owner user, read and write to owner group and no permission to others.

According to question: We should give the full permission to user user1 without changing the previous permission.

ACL (Access Control List), in ext3 file system we can give permission to certain user and certain group without changing previous permission. But that partition should mount using acl option. Follow the steps

vi /etc/fstab

/dev/hda14/dataext3defaults,acl0 1

Either Reboot or use: mount –o remount /data

setfacl –m u:user1:rwx /data

Verify using: getfacl /data

Maintenance mode also known as emergency mode. System boots on emergency mode when file system error occurred. It is due to unknown partition, bad filesystem specified in /etc/fstab. To slove follow the steps

Give the Root password

fdisk –lVerify the Number of parations.

Identify the Root partition, e2label /dev/hda1, e2label /dev/hda2…..

Remount the root partation on rw mode: mount –o remount,defaults /dev/hda6 /

vi /etc/fstab

Correct all partitions, mount point, mount options, file system etc.

6.Press ctrl+d

Very Tricky question from redhat. Actually question is giving scenario to you to implement quota to neo user. You should apply the quota to neo user on /home that neo user shouldn’t occupied space more than 70K.

1.vi /etc/fstab

LABEL=/home/homeext3defaults,usrquota0 0To enable the quota on filesystem you should mount the filesystem with usrquota for user quota and grpquota for group quota.

2.touch /home/aquota.userCreating blank quota database file.

3.mount -o remount /homeRemounting the /home with updated mount options. You can verify that /home is mounted with usrquota options or not using mount command.

4.quotacheck -u /homeInitialization the quota on /home

5.edquota –u neo /homeQuota Policy editor

See the snapshot

1 Disk quotas for user neo (uid 500):

2 Filesystem blocks soft hard inodes soft hard

4 /dev/mapper/vo-myvol 2 30 70 1 0 0

Can you set the hard limit 70 and soft limit as you think like 30.

Maintenance mode also known as emergency mode. System boots on emergency mode when file system error occurred. It is due to unknown partition, bad filesystem specified in /etc/fstab. To slove follow the steps

Give the Root password

fdisk –lVerify the Number of parations.

Identify the Root partition, e2label /dev/hda1, e2label /dev/hda2…..

Remount the root partation on rw mode: mount –o remount,defaults /dev/hda6 /

vi /etc/fstab

Correct all partitions, mount point, mount options, file system etc.

6.Press ctrl+d

When root unable to login into the system think:

1. Is password correct?

2. Is account expired?

3. Is terminal Blocked?

Do these Steps:

Boot the System on Single user mode.

Change the password

Check the account expire date by using chage –l root command.

If account is expired, set net expire date: chage –E “NEVER” root

Check the file /etc/securettyWhich file blocked to root login from certain terminal.

If terminal is deleted or commented write new or uncomment.

Reboot the system and login as a root.

Do the following steps as:

hostname station?.example.comThis will set the host name only for current session. To set hostname permanently.

vi /etc/sysconfig/network

HOSTNAME=station?.example.com

service network restart

Do the following steps as:

Use fdisk /dev/hdaTo create new partition.

Type nFor New partitions

It will ask for Logical or Primary Partitions. Press l for logical.

It will ask for the Starting Cylinder: Use the Default by pressing Enter Key.

Type the Size: +100MYou can Specify either Last cylinder of Size here.

Press P to verify the partitions lists and remember the partitions name.

Press w to write on partitions table.

Either Reboot or use partprobe command.

Use mkfs –t ext3 /dev/hda?

Or

mke2fs –j /dev/hda? To create ext3 filesystem.

vi /etc/fstab

Write:

/dev/hda?/dataext3defaults0 0

Verify by mounting on current Sessions also:

mount /dev/hda? /data

The LVM system organizes hard disks into Logical Volume (LV) groups. Essentially, physical hard disk partitions (or possibly RAID arrays) are set up in a bunch of equal-sized chunks known as Physical Extents (PE). As there are several other concepts associated with the LVM system, let's start with some basic definitions:

Physical Volume (PV)is the standard partition that you add to the LVM mix. Normally, a physical volume is a standard primary or logical partition. It can also be a RAID array.

Physical Extent (PE)is a chunk of disk space. Every PV is divided into a number of equal sized PEs. Every PE in a LV group is the same size. Different LV groups can have different sized PEs.

Logical Extent (LE)is also a chunk of disk space. Every LE is mapped to a specific PE.

Logical Volume (LV)is composed of a group of LEs. You can mount a filesystem such as /home and /var on an LV.

Volume Group (VG)is composed of a group of LVs. It is the organizational group for LVM. Most of the commands that you'll use apply to a specific VG.

1.Verify the size of Logical Volume:lvdisplay /dev/vg0/lv1

2.Verify the Size on mounted directory:df –h or df –h mounted directory name

3.Use :lvextend –L+400M /dev/vg0/lv1

4. resize2fs /dev/vg0/lv1to bring extended size online.

5. Again Verify using lvdisplay and df –h command.

It is due to either default runlevel or runlevel specific scripts.

id:?:initdefault:Where default runlevel is specified. It shouldn’t be 6.

l3:3:wait:/etc/rc.d/rc 6It reads the scripts of runlevel 6 while booting system on rulevel 3.

It should be like:

si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0

l1:1:wait:/etc/rc.d/rc 1

l2:2:wait:/etc/rc.d/rc 2

l3:3:wait:/etc/rc.d/rc 3 Should be like this

l4:4:wait:/etc/rc.d/rc 4

l5:5:wait:/etc/rc.d/rc 5

l6:6:wait:/etc/rc.d/rc 6