Skip to main content

Explain the GRUB configuration file.

19.Explain the GRUB configuration file.
Ans.
1. When the system boots, GRUB presents a graphical screen showing the operating systems that we can boot.

2. The ‘/boot/grub/grub.conf’ file controls what information is displayed on the graphical screen, the file even controls whether you see the graphical screen at all.

3. All lines in grub.conf file begins with a # symbol (hash character) are comments and will be ignored, GRUB also ignores blank lines.

4. The lines following the lines beginning with hash character and before the line beginning with the title are the menu interface command that GRUB uses to display the menu.
These lines have the following meaning:

5. ‘default=0’ – This  command tells GRUB to boot the first listing beginning with title, if we can set this number to 1 to boot the second entry.

6. ‘timeout=5’ – This command tells GRUB to boot the default entry after five seconds to change the time increase or decrease the number as desired.

7. ‘splashimage=(hd0,0)/grub/splash.xpm.gz’ – This command tells GRUB where to look for the splash image, it displays for the menu, we can create our own image.

8. ‘hiddenmenu’ – This command tells GRUB not to display the menu and to boot the default after the timeout expires, we can still see the menu by pressing any key.

9. ‘title’ – This command tells GRUB to list a boot name on the menu using the name following the title command, the line follows the title are explained as follows:

10. ‘root(hd0,0)’ – This line tells the GRUB to boot the system from  the first partition of the first hard drive.

11. ‘kernal…’ – This line tells GRUB the location of the kernel, as well as passes the kernel parameters to the kernel. If we want to pass kernel parameters to the kernel before it loads, this is the line to add them up.

12. ‘initrd…’ – This line tells GRUB the location of the initial ramdisk image that is used to load special drivers for the system.


Comments

Popular posts from this blog

Explain the backing up and restoring files in Linux.

9.Explain the backing up and restoring files in Linux. Ans. 1. Backing-up and restoring files is done only by system administrator. 2. Because of built-in features, Linux doesn’t allow users to back-up their own files to removable disks. 3. It’s not enough to know that performing backup is your job, you need to formulate a strategy to making sure your system is not vulnerable to sudden disastrous disruptions. 4. If you have a high capacity tape drive and several good set of restore disks you can take backup every few days. 5. If you are managing a system with scores of users, you might find it more sensible to back up accounts and system configurations. 6. Only you can decide ‘what’ to backup, you need to decide ‘how frequently’ to perform backups, whether to maintain series of incremental backup. 7. You should maintain perfect backups without ever needing to restore to them, this means encouraging users to keep multiple copies of their important files in their ho...

Explain the file systems supported by Linux.

21.Explain the file systems supported by Linux. Ans. 1. Linux can read/write to several file system that originated with other operating system much different from Linux. 2. One reason that Linux supports so many file systems is the design of its virtual file system (VFS) layer, its provides a fairly universal forms of file support, file systems supported by Linux are as follows: 3. ext3: • Ext3 stands for third extended file system. • Starting from Linux Kernel 2.4.15 ext3 was available. • The main benefit of ext3 is that it allows journaling. • Journaling has a dedicated area in the file system, where all the changes are tracked. • When the system crashes, the possibility of file system corruption is less because of journaling. (If no journaling, then fsck command (file system consistency check) is used to check for the corrupted file and to repair that file). • ext3 keeps a record of uncommitted file transactions and applies only those transactions when the sy...

Explain the rc script and how they can be managed by manually.

18.Explain the rc script and how they can be managed by manually. Ans. 1. ‘rc’ scripts are stored in ‘/etc/rc.d’ directory, rc scripts are used to stop and start services for runlevels. 2. In ‘/etc/rc.d’ directory we have some additional directories rc0.d, rc1.d, rc2.d, rc3.d, rc4.d, rc5.d and rc6.d, the numbers in directory name corresponds to the runlevel and contains the scripts for runlevels. 3. For example let’s take runlevel 5, init program looks in the ‘/etc/rc.d/rc5.d/’ directory for the processes to start and stop. 4. All the scripts in the rc5.d directory are symbolic like to the actual scripts that are located in the ‘/etc/rc.d/init.d/’ directory. The use of symbolic link means that the runlevel can be modified by adding or removing symlinks or changing the order the script run. 5. rc scripts contains symbolic links which can be modified to change the runlevels. 6. Symbolic links begins with a ‘k’ and a number or an ‘s’ and a number. Example: S25netfs -...