grml-debootstrap --target /dev/sda1 --grub /dev/sda+ Enable the contrib repository in COMPONENTS. By default only + the main repository is enabled. +
++ Partition where EFI boot manager should be installed to. If the + specified device doesn’t use a FAT filesystem yet grml-debootstrap + automatically creates the filesystem. If a FAT filesystem is already + present the filesystem creation is skipped. Please ensure that it’s + a valid FAT32 filesystem and the partition has the boot and esp + flags enabled. This option requires EFI support on the running system + and the option is NOT supported for Virtual Machine deployments. +
++ Enable the non-free repository in COMPONENTS. By default only + the main repository is enabled. +
+- Specify release of new Debian system. Supported releases names: lenny, - squeeze, wheezy (note: requires current version of debootstrap) and sid. - Corresponding with configuration variable RELEASE. + Execute scripts from specified directory after executing the chroot script. + This allows customisation of the system after the chroot has been set up. + The environment variable $MNTPOINT is available inside the scripts for + direct access of the chroot. + Default directory: /etc/debootstrap/post-scripts/
+ Specify release of new Debian system. Supported releases names: lenny, + squeeze, wheezy, jessie, stretch (note: requires a recent version of debootstrap) + and sid. Corresponding with configuration variable RELEASE. +
+- Execute scripts from specified directory. This allows customisation of - the system after the chroot has been set up. The environment variable - $MNTPOINT is available inside the scripts for direct access of the chroot. - Default directory: /etc/debootstrap/scripts/ + Delete grml-debootstrap configuration files (/etc/debootstrap/*) from installed + system. Useful for reproducible builds or if you don’t want to leak information.
- Set up a Virtual Machine instead of installing to a partition or directory. - This allows deployment of a Virtual Machine. The options needs to be - combined with the --target option. + Set up a Virtual Machine using a regular file instead of installing to a + partition/block device or directory. This allows deployment of a Virtual + Machine. The options needs to be combined with the --target option + (qemu-img create -f raw … is executed on the specified target). Usage example: --vmfile --target /mnt/sda1/qemu.img
grml-debootstrap --target /dev/sda1 --grub /dev/sdaInstall default Debian release (wheezy) on /dev/sda1 and install bootmanager +
Install default Debian release (jessie) on /dev/sda1 and install bootmanager Grub in MBR (master boot record) of /dev/sda and use /dev/sda1 as system partition.
mount /dev/sda1 /data/chroot
grml-debootstrap --target /data/chrootInstall default Debian release (wheezy) in directory /data/chroot (without +
Install default Debian release (jessie) in directory /data/chroot (without any bootloader).
grml-debootstrap --target /dev/sda3 --grub /dev/sda --mirror ftp://ftp.tugraz.at/mirror/debianInstall default debian release (wheezy) in a Virtual Machine file with -3GB disk size (including Grub as bootmanager in MBR of the virtual disk file):
Install default Debian release (jessie) on /dev/sda3 and install bootmanager +Grub in MBR (master boot record) of /dev/sda and use /dev/sda3 as system partition. +Use specified mirror instead of the default (http://httpredir.debian.org/debian) one.
mount /dev/sda1 /mnt/sda1
grml-debootstrap --vmfile --vmsize 3G --target /mnt/sda1/qemu.imgInstall default Debian release (wheezy) on /dev/sda3 and install bootmanager -Grub in MBR (master boot record) of /dev/sda and use /dev/sda3 as system partition. -Use specified mirror instead of the default (ftp://ftp.debian.de/debian) one.
Install default debian release (jessie) in a Virtual Machine file with +3GB disk size (including Grub as bootmanager in MBR of the virtual disk file):
mount -o loop /mnt/sda6/debian-CD-1.iso /mnt/iso
@@ -1250,14 +1293,14 @@ target=/dev/sda1release=...Specify release of new Debian system. Defaults to Debian wheezy. Supported -relases: lenny, squeeze, wheezy and sid. Usage example: release=sid
Specify release of new Debian system. Defaults to Debian jessie. Supported +releases: lenny, squeeze, wheezy, jessie, stretch and sid. Usage example: release=sid
mirror=...Specify mirror which should be used for apt-get/aptitude instead -of the default one (http://http.debian.net/debian). +of the default one (http://httpredir.debian.org/debian). Usage example: mirror=ftp://ftp.tugraz.at/mirror/debian
| - Release / - | -- Tool debootstrap - | -- cdebootstrap - | -
|---|---|---|
| Release | +Status | +|
| - Lenny - | -- works [1] - | -- works [1] - | -
| - Squeeze - | -- works - | -- works - | -
| - Wheezy - | -- works - | -- works - | -
| - Sid - | -- works [2] - | -- works [2] - | -
lenny |
+works[1] |
+|
squeeze |
+works |
+|
wheezy |
+works |
+|
jessie |
+works |
+|
stretch |
+works |
+|
sid |
+works[2] |
+
[1] Please notice that lenny is an unsupported release within Debian nowadays. grml-debootstrap can handle the release but you really should not use lenny -anymore unless you really know what you are doing. Choose Debian 6.0 (squeeze) -or Debian 7.0 (wheezy) instead.
Notice that you need to specify a mirror providing the lenny release, the -default (http://http.debian.net/debian) doesn’t provide it any longer nowadays. +default (http://httpredir.debian.org/debian) doesn’t provide it any longer nowadays. Set the mirror to e.g. http://archive.debian.org/debian/ if you don’t have your own lenny mirror.
You also need to specify a filesystem that’s supported by lenny, e.g. +--filesystem ext3 since grml-debootstrap’s current default (ext4) isn’t +supported by lenny.
Also when debootstrapping lenny on a live system with a kernel version +like "3.16-1-grml-amd64" lenny’s libc will fail to install with:
[...]
+/var/lib/dpkg/tmp.ci/preinst: line 265: [: 3.16-1-grml-amd64: integery expression expected
+/var/lib/dpkg/tmp.ci/preinst: line 231: 3.16-1-grml-amd64: syntax error: invalid arithemtic operator (error token is ".16-1-grml-amd64")
+dpkg: error processing /var/cache/apt/archives/libc6_2.7-18lenny7_amd64.deb (--install):
+[....]To workaround this either debootstrap from a system with an according +kernel version or use the "fake uname" workaround (just google for it).
When installing lenny to a new mdraid, grml-debootstrap will use md metadata format version 0.90. This limits the device to a maximum size of 2TB, but has the advantage of grub-legacy actually being able to boot from it.
[2] Please notice that jessie (Debian/testing) and sid (Debian/unstable) might +
[2] Please notice that Debian/testing and Debian/unstable (sid) might not be always installable due to their nature. What might work instead is deploying a stable release and upgrade it after installation finished.