.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT 7 30.05.2010 2.0~a3 "Debian Live Projekt"
+.TH LIVE\-BOOT 7 2012\-04\-09 3.0~a27\-1 "Debian Live Project"
.SH NAME
-\fBlive\-boot\fP \- System Boot Skripte
+\fBlive\-boot\fP \- System Boot Scripts
-.SH BESCHREIBUNG
-\fBlive\-config\fP enthaelt die Skripte welche ein Debian Live System waehrend
-des Startvorganes (early userspace) konfigurieren.
+.SH DESCRIPTION
+\fBlive\-boot\fP contains the scripts that configure a Debian Live system during
+the boot process (early userspace).
.PP
.\" FIXME
live\-boot is a hook for the initramfs\-tools, used to generate a initramfs
squashfs) is stored. If found, it will create a writable environment, using
aufs, for Debian like systems to boot from.
-.SH KONFIGURATION
-\fBlive\-boot\fP kann durch Boot Parameter oder durch Konfigurationsdateien
-konfiguriert werden.
+.SH CONFIGURATION
+\fBlive\-boot\fP can be configured through a boot parameter or a configuration
+file.
+.PP
+To configure the live\-boot parameters used by default in a live image, see
+the \-\-bootappend\-live option in the \fIlb_config\fP(1) manual page.
-.SS "Kernel Parameter"
-\fBlive\-boot\fP ist nur dann aktiv, wenn 'boot=live' als Kernel Parameter
-benutzt wird.
+.SS "Kernel Parameters"
+\fBlive\-boot\fP is only activated if 'boot=live' was used as a kernel
+parameter.
.PP
In addition, there are some more boot parameters to influence the behaviour,
see below.
-.SS Konfigurationsdateien
+.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.conf.d/), or on the live media
-(live/boot.conf, live/boot.conf.d/).
+(/etc/live/boot.conf, /etc/live/boot.d/*.conf), or on the live media
+(live/boot.conf, live/boot.d/*.conf).
-.SH OPTIONEN
+.SH OPTIONS
.\" FIXME
\fBlive\-boot\fP currently features the following parameters.
.IP \fBaccess\fP=\fIACCESS\fP 4
"console=ttyS0,115200"
.IP \fBdebug\fP 4
Makes initramfs boot process more verbose.
+.br
+Use: debug=1
+.br
+Without setting debug to a value the messages may not be shown.
.IP \fBfetch\fP=\fIURL\fP 4
-Another form of netboot by downloading a squashfs image from a given url,
-copying to ram and booting it. Due to current limitations in busyboxs wget
-and DNS resolution, an URL can not contain a hostname but an IP only.
+.IP \fBhttpfs\fP=\fIURL\fP 4
+Another form of netboot by downloading a squashfs image from a given url.
+The fetch method copies the image to ram and the httpfs method uses fuse and
+httpfs2 to mount the image in place. Copying to ram requires more memory and
+might take a long time for large images. However, it is more likely to work
+correctly because it does not require networking afterwards and the system
+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
+not contain a hostname but an IP only.
.br
Not working: http://example.com/path/to/your_filesystem.squashfs
.br
Also note that therefore it's currently not possible to fetch an image from
a namebased virtualhost of an httpd if it is sharing the ip with the main
httpd instance.
+.br
+You may also use the live iso image in place of the squashfs image.
+.IP \fBiscsi\fP=\fIserver\-ip[,server\-port];target\-name\fP 4
+Boot from an iSCSI target that has an iso or disk live image as one of its
+LUNs. The specified target is searched for a LUN which looks like a live
+media. If you use the \fBiscsitarget\fP software iSCSI target solution which is
+packaged in Debian your ietd.conf might look like this:
+.br
+# The target\-name you specify in the iscsi= parameter
+.br
+Target <target\-name>
+ 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.
.IP \fBignore_uuid\fP 4
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
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=[\fICLIENT_IP\fP]:[\fISERVER_IP\fP]:[\fIGATEWAY_IP\fP]:[\fINETMASK\fP]:[\fIHOSTNAME\fP]:[\fIDEVICE\fP]:[\fIAUTOCONF\fP] [,[\fICLIENT_IP\fP]:[\fISERVER_IP\fP]:[\fIGATEWAY_IP\fP]:[\fINETMASK\fP]:[\fIHOSTNAME\fP]:[\fIDEVICE\fP]:[\fIAUTOCONF\fP]]" 4
+.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
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
If this variable is set, dhcp and static configuration are just skipped and
the system will use the (must be) media\-preconfigured
/etc/network/interfaces instead.
-.IP "{\fBkeyb\fP|\fBkbd\-chooser/method\fP}=\fIKEYBOARD\fP, {\fBklayout\fP|\fBconsole\-setup/layoutcode\fP}=\fILAYOUT\fP, {\fBkvariant\fP|\fBconsole\-setup/variantcode\fP}=\fIVARIANT\fP, {\fBkmodel\fP\fI|\fP\fBconsole\-setup/modelcode\fP}=\fICODE\fP, \fBkoptions\fP=\fIOPTIONS\fP" 4
-Configure the running keyboard as specified, if this one misses live\-boot
-behaves as if "keyb=us" was specified. It will be interfered from "locale="
-if locale is only 2 lowecase letters as a special case. You could also
-specify console layout, variant, code, and options (no defaults).
-.IP \fBlive\-getty\fP 4
-This changes the auto\-login on virtual terminals to use the (experimental)
-live\-getty code. With this option set the standard kernel argument
-"console=" is parsed and if a serial console is specified then live\-getty is
-used to autologin on the serial console.
.IP {\fBlive\-media\fP|\fBbootfrom\fP}=\fIDEVICE\fP 4
If you specify one of this two equivalent forms, live\-boot will first try to
find this device for the "/live" directory where the read\-only root
/etc/fstab. If you have static filesystems on your harddisk and you want
them to be checked at boot time, use this parameter, otherwise they are
skipped.
-.IP \fBnopersistent\fP 4
-disables the "persistent" feature, useful if the bootloader (like syslinux)
-has been installed with persistent enabled.
+.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 \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
+default of mount applies (currently 50% of available RAM). Note that this
+option has no currently no effect when booting with toram.
.IP \fBswapon\fP 4
This parameter enables usage of local swap partitions.
-.IP \fBnoxautoconfig\fP 4
-This parameter disables Xorg auto\-reconfiguration at boot time. This is
-valuable if you either do the detection on your own, or, if you want to ship
-a custom, premade xorg.conf in your live system.
-.IP \fBpersistent\fP[=nofiles] 4
-live\-boot will look for persistent and snapshot partitions or files labeled
-"live\-rw", "home\-rw", and files called "live\-sn*", "home\-sn*" and will try
-to, in order: mount as /cow the first, mount the second in /home, and just
-copy the contents of the latter in appropriate locations
-(snapshots). Snapshots will be tried to be updated on reboot/shutdown. Look
-at live\-snapshot(1) for more informations. If "nofiles" is specified, only
-filesystems with matching labels will be searched; no filesystems will be
-traversed looking for archives or image files. This results in shorter boot
-times.
-.IP \fBpersistent\-path\fP=\fIPATH\fP 4
+.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\-persistence.conf\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".
+.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
+allow unencrypted media; if "luks" is in the list, we allow LUKS\-encrypted
+media. Whenever a device containing encrypted media is probed the user will
+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.
+.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".
+.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 {\fBpreseed/file\fP|\fBfile\fP}=\fIFILE\fP 4
-A path to a file present on the rootfs could be used to preseed debconf
-database.
-.IP \fBpackage/question\fP=\fIVALUE\fP 4
-All debian installed packages could be preseeded from command\-line that way,
-beware of blanks spaces, they will interfere with parsing, use a preseed
-file in this case.
+.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.
+.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 \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 \fBsilent\fP 4
If you boot with the normal quiet parameter, live\-boot hides most messages
of its own. When adding silent, it hides all.
-.IP \fBtextonly\fP 4
-Start up to text\-mode shell prompts, disabling the graphical user interface.
.IP \fBtodisk\fP=\fIDEVICE\fP 4
Adding this parameter, live\-boot will try to copy the entire read\-only media
to the specified device before mounting the root filesystem. It probably
to the computer's RAM before mounting the root filesystem. This could need a
lot of ram, according to the space used by the read\-only media.
.IP \fBunion\fP=aufs|unionfs 4
+.\" FIXME
By default, live\-boot uses aufs. With this parameter, you can switch to
unionfs.
-.IP \fBxdebconf\fP 4
-Uses xdebconfigurator, if present on the rootfs, to configure X instead of
-the standard procedure (experimental).
-.IP \fBxvideomode\fP=\fIRESOLUTION\fP 4
-.\" FIXME
-Doesn't do xorg autodetection, but enforces a given resolution.
.\" FIXME
.SH "FILES (old)"
merged into the root aufs, and they will be loaded in the order listed
here. The first entry in this file will be the "lowest" point in the aufs,
and the last file in this list will be on the "top" of the aufs, directly
-below /cow. Without this file, any images in the "/live" directory are
+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
regenerated each time. This is achieved by bind mounting each listed
directory with a tmpfs on the original path.
-.SH DATEIEN
+.SH FILES
.IP \fB/etc/live/boot.conf\fP 4
-.IP \fB/etc/live/boot.conf.d/\fP 4
+.IP \fB/etc/live/boot.d/*.conf\fP 4
.IP \fBlive/boot.conf\fP 4
-.IP \fBlive/boot.conf.d/\fP 4
+.IP \fBlive/boot.d/*.conf\fP 4
+.IP \fBlive\-persistence.conf\fP 4
-.SH "SIEHE AUCH"
+.SH "SEE ALSO"
\fIlive\-snapshot\fP(1)
.PP
+\fIlive\-persistence.conf\fP(5)
+.PP
+\fIlive\-build\fP(7)
+.PP
\fIlive\-config\fP(7)
.PP
-\fIlive\-helper\fP(7)
+\fIlive\-tools\fP(7)
.SH HOMEPAGE
-Weitere Informationen ueber live\-boot und das Debian Live Projekt koennen
-auf der Homepage unter <\fIhttp://live.debian.net/\fP> und im Handbuch
-unter <\fIhttp://live.debian.net/manual/\fP> gefunden werden.
+More information about live\-boot and the Debian Live project can be found on
+the homepage at <\fIhttp://live.debian.net/\fP> and in the manual at
+<\fIhttp://live.debian.net/manual/\fP>.
-.SH FEHLER
-Fehler koennen durch Einreichen eines Fehlerberichtes fuer das live\-boot
-Paket im Debian Bug Tracking System unter
-<\fIhttp://bugs.debian.org/\fP> oder durch Senden einer E\-Mail an die
-Debian Live Mailing Liste unter <\fIdebian\-live@lists.debian.org\fP>
-(englischsprachig) mitgeteilt werden.
+.SH BUGS
+Bugs can be reported by submitting a bugreport for the live\-boot package in
+the Debian Bug Tracking System at <\fIhttp://bugs.debian.org/\fP> or by
+writing a mail to the Debian Live mailing list at
+<\fIdebian\-live@lists.debian.org\fP>.
-.SH AUTOR
-live\-boot wurde von Daniel Baumann <\fIdaniel@debian.org\fP> fuer das
-Debian Projekt geschrieben.
+.SH AUTHOR
+live\-boot was written by Daniel Baumann <\fIdaniel@debian.org\fP> for
+the Debian project.
projects / live-boot-grml.git / blobdiff