Lines Matching refs:dfn

121 @dfn{chaining} mechanisms can be a nightmare. There is little or no
172 using precalculated @dfn{block lists} (e.g. LILO), loading from a
173 special @dfn{boot partition} (e.g. OS/2), or even loading from within
224 @dfn{Multiboot header} (@pxref{OS image format}), which allows the boot
256 @table @dfn
258 We use the term @dfn{must}, when any boot loader or OS image needs to
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
277 to be @dfn{Multiboot-compliant}; earlier boot loader stages may be
292 @dfn{must} is Multiboot-compliant. When this specification specifies a
293 rule as @dfn{should} or @dfn{may}, a Multiboot-complaint boot loader/OS
347 An OS image must contain an additional header called @dfn{Multiboot
456 supposed to be loaded. This field serves to @dfn{synchronize} the
582 @dfn{normal working order}, i.e. as initialized by the @sc{bios} (or
597 physical address of a @dfn{Multiboot information} data structure,
673 determining its own @dfn{root} device, but is not required to. The
690 specifies the @dfn{top-level} partition number, @samp{part2} specifies a
691 @dfn{sub-partition} in the top-level partition, etc. Partition numbers
698 using BSD's @dfn{disklabel} strategy, then @samp{part1} contains the DOS
765 long) of an array of a.out format @dfn{nlist} structures, followed
890 returned by the @dfn{GET CONFIGURATION} @sc{bios} call. If the @sc{bios}
1054 original copies for the @dfn{clean @sc{bios} virtual machine} to be
1062 Create a @dfn{clean @sc{bios} virtual machine}.
1073 @dfn{restricted} I/O areas (hopefully, this will be an @dfn{xor}
1181 @dfn{Multiboot Standard} is renamed to @dfn{Multiboot Specification}.