Grub.conf generated by anaconda

  1. Home
  2. /
  3. Pendidikan
  4. /
  5. Grub.conf generated by anaconda
Grub.conf generated by anaconda

Grub.conf generated by anaconda

Posted in : Pendidikan on by : admin

Grub.conf generated by anaconda

Grub.conf generated by anaconda

Grub.conf generated by anaconda

# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a / boot partition. This means that
# All kernel and initrd paths are relative to / boot /, eg.
# Root (hd0, 0)
# Kernel / vmlinuz-version ro root = / dev/hda5
# Initrd / initrd-version.img
# boot = / dev / hda
Default = 0
timeout = 10
splashimage = (hd0, 0) / grub / splash.xpm.gz
title Red Hat Linux (2.4.7-10)
root (hd0, 0)
kernel / vmlinuz-2.4.7-10 ro root = / dev/hda5
initrd / initrd-2.4.7-10.img

The file is created during installation with Anaconda Installer from Red Hat 7.2.
If all goes well, you can load your Linux distribution with a GRUB bootdisk. GRUB is the boot loader should be calculated, because you can dynamically configure / change according to your wishes. Furthermore, the authors show how to create Loader GRUB menu of your typing 3 GRUB command line. But before that let us deepen our knowledge about the workings of GRUB.

How to Work GRUB
To set up the boot floppy, we do 2 things, we first copy 2 files from the directory / usr/share/grub/i386-redhat / to / boot / grub / floppy that berfilesystem ext2 and run the setup program from GRUB.
grub> setup (fd0)
Install GRUB loader “stage1” to the boot record on floppy and also configure the “stage1” to mengload to “stage2” directly from the ext2 file system. GRUB actually do this by creating a list that consists of blocks to the floppy containing data “stage2”. So “stage1” does not need to know anything about the ext2 filesystem to load “stage2”.
However, in some cases, installing the GRUB loader “stage1.5” to boot record after installing a “stage1.” Loader “stage1.5” This will create a special “stage2” can be in loads without using a blocklist ancient / long (primitive blocklist), but by using standard-based approach to the path that is more flexible. This ability of the GRUB to identify the structure of the filesystem directly, which can make GRUB powerfull more than LILO. If there Defraksi on file at the bootdisk, directly, stage1 (owing to the ext2 stage1.5) can find stage2. This can not be done by LILO, because LILO is depending on the file folder. This map files must be re-run every time you update your kernel, or move something physical / rough on the disk, although the paths are not changed.
You will be amazed at the same time wonder if you made bootdisk with the FAT file system other than the ext2 file system. Yes! it can be done, because when we run the “setup (fd0)” GRUB will menginstallkan “stage1.5” in accordance with the type of file in the root. Even if there is no place for “stage1.5,” GRUB can load stage2 with the way the approach to turn the ancient block-list.

Installing GRUB on the hard drive
Now we have to make bootdisk floppy GRUB, what if we want to menginstallnya in the hard disk? How very simple, we first determine where the root GRUB placed, and then create the directory / boot / grub / GRUB on the root partition. Remember the root of GRUB is not defined with the same root partition on Linux. Then copy the files stage1 and stage2 to the directory / boot / grub /. For example, if the directory / boot / grub / placed / dev/hda4 the root set to “(hd0, 3)”
grub> root (hd0, 3)
Now, living decided whether GRUB will be placed in the MBR? If yes, then put GRUB in the entire disk without partition, as for example in hd0 (/ dev / hda), then run the following command:
grub> setup (hd0)
If you menginstallnya in other partitions, living mentioned in the partition where, for example, on the partition hda5,
grub> setup (hd0, 4)
Now GRUB has been installed. If you memboot system then you will exit the GRUB console display (If you put them in the MBR) as the example above, we now live make a boot menu so that you do not type the command line per line at the top.

Making the GRUB menu
To make the GRUB boot menu, we only make a plain text file named menu.lst and in place in the directory / boot / grub / files between stage1 and stage1, following the example files menu.lst.
Default = 0
timeout = 10
splashimage = (hd0, 0) / grub / splash.xpm.gz
title Red Hat Linux (2.4.7-10)
root (hd0, 0)
kernel / vmlinuz-2.4.7-10 ro root = / dev/hda5
initrd / initrd-2.4.7-10.img

Windows 2000 title
root (hd0, 3)
chainloader 1

In Red Hat 7.2, the files in menu.lst-link to grub.conf.
The following explanation file GRUB boot menu at the top:
The first line, Default boot which will be run (starting from 0 next 1, 2 and so on). The second line, choose the time, if by the time of the set, the default will be selected. The third line (splashimage) to display the boot loader such wallpaper, which can also be replaced with the “color” according to taste, for example:
color white / blue blue / red
The display will drape the GRUB menu.
The next line is the Boot Linux, in accordance with the parameters of-its parameters, the root partition and so forth … Also can use initrd (initial root disk).
The last line, is working with chainloader memboot (boot record) Windows 2000 on its own partition hda2 and membootnya. This is called a chain lifting with the techniques, GRUB will load to the partition boot record that it’s correct and memboot system from there. These techniques work well in Windows and DOS versions of what.
You do not need to re-install GRUB to update the kernel / replace the new version of the kernel or change the location of your partition. You only need to change the file menu.lst. Only if there are some conditions in the GRUB need to re-install, if you will first replace the root filesystem on the GRUB, for example, from ext2 to reiserfs, the second replaces the file if stage1 and stage2 to the latest version.

Sumber : https://anchorstates.net/