summaryrefslogtreecommitdiff
path: root/manpages/de/lb_config.de.1
diff options
context:
space:
mode:
authorDaniel Baumann <daniel@debian.org>2011-09-13 09:10:28 +0200
committerDaniel Baumann <daniel@debian.org>2011-09-13 09:10:30 +0200
commitf38ef7f469ca31f96fda42da265c8d2c90b897ee (patch)
tree3e3da76f896c73e83da8b0502439685cbb00e8ba /manpages/de/lb_config.de.1
parent6f55ec4fb1188e24a081dab1cea704a5370c475d (diff)
downloadvyos-live-build-f38ef7f469ca31f96fda42da265c8d2c90b897ee.tar.gz
vyos-live-build-f38ef7f469ca31f96fda42da265c8d2c90b897ee.zip
Renaming usb-hdd binary image type to simply hdd.
This is the first step in conglomerating code for all hdd-ish image types, independent of the partitioning scheme being used, and adding future hdd-ish image types for virtualiziation software.
Diffstat (limited to 'manpages/de/lb_config.de.1')
-rw-r--r--manpages/de/lb_config.de.128
1 files changed, 14 insertions, 14 deletions
diff --git a/manpages/de/lb_config.de.1 b/manpages/de/lb_config.de.1
index 305033841..67fc1cad8 100644
--- a/manpages/de/lb_config.de.1
+++ b/manpages/de/lb_config.de.1
@@ -3,7 +3,7 @@
.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BUILD 1 2011\-09\-07 3.0~a31\-1 "Debian Live Project"
+.TH LIVE\-BUILD 1 2011\-09\-13 3.0~a31\-1 "Debian Live Project"
.SH NAME
\fBlb config\fP \- Create config directory
@@ -36,7 +36,7 @@
.br
[\-a|\fB\-\-architectures\fP \fIARCHITECTURE\fP]
.br
- [\-b|\fB\-\-binary\-images\fP iso|iso\-hybrid|net|tar|usb\-hdd|virtual\-hdd]
+ [\-b|\fB\-\-binary\-images\fP iso|iso\-hybrid|net|tar|hdd|virtual\-hdd]
.br
[\fB\-\-binary\-filesystem\fP fat16|fat32|ext2|ext3|ext4]
.br
@@ -220,7 +220,7 @@
.br
[\fB\-\-source\fP true|false]
.br
- [\-s|\fB\-\-source\-images\fP iso|net|tar|usb\-hdd]
+ [\-s|\fB\-\-source\-images\fP iso|net|tar|hdd]
.br
[\fB\-\-syslinux\-theme\fP \fITHEME_SUFFIX\fP]
.br
@@ -317,19 +317,19 @@ architecture if your host system is not able to execute binaries for the
target architecture natively. For example, building amd64 images on i386 and
vice versa is possile if you have a 64bit capable i386 processor and the
right kernel. But building powerpc images on an i386 system is not possible.
-.IP "\-b|\fB\-\-binary\-images\fP iso|iso\-hybrid|net|tar|usb\-hdd" 4
+.IP "\-b|\fB\-\-binary\-images\fP iso|iso\-hybrid|net|tar|hdd" 4
defines the image type to build. By default, for images using syslinux this
-is set to iso\-hybrid to build CD/DVD images that may also be used like
-usb\-hdd images, for non\-syslinux images, it defaults to iso.
+is set to iso\-hybrid to build CD/DVD images that may also be used like hdd
+images, for non\-syslinux images, it defaults to iso.
.IP "\fB\-\-binary\-filesystem\fP fat16|fat32|ext2|ext3|ext4" 4
defines the filesystem to be used in the image type. This only has an effect
if the selected binary image type does allow to choose a filesystem. For
example, when selection iso the resulting CD/DVD has always the filesystem
-ISO9660. When building usb\-hdd images for usb sticks, this is active. Note
-that it defaults to fat16 on all architectures except sparc where it
-defaults to ext4. Also note that if you choose fat16 and your resulting
-binary image gets bigger than 2GB, the binary filesystem automatically gets
-switched to fat32.
+ISO9660. When building hdd images for usb sticks, this is active. Note that
+it defaults to fat16 on all architectures except sparc where it defaults to
+ext4. Also note that if you choose fat16 and your resulting binary image
+gets bigger than 2GB, the binary filesystem automatically gets switched to
+fat32.
.IP "\fB\-\-bootappend\-install\fP \fIPARAMETER\fP|\(dq\fIPARAMETERS\fP\(dq" 4
sets boot parameters specific to debian\-installer, if included.
.IP "\fB\-\-bootappend\-live\fP \fIPARAMETER\fP|\(dq\fIPARAMETERS\fP\(dq" 4
@@ -343,8 +343,8 @@ bootloader. For example, if you build a iso, always syslinux (or more
precise, isolinux) is being used. Also note that some combinations of binary
images types and bootloaders may be possible but live\-build does not support
them yet. \fBlb config\fP will fail to create such a not yet supported
-configuration and give a explanation about it. For usb\-hdd images on amd64
-and i386, the default is syslinux. yaboot is only used on powerpc.
+configuration and give a explanation about it. For hdd images on amd64 and
+i386, the default is syslinux. yaboot is only used on powerpc.
.IP "\fB\-\-bootstrap\fP cdebootstrap|cdebootstrap\-static|debootstrap|copy" 4
defines which program is used to bootstrap the debian chroot, default is
debootstrap. Note that if you set the bootstrap program to copy, then your
@@ -727,7 +727,7 @@ build. By default this is false because most people do not require this and
would require to download quite a few source packages. However, once you
start distributing your live image, you should make sure you build it with a
source image alongside.
-.IP "\-s|\fB\-\-source\-images\fP iso|net|tar|usb\-hdd" 4
+.IP "\-s|\fB\-\-source\-images\fP iso|net|tar|hdd" 4
defines the image type for the source image. Default is tar.
.IP "\fB\-\-swap\-file\-path\fP \fIPATH\fP" 4
defines the path to a swap file to create in the binary image. Default is