Lines Matching full:load
151 GNU GRUB is a very powerful boot loader, which can load a wide variety
153 chain-loading@footnote{@dfn{chain-load} is the mechanism for loading
161 filesystems and kernel executable formats, so you can load an arbitrary
163 position of your kernel on the disk. Thus you can load the kernel
236 or above are presently supported. Any attempt to load below that
254 @item Load multiples modules
257 @item Load a configuration file
259 commands. You can also load another configuration file dynamically and
332 support. You can load OS images from a network by using the @dfn{TFTP}
587 one, you must chain-load GRUB from another boot loader. Refer to the
588 manual for the boot loader to know how to chain-load GRUB.
721 -boot-load-size 4 -boot-info-table -o grub.iso iso}
727 setup GRUB on the disc. (Note that the @kbd{-boot-load-size 4} bit is
739 GRUB can load Multiboot-compliant kernels in a consistent way,
753 GRUB has two distinct boot methods. One of the two is to load an
754 operating system directly, and the other is to chain-load another boot
755 loader which then will load an operating system actually. Generally
758 load an operating system from an arbitrary disk/partition. However,
775 will have to chain-load them (@pxref{Chain-loading}).
786 Load the kernel image with the command @command{kernel} (@pxref{kernel}).
789 If you need modules, load them with the command @command{module}
797 manner. You load a kernel image with the command @command{kernel} and
805 @subsection Load another boot loader to boot unsupported operating systems
808 chain-load a boot loader for the operating system. Normally, the boot
831 Load the boot loader with the command @command{chainloader}
882 Load the kernel and the module, like this:
908 Load the kernel:
946 GRUB can load the kernel directly, either in ELF or a.out format. But
966 GRUB can load NetBSD a.out and ELF directly, follow these steps:
973 Load the kernel with @command{kernel} (@pxref{kernel}). You should
974 append the ugly option @option{--type=netbsd}, if you want to load an
986 it may be better to chain-load it instead. For more information, please
1000 GRUB cannot boot DOS or Windows directly, so you must chain-load them
1002 deficiencies, so it may not work to just chain-load them. To overcome
1517 to load a configuration file from the network, if specified. The usage
1521 formats. Since the way to load a second stage image you want to use
1717 In this case, GRUB will load @file{/boot/grub/menu-admin.lst} as a
1764 All @file{stage1} must do is to load Stage 2 or Stage 1.5 from a local
2218 fetch and load a configuration file specified by your BOOTP server
2339 fetch and load a configuration file specified by your DHCP server
2664 * chainloader:: Chain-load another boot loader
2666 * configfile:: Load a configuration file
2677 * initrd:: Load an initrd
2680 * kernel:: Load a kernel
2685 * module:: Load a module
2686 * modulenounzip:: Load a module without decompression
2695 * testload:: Load a file for testing a filesystem
2738 Load @var{file} as a chain-loader. Like any other file loaded by the
2741 option @option{--force}, then load @var{file} forcibly, whether it has a
2742 correct signature or not. This is required when you want to load a
2773 Load @var{file} as a configuration file.
2903 Load an initial ramdisk for a Linux format boot image and set the
2921 In slightly more detail, it will load @var{stage1_file}, validate that
2980 Attempt to load the primary boot image (Multiboot a.out or @sc{elf},
2990 load a NetBSD @sc{elf} kernel, because GRUB can automatically determine
3036 necessary when you chain-load some operating systems, such as DOS, if
3065 Load a boot module @var{file} for a Multiboot format boot image (no
3069 @command{kernel} command. You must load a Multiboot kernel image before
3419 This error is returned if the module load command is used before loading
3457 This error is returned if a kernel, module, or raw file load command is
3458 either trying to load its data such that it won't fit into memory or it
