Lines Matching refs:dfn

145 Briefly, a @dfn{boot loader} is the first software program that runs when
147 control to an operating system @dfn{kernel} software (such as Linux or
153 chain-loading@footnote{@dfn{chain-load} is the mechanism for loading
182 Besides the GRUB boot loader itself, there is a @dfn{grub shell}
215 @dfn{Multiboot Specification}, which is described in @ref{Top, Multiboot
234 @dfn{piggyback} format), all kernels will be started in much the same
246 Support many of the @dfn{a.out} variants plus @dfn{ELF}. Symbol
285 @dfn{BSD FFS}, @dfn{DOS FAT16 and FAT32}, @dfn{Minix fs}, @dfn{Linux
286 ext2fs}, @dfn{ReiserFS}, @dfn{JFS}, @dfn{XFS}, and @dfn{VSTa
321 In traditional disk calls (called @dfn{CHS mode}), there is a geometry
326 have the new interface, Logical Block Address (@dfn{LBA}) mode. GRUB
332 support. You can load OS images from a network by using the @dfn{TFTP}
410 This specifies the first @dfn{extended partition} of the first hard disk
489 called the @dfn{image directory}, and the directory where the boot
491 the @dfn{boot directory}.
550 (@pxref{Command-line interface}). First, set the GRUB's @dfn{root
601 map BIOS drives to OS devices correctly---GRUB merely @dfn{guesses}
604 @dfn{device map}, which you must fix if it is wrong. @xref{Device
609 grub-install}) as the superuser (@dfn{root}).
681 GRUB supports the @dfn{no emulation mode} in the El Torito
809 loader is embedded in the @dfn{boot sector} of the partition on which
822 Set the @dfn{active} flag in the partition using the command
1017 This performs a @dfn{virtual} swap between your first and second hard
1030 If GRUB @dfn{hide}s a DOS (or Windows) partition (@pxref{hide}), DOS (or
1031 Windows) will ignore the partition. If GRUB @dfn{unhide}s a DOS (or
1098 fails. This is possible with the @dfn{fallback} system in GRUB.
1171 use the @dfn{fallback} mechanism of GRUB. Look at next subsection for
1611 GRUB supports a @dfn{preset menu} which is to be always loaded before
1684 Thus, GRUB provides a @dfn{password} feature, so that only administrators
1757 called @dfn{Stage 1.5}, one image for bootable CD-ROM, and two network
1785 These are called @dfn{Stage 1.5}, because they serve as a bridge
1799 This is a boot image for CD-ROMs using the @dfn{no emulation mode} in
1883 There are two ways to specify files, by @dfn{absolute file name} and by
1884 @dfn{block list}.
1891 GRUB's @dfn{root device} implicitly. So if you set the root device to,
1913 does not contain a device name, then GRUB uses GRUB's @dfn{root
1927 entries were found in the file. If you choose the @dfn{command-line} menu
2015 Basically, the menu interface provides a list of @dfn{boot entries} to
2024 edit any of the @dfn{boot entries} by pressing @key{e}.
2052 does not support @dfn{undo}, you can do almost the same thing by just
2216 Initialize a network device via the @dfn{BOOTP} protocol. This command
2336 Initialize a network device via the @dfn{DHCP} protocol. Currently,
2351 Hide the partition @var{partition} by setting the @dfn{hidden} bit in
2422 Initialize a network device via the @dfn{RARP} protocol.  This command
2649 Unhide the partition @var{partition} by clearing the @dfn{hidden} bit in
2804 @dfn{upper/lower memory} display uses the standard BIOS interface for
2805 the available memory in the first megabyte, or @dfn{lower memory}, and a
2807 at 1MB and going up to the first chipset hole for @dfn{upper memory}
2808 (the standard PC @dfn{upper memory} interface is limited to reporting a
2818 @var{device} is a drive, or in the @dfn{boot loader} area if @var{device}
2985 @var{file}. The rest of the line is passed verbatim as the @dfn{kernel
3071 line is passed as the @dfn{module command-line}, like the
3127 Set the current @dfn{root device} to the device @var{device}, then
3199 current @dfn{root device}, which can be set by the command
3581 The installation procedure is the same as under the @dfn{native} Stage
3585 What you should be careful about is @dfn{buffer cache}. @command{grub}
3635 the grub shell creates the @dfn{device map file} automatically unless it
3691 you have a separate @dfn{boot} partition which is mounted on