Lines Matching refs:is
1 This is grub.info, produced by makeinfo version 4.0 from grub.texi.
19 Permission is granted to make and distribute verbatim copies of this
23 Permission is granted to copy and distribute modified versions of
25 that the entire resulting derived work is distributed under the terms
28 Permission is granted to copy and distribute translations of this
41 This command is fairly complex, and you should not use this command
46 Stage 1.5(1) (*note install-Footnote-1::) is in its final install
50 it is a GRUB Stage 1 of the right version number, install in it a
52 is present, the Stage 1 will always look for the actual disk
55 for a true Stage 2, and `0x2000' for a Stage 1.5. If ADDR is not
63 REAL_CONFIG_FILE is present and STAGE2_FILE is a Stage 1.5, then
64 the Stage 2 CONFIG_FILE is patched with the configuration file
66 hard disks, the partition table) of the sector the Stage 1 is to
83 solution to ignore the wrong bitmap, that is, the option
118 FILE. The rest of the line is passed verbatim as the "kernel
130 The option `--no-mem-option' is effective only for Linux. If the
131 option is specified, GRUB doesn't pass the option `mem=' to the
132 kernel. This option is implied for Linux kernels 2.4.18 and newer.
145 This command is used in a menu, as shown in this example:
147 title This entry is too dangerous to be executed by normal users
162 This command is limited to _primary_ PC partitions on a hard disk.
171 Map the drive FROM_DRIVE to the drive TO_DRIVE. This is necessary
173 an OS resides at a non-first drive. Here is an example:
202 of the line is passed as the "module command-line", like the
214 decompression is disabled.
223 Print the MESSAGE, then wait until a key is pressed. Note that
225 to emit the standard beep sound, which is useful when prompting
269 sub-partition is located. The optional HDBIAS parameter is a
271 controllers before the current one. For example, if there is an
272 IDE disk and a SCSI disk, and your FreeBSD root partition is on
285 partition. This is useful for when an OS is outside of the area of
287 is still desired. Note that the items mentioned in `root' above
298 entry. Here is an example:
318 fallback entry is saved. Next fallback entry is chosen from
335 IMAGE_DEVICE is specified, then find the GRUB images (*note
338 INSTALL_DEVICE is a hard disk, then embed a Stage 1.5 in the disk
342 images are put. If it is not specified, GRUB automatically
356 compare them, to test the filesystem code. The output is somewhat
358 filepos=Y' reading has X and Y equal, then it is definitely
361 step is to try loading a kernel.
396 Probe VESA BIOS EXTENSION information. If the mode MODE is
408 encounter trouble. *Note Invoking the grub shell::, if your problem is
423 The general way that the Stage 1 handles errors is to print an error
426 The following is a comprehensive list of error messages for the
430 The stage2 or stage1.5 is being read from a hard disk, and the
434 The stage2 or stage1.5 is being read from a floppy disk, and the
437 is different than for hard disks.
444 The location of the stage2 or stage1.5 is not in the portion of
447 user or the disk is moved to another machine or controller after
458 The general way that the Stage 1.5 handles errors is to print an
471 The general way that the Stage 2 handles errors is to abort the
476 The following is a comprehensive list of error messages for the
481 This error is returned if a file name is requested which doesn't
485 This error is returned if a file requested is not a regular file,
489 This error is returned if the run-length decompression code gets an
490 internal error. This is usually from a corrupt file.
493 This error is returned if the file header for a supposedly
494 compressed file is bad.
497 This error is returned if the sanity checks on the integrity of the
498 partition table fail. This is a bad sign.
501 This error is returned if the install command points to
503 detect corruption in general, but this is a sanity check on the
506 7 : Loading below 1MB is not supported
507 This error is returned if the lowest address in a kernel is below
508 the 1MB boundary. The Linux zImage format is a special case and
513 This error is returned if GRUB is told to execute the boot sequence
517 This error is returned if the boot attempt did not succeed for
521 This error is returned when the Multiboot features word in the
522 Multiboot header requires a feature that is not recognized. The
523 point of this is that the kernel requires special handling which
524 GRUB is probably unable to provide.
527 This error is returned if a device string was expected, and the
532 This error is returned if a device string is recognizable but does
536 This error is returned if the kernel image being loaded is not
542 length of the files it can read. This error is returned when the
546 This error is returned if the specified file name cannot be found,
547 but everything else (like the disk/partition info) is OK.
550 This error is returned by the filesystem code to denote an internal
552 disk not matching what it expects. This is usually caused by a
556 This error is returned if the partition requested exists, but the
560 This error is returned when a read is attempted at a linear block
562 happens if your disk is larger than the BIOS can handle (512MB for
566 This error is returned if the initrd command is used before
570 This error is returned if the module load command is used before
576 This error is returned if the device part of a device- or full
577 file name refers to a disk or BIOS device that is not present or
581 This error is returned if a partition is requested in the device
586 This error is returned if GRUB was expecting to read a number and
590 This error is returned if a linear block address is outside of the
596 This error is returned if there is a disk read error when trying to
600 This error is returned if the link count is beyond the maximum
604 This error is returned if an unrecognized command is entered on the
606 and that entry is selected.
609 This error is returned if a kernel, module, or raw file load
610 command is either trying to load its data such that it won't fit
611 into memory or it is simply too big.
614 This error is returned if there is a disk write error when trying
619 This error is returned if an argument specified to a command is
622 31 : File is not sector aligned
628 This error is returned if you try to run a locked entry. You should
632 This error is returned if you try to change your terminal to a
636 This error is returned if a disk doesn't have enough spare space.
648 shell is an emulator; it doesn't run under the native environment, so it
650 much. If there is anything wrong with it, don't hesitate to try the
668 or when fixing a bug. `grub' is almost the same as the Stage 2, and, in
670 same commands (*note Commands::) in `grub'. It is emulated by replacing
685 Use the device map file FILE. The format is described in *Note
690 option `--device-map' is specified (*note Device map::).
693 Probe the second floppy drive. If this option is not specified,
700 The format is the same as the normal GRUB syntax. See *Note
716 is available.
725 Wait until a debugger will attach. This option is useful when you
734 The installation procedure is the same as under the "native" Stage
736 `grub'-specific information is described here.
738 What you should be careful about is "buffer cache". `grub' makes use
741 inconsistency may corrupt your filesystems. What we recommend is:
750 that no activity is being done on it while the command `grub' is
753 * Reboot your operating system as soon as possible. This is probably
754 not required if you follow the rules above, but reboot is the most
758 installation. That is _very important_ because `quit' makes the buffer
762 option in the command-line. This is a simple example:
781 already exists. The file name `/boot/grub/device.map' is preferred.
788 DEVICE is a drive specified in the GRUB syntax (*note Device
789 syntax::), and FILE is an OS file, which is normally a device file.
791 The reason why the grub shell gives you the device map file is that
798 line is just a comment if the first character is `#'.
812 The device name INSTALL_DEVICE is an OS device name or a GRUB device
830 directory. This option is useful when you want to install GRUB
831 into a separate partition or a removable disk. Here is an example
832 in which you have a separate "boot" partition which is mounted on
855 This is just a frontend of the grub shell (*note Invoking the grub
879 that your terminal is vt100-compatible by default, this would be useful
880 only if your terminal is uncommon (such as vt52).
902 directory (i.e. `/boot/grub'), if it is not present. This file is used
918 define the location of the default file. This is useful when you
919 mount a disk which is used for another system.
922 argument is normally the number of a default boot entry. For example,
941 Because the entry for GNU/Linux is `1'. Note that entries are
945 This feature is very useful if you want to test a new kernel or to
981 GRUB is available from the GNU alpha archive site
983 named grub-version.tar.gz. The current version is 0.95, so the file you
984 should grab is:
1004 Also, the latest version is available from the CVS. See
1027 up when it boots' is not enough.
1029 The information on your hardware is also essential. These are
1040 5. Explain what you wanted to do. It is very useful to know your
1045 patch is even better.
1050 patch is for.
1058 is much better than omitting something important.
1088 As a general rule of software development, it is impossible to keep
1089 the descriptions of the internals up-to-date, and it is quite hard to
1120 Here is the memory map of the various components:
1132 The optional Stage 1.5 is loaded here
1138 Stage 1 is loaded here by BIOS or another boot loader
1144 Stage2 is loaded here
1186 The boot drive. If it is 0xFF, use a drive passed by BIOS.
1207 is determined when assembling the file `stage2/start.S'.
1209 The trick here is that it is actually read backward, and the first
1210 8-byte block list is not read here, but after the pointer is decremented
1212 until it is finished. The terminating condition is when the number of
1213 sectors to be read in the next block list is zero.
1216 just before the `firstlist' label. Note that it is always from the
1250 For any particular partition, it is presumed that only one of the
1252 is a switch table managed by the functions in `disk_io.c'. The notation
1253 is that you can only "mount" one at a time.
1291 Filesystem buffer which is 32K in size, to use in any way which the
1316 Only read sectors from within a partition. Sector 0 is the first
1324 If PRINT_POSSIBILITIES is true, call `print_a_completion' for each
1328 described at least moderately in the file `filesys.h'. Their usage is
1333 filesystem, presume the filesystem buffer `FSYS_BUF' is corrupted, and
1335 presume that the data from the `mount' is available, and doesn't get
1352 specifies how the function is called, using a bit mask. The return
1353 value must be zero if successful, otherwise non-zero. So it is normally
1356 The table of the information is represented by the structure `struct
1363 The table is finally registered in the table BUILTIN_TABLE, so that