[SCM] live-manual branch, debian, updated. debian/3.0_a17-1

[Ben Armstrong]

The following commit has been merged in the debian branch:
commit abd7547f5cb1221c3dc76fa4d82f29188e1f0b85
Author: Ben Armstrong <synrg at debian.org>
Date:   Tue Sep 25 12:22:58 2012 -0300

    Adding section on Kernel flavour and version.

diff --git a/manual/en/user_customization-packages.ssi b/manual/en/user_customization-packages.ssi
index f57c020..b2b3e90 100644
--- a/manual/en/user_customization-packages.ssi
+++ b/manual/en/user_customization-packages.ssi
@@ -209,6 +209,23 @@ code{
 
 }code
 
+3~kernel-flavour-and-version Kernel flavour and version
+
+Your choice of architecture determines the default flavour or flavours of kernel included in the image, and each flavour is suffixed to the default kernel package name stub #{linux-image}# to form each metapackage name which in turn depends on an exact kernel to include in your image. Thus, an #{amd64}# architecture image will include the #{linux-image-amd64}# flavour metapackage, and an #{i386}# architecture image will include the #{linux-image-486}# and #{linux-image-686-pae}# metapackages. At time of writing, these packages depend on #{linux-image-3.2.0-3-amd64}#, #{linux-image-3.2.0-3-486}# and #{linux-image-3.2.0-3-686-pae}#, respectively.
+
+When more than one kernel package version is available in your configured archives, you can specify a different kernel package name stub with the #{--linux-packages}# option. For example, supposing you are building an #{amd64}# architecture image and add the experimental archive for testing purposes so you can install the #{linux-image-3.5-trunk-amd64}# kernel. You would configure that image as follows:
+
+code{
+ 
+ $ lb config -a amd64 --linux-packages linux-image-3.5-trunk
+ $ echo "deb http://mirror/debian sid main" > config/archives/sid.list.chroot
+
+}code
+
+Please note that live-build supports only kernels that are integrated within the Debian package management system and does not support kernels not built as #{.deb}# packages.
+
+You may build and use your own custom kernel package in a similar fashion, including it in your configuration just the way you would any other package and specifying an appropriate #{--linux-packages}# stub. Of course you must satisfy the minimum requirements for running a live environment, i.e. at least include any kernel modules needed to handle the live filesystem (usually aufs and squashfs) and don't forget to suffix the package names with the flavour (e.g. #{-amd64}#).
+
 2~installing-modified-or-third-party-packages Installing modified or third-party packages
 
 Whilst it is against the philosophy of Debian Live, it may sometimes be necessary to build a Live system with modified versions of packages that are in the Debian repository. This may be to modify or support additional features, languages and branding, or even to remove elements of existing packages that are undesirable. Similarly, "third-party" packages may be used to add bespoke and/or proprietary functionality.

-- 
live-manual