.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT 7 2012\-04\-08 3.0~a26\-1 "Debian Live Project"
+.TH LIVE\-BOOT 7 10.03.2013 4.0~a8\-1 "Debian Live Project"
.SH NAME
\fBlive\-boot\fP \- System Boot Scripts
.SS "Configuration Files"
\fBlive\-boot\fP can be configured (but not activated) through configuration
files. Those files can be placed either in the root filesystem itself
-(/etc/live/boot.conf, /etc/live/boot.d/*.conf), or on the live media
-(live/boot.conf, live/boot.d/*.conf).
+(/etc/live/boot.conf, /etc/live/boot/*), or on the live media
+(live/boot.conf, live/boot/*).
.SH OPTIONS
.\" FIXME
\fBlive\-boot\fP currently features the following parameters.
.IP \fBaccess\fP=\fIACCESS\fP 4
-Set the accessibility level for physically or visually impared users. ACCESS
-must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment,
-v2=moderate visual impairment, v3=blindness, m1=minor motor difficulties,
-m2=moderate motor difficulties.
+Set the accessibility level for physically or visually impaired
+users. ACCESS must be one of v1, v2, v3, m1, or m2. v1=lesser visual
+impairment, v2=moderate visual impairment, v3=blindness, m1=minor motor
+difficulties, m2=moderate motor difficulties.
.IP \fBconsole\fP=\fITTY,SPEED\fP 4
Set the default console to be used with the "live\-getty" option. Example:
"console=ttyS0,115200"
operates faster once booted because it does not require to contact the
server anymore.
.br
-Due to current limitations in busyboxs wget and DNS resolution, an URL can
+Due to current limitations in busybox's wget and DNS resolution, an URL can
not contain a hostname but an IP only.
.br
Not working: http://example.com/path/to/your_filesystem.squashfs
Lun 0 Path=<path\-to\-your\-live\-image.iso>,Type=fileio,IOMode=ro
# If you want to boot multiple machines you might want to look at tuning some parameters like
# Wthreads or MaxConnections
+.IP \fBfindiso\fP=\fI/PATH/TO/IMAGE\fP 4
+Look for the specified ISO file on all disks where it usually looks for the
+\&.squashfs file (so you don't have to know the device name as in
+fromiso=....).
.IP \fBfromiso\fP=\fI/PATH/TO/IMAGE\fP 4
Allows to use a filesystem from within an iso image that's available on
live\-media.
Do not check that any UUID embedded in the initramfs matches the discovered
medium. live\-boot may be told to generate a UUID by setting
LIVE_GENERATE_UUID=1 when building the initramfs.
-.IP \fBintegrity\-check\fP 4
+.IP \fBverify\-checksums\fP 4
If specified, an MD5 sum is calculated on the live media during boot and
compared to the value found in md5sum.txt found in the root directory of the
live media.
-.IP "\fBip\fP=[\fIDEVICE\fP]:[\fICLIENT_IP\fP]:[\fISERVER_IP\fP]:[\fIGATEWAY_IP\fP]:[\fINETMASK\fP]:[\fIHOSTNAME\fP]:[\fIAUTOCONF\fP] [,[\fIDEVICE\fP]:[\fICLIENT_IP\fP]:[\fISERVER_IP\fP]:[\fIGATEWAY_IP\fP]:[\fINETMASK\fP]:[\fIHOSTNAME\fP]:[\fIAUTOCONF\fP]]" 4
+.IP "\fBip\fP=[\fIDEVICE\fP]:[\fICLIENT_IP\fP]:[\fINETMASK\fP]:[\fIGATEWAY_IP\fP]:[\fINAMESERVER\fP] [,[\fIDEVICE\fP]:[\fICLIENT_IP\fP]:[\fINETMASK\fP]:[\fIGATEWAY_IP\fP]:[\fINAMESERVER\fP]]" 4
Let you specify the name(s) and the options of the interface(s) that should
be configured at boot time. Do not specify this if you want to use dhcp
(default). It will be changed in a future release to mimick official kernel
.IP \fBnopersistence\fP 4
disables the "persistence" feature, useful if the bootloader (like syslinux)
has been installed with persistence enabled.
-.IP \fBnoprompt\fP 4
-Do not prompt to eject the CD or remove the USB flash drive on reboot.
-.IP \fBnoprompt\fP=\fITYPE\fP 4
-This tells live\-boot not to prompt to eject the CD (when noprompt=cd) or
-remove the USB flash drive (when noprompt=usb) on reboot.
+.IP \fBnoeject\fP 4
+Do not prompt to eject the live medium.
.IP \fBramdisk\-size\fP 4
This parameters allows to set a custom ramdisk size (it's the '\-o size'
option of tmpfs mount). By default, there is no ramdisk size set, so the
This parameter enables usage of local swap partitions.
.IP \fBpersistence\fP 4
live\-boot will probe devices for persistence media. These can be partitions
-(with the correct GPT name), filesystems (with the correct label) or
-image/archive files (with the correct file name). Overlays are labeled/named
-either "full\-ov", which will be mounted on /, or "custom\-ov", which can be
-completely customized (see \fIlive.persist\fP(5)); snapshots are labeled/named
-either "live\-sn" or "home\-sn" and will be extracted into / or /home,
-respectively (see \fIlive\-snapshot\fP(1) for more information). The order these
-are handled are: full\-ov, custom\-ov, live\-sn, home\-sn. Overlay image files
-and snapshot archive files have extensions which determines their filesystem
-or archive type, e.g. "custom\-ov.ext4" and "\home\-sn.squashfs".
+(with the correct GPT name), filesystems (with the correct label) or image
+files (with the correct file name). Overlays are labeled/named "persistence"
+(see \fIpersistence.conf\fP(5)). Overlay image files have extensions which
+determines their filesystem, e.g. "persistence.ext4".
.IP "\fBpersistence\-encryption\fP=\fITYPE1\fP,\fITYPE2\fP ... \fITYPEn\fP" 4
This option determines which types of encryption that we allow to be used
when probing devices for persistence media. If "none" is in the list, we
be prompted for the passphrase. The default value is "none".
.IP \fBpersistence\-media\fP={\fIremovable\fP|\fIremovable\-usb\fP} 4
If you specify the keyword 'removable', live\-boot will try to find
-persistence and snapshot partitions on removable media only. Note that if
-you want to further restrict the media to usb mass storage only, you can use
-the 'removable\-usb' keyword.
+persistence partitions on removable media only. Note that if you want to
+further restrict the media to usb mass storage only, you can use the
+\&'removable\-usb' keyword.
.IP "\fBpersistence\-method\fP=\fITYPE1\fP,\fITYPE2\fP ... \fITYPEn\fP" 4
This option determines which types of persistence media we allow. If
"overlay" is in the list, we consider overlays (i.e. "live\-rw" and
-"home\-rw"); if "snapshot" is in the list, we consider snapshots
-(i.e. "live\-sn" and "home\-sn"). The default is "overlay,snapshot".
+"home\-rw"). The default is "overlay".
.IP \fBpersistence\-path\fP=\fIPATH\fP 4
live\-boot will look for persistency files in the root directory of a
partition, with this parameter, the path can be configured so that you can
have multiple directories on the same partition to store persistency files.
.IP \fBpersistence\-read\-only\fP 4
Filesystem changes are not saved back to persistence media. In particular,
-overlays and netboot NFS mounts are mounted read\-only, and snapshots are not
-resynced on shutdown.
+overlays and netboot NFS mounts are mounted read\-only.
.IP "\fBpersistence\-storage\fP=\fITYPE1\fP,\fITYPE2\fP ... \fITYPEn\fP" 4
This option determines which types of persistence storage to consider when
probing for persistence media. If "filesystem" is in the list, filesystems
with matching labels will be used; if "file" is in the list, all filesystems
will be probed for archives and image files with matching filenames. The
default is "file,filesystem".
-.IP \fBpersistence\-subtext\fP=\fISUFFIX\fP 4
-Add a suffix when searching for the image filenames or partition labels to
-use for the above mentioned persistence feature, the SUFFIX will be added
-after a dash (e.g.: "live\-sn" would transform to "live\-sn\-SUFFIX"). This is
-handy to test multiple live\-boot based live\-systems with different
-persistence storage choices.
+.IP \fBpersistence\-label\fP=\fILABEL\fP 4
+live\-boot will use the name "LABEL" instead of "persistence" when searching
+for persistent storage. LABEL can be any valid filename, partition label, or
+GPT name.
.IP \fBquickreboot\fP 4
This option causes live\-boot to reboot without attempting to eject the media
and without asking the user to remove the boot media.
.IP \fBshowmounts\fP 4
This parameter will make live\-boot to show on "/" the ro filesystems (mostly
-compressed) on "/live". This is not enabled by default because could lead to
-problems by applications like "mono" which store binary paths on
+compressed) on "/lib/live". This is not enabled by default because could
+lead to problems by applications like "mono" which store binary paths on
installation.
.IP \fBsilent\fP 4
If you boot with the normal quiet parameter, live\-boot hides most messages
Some variables can be configured via this config file (inside the live
system).
.IP \fBlive/filesystem.module\fP 4
+.\" FIXME
This optional file (inside the live media) contains a list of white\-space or
carriage\-return\-separated file names corresponding to disk images in the
"/live" directory. If this file exists, only images listed here will be
and the last file in this list will be on the "top" of the aufs, directly
below /overlay. Without this file, any images in the "/live" directory are
loaded in alphanumeric order.
-.IP \fB/etc/live\-persistence.binds\fP 4
-This optional file (which resides in the rootfs system, not in the live
-media) is used as a list of directories which not need be persistent:
-ie. their content does not need to survive reboots when using the
-persistence features.
-.br
-.\" FIXME
-This saves expensive writes and speeds up operations on volatile data such
-as web caches and temporary files (like e.g. /tmp and .mozilla) which are
-regenerated each time. This is achieved by bind mounting each listed
-directory with a tmpfs on the original path.
.SH FILES
.IP \fB/etc/live/boot.conf\fP 4
-.IP \fB/etc/live/boot.d/*.conf\fP 4
+.IP \fB/etc/live/boot/*\fP 4
.IP \fBlive/boot.conf\fP 4
-.IP \fBlive/boot.d/*.conf\fP 4
-.IP \fBlive.persist\fP 4
+.IP \fBlive/boot/*\fP 4
+.IP \fBpersistence.conf\fP 4
.SH "SEE ALSO"
-\fIlive\-snapshot\fP(1)
-.PP
-\fIlive.persist\fP(5)
+\fIpersistence.conf\fP(5)
.PP
\fIlive\-build\fP(7)
.PP
projects / live-boot-grml.git / blobdiff