Lines Matching refs:boot
30 * grub-set-default: (grub)Invoking grub-set-default. Set a default boot
97 a flexible and powerful boot loader program for @sc{pc}s.
106 * Booting:: How to boot different operating systems
121 * Invoking grub-set-default:: How to set a default boot entry
138 * Role of a boot loader:: The role of a boot loader
145 Briefly, a @dfn{boot loader} is the first software program that runs when
151 GNU GRUB is a very powerful boot loader, which can load a wide variety
154 unsupported operating systems by loading another boot loader. It is
179 install GRUB on your drive (@pxref{Installation}), and how to boot your
182 Besides the GRUB boot loader itself, there is a @dfn{grub shell}
184 you are in your operating system. It emulates the boot loader and can
185 be used for installing the boot loader.
191 GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU
196 number of mutually-incompatible PC boot methods.
198 Erich then began modifying the FreeBSD boot loader so that it would
200 to write his own boot loader from scratch than to keep working on the
201 FreeBSD boot loader, and so GRUB was born.
252 Linux). Chain-loading of other boot loaders is also supported.
258 Support a human-readable text configuration file with preset boot
266 A menu interface listing preset boot commands, with a programmable
267 timeout, is available. There is no fixed limit on the number of boot
272 is available to edit any preset commands, or write a new boot command
307 Unlike many other boot loaders, GRUB makes the particular drive
331 GRUB is basically a disk-based boot loader but also has network
342 @node Role of a boot loader
343 @section The role of a boot loader
355 @emph{boot loader} is the most important software of all. I used to
357 a boot loader that everybody uses, but nobody likes.} or ``GRUB''
364 remember that they are actually paying homage to the best boot loader
369 fanaticism, but it helps to remember that boot loaders deserve
444 is not true if you change the boot sequence by swapping IDE and SCSI
465 In order to install GRUB as your boot loader, you need to first
470 After you have done that, you need to install the boot loader on a
478 have an emergency boot disk ready, so that you can rescue your computer
481 GRUB comes with boot images, which are normally put in the directory
484 @file{*stage1_5} to the directory @file{/boot/grub}, and run the
489 called the @dfn{image directory}, and the directory where the boot
490 loader needs to find them (usually @file{/boot/grub}) will be called
491 the @dfn{boot directory}.
494 * Creating a GRUB boot floppy::
501 @node Creating a GRUB boot floppy
502 @section Creating a GRUB boot floppy
504 To create a GRUB boot floppy, you need to take the files @file{stage1}
534 normal boot-sector used by an OS.
536 GRUB can currently boot GNU Mach, Linux, FreeBSD, NetBSD, and OpenBSD
537 directly, so using it on a boot sector (the first sector of a
545 definitely desirable, you'll need to create a GRUB boot disk, and
554 partition containing the boot directory, like this:
564 grub> @kbd{find /boot/grub/stage1}
567 This will search for the file name @file{/boot/grub/stage1} and show the
577 This command will install the GRUB boot loader on the Master Boot
578 Record (MBR) of the first drive. If you want to put GRUB into the boot
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.
590 After using the setup command, you will boot into GRUB without the
591 GRUB floppy. See the chapter @ref{Booting} to find out how to boot
612 argument to the program, namely, where to install the boot loader. The
643 boot floppy with a filesystem. Here is an example:
654 Another example is when you have a separate boot partition
655 which is mounted at @file{/boot}. Since GRUB is a boot loader, it
660 # @kbd{grub-install --root-directory=/boot /dev/hda}
668 computer will be able to boot with no problem.
675 boot loader on a running OS may be extremely dangerous.
691 because El Torito is quite different from the standard boot process.
704 $ @kbd{mkdir -p iso/boot/grub}
710 $ @kbd{cp /usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub}
713 If desired, make the config file @file{menu.lst} under @file{iso/boot/grub}
720 $ @kbd{mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \
721 -boot-load-size 4 -boot-info-table -o grub.iso iso}
725 into a CD (or a DVD). @kbd{mkisofs} has already set up the disc to boot
726 from the @kbd{boot/grub/stage2_eltorito} file, so there is no need to
727 setup GRUB on the disc. (Note that the @kbd{-boot-load-size 4} bit is
744 * General boot methods:: How to boot OSes with GRUB generally
750 @node General boot methods
751 @section How to boot operating systems
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
757 install or maintain other boot loaders and GRUB is flexible enough to
769 @subsection How to boot an OS directly with GRUB
774 NetBSD and OpenBSD. If you want to boot other operating systems, you
777 Generally, GRUB can boot any Multiboot-compliant OS in the following
793 Run the command @command{boot} (@pxref{boot}).
798 then run the command @command{boot}. If the kernel requires some
805 @subsection Load another boot loader to boot unsupported operating systems
807 If you want to boot an unsupported operating system (e.g. Windows 95),
808 chain-load a boot loader for the operating system. Normally, the boot
809 loader is embedded in the @dfn{boot sector} of the partition on which
831 Load the boot loader with the command @command{chainloader}
843 Run the command @command{boot} (@pxref{boot}).
871 Since GNU/Hurd is Multiboot-compliant, it is easy to boot it; there is
878 command @code{find /boot/gnumach} or similar can help you
886 grub> @kbd{kernel /boot/gnumach root=hd0s1}
887 grub> @kbd{module /boot/serverboot}
892 Run the command @command{boot} (@pxref{boot}).
899 It is relatively easy to boot GNU/Linux from GRUB, because it somewhat
900 resembles to boot a Multiboot-compliant OS.
933 Finally, run the command @command{boot} (@pxref{boot}).
952 @file{/boot/loader} instead. See this example:
957 grub> @kbd{kernel /boot/loader}
958 grub> @kbd{boot}
982 Run @command{boot} (@pxref{boot}).
1000 GRUB cannot boot DOS or Windows directly, so you must chain-load them
1001 (@pxref{Chain-loading}). However, their boot loaders have some critical
1006 have to use the disk swapping technique, because that OS cannot boot
1034 and the second partition of the first hard disk, and you want to boot
1044 grub> @kbd{boot}
1052 It is known that the signature in the boot loader for SCO UnixWare is
1061 grub> @kbd{boot}
1069 QNX seems to use a bigger boot loader, so you need to boot it up, like
1076 grub> @kbd{boot}
1085 that your computer can boot even if the new system is unbootable. This
1097 You must direct GRUB to boot a working system when the new system
1119 You can teach GRUB to boot an entry only at next boot time. Suppose
1121 @file{new_kernel}. You know that @file{old_kernel} can boot
1126 try the new kernel only once and boot the old kernel after that.
1153 With this configuration file, after all, GRUB always tries to boot the
1157 The next step is to tell GRUB to boot the new kernel at next boot
1169 booting, if there is any error in the boot entry, such that the new
1179 entries if a default boot entry fails. You can specify multiple
1183 @samp{C}. @samp{A} is a system which you want to boot by
1184 default. @samp{B} is a backup system which is supposed to boot
1188 Then you may want GRUB to boot the first system which is bootable
1216 and @samp{savedefault fallback} are used. GRUB will boot a saved entry
1217 by default and save a fallback entry as next boot entry with this
1220 When GRUB tries to boot @samp{A}, GRUB saves @samp{1} as next boot
1223 will try to boot @samp{B} at next boot time.
1225 Likewise, when GRUB tries to boot @samp{B}, GRUB saves @samp{2} as
1226 next boot entry, because @command{fallback} specifies @samp{2} as next
1227 fallback entry. This makes sure that GRUB will boot @samp{C} after
1238 after it crashes, since GRUB always sets next boot entry to a fallback
1240 @file{rc.local} to boot @samp{A} by default:
1246 where @samp{0} is the number of the boot entry for the system
1250 file @file{/boot/grub/default} (or @file{/grub/default} in
1262 You've probably noticed that you need to type several commands to boot your
1265 keys) that will do everything to boot an OS.
1268 @file{menu.lst} under the boot directory. We'll analyze an example
1279 # Sample boot menu configuration file
1289 # By default, boot the first entry.
1304 As the comment says, GRUB will boot automatically in 30 seconds, unless
1324 @command{boot} (@pxref{boot}) at the end of each item. That is because
1325 GRUB automatically executes @command{boot} if it loads other commands
1337 kernel /boot/gnumach.gz root=hd0s1
1338 module /boot/serverboot.gz
1360 kernel (fd0)/boot/kernel root=hd0s3
1361 module (fd0)/boot/bootstrap
1375 kernel /boot/loader
1379 This item will boot FreeBSD kernel loaded from the @samp{a} partition of
1391 #chainloader /boot/chain.os2
1395 This will boot OS/2, using a chain-loader (@pxref{Chain-loading}).
1400 title Windows NT / Windows 95 boot menu
1440 Although GRUB is a disk-based boot loader, it does provide network
1498 grub> @kbd{boot}
1506 It is sometimes very useful to boot from a network, especially when you
1511 second stage boot image from the network. Then, the second image will
1512 try to boot an operating system actually from the network.
1625 menu, if available. This includes running commands and reading boot
1635 If the preset menu includes any boot entries, they are cleared when
1637 configuration file has any entries or no entry. The boot entries in the
1717 password PASSWORD /boot/grub/menu-admin.lst
1720 In this case, GRUB will load @file{/boot/grub/menu-admin.lst} as a
1747 @command{lock}. In this case the boot process will ask for the password
1758 boot images. Here is a short overview of them. @xref{Internals}, for
1764 embedded in an MBR or the boot sector of a partition. Because a PC boot
1796 or the boot loader area of a ReiserFS or a FFS.
1799 This is a boot image for CD-ROMs using the @dfn{no emulation mode} in
1804 This is a network boot image for the Network Image Proposal used by some
1805 network boot loaders, such as Etherboot. This is mostly the same as
1810 This is another network boot image for the Preboot Execution Environment
1869 represents using the first partition of the disk (or the boot sector
1876 If you boot GRUB from a CD-ROM, @samp{(cd)} is available. @xref{Making
1888 example is @samp{(hd0,0)/boot/grub/menu.lst}. This means the file
1889 @file{/boot/grub/menu.lst} in the first partition of the first hard
1893 @code{/boot/kernel} is the same as @code{(hd1,0)/boot/kernel}.
1923 any desired combination of boot commands.
2015 Basically, the menu interface provides a list of @dfn{boot entries} to
2018 available to boot the default entry (the first one if not set), which is
2024 edit any of the @dfn{boot entries} by pressing @key{e}.
2043 user hits @key{RET}, GRUB replaces the line in question in the boot
2147 Go into unattended boot mode: if the default boot entry has any errors,
2181 Start a new boot entry, and set its name to the contents of the rest of
2665 * boot:: Start up your operating system
2667 * chainloader:: Chain-load another boot loader
2714 @node boot
2715 @subsection boot
2717 @deffn Command boot
2746 defective boot loader, such as SCO UnixWare 7.1 (@pxref{SCO UnixWare}).
2818 @var{device} is a drive, or in the @dfn{boot loader} area if @var{device}
2834 @code{/boot/grub/stage1}.
2897 table and boot the various CPUs which are found into a tight loop. This
2906 Load an initial ramdisk for a Linux format boot image and set the
2937 telling the stage2 where to look for a configuration file at boot
2983 Attempt to load the primary boot image (Multiboot a.out or @sc{elf},
3068 Load a boot module @var{file} for a Multiboot format boot image (no
3129 descriptor in @code{ES:ESI}, used by some chain-loaded boot loaders), the
3130 BSD drive-type (for booting BSD kernels using their native boot format),
3168 kernel /boot/vmlinuz root=/dev/sda1 vga=ext
3169 initrd /boot/initrd
3174 kernel /boot/loader
3205 in @file{/boot/grub} and @file{/grub}.
3366 This error is returned if GRUB is told to execute the boot sequence
3369 @item 9 : Unknown boot failure
3370 This error is returned if the boot attempt did not succeed for reasons
3456 command-line or in a boot sequence section of a configuration file and
3548 @file{/boot/grub/menu.lst}. The format is the same as the normal GRUB
3551 @item --boot-drive=@var{drive}
3636 already exists. The file name @file{/boot/grub/device.map} is preferred.
3651 some environments. For example, if you exchange the boot sequence
3691 you have a separate @dfn{boot} partition which is mounted on
3692 @file{/boot}:
3695 @kbd{grub-install --root-directory=/boot hd0}
3707 Recheck the device map, even if @file{/boot/grub/device.map} already
3764 The program @command{grub-set-default} sets the default boot entry for
3766 your GRUB directory (i.e. @file{/boot/grub}), if it is not
3767 present. This file is used to determine the default boot entry when
3769 configuration file (@pxref{default}), and to save next default boot
3770 entry when you use @samp{savedefault} in a boot entry
3789 argument is normally the number of a default boot entry. For example,
3807 and if you want to set the next default boot entry to GNU/Linux, you
3916 If GRUB cannot boot your operating system, write down
3918 @samp{The foo OS crashes with GRUB, even though it can boot with the
3919 bar boot loader just fine}. Mention the commands you executed, the