GRUB Legacy vs GRUB 2

[KiaKya]

I think that many members must be knowing that the well-known Linux default boot manager GRUB goes to the second generation. Only the boot loader is in beta stage, but many distributions already use GRUB 2. Now question for me is that what is the difference between GRUB Legacy and GRUB 2. I have tried to search on web, found some differences but I think that there should be many more (just guessing). Since you members explain in details, I am posting here my doubt expecting that somebody over there will post some additional details about the GRUB Legacy and GRUB 2.

[Swetlano]

GRUB 2 has slowly but surely moving into the Linux derivatives. For example, using the current edition of the popular distribution Ubuntu, the latest edition of the GRUB boot loader. The second generation of the Grand Unified Boot Loader brings some new features. Unlike his predecessor GRUB Legacy of it ext4 file system can start. It also supports the latest issue from Booting LVM (Logical Volume Manager) and RAID -composites. In order to integrate the two aforementioned support, the module must be loaded via insmod. Furthermore, using GRUB 2 as the standard UUID (Universally Unique Identifier) to the root system to address. Also new is support for EFI (Extensible Firmware Interface), which is currently available for Mac users might be interesting before all things.

[Justvicks]

GRUB 2 does, in contrast to the previous stage is no longer 1.5. This was between the MBR and the first block of the first partition. The Stage 2 of GRUB 2 includes a kernel that only contains the necessary code. These include an ELF loader, disk access, a rescue shell and code for decompression. During the installation of GRUB 2 generates a module the file system in the file and compresses them for core.img usually means LZMA or LZO. This file is usually so small that they can put in the boot area behind the MBR. During the launch GRUB extract 2, the corresponding modules and loads the configuration file grub.cfg. Expert on the previous edition will be based on the last paragraph may already think that the just mentioned grub.cfg menu.lst file as configuration file replaces. Which is now grub.cfg control of the menu and is responsible for the GRUB-2 scripts generated automatically. Since GRUB partially modified commands used 2, the content can not simply copy the menu.lst and copy in grub.cfg. Edit this file to users in any case, since it is overwritten by any updates. Separate entries are in / etc/grub.d/40_custom land exclusively. With GRUB 2, it is now possible in a relatively simple way to embellish the boot menu to your preference. GRUB 2 supports Themes, which you can spice up the start menu. The responsible for that file can be found in / etc / default / grub.

[Michael25]

GRUB 2 supports Themes, which you can spice up the start menu. The responsible for that file can be found in / etc / default / grub.

All changes to the configuration files, the system only after the call to the command grub-mkconfig-o / boot / grub / grub.cfg. For example, work on Ubuntu, the command also update-grub and update-grub2. Other operating systems such as Microsoft Windows should automatically detect the bootloader menu and add to it. The current version of the Grand Unified Boot Loader can also be called as a payload for a free BIOS Alternative Core Boot use the name of the LinuxBIOS was developed earlier. In this case, GRUB 2 does not use the MBR of a disk but writes directly in the BIOS chip of the system. Coreboot initialized in this case, the hardware and then passes control to GRUB second If you install GRUB 2 from a live CD, so it's not difficult in principle. Take, for example, Ubuntu 9.10 "Karmic" and start in live mode. Then you can use a terminal and df-Th out more about which system is the partition. Include this example via mount to / media / tmp to. If you have a separate boot partition, you must also mount in this case to / media / tmp / boot via embed. Then you can boot loader grub-install --directory = / media / tmp / dev / sdX install root.

[Vitus]

The / etc / grub.d behaves essentially like the init directories under Linux. The scripts have a number followed by an underscore and a description. It works GRUB 2, these scripts sequentially after ascending numbering. As an example, the prober bootloader file 30_os-40_custom before calling. You can include your own scripts in separate files and thus will control itself, which is run when GRUB 2. Note that the file must be executable. This is done under Linux with the command chmod + x filename. To effectively make the changes, you must complete the command grub-mkconfig-o / boot / grub / call grub.cfg. GRUB 2 currently supports a simple password protection that can be encrypted, however. Anyone who has access to the computer and experience with Linux could gain the passwords in a simple manner. The GRUB users, however, differ from the users of the system and their passwords. Be warned however, that error setting password protection to a not booting system can result. This you would have to repair it, for example by means of a live CD.

[Shutdown]

If you still want to enable password protection one, you have super user in the / define a etc/grub.d/00_header. Then you can have as many users as you like. Just add in the aforementioned file set super users = "<Anwender1>" and then password <Anwender1> <Password> one. Another user of the line would you create password <Anwender2> <Passwort2> means. The superuser can run any menu item, and use the GRUB-2 command line. If this is done, then you define in the corresponding script files, which entries you share what users. See, for example in / etc/grub.d/10_linux the line that begins with menu entry and add before the brackets - User1 to users. Thus, only User1 should run this option. You can specifically control theory, which user is allowed to start what menu item. If you are the sole user, you can protect the system in general.