The mapping is necessary before chainloading TrueCrypt bootloader in the case that the boot disk (hd1 as shown in the example above) should appear as the primary boot device (hd0), otherwise TrueCrypt would fail to boot because the correct disk will not be found.Ĭhainloading a disk with TrueCrypt in the MBR or a rescue CD image located in encrypted partitions is not possible with GRUB2 (see bug #385619). The remapping may not be necessary if the system has a single boot disk. To chainload an ISO with custom or default kernel command line arguments, an entry similar to the following can be added to GRUB2's grub.cfg file: No more need to listen to a whining CD/DVD drive on each new command!
#Grub2 windows 10 install
This makes it possible to have a handy way to install an operating system with everything in RAM, especially for "light weight" LiveCDs. Gentoo liveCD is handy because it has a minimal shell which lets the user mount the squashed image to the correct location and then press the Esc key to continue the boot process. Without kernel cmdline options, booting ISO images with GRUB2 will fail in the physical media check/test stage of the ISOs boot process. In any case, the ISO images in question should be built keeping kernel cmdline arguments in mind.
It is possible to chainload ISO images (LiveCD/DVDs) with GRUB Legacy, however there exists no way to pass kernel cmdline arguments before boot. The new ISO (or loop) chainload mechanism makes chainloading a breeze.
0 kommentar(er)
