Feedback
Home
You may like this!
46.
You attempt to boot your computer but get only a grub > prompt. You then type the following command and receive the response shown:
grub > ls
(hd0) (hd0,1)
Where is your Linux kernel most likely to be found?
  • A.
    On /dev/hda0
  • B.
    On /dev/hd0
  • C.
    On /dev/sd0
  • D.
    On (hd0,1)
  • Answer & Explanation
  • Report
Answer : [D]
Explanation : The output of the GRUB ls command reveals that GRUB can see one whole hard disk, which it identifies as (hd0) , and that this disk has one partition, which GRUB identifies as (hd0,1) . Thus, there's one possible location for the Linux kernel: (hd0,1) . This partition probably corresponds to Linux's /dev/sda1 , but it could be /dev/hda1 or some other device. Options A, B, and C all describe non - standard Linux device descriptors, so none of them is a likely location for the kernel. The problem that caused GRUB to display its grub > prompt could be serious enough that GRUB is failing to detect a hard disk; thus, the kernel could reside elsewhere. Given the provided information, though, option D is the single most likely location and is the only possible location among those specified.
Report
Name Email  
47.
What normally resides in /etc/init.d , if it's present on the Linux computer?
  • A.
    Upstart configuration files
  • B.
    Boot loader configuration files
  • C.
    SysV startup scripts
  • D.
    The BIOS configuration utility
  • Answer & Explanation
  • Report
Answer : [C]
Explanation :
Most Linux distributions place SysV startup scripts in /etc/init.d or /etc/rc.d/ init.d , so option C is correct. Upstart configuration files normally reside in /etc/init , so option A is incorrect. Linux boot loader configuration files normally reside in /etc/ lilo.conf , /boot/grub , or /boot/grub2 , depending on the boot loader in use, so option B is incorrect. The BIOS configuration utility is built into the computer's hardware, so it's not accessible from the Linux filesystem at all, making option D incorrect.
Report
Name Email  
48.
You've compiled a new kernel and created a new GRUB 2 configuration for it. Just after you reboot, however, you realize that you mistyped the filename of the new kernel in the GRUB configuration file. How can you boot the new kernel despite this error?
  • A.
    Select the almost - correct entry from the GRUB menu, and type E to edit it.
  • B.
    Select the Create Entry option from the GRUB menu to create a new entry.
  • C.
    Select the Auto - Detect OSs entry from the GRUB menu to detect your new kernel.
  • D.
    You can't.
  • Answer & Explanation
  • Report
Answer : [A]
Explanation :
You can edit a GRUB 2 menu entry by selecting it and typing E, as described in option A. You will, however, have to know exactly what your error was or be able to use the GRUB shell to locate the exact filename. The GRUB interactive menu doesn't have a Create Entry or Auto - Detect OSs option, making options B and C incorrect. Since option A is correct, option D can't be correct.
Report
Name Email  
49.
You install Linux on a computer with a single SATA disk and used GRUB 2 to boot it. In experimenting with disk utilities, you accidentally overwrite GRUB's MBR entry. You use Super GRUB Disk to boot into your normal Linux installation. How can you re - install GRUB to the MBR so that you can boot normally without using Super GRUB Disk in the future?
  • A.
    Edit /boot/mbr/contents as root .
  • B.
    Type mbr - restore /dev/sda as root
  • C.
    Type grub - install /dev/sda as root .
  • D.
    Edit /boot/grub/grub.cfg as root .
  • Answer & Explanation
  • Report
Answer : [C]
Explanation :
The grub - install utility installs GRUB to the MBR or to other locations specified in the GRUB configuration file or on the command line, so option C is correct. There is no /boot/mbr/contents file or mbr - restore utility, so options A and B are both incorrect. Although /boot/grub/grub.cfg is GRUB 2's configuration file, the fact that Super GRUB Disk was able to boot the computer means that this file is intact enough to boot Linux, so it doesn't need to be edited. Furthermore, editing this file would not correct the damage to the MBR, so option D is incorrect.
Report
Name Email  
50.
You want to examine the kernel ring buffer to debug a hardware problem. How would you do this?
  • A.
    Type ringbuffer at a command prompt.
  • B.
    Type dmesg at a command prompt.
  • C.
    Reboot and add the string ring to the kernel line in GRUB.
  • D.
    Install a Token Ring device and examine its output.
  • Answer & Explanation
  • Report
Answer : [B]
Explanation :
The dmesg command displays the contents of the kernel ring buffer, which holds kernel messages, so option B is correct. There is no standard ringbuffer command, so option A is incorrect. Adding ring to the kernel options when booting will not have the desired effect, so option C is incorrect. Token Ring is a network hardware standard, not a way to examine the kernel ring buffer, so option D is incorrect.
Report
Name Email  
 
  © 2024 infibee.com. All Rights Reserved.   Copyright | Privacy Policy | Sitemap  
Contact us on : info@infibee.com  
 
 
Share   Facebook   Twitter   Google +   Digg