.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT 7 12.02.2013 3.0.0\-1 "Debian Live Project"
+.TH LIVE\-BOOT 7 2014\-03\-31 4.0~alpha20\-1 "Live Systems Project"
.SH NAME
-\fBlive\-boot\fP \- System Boot Scripts
+\fBlive\-boot\fP \- System Boot Components
.SH DESCRIPTION
-\fBlive\-boot\fP contains the scripts that configure a Debian Live system during
-the boot process (early userspace).
+\fBlive\-boot\fP contains the components that configure a live system during the
+boot process (early userspace).
.PP
.\" FIXME
live\-boot is a hook for the initramfs\-tools, used to generate a initramfs
capable to boot live systems, such as those created by
-\fIlive\-helper\fP(7). This includes the Debian Live isos, netboot tarballs, and
-usb stick images.
+\fIlive\-helper\fP(7). This includes the Live systems ISOs, netboot tarballs,
+and usb stick images.
.PP
.\" FIXME
-At boot time it will look for a (read\-only) media containing a "/live"
+At boot time it will look for a (read\-only) medium containing a "/live"
directory where a root filesystems (often a compressed filesystem image like
squashfs) is stored. If found, it will create a writable environment, using
-aufs, for Debian like systems to boot from.
+aufs, to boot the system from.
.SH CONFIGURATION
\fBlive\-boot\fP can be configured through a boot parameter or a configuration
Without setting debug to a value the messages may not be shown.
.IP \fBfetch\fP=\fIURL\fP 4
.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
+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 busybox's wget and DNS resolution, an URL can
-not contain a hostname but an IP only.
+not contain a hostname but an IP address only.
.br
Not working: http://example.com/path/to/your_filesystem.squashfs
.br
Working: http://1.2.3.4/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.
+a name\-based virtualhost of an httpd if it is sharing the IP address with
+the main httpd instance.
.br
-You may also use the live iso image in place of the squashfs image.
+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
+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:
+medium. If you use the \fBiscsitarget\fP software iSCSI target solution your
+ietd.conf might look like this:
.br
# The target\-name you specify in the iscsi= parameter
.br
\&.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
+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
storage only, you can use the 'removable\-usb' keyword.
.IP {\fBlive\-media\-encryption\fP|\fBencryption\fP}=\fITYPE\fP 4
live\-boot will mount the encrypted rootfs TYPE, asking the passphrase,
-useful to build paranoid live systems :\-). TYPE supported so far are "aes"
+useful to build paranoid live systems :\-). TYPE supported so far is "aes"
for loop\-aes encryption type.
.IP \fBlive\-media\-offset\fP=\fIBYTES\fP 4
This way you could tell live\-boot that your image starts at offset BYTES in
the above specified or autodiscovered device, this could be useful to hide
-the Debian Live iso or image inside another iso or image, to create "clean"
+the live system ISO or image inside another ISO or image, to create "clean"
images.
.IP \fBlive\-media\-path\fP=\fIPATH\fP 4
Sets the path to the live filesystem on the medium. By default, it is set to
.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'
+This parameter 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
+option has currently no effect when booting with toram.
+.IP \fBswap=true\fP 4
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
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".
+(see \fIpersistence.conf\fP(5)). Overlay image files are named "persistence".
.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
.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. This option replaces the less flexible persistent\-subtext option
-from version 2 of live\-boot. If you wish to continue using legacy names for
-persistent storage, use the full name with this option,
-e.g. persistence\-label=live\-rw\-foo
-.IP \fBquickreboot\fP 4
+GPT name.
+.IP \fBnoeject\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
\fIlive\-tools\fP(7)
.SH HOMEPAGE
-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>.
+More information about live\-boot and the Live Systems project can be found
+on the homepage at <\fIhttp://live\-systems.org/\fP> and in the manual
+at <\fIhttp://live\-systems.org/manual/\fP>.
.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
+the Bug Tracking System at <\fIhttp://bugs.debian.org/\fP> or by
+writing a mail to the Live Systems mailing list at
<\fIdebian\-live@lists.debian.org\fP>.
.SH AUTHOR
-live\-boot was written by Daniel Baumann <\fIdaniel@debian.org\fP> for
-the Debian project.
+live\-boot was written by Daniel Baumann <\fImail@daniel\-baumann.ch\fP>.
projects / live-boot-grml.git / blobdiff