Add support for building "foreign" images, ie non host arch images. This make it possible to use vmdebootstrap to create Raspberry Pi images. It add support for these new options:
--bootsize size when not the defautl '0%', create /boot/ partition
of the given size
--boottype fstype file system type of /boot/ (default ext2)
--foreign /path/to/binfmt_handler
When set, use foreign support in debootstrap.
--variant variant ask debootstrap to build variant, not the
default base system.
--no-extlinux skip installation of extlinux, depend on customize
script to make image bootable.
With this patch in place, I got a working Raspberry PI image by adding
a small customize script to install the binary blob needed to boot the
Raspberry Pi.
Antonio Terceiro [Tue, 11 Jun 2013 14:44:04 +0000 (11:44 -0300)]
Optimize final image compression rate
Filling up the image with zeros makes its compression rate a lot higher.
Together with running `apt-get clean`, I got an 1GB image compressed
down to 106M, against to 210M without these 2 changes.
Antonio Terceiro [Tue, 11 Jun 2013 14:44:02 +0000 (11:44 -0300)]
Allow custom command to handle the serial console
The need I am addressing with this is making the serial console
auto-login as root. For this right now I'm using the auto-serial-console
program from the linaro-overlay package:
Richard Maw [Wed, 10 Oct 2012 15:59:31 +0000 (16:59 +0100)]
Add --tarball option to create a tar of the disk
The configuration of debootstrap is useful even if a disk image is
not created, and allows the same configuration to be used for targets
that don't accept a raw disk image.
It's possible to use both --image and --tarball, in which case
it behaves the same as --image, but also creates a tarball of the
contents of the disk image.
If --tarball is specified, but --image isn't then, instead of creating
a disk image, it will debootstrap into a temporary directory.
Lars Wirzenius [Sun, 15 May 2011 10:18:47 +0000 (11:18 +0100)]
Remove persistent udev rules.
When debootstrap installs udev, it picks up at least the net devices
from the host that is building the image. This is not useful, so we
remove the files. Upon booting the image, udev will re-create the
files, so that's all fine.