32
32
similar to tools such as #{dh-make}#. For more information about #{lb
33
33
config}#, please see {The lb config command}#lb-config.
35
Besides the common config/common, which is used by all live-build commands,
36
some additional files can be used to configure the behavior of specific
37
helper commands. These files are typically named config/command or
38
config/stage (where "stage", of course, is replaced with the name of the
39
stage that they belong to, and "command" with the name of the command).
41
For example, the #{lb_bootstrap_debootstrap}# command uses files named
42
config/bootstrap and config/bootstrap_debootstrap to read the options it
43
will use. Generally, these files contain variables with values assigned, one
44
variable per line. Some commands of live-buil use pairs of values or
45
slightly more complicated variable assignments.
47
live-build respects environment variables which are present in the context
48
of the shell it is running. If variables can be read from config files, then
49
they override environment variables, and if command line options are used,
50
they override values from config files. If no value for a given variable can
51
be found (and is thus unset), live-build will automatically set it to a
54
All config files are shell scripts which are sourced by a live-build
55
command. That means they have to follow the normal shell syntax. You can
56
also put comments in these files; lines beginning with "#" are ignored.
58
In some rare cases you may want to have different versions of these files
59
for different architectures or distributions. If files named
60
config/stage.arch or config/stage_command.arch, and config/stage.dist or
61
config/stage_command.dist exist (where "arch" is the same as the output of
62
dpkg --print-architecture and "dist" is the same as the codename of the
63
target distribution), then they will be used in preference to the other,
66
35
The remainder of this section discusses the three most important commands:
68
37
_* *{lb config}*: Responsible for initializing a Live system configuration
119
88
Using #{lb config}# without any arguments would be suitable for users who
120
are either happy editing the generated files, or are simply happy with the
89
need a very basic image, or who intend to later provide a more complete
90
configuration via auto/config (see {Managing a
91
configuration}#managing-a-configuration for details).
123
You can ask #{lb config}# to generate a config/ directory "preseeded" with
124
various options. This might be suitable if you do not require the default
125
settings but do not need to change a large number of options. For example:
93
Normally, you will want to specify some options. For example, to include the
94
'gnome' package list in your configuration:
159
126
live-boot is a collection of scripts providing hooks for the
160
127
initramfs-tools, used to generate an initramfs capable of booting live
161
128
systems, such as those created by live-build. This includes the Debian Live
162
isos, netboot tarballs, and usb stick images.
129
ISOs, netboot tarballs, and USB stick images.
164
131
At boot time it will look for read-only media containing a "/live" directory
165
132
where a root filesystem (often a compressed filesystem image like squashfs)