From 1f39dc1100b58db9ffa6c5486d40521fddb064dd Mon Sep 17 00:00:00 2001 From: Peter Jones Date: Mon, 16 Jun 2014 14:26:05 -0400 Subject: [PATCH 07/22] We don't actually have docbook hooked up to the builds, so ditch it. Frankly I'm more comfortable maintaining groff anyway, but right now they just get out of sync all the time. Signed-off-by: Peter Jones --- src/man/man8/efibootmgr.8.docbook | 462 -------------------------------------- 1 file changed, 462 deletions(-) delete mode 100644 src/man/man8/efibootmgr.8.docbook diff --git a/src/man/man8/efibootmgr.8.docbook b/src/man/man8/efibootmgr.8.docbook deleted file mode 100644 index 3438d56..0000000 --- a/src/man/man8/efibootmgr.8.docbook +++ /dev/null @@ -1,462 +0,0 @@ -dannf@debian.org, - and was based on an example constructed by Colin Watson - cjwatson@debian.org, which was based on a man page template - provided by Tom Christiansen tchrist@jhereg.perl.com - and a DocBook man page example by Craig Small - csmall@debian.org. - - The content was mostly taken from the efibootmgr README file in the - Debian package, which was written by Matt Domsch - Matt_Domsch@dell.com. - --> - - - dann"> - frazier"> - - 2005-08-11"> - - 8"> - dannf@debian.org"> - - EFIBOOTMGR"> - -]> - - - -
- &manemail; -
- - &manfirstname; - &mansurname; - - - 2002, 2003, 2004 - &manusername; - - &mandate; - - - &manucpackage; - - &mansection; - - - &manpackage; - - manipulate the EFI Boot Manager - - - - &manpackage; - - -a - -A - -b XXXX - -B XXXX - -c - -d DISK - -e 1|3|-1 - -E NUM - -g - -H XXXX - -i NAME - -l NAME - -L LABEL - -n XXXX - -N - -o XXXX,YYYY,ZZZZ - -O - -p PART - -q - -t seconds - -T - -u - -U XXXX - -v - -V - -w - -@ file - - - - DESCRIPTION - - &manpackage; is a userspace application used to - modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This - application can create and destroy boot entries, change the boot order, - change the next running boot option, and more. - - - Details on the EFI Boot Manager are available from the EFI - Specification, v1.02 or later, available from: - - - - - - &manpackage; requires that the kernel support access to EFI - non-volatile variables (through - /proc/efi/vars on 2.4 kernels, - /sys/firmware/efi/vars on 2.6 kernels). - modprobe efivars should do the trick. - - - - - OPTIONS - - The following is a list of options accepted by &manpackage;: - - - - | - - Sets bootnum active - - - - | - - Sets bootnum inactive - - - - | XXXX - - Modify BootXXXX (hex) - - - - | - - Delete bootnum (hex) - - - - | - - Create new variable bootnum and add to bootorder - - - - | DISK - - The disk containing the loader (defaults to - /dev/sda) - - - - | 1|3|-1 - - Force EDD 1.0 or 3.0 creation variables, or guess. - - - - | NUM - - EDD 1.0 device number (defaults to 0x80) - - - - | - - Force disk with invalid PMBR to be treated as GPT - - - - | XXXX - - set the ACPI HID (used with ) - - - - | NAME - - create a netboot entry for the named interface - - - - | NAME - - Specify a loader (defaults to \\elilo.efi) - - - - - | LABEL - - Boot manager display label (defaults to "Linux") - - - - | XXXX - - Set BootNext to XXXX (hex) - - - - | - - Delete BootNext - - - - | XXXX,YYYY,ZZZZ - - Explicitly set BootOrder (hex) - - - - | - - Delete BootOrder - - - - | PART - - Partition number containing the bootloader (defaults to 1) - - - - | - - Quiet mode - supresses output. - - - - filename - - Don't write to NVRAM, write to filename. - - - - | seconds - - Boot Manager timeout, in seconds. - - - - | - - Delete Timeout variable. - - - - | | - - pass extra command line arguments as UCS-2 (default is - ASCII) - - - - | XXXX - - set the ACPI UID (used with ) - - - - | - - Verbose mode - prints additional information - - - - | - - Just print version string and exit. - - - - | - - write unique signature to the MBR if needed - - - - | - - - - append extra variable args from file (use - to read - from stdin). Data in file is appended as command line - arguments to the boot loader command, with no modification to - the data, so you can pass any binary or text data necessary. - - - - - - - - EXAMPLES - - - - Displaying the current settings (must be root). - - - - [root@localhost ~]# efibootmgr - BootCurrent: 0004 - BootNext: 0003 - BootOrder: 0004,0000,0001,0002,0003 - Timeout: 30 seconds - Boot0000* Diskette Drive(device:0) - Boot0001* CD-ROM Drive(device:FF) - Boot0002* Hard Drive(Device:80)/HD(Part1,Sig00112233) - Boot0003* PXE Boot: MAC(00D0B7C15D91) - Boot0004* Linux - - - This shows: - - - BootCurrent - the boot entry used to start the currently - running system - - - - BootOrder - the boot order as would appear in the boot manager. - The boot manager tries to boot the first active entry in this - list. If unsuccessful, it tries the next entry, and so on. - - - - - BootNext - the boot entry which is scheduled to be run on next - boot. This supercedes BootOrder for one boot only, and is - deleted by the boot manager after first use. This allows you - to change the next boot behavior without changing BootOrder. - - - - - Timeout - the time in seconds between when the boot - manager appears on the screen until when it - automatically chooses the startup value from BootNext - or BootOrder. - - - - - Five boot entries (0000 - 0004), along with the active/inactive - flag (* means active) and the name displayed on the screen. - - - - - - - - Creating a new boot option - - An OS installer would call &manpackage; -c. - This assumes that /boot/efi is your EFI System - Partition, and is mounted at /dev/sda1. This - creates a new boot option, called "Linux", and puts it at the top of - the boot order list. Options may be passed to modify the default - behavior. The default OS Loader is elilo.efi. - - - - - - Changing the Boot Order - - Assuming the configuration in Example #1, - &manpackage; -o 3,4 could be called to specify - PXE boot first, then Linux boot. - - - - - - Changing the Boot Order for the Next Boot Only - - Assuming the configuration in Example #1, - &manpackage; -n 4 could be called to specify - that the Linux entry be taken on next boot. - - - - - - Deleting a boot option - - Assuming the configuration in Example #1, - &manpackage; -b 4 -B could be called to delete - entry 4 and remove it from the BootOrder. - - - - - - Creating network boot entries - - A system administrator wants to create a boot option to network - boot (PXE). Unfortunately, this requires knowing a little more - information about your system than can be easily found by - efibootmgr, so you've got to pass additional information - the ACPI - HID and UID values. These can generally be found by using the EFI - Boot Manager (in the EFI environment) to create a network boot - entry, then using efibootmgr to print it verbosely. Here's one example: - - Boot003* Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510) \ - ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0) - - In this case, the ACPI HID is "0A0341d0" and the UID is "0". - For the zx2000 gigE, the HID is "222F" and the UID is "500". - For the rx2000 gigE, the HID is "0002" and the UID is "100". - - You create the boot entry with: - efibootmgr -c -i eth0 -H 222F -U 500 -L netboot - - - - - - - - BUGS - - Please direct any bugs, features, patches, etc. to Peter Jones: - . - - - - - AUTHOR - This man page was generated by dann frazier &manemail; for the - Debian GNU/Linux operating system, but may be used by others. - - - - SEE ALSO - - elilo(1) - - - - -- 1.9.3