- Home
- Server Administration
- LPIC-2 Linux Engineer 201
6.
What file would you edit to add an unusual operating system to a GRUB 2 boot menu?
- A./boot/grub/custom
- B./boot/grub/menu.lst
- C./etc/grub.d/40_custom
- D./boot/grub/grub.conf
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
| When a system uses GRUB 2, system administrators are encouraged to edit /etc/grub .d/40_custom to add custom GRUB configurations for locally compiled kernels or unusual OSs. After making such a change, you should type update - grub to update the GRUB run - time configuration file, /boot/grub/grub.cfg . Option A is a fictitious file. Options B and D are two names for the GRUB Legacy configuration file; editing them has no effect on GRUB 2. |
7.
The following line is present in a Linux computer's /etc/inittab file. What can you say
about it?
id:3:initdefault:
id:3:initdefault:
- A.The computer boots into runlevel 3.
- B.The computer starts in text mode (X isn't run).
- C.The computer shuts down as soon as it boots.
- D.The computer uses the Upstart startup system.
- Answer & Explanation
- Report
Answer : [A]
Explanation :
Explanation :
| The id line in /etc/inittab specifies the default runlevel, which in this example is 3, as specified in option A. Although runlevel 3 is a text - mode - only runlevel on Red Hat and related distributions, as option B specifies, this isn't true of all distributions; Debian, Ubuntu, Gentoo, and others control the startup of X in ways other than by the default runlevel. Thus, option B is not a correct answer. Option C describes the effect of setting the default runlevel to 0, not to 3, so it is incorrect. The /etc/inittab file is a standard part of the SysV startup system, and it's present on some Upstart - based systems. Thus, the presence of this file, or the presence of the specified line in this file, is not diagnostic of an Upstart - based system, and option D is incorrect. |
8.
What might you find in the /etc/init.d directory?
- A.Upstart startup scripts
- B.SysV startup scripts
- C.User login scripts
- D.System login scripts
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| The /etc/init.d directory holds SysV startup scripts on many Linux systems, as option B specifies. Upstart startup scripts reside in /etc/init or /etc/event.d , so option A is incorrect. User login scripts are stored in the users'home directories under various names, so option C is incorrect. System login names reside in /etc or subdirectories of it, usually under names related to the shell, but not in /etc/init.d , so option D is incorrect. |
9.
Where might you find runlevel - specific symbolic links to SysV startup scripts? (Choose all
that apply.)
- A./etc/inittab
- B./etc/init
- C./etc/init.d/rc ? .d
- D./etc/rc ? .d
- Answer & Explanation
- Report
Answer : [C, D]
Explanation :
Explanation :
| Options C and D both specify directories where runlevel - specific symbolic links to SysV startup scripts may reside (the ? is a stand - in for a runlevel number), depending on the distribution in use. The /etc/inittab file is the configuration file for init in the SysV startup system, but it doesn't hold symbolic links, so option A is incorrect. The /etc/init directory holds Upstart scripts on Upstart - based systems, not SysV startup scripts or links to them, so option B is incorrect. |
10.
You want to check the configuration of a server called waiter on a Fedora system, to see in
which runlevels it runs. What might you type to do this?
- A.chkconfig - - list waiter
- B.info waiter
- C.ps ax | grep waiter
- D.runlevel waiter
- Answer & Explanation
- Report
Answer : [A]
Explanation :
Explanation :
| The chkconfig command displays information on or modifies the status of services started by SysV startup scripts. The - - list option displays the status of a service by the specified name, so option A does as the question asks. The info command is a system documentation tool; option B displays the info page, if it's present, for the waiter command, which is not what the question asks. Option C displays process information on any processes called waiter or that include the string waiter in the command line. This won't reveal in what runlevels these processes run, so option C is incorrect. The runlevel command displays the current and previous runlevel, but it won’t tell you in which runlevels a particular program runs, so option D is incorrect. |
|
|
||||||||||||||||||||||||||||
