RH302 Exam Dumps - RedHat RHCE Questions and Answers

This is boot related problem. There will be same questions repeated two times but problem is different.

First When you restart the system you will get the Error:

mount: error 15 mounting ext3

mount: error 2 mounting none

switchroot: mount failed: 22

umount /initrd/dev/: 2

Kernel Panic: no syncing: Attempted to kill init !

This error occurred in your system before showing welcome redhat linux. That means problem in grub boot loader.

Restart the System

Check the grub boot loader configuration by pressing e shortcut key.

You will see like:

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root= / rhgb quiet

initrd /initrd-2.6.9-5.EL.img

OR

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/root rhgb quiet

initrd /initrd-2.6.9-5.EL.img

Then Edit Boot loader to make like

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet

initrd /initrd-2.6.9-5.EL.img

Check all lines and edit as same as above. Press b to boot the system

After booting the system you should correct the /etc/grub.conf file.

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

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?/dataext3defaults1 2

11. Verify by mounting on current Sessions also:

mount /dev/hda? /data

Quotas are used to limit a user's or a group of users' ability to consume disk space. This prevents a small group of users from monopolizing disk capacity and potentially interfering with other users or the entire system. Disk quotas are commonly used by ISPs, by Web hosting companies, on FTP sites, and on corporate file servers to ensure continued availability of their systems.

Without quotas, one or more users can upload files on an FTP server to the point of filling a filesystem. Once the affected partition is full, other users are effectively denied upload access to the disk. This is also a reason to mount different filesystem directories on different partitions. For example, if you only had partitions for your root (/) directory and swap space, someone uploading to your computer could fill up all of the space in your root directory (/). Without at least a little free space in the root directory (/), your system could become unstable or even crash.

You have two ways to set quotas for users. You can limit users by inodes or by kilobyte-sized disk blocks. Every Linux file requires an inode. Therefore, you can limit users by the number of files or by absolute space. You can set up different quotas for different filesystems. For example, you can set different quotas for users on the /home and /tmp directories if they are mounted on their own partitions.

Limits on disk blocks restrict the amount of disk space available to a user on your system. Older versions of Red Hat Linux included LinuxConf, which included a graphical tool to configure quotas. As of this writing, Red Hat no longer has a graphical quota configuration tool. Today, you can configure quotas on RHEL only through the command line interface.

1. vi /etc/fstab

/dev/hda11/dataext3defaults,usrquota 1 2

2. Either Reboot the System or remount the partition.

Mount –o remount /dev/hda11 /data

3. touch /data/aquota.user

4. quotacheck –ufm /data

5. quotaon -u /data

6. edquota –u user1 /data

and Specified the Soft limit and hard limit on opened file.

To verify either quota is working or not:

Soft limit specify the limit to generate warnings to users and hard limit can’t cross by the user. Use the quota command or repquota command to monitor the quota information.

To understand the role of a boot loader, take a step back from Linux. When you boot your computer, the BIOS starts by detecting basic hardware, including your hard drives. Once it's done, it looks for the boot loader on the Master Boot Record of the first available disk. If you're working with an older PC, the BIOS can't find your boot loader unless it's located within the first 1,024 cylinders of the hard disk.

Newer BIOSes overcome this problem with Logical Block Addressing, which is also known as LBA mode. LBA mode reads 'logical' values for the cylinder, head, and sector, which allows the BIOS to 'see' a larger disk drive.

If you have multiple hard drives, there is one more caveat. If your drives are IDE hard drives, the /boot directory must be on a hard drive attached to the primary IDE controller. If your drives are all SCSI hard drives, the /boot directory must be located on a hard drive with SCSI ID 0 or ID 1. If you have a mix of hard drives, the /boot directory must be located on either the first IDE drive or a SCSI drive with ID 0. In other words, this is not an issue on the Red Hat exams unless the computer that you're tested on has more than two hard drives. And I believe that's less likely, as that would increase the cost of the exam.

If you are getting the Kernel panic error, it means it is boot loader related problem. Redhat Enterprise Linux uses the GRUB boot loader. You can pass the kernel parameter from the boot loader as well as you can correct the kernel parameter passing from boot loader from GRUB screen at boot time.

GRUB boot loader configuration file is: /etc/grub.conf

And Correct Configuration is:

default=0

timeout=5

splashimage=(hd0,0)/grub/splash.xpm.gz

hiddenmenu

title Red Hat Enterprise Linux ES (2.6.9-5.EL)

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet

initrd /initrd-2.6.9-5.EL.img

Probably miss-configured the boot loader, so giving this problem. You can pass the correct parameter from GRUB prompt:

Table 3-3:GRUB Editing Commands

Command

Description

b

Boot the currently listed operating system

d

Delete the current line

e

Edit the current line

o

Create an empty line underneath the current line

O

Create an empty line above the current line

If you know all parameters and sequence of the boot loader you can enter in command prompt also.

Press c on GRUB screen.

Grub>root (hd0,0)

grub>kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet

grub>initrd /initrd-2.6.9-5.EL.img

grub>boot

Do the following steps as:

useradd user1

useradd user2

useradd user3

passwd user1

passwd user2

passwd user3

We create the user using useradd command and we change the password of user using passwd command. If you want to set the blank password use: passwd -d username.

According to question, log server is already configured. We have to configure the mail, web and dns server for log redirection.

In mail, web and dns server:

1.vi /etc/syslog.conf

mail.*@logserveraddress

2.service syslog restart

mail is the facility and * means the priority. It sends all logs of mail service to mail into log server.

Do the following steps as:

1.vi /etc/hosts.deny

sshd:ALL EXCEPT .example.com

or

1.vi /etc/hosts.deny

sshd:ALL

2.vi /etc/hosts.allow

sshd:.example.com

We can secure the services using tcp_wrappers. There are main two files, /etc/hosts.allow and /etc/hosts.deny.

There will be three stage access checking

- Is access explicitly permitted? Means permitted from /etc/hosts.allow?

- Otherwise, Is access explicitly denied? Means denied from /etc/hosts.deny?

- Otherwise, by default permit access if neither condition matched.

To deny the services we can configure /etc/hosts.deny file using ALL and EXCEPT operation. Pattern of /etc/hosts.allow and /etc/hosts.deny file is:

Demon_list:client_list:options

In Client list can be either domain name or IP address.

Note: In Exam Lab there will be two different domain example.com which is known as local domain and another is cracker.org which is called non trusted domain. So only from .example.com means allow only to example.com deny to every one.

Do the following steps as:

1.Open the Browser either firefox or links

2.Type :http://localhost:631

3.Click on Manage Printer

4.Click on Add Printer

5.Type Queue name like stationx and click on continue

6.Type Device type or printing Protocol: i.e Internet printing Protocol

7.Click on Continue

8.Type Device URL: ipp://server1.example.com/printers/printerx

9.Click on Continue

10.Select RAW Model printer

11.Click on Continue

12.Test by sending the printing job

While you load the X Window System, you will get the problem. Problem may caused by different error.

1.Check the /tmp is full ?

2.Check your quota, hard limit is already crossed ?

3.Check xfs service is running ?

4.Configure the Video card, Resolution, monitor type using: system-config-display (Most Probably in Redhat exam)

5.Edit the /etc/inittab to set default runlevel 5.

id:5:initdefault: