Lines Matching full:loader
116 Every operating system ever created tends to have its own boot loader.
131 boot loader and a operating system, such that any complying boot loader
171 interpretation of specific file systems (e.g. the BSD/Mach boot loader),
189 how this configuration information is obtained by the boot loader, it
190 should provide a standard means for the boot loader to pass such
203 a boot loader, that is probably appropriate, because all the memory
204 consumed by the boot loader will typically be made available again after
208 switching code generally needs to be in the boot loader anyway in order
219 existence in order to load the OS image --- otherwise the boot loader
225 loader to load the image without having to understand numerous a.out
243 system and user if the boot loader can load these additional modules
247 loader to indicate to the operating system what auxiliary boot modules
258 We use the term @dfn{must}, when any boot loader or OS image needs to
259 follow a rule --- otherwise, the boot loader or OS image is @emph{not}
263 We use the term @dfn{should}, when any boot loader or OS image is
267 We use the term @dfn{may}, when any boot loader or OS image is allowed
270 @item boot loader
272 operating system to be run on the machine. The boot loader may itself
275 loader --- the stage that eventually transfers control to an operating
277 to be @dfn{Multiboot-compliant}; earlier boot loader stages may be
281 The initial binary image that a boot loader loads into memory and
286 Other auxiliary files that a boot loader loads into memory along with
291 A boot loader or an OS image which follows the rules defined as
293 rule as @dfn{should} or @dfn{may}, a Multiboot-complaint boot loader/OS
316 There are three main aspects of a boot loader/OS image interface:
320 The format of an OS image as seen by a boot loader.
323 The state of a machine when a boot loader starts an operating
327 The format of information passed by a boot loader to an operating
402 requires of an boot loader. Bits 0-15 indicate requirements; if the
403 boot loader sees any of these bits set but doesn't understand the flag
406 optional features; if any bits in this range are set but the boot loader
421 boot loader is capable of passing a memory map (the @samp{mmap_*} fields)
429 8-24 in the Multiboot header are valid, and the boot loader should use
470 If this field is zero, the boot loader assumes that the text and data
475 loader initializes this area to zero, and reserves the memory it
477 operating system in that area. If this field is zero, the boot loader
481 The physical address to which the boot loader should jump in order to
491 mode by the OS image. If the mode exists, the boot loader should set
493 boot loader should fall back to a similar mode, if available.
501 expansion. Note that the boot loader may set a text mode, even if this
524 When the boot loader invokes the 32-bit operating system, the machine
531 Multiboot-compliant boot loader (e.g. as opposed to another type of
532 boot loader that the operating system can also be loaded from).
536 information structure provided by the boot loader (@pxref{Boot
581 However, other machine state should be left by the boot loader in
583 DOS, if that's what the boot loader runs from). In other words, the
586 structures before doing so. Also, the boot loader must leave the
598 through which the boot loader communicates vital information to the
600 the structure as it chooses; all information passed by the boot loader
604 placed anywhere in memory by the boot loader (with the exception of the
654 be set to zero by the boot loader. Any set bits that the operating
670 loader loaded the OS image from. If the OS image was not loaded from a
705 nature. For example, if the boot loader boots from the second extended
745 set to 0 by the boot loader and ignored by the operating system.
865 loader. Currently, the following modes are defined:
895 loader booting the kernel. The name is a normal C-style zero-terminated
960 loader writers.
966 * Example boot loader code::
995 boot loader to work unmodified with any reasonable extensions of the
1092 Multiboot-compliant boot loader and for reference to how to implement a
1100 comply with the specification. When a Multiboot-compliant boot loader
1106 which checks if the magic number passed by the boot loader is valid and
1160 @node Example boot loader code
1161 @section Example boot loader code
1164 is a full Multiboot-compliant boot loader, supporting all required and
1188 loader, APM information, and graphics information are added to Multiboot
