Lines Matching refs:OS
108 * Network:: Downloading OS images from a network
171 interface, you just select an OS using the arrow keys. The menu is
229 Linux. Proprietary kernels (such as DOS, Windows NT, and OS/2) are
332 support. You can load OS images from a network by using the @dfn{TFTP}
468 from the source tarball, or as a package for your OS.
473 grub-install}) on a UNIX-like OS, or by running GRUB itself from a
477 Also, if you install GRUB on a UNIX-like OS, please make sure that you
527 The device file name may be different. Consult the manual for your OS.
534 normal boot-sector used by an OS.
552 your OS's root partition; if you need to specify a root partition for
553 your OS, add the argument into the command @command{kernel}.} to the
601 map BIOS drives to OS devices correctly---GRUB merely @dfn{guesses}
607 If you still do want to install GRUB under a UNIX-like OS (such
664 correctly under a UNIX-like OS. Thus, @command{grub-install} will prompt
675 boot loader on a running OS may be extremely dangerous.
740 but for some free operating systems you need to use some OS-specific
745 * OS-specific notes:: Notes on some operating systems
769 @subsection How to boot an OS directly with GRUB
777 Generally, GRUB can boot any Multiboot-compliant OS in the following
782 Set GRUB's root device to the drive where the OS images are stored with
800 file name of the kernel. Also, please refer to @ref{OS-specific notes},
801 for information on your OS-specific issues.
851 @node OS-specific notes
852 @section Some caveats on OS-specific issues
900 resembles to boot a Multiboot-compliant OS.
1006 have to use the disk swapping technique, because that OS cannot boot
1021 to access the swapped disks. If that OS uses a special driver for the
1084 When you test a new kernel or a new OS, it is important to make sure
1101 The former requirement is very specific to each OS, so this
1263 OS. There's a solution to that - GRUB provides a menu interface
1265 keys) that will do everything to boot an OS.
1321 Now, on to the actual OS definitions. You will see that each entry
1384 # For booting OS/2
1385 title OS/2
1388 # chainload OS/2 bootloader from the first sector
1395 This will boot OS/2, using a chain-loader (@pxref{Chain-loading}).
1438 @chapter Downloading OS images from a network
1481 Finally, download your OS images from your network. The network can be
1726 entry for booting an insecure OS like DOS.
1822 device is equivalent to which OS device. Normally, that will be clear if
2304 title OS-BS like
2718 Boot the OS or chain-loader which has been loaded. Only necessary if
2729 to remind you of your OS's root partition:
3040 such an OS resides at a non-first drive. Here is an example:
3147 partition. This is useful for when an OS is outside of the area of the
3247 also be used for debugging purposes to lie to an OS.
3501 BIOS drives and OS devices.
3506 * Device map:: The map between BIOS drives and OS devices
3632 @section The map between BIOS drives and OS devices
3639 drives to OS devices. This file consists of lines like this:
3646 syntax}), and @var{file} is an OS file, which is normally a device
3650 cannot guess the map between BIOS drives and OS devices correctly in
3670 The device name @var{install_device} is an OS device name or a GRUB
3918 @samp{The foo OS crashes with GRUB, even though it can boot with the