Lines Matching refs:GRUB
5 * GRUB: (grub). The GRand Unified Bootloader
6 * grub-install: (grub)Invoking grub-install. Install GRUB on your drive
35 GRUB manual
38 This is the documentation of GNU GRUB, the GRand Unified Bootloader,
45 * Introduction:: Capturing the spirit of GRUB
46 * Naming convention:: Names of your drives in GRUB
47 * Installation:: Installing GRUB on your drive
51 * Serial terminal:: Using GRUB via a serial line
52 * Preset Menu:: Embedding a configuration file into GRUB
54 * Images:: GRUB image files
58 * Troubleshooting:: Error messages produced by GRUB
60 * Invoking grub-install:: How to use the GRUB installer
65 * Obtaining and Building GRUB:: How to obtain and build GRUB
67 * Future:: Some future plans on GRUB
68 * Internals:: Hacking GRUB
74 Introduction to GRUB
79 * Overview:: What exactly GRUB is and how to use it
81 * Features:: GRUB features
96 GNU GRUB is a very powerful boot loader, which can load a wide
98 systems with chain-loading(1) (*note Overview-Footnote-1::). GRUB is
103 One of the important features in GRUB is flexibility; GRUB
110 When booting with GRUB, you can use either a command-line interface
120 partition, and a file name (*note Naming convention::) to GRUB, how to
121 install GRUB on your drive (*note Installation::), and how to boot your
124 Besides the GRUB boot loader itself, there is a "grub shell" `grub'
139 History of GRUB
142 GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU
152 FreeBSD boot loader, and so GRUB was born.
154 Erich added many features to GRUB, but other priorities prevented him
156 1999, Gordon Matzigkeit and Yoshinori K. Okuji adopted GRUB as an
159 GRUB::, for more information.
164 GRUB features
167 The primary requirement for GRUB is that it be compliant with the
188 In addition to the requirements above, GRUB has the following
190 features that GRUB supports):
207 and embed a preset configuration file in a GRUB image file. The
222 GRUB drops to the command-line.
255 Unlike many other boot loaders, GRUB makes the particular drive
258 adverse effects or changes in GRUB's configuration.
261 GRUB can generally find all the installed RAM on a PC-compatible
265 use of this information, but GRUB provides it for those who do.
271 and to at most 8GB. GRUB can't universally solve this problem, as
274 Address ("LBA") mode. GRUB automatically detects if LBA mode is
275 available and uses it if available. In LBA mode, GRUB can access
279 GRUB is basically a disk-based boot loader but also has network
284 To support computers with no console, GRUB provides remote terminal
285 support, so that you can control GRUB from a remote host. Only
301 The following is a quotation from Gordon Matzigkeit, a GRUB fanatic:
312 boot loader-Footnote-1::) or "GRUB" systems.
315 now I just use the word "GNU" as a pseudonym for GRUB.
319 boot loader around... GRUB!
321 We, the GRUB maintainers, do not (usually) encourage Gordon's level
323 recognition. We hope that you enjoy using GNU GRUB as much as we did
338 The device syntax used in GRUB is a wee bit different from what you
346 First of all, GRUB requires that the device name be enclosed with
349 means that GRUB will use the whole floppy disk.
359 this case, GRUB uses one partition of the disk, instead of the whole
373 like this: `(hd1,0,a)'. If the PC slice number is omitted, GRUB
376 Of course, to actually access the disks or partitions with GRUB, you
379 partition you want, the GRUB command-line (*note Command-line
385 followed by a <TAB>, and GRUB will display the list of drives,
390 Note that GRUB does _not_ distinguish IDE from SCSI - it simply
406 to actually install GRUB on your drive.
414 In order to install GRUB as your boot loader, you need to first
415 install the GRUB system and utilities under your UNIX-like operating
416 system (*note Obtaining and Building GRUB::). You can do this either
422 UNIX-like OS, or by running GRUB itself from a floppy. These are quite
426 Also, if you install GRUB on a UNIX-like OS, please make sure that
431 GRUB comes with boot images, which are normally put in the directory
437 GRUB images are initially placed (normally `/usr/lib/grub/i386-pc')
444 * Creating a GRUB boot floppy::
445 * Installing GRUB natively::
446 * Installing GRUB using grub-install::
447 * Making a GRUB bootable CD-ROM::
450 File: grub.info, Node: Creating a GRUB boot floppy, Next: Installing GRUB natively, Up: Installa…
452 Creating a GRUB boot floppy
455 To create a GRUB boot floppy, you need to take the files `stage1'
478 File: grub.info, Node: Installing GRUB natively, Next: Installing GRUB using grub-install, Prev:…
480 Installing GRUB natively
483 *Caution:* Installing GRUB's stage1 in this manner will erase the
486 GRUB can currently boot GNU Mach, Linux, FreeBSD, NetBSD, and OpenBSD
490 GRUB's stage1. This isn't as important if you are installing GRUB on
494 If you decide to install GRUB in the native environment, which is
495 definitely desirable, you'll need to create a GRUB boot disk, and
496 reboot your computer with it. Otherwise, see *Note Installing GRUB
499 Once started, GRUB will show the command-line interface (*note
500 Command-line interface::). First, set the GRUB's "root device"(1)
501 (*note Installing GRUB natively-Footnote-1::) to the partition
519 This command will install the GRUB boot loader on the Master Boot
520 Record (MBR) of the first drive. If you want to put GRUB into the boot
522 partition into which you want to install GRUB:
526 If you install GRUB into a partition or a drive other than the first
527 one, you must chain-load GRUB from another boot loader. Refer to the
528 manual for the boot loader to know how to chain-load GRUB.
530 After using the setup command, you will boot into GRUB without the
531 GRUB floppy. See the chapter *Note Booting:: to find out how to boot
532 your operating systems from GRUB.
535 File: grub.info, Node: Installing GRUB natively-Footnotes, Up: Installing GRUB natively
537 (1) Note that GRUB's root device doesn't necessarily mean your OS's
542 …ile: grub.info, Node: Installing GRUB using grub-install, Next: Making a GRUB bootable CD-ROM, …
544 Installing GRUB using grub-install
549 most operating systems don't tell GRUB how to map BIOS drives to OS
550 devices correctly--GRUB merely "guesses" the mapping. This will succeed
551 in most cases, but not always. Therefore, GRUB provides you with a map
555 If you still do want to install GRUB under a UNIX-like OS (such as
562 specified in GRUB's notation. For example, under Linux the following
563 will install GRUB into the MBR of the first IDE disk:
579 But all the above examples assume that GRUB should use images under
580 the root directory. If you want GRUB to use images under a directory
582 `--root-directory'. The typical usage is that you create a GRUB boot
591 mounted at `/boot'. Since GRUB is a boot loader, it doesn't know
606 shell::). Therefore, you may run `grub' directly to install GRUB,
608 very familiar with the internals of GRUB. Installing a boot loader on a
612 File: grub.info, Node: Making a GRUB bootable CD-ROM, Prev: Installing GRUB using grub-install, …
614 Making a GRUB bootable CD-ROM
617 GRUB supports the "no emulation mode" in the El Torito
618 specification(1) (*note Making a GRUB bootable CD-ROM-Footnote-1::).
619 This means that you can use the whole CD-ROM from GRUB and you don't
623 For booting from a CD-ROM, GRUB uses a special Stage 2 called
624 `stage2_eltorito'. The only GRUB files you need to have in your
634 Make a directory for GRUB:
653 the `boot/grub/stage2_eltorito' file, so there is no need to setup GRUB
658 file. This is not required; GRUB automatically sets the root device to
663 File: grub.info, Node: Making a GRUB bootable CD-ROM-Footnotes, Up: Making a GRUB bootable CD-ROM
674 GRUB can load Multiboot-compliant kernels in a consistent way, but
679 * General boot methods:: How to boot OSes with GRUB generally
689 GRUB has two distinct boot methods. One of the two is to load an
693 install or maintain other boot loaders and GRUB is flexible enough to
695 latter is sometimes required, since GRUB doesn't support all the
706 How to boot an OS directly with GRUB
710 native format supported by GRUB. For the sake of convenience, there is
715 Generally, GRUB can boot any Multiboot-compliant OS in the following
718 1. Set GRUB's root device to the drive where the OS images are stored
746 1. Set GRUB's root device to the partition by the command
762 `+1' indicates that GRUB should read one sector from the start of
806 1. Set GRUB's root device to the same drive as GNU/Hurd's. Probably
823 It is relatively easy to boot GNU/Linux from GRUB, because it
826 1. Set GRUB's root device to the same drive as GNU/Linux's. Probably
850 to specify the same memory size to GRUB. To let GRUB know the size, run
860 GRUB can load the kernel directly, either in ELF or a.out format. But
862 changes heavily, so GRUB can't guarantee to pass kernel parameters
878 GRUB can load NetBSD a.out and ELF directly, follow these steps:
880 1. Set GRUB's root device with `root' (*note root::).
890 For now, however, GRUB doesn't allow you to pass kernel parameters,
909 GRUB cannot boot DOS or Windows directly, so you must chain-load them
912 the problems, GRUB provides you with two helper functions.
916 from any disks but the first one. The workaround used in GRUB is the
935 If GRUB "hide"s a DOS (or Windows) partition (*note hide::), DOS (or
936 Windows) will ignore the partition. If GRUB "unhide"s a DOS (or
994 2. You must direct GRUB to boot a working system when the new system
995 fails. This is possible with the "fallback" system in GRUB.
1001 So let's see the GRUB part. There are two possibilities: one of them
1004 start as long as GRUB itself is bootable.
1017 You can teach GRUB to boot an entry only at next boot time. Suppose
1023 new kernel fails (e.g. it panics), you can specify that GRUB should try
1043 entry for the new kernel. This means that GRUB boots a saved entry by
1047 With this configuration file, after all, GRUB always tries to boot
1051 The next step is to tell GRUB to boot the new kernel at next boot
1059 This method is useful, but still not very robust, because GRUB stops
1062 the "fallback" mechanism of GRUB. Look at next subsection for this
1071 GRUB supports a fallback mechanism of booting one or more other
1080 Then you may want GRUB to boot the first system which is bootable
1103 `savedefault fallback' are used. GRUB will boot a saved entry by
1107 When GRUB tries to boot `A', GRUB saves `1' as next boot entry,
1109 entry. The entry `1' is `B', so GRUB will try to boot `B' at next boot
1112 Likewise, when GRUB tries to boot `B', GRUB saves `2' as next boot
1114 makes sure that GRUB will boot `C' after booting `B'.
1116 It is noteworthy that GRUB uses fallback entries both when GRUB
1119 even if GRUB cannot find your kernel or if your kernel panics.
1123 crashes, since GRUB always sets next boot entry to a fallback entry.
1134 strongly recommended *not to modify this file directly*, because GRUB
1146 boot your OS. There's a solution to that - GRUB provides a menu
1163 with a hash character (`#'), and blank lines, are ignored by GRUB.
1174 As the comment says, GRUB will boot automatically in 30 seconds,
1190 boot::) at the end of each item. That is because GRUB automatically
1220 cause GRUB to display a prompt and delay, before actually executing the
1252 # For installing GRUB into the hard disk
1253 title Install GRUB into the hard disk
1257 This will just (re)install GRUB onto the hard disk.
1265 because it can be used both in the command-line and in the menu. GRUB
1269 GRUB. To learn more about GRUB, see the following chapters.
1277 Although GRUB is a disk-based boot loader, it does provide network
1279 network driver in the GRUB build process. For more information please
1293 GRUB requires a file server and optionally a server that will assign
1294 an IP address to the machine on which GRUB is running. For the former,