summaryrefslogtreecommitdiff
path: root/manpages/en/lb_config.1
diff options
context:
space:
mode:
authorDaniel Baumann <daniel@debian.org>2011-08-25 23:47:30 +0200
committerDaniel Baumann <daniel@debian.org>2011-08-25 23:47:30 +0200
commit5d2fbf5d5adfd82f59b039d914c09e5dbca8296b (patch)
tree5b3558887cd68edba4f157c221dc9e5965f1d592 /manpages/en/lb_config.1
parent40a843bddd72c5222ee5d0983548c63b524326de (diff)
downloadvyos-live-build-5d2fbf5d5adfd82f59b039d914c09e5dbca8296b.tar.gz
vyos-live-build-5d2fbf5d5adfd82f59b039d914c09e5dbca8296b.zip
Adding support for ext4 for binary and chroot filesystem, including partial patch from Ben Howard <ben.howard@canonical.com> (Closes: #639298).
Diffstat (limited to 'manpages/en/lb_config.1')
-rw-r--r--manpages/en/lb_config.112
1 files changed, 6 insertions, 6 deletions
diff --git a/manpages/en/lb_config.1 b/manpages/en/lb_config.1
index d6fd4fcd0..fc132b51d 100644
--- a/manpages/en/lb_config.1
+++ b/manpages/en/lb_config.1
@@ -1,4 +1,4 @@
-.TH LIVE\-BUILD 1 2011\-08\-24 3.0~a30-1 "Debian Live Project"
+.TH LIVE\-BUILD 1 2011\-08\-25 3.0~a30-1 "Debian Live Project"
.SH NAME
\fBlb config\fR \- Create config directory
@@ -33,7 +33,7 @@
.br
[\-b|\fB\-\-binary\-images\fR iso|iso\-hybrid|net|tar|usb\-hdd|virtual\-hdd]
.br
- [\fB\-\-binary\-filesystem\fR fat16|fat32|ext2]
+ [\fB\-\-binary\-filesystem\fR fat16|fat32|ext2|ext3|ext4]
.br
[\fB\-\-bootappend\-install\fR \fIPARAMETER\fR|\fI"PARAMETERS"\fR]
.br
@@ -61,7 +61,7 @@
.br
[\fB\-\-build\-with\-chroot\fR true|false]
.br
- [\fB\-\-chroot\-filesystem\fR ext2|ext3|squashfs|plain|jffs2]
+ [\fB\-\-chroot\-filesystem\fR ext2|ext3|ext4|squashfs|plain|jffs2]
.br
[\fB\-\-clean\fR]
.br
@@ -275,8 +275,8 @@ defines if deb-src entries should be included in the resulting live image or not
defines the architecture of the to be build image. By default, this is set to the host architecture. Note that you cannot crossbuild for another 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\fR iso|iso\-hybrid|net|tar|usb\-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.
-.IP "\fB\-\-binary\-filesystem\fR fat16|fat32|ext2" 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 ext2. 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\-\-binary\-filesystem\fR 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.
.IP "\fB\-\-bootappend\-install\fR \fIPARAMETER\fR|""\fIPARAMETERS\fR""" 4
sets boot parameters specific to debian\-installer, if included.
.IP "\fB\-\-bootappend\-live\fR \fIPARAMETER\fR|""\fIPARAMETERS\fR""" 4
@@ -303,7 +303,7 @@ defines if the binary image should contain a file called md5sums.txt, sha1sums.t
defines the compression program to be used to compress tarballs. Defaults to gzip.
.IP "\fB\-\-build\-with\-chroot\fR true|false" 4
defines whetever live\-build should use the tools from within the chroot to build the binary image or not by using and including the host systems tools. This is a very dangerous option, using the tools of the host system can lead to tainted and even non-bootable images if the host systems version of the required tools (mainly these are the bootloaders such as syslinux, grub and yaboot, and the auxilliary tools such as dosfstools, genisoimage, squashfs-tools and others) do not \fBexactely\fR match what is present at build-time in the target distribution. Never do disable this option unless you are \fBexactely\fR sure what you are doing and have \fBcompletely\fI understood its consequences.
-.IP "\fB\-\-chroot\-filesystem\fR ext2|ext3|squashfs|plain|jffs2" 4
+.IP "\fB\-\-chroot\-filesystem\fR ext2|ext3|ext4|squashfs|plain|jffs2" 4
defines which filesystem type should be used for the root filesystem image. If you use plain, then no filesystem image is created and the root filesystem content is copied on the binary image filesystem as flat files. Depending on what binary filesystem you have choosen, it may not be possible to build with a plain root filesystem, e.g. fat16/fat32 and plain don't work as linux does not support to run on them.
.IP "\fB\-\-clean\fR" 4
minimizes config directory by automatically removing unused and thus empty subdirectories.