summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLyndon Brown <jnqnfe@gmail.com>2020-03-28 01:47:21 +0000
committerLyndon Brown <jnqnfe@gmail.com>2020-04-23 11:46:36 +0100
commitae9143141d460ffbbe6084209977653cdc375bdb (patch)
treeaa92e2efb94e1c9b1c5f7741a990f7a6cb172d9e
parent286caf03bed722e3438f37a54e7c2d9720fc6535 (diff)
downloadvyos-live-build-ae9143141d460ffbbe6084209977653cdc375bdb.tar.gz
vyos-live-build-ae9143141d460ffbbe6084209977653cdc375bdb.zip
manpages: fix mistake
the bootloader list should be comma separated not space. i do not know what possessed me to write space based in aed4e0fef2b87e20ea13ea86d36b9b12ac23426d. fix "booloader" typo while at it. Gbp-Dch: Ignore
-rw-r--r--manpages/en/lb_config.12
1 files changed, 1 insertions, 1 deletions
diff --git a/manpages/en/lb_config.1 b/manpages/en/lb_config.1
index 1ea3f2f88..31d63d72e 100644
--- a/manpages/en/lb_config.1
+++ b/manpages/en/lb_config.1
@@ -286,7 +286,7 @@ sets boot parameters specific to debian\-live. A complete list of boot parameter
.IP "\fB\-\-bootappend\-live\-failsafe\fR \fIPARAMETER\fR|""\fIPARAMETERS\fR""" 4
sets boot parameters specific to debian\-live failsafe boot entries. A complete list of boot parameters can be found in the \fIlive\-boot\fR(7) and \fIlive\-config\fR(7) manual pages.
.IP "\fB\-\-bootloaders\fR grub-legacy|grub-pc|syslinux|grub-efi" 4
-defines which bootloaders to use in the generated image. This only has an effect if the selected binary image type lets you choose the bootloader. For example, if you build an ISO then syslinux (or more precise, isolinux) is always used. Also note that not all combinations of binary images types and bootloaders are supported (\fBlb config\fR will fail to create such an unsupported configuration and will give a explanation about it). For HDD images on amd64 and i386, the default is syslinux. This option supports more than one booloader to be specified (space separated) in order to allow for both BIOS and EFI bootloaders to be included, though note that only one of each type can be used (i.e. do not try to use two BIOS bootloaders).
+defines which bootloaders to use in the generated image. This only has an effect if the selected binary image type lets you choose the bootloader. For example, if you build an ISO then syslinux (or more precise, isolinux) is always used. Also note that not all combinations of binary images types and bootloaders are supported (\fBlb config\fR will fail to create such an unsupported configuration and will give a explanation about it). For HDD images on amd64 and i386, the default is syslinux. This option supports more than one bootloader to be specified (comma separated) in order to allow for both BIOS and EFI bootloaders to be included, though note that only one of each type can be used (i.e. do not try to use two BIOS bootloaders).
.IP "\fB\-\-bootstrap\-qemu\-arch \fIARCH\fR" 4
sets the architectures to use foreign bootstrap. Defaults to empty.
.IP "\fB\-\-bootstrap\-qemu\-exclude \fIPACKAGES\fR" 4