- Home
- Server Administration
- LPIC-1 Linux Administrator 101
81.
Where might the BIOS find a boot loader?
- A.RAM
- B./dev/boot
- C.MBR
- D./dev/kmem
- E.The swap partition
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
| The Master Boot Record (MBR) can contain a boot loader that is up to 446 bytes in size, so option C is correct. If more space is required, the boot loader must load a secondary boot loader. Although the boot loader is loaded into RAM (option A), it’s not stored there permanently because RAM is volatile storage. Both /dev/boot and /dev/kmem (options B and D) are references to files on Linux filesystems; they’re meaningful only after the BIOS has found a boot loader and run it and lots of other boot processes have occurred. The swap partition (option E) is used as an adjunct to RAM; the BIOS won’t look there for a boot loader. |
82.
You want to boot a Linux system into single-user mode. What option might you add to a
Linux kernel’s options list at a boot loader to accomplish this task?
- A.one
- B.single-user
- C.1
- D.telinit 6
- E.telinit 1
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
83.
After booting, one of your hard disks doesn’t respond. What might you do to find out
what’s gone wrong?
- A.Check the /var/log/diskerror log file to see what’s wrong.
- B.Verify that the disk is listed in /mnt/disks.
- C.Check the contents of /etc/inittab to be sure it’s mounting the disk.
- D.Type dmesg | less, and peruse the output for disk-related messages.
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
| The kernel ring buffer, which can be viewed by typing dmesg (piping this through less is a good supplement), contains messages from the kernel, including those from hardware drivers. These messages may provide a clue about why the disk didn’t appear; thus, option D is correct. The /var/log/diskerror file (option A) is fictitious, as is /mnt/disks (option B). The /etc/inittab file (option C) doesn’t directly control disk access and so is unlikely to provide useful information. The files specified in option C are GRUB Legacy and GRUB 2 configuration files, which don’t contain information that could explain why a disk isn’t responding. |
84.
What is the first program that the Linux kernel runs once it’s booted in a normal boot process?
- A.dmesg
- B.init
- C.startup
- D.rc
- E.lilo
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| Ordinarily, Linux runs init (option B) as the first program; init then runs, via various scripts, other programs. The dmesg program (option A) is a user diagnostic and information tool used to access the kernel ring buffer; it’s not part of the startup process. The startup program (option C) is fictitious. The rc program (option D) is a script that some versions of init call, typically indirectly, during the startup sequence, but it’s not the first program the kernel runs. LILO is an older boot loader for Linux on BIOS systems, and lilo (option E) is the command that installs this boot loader to the MBR. Since boot loaders run before the kernel loads, this option is incorrect. |
85.
Which of the following is the GRUB 2 boot loader configuration file?
- A./dev/grub
- B.The MBR
- C./boot/grub/grub.conf
- D./boot/grub/grub.cfg
- E./boot/grub/menu.lst
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
| Option D is the correct GRUB 2 configuration file. Option A is a fictitious file; it doesn’t exist. Although some of GRUB 2’s boot loader code may be written to the MBR, as implied by option B, this isn’t the location of the program’s configuration file. Options C and D are both possible names for the GRUB Legacy configuration file, but that name is not shared by GRUB 2. |
|
|
||||||||||||||||||||||||||||
