Note that a TARGET directory must be specified so debootstrap can download Packages files to determine which packages should be installed, and to resolve dependencies. You can run it with the --second-stage option to complete the bootstrapping process.
Other arguments are generally not needed. The resulting tarball may be passed to a later --unpack-tarball. Supported extractors are: dpkg-deb and ar. Note that an empty or non-existing TARGET directory must be specified so that debootstrap can download Packages files to determine which packages should be installed, and to resolve dependencies.
You can run it with the --second-stage option to complete the bootstrapping process. Other arguments are generally not needed. It should be an absolute path. The resulting tarball may be passed to a later --unpack-tarball. Note that an empty or non-existing TARGET directory must be specified so that debootstrap can download packages to prepare the tarball. Supported extractors are: dpkg-deb and ar. As an exception to the normal stage names, also rootfs can be used here which does only cache the generated root filesystem in filesystem.
This is useful during development if you want to rebuild the binary stage but not regenerate the root filesystem all the time. These lists all files on the image together with their checksums. This in turn can be used by live-boot's built-in integrity-check to verify the medium if specified at boot prompt. In general, this should not be false and is an important feature of live system released to the public.
However, during development of very big images it can save some time by not calculating the checksums. Defaults to gzip. 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 and grub, and the auxiliary tools such as dosfstools, xorriso, squashfs-tools and others do not exactly match what is present at build-time in the target distribution.
Never do disable this option unless you are exactly sure what you are doing and have completely understood its consequences. If you use none, 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 chosen, it may not be possible to build with such a plain root filesystem, e. Note that setting it to anything but noninteractive, which is the default, makes your build asking questions during the build.
By default, it is set to critical, which means that almost no questions are displayed. Note that this only has an effect if you use any debconf frontend different from noninteractive. By default, no installer is included. All available flavours except live are the identical configurations used on the installer media produced by regular debian-cd. When live is chosen, the live-installer udeb is included so that debian-installer will behave different than usual - instead of installing the debian system from packages from the medium or the network, it installs the live system to the disk.
Normally, this should be set to the same distribution as the live system. However, some times, one wants to use a newer or even daily built installer. In Debian mode and for most versions of Ubuntu, this option is true, whereas otherwise false, by default.
This is useful to provide if you submit bug reports, we do get all information required for us to locate and replicate an error. This is autodetected and does generally not need any customization. Use only if you know what you are doing. It is generally safer to use lb clean to clean up before re-executing lb build.
By default, this is set to --best to use highest but slowest compression. Dynamically, if the host system supports it, also --rsyncable is added. Normally, there are no hooks executed.
Make sure you know and understood the hook before you enable it. This is useful if you want to set global settings, such as mirror locations, and don't want to specify them all of the time. By default, auto is used, which means that at build time of the image rather than on configuration time, the value will be expanded to casper when building ubuntu systems, to live-boot for all other systems. Using 'none' is useful if the resulting system image should not be a live image experimental. Once you close the shell with logout or exit, the build will continue as usual.
Note that it's strongly discouraged to use this for anything else than testing. Modifications that should be present in all builds of a live system should be properly made through hooks. Everything else destroys the beauty of being able to completely automatise the build process and making it non interactive. By default, this is of course false.
0コメント