Anonymous user
I use a Custom Filesystem - What Bootloader Solution is right for me?: Difference between revisions
I use a Custom Filesystem - What Bootloader Solution is right for me? (view source)
Revision as of 01:53, 23 January 2017
, 7 years ago→What GRUB can do
| [unchecked revision] | [unchecked revision] |
mNo edit summary |
|||
Line 13:
* For Windows, a record is placed which indicates the partition Windows is installed on, and an instruction to ''chainload'' one sector (512 bytes) into RAM at 0x7C00, and jump to it; In other words, simply load the Windows bootloader into RAM as if it was placed there by the BIOS.
* For OSs that use EXT, ReiserFS, or other directly supported GRUB filesystems, you have the convenience of being able to ask GRUB to look into the partition and ''find'' your kernel file and load it into memory.
* For OSs that do ''not'' use a GRUB supported File system, the convention has been to simply ask GRUB to chainload the partition boot sector for your OSs partition and jump to it. However, using some logic, it is possible to avoid having to do anything whatsoever in real mode, or having to write a bootloader, even for a custom
=== The GRUB 'kernel' and 'chainloader' commands ===
Line 20:
* Simply take note of the fact that the user wants to set that partition as the root, or
* If the partition has a recognizable
When a partition is chosen as the root for GRUB's operations, there are two ways to load an executable image:
Line 29:
'''The 'chainloader' command:'''
The chainloader command loads an executable image of the assumed format 'binary' at 0x7C00 and jumps to the address 0x7C00.
== How may I use this information to ensure that GRUB can load an executable image off my custom FS? ==
| |||