At the moment this only works with the root volume
on nfs as well. If we add a switch to configure the
network early in the boot process then this option
could be made available for other root mediums. This
option works reliably on the latest kernel 2.6.23.1
On earlier kernels I experienced frequent oopses.
To make the root filesystem as small as possible, it can be useful to exclude
certain files or directories. This is now possible by using the file
config/binary_rootfs/exclude, which contains a whitespace separated list of
file paths to exclude; wildcards are allowed. These paths are removed from the
chroot copy before the root filesystem is built.
When an ISO is created with the kernel image file name ending in ".img", the
ISO will not boot. In Qemu, the following error will be shown:
FATAL: Int13 eltorito call with AX=4C00
This means a non-implemented BIOS entry was called. In VMware and on real
hardware there is a different error message:
Cannot load disk image (invalid file)?
Removing the ".img" part of the file name solves this.
This option allows you to expose the root read only. Using
this option a person could upgrade the root filesystem or
add packages without requiring the user to reboot. The root
filesystem could be kept on an nfs volume or some other
persistent medium. Multiple clients could then be booted off
the same root fs. I used LTSP as a template to determine which
directories to make rw.
I did not realize that the syslinux boot methods,
iso, net, & hdd do not have feature parity for any
given version. As per old comments etch syslinux
v3.31 does not support sub directories on FAT images
share more code.
Change pxelinux directory setup to match debian installer
Change syslinux templates to use {$VAR} syntax so the
templates are easier to read
Remove etch support for syslinux, since INCLUDE syntax
is not available in etch syslinux v3.31
To properly support syslinux menus we need to provide fonts (specially
when using accents and like) and those files are usually found on
systems using multiple dots on their filenames (e.g iso01.f14.psf) and
then makes sense to support this by default or our users can spent _a
lot_ of time to sort this kind of problem out.
While doing it, the duplicated command line has been removed and code
changed to avoid this duplication making future changes need to touch
just one place.
To allow better customization of resulting system, support to include
and exclude packages of base system has been added. It has been
included for debootstrap and cdebootstrap helpers.
