X-Git-Url: https://git.grml.org/?p=grml-debootstrap.git;a=blobdiff_plain;f=grml-debootstrap.8.txt;h=a836fa8c01e6ecc8f6f9213c71e1bc46ddb1b066;hp=334843dc60eab498bfce8370212e2ea3da6939d6;hb=21658d381a6daa564ccb42cb70b43667f9410fba;hpb=6c597252744ccc9ba7608188a41a3006e97b20b1 diff --git a/grml-debootstrap.8.txt b/grml-debootstrap.8.txt index 334843d..a836fa8 100644 --- a/grml-debootstrap.8.txt +++ b/grml-debootstrap.8.txt @@ -60,6 +60,11 @@ Options and environment variables are executed at the end of the chroot procedure. Default directory: /etc/debootstrap/chroot-scripts/ +*--contrib*:: + + Enable the 'contrib' repository in COMPONENTS. By default only + the 'main' repository is enabled. + *-d*, *--confdir* _path_:: Place of configuration files for debootstrap, defaults to /etc/debootstrap. @@ -135,7 +140,7 @@ Options and environment variables *--nointerfaces*:: Do not copy /etc/network/interfaces from host system to the target. - This option is automatically enabled when using --vmfile. + This option is automatically enabled when using --vm or --vmfile. *--nokernel*:: @@ -144,6 +149,11 @@ Options and environment variables need to provide regular boot, e.g. a system which provides ISOs for booting via GRUB using grml-rescueboot. +*--non-free*:: + + Enable the 'non-free' repository in COMPONENTS. By default only + the 'main' repository is enabled. + *--nopackages*:: Skip installation of packages defined in /etc/debootstrap/packages. @@ -172,11 +182,13 @@ Options and environment variables command line might be visible in the process list and the shell history. It's meant for automatic installation only. -*-r*, *--release* _releasename_:: +*--post-scripts* _directory_:: - 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/ *--pre-scripts* _directory_:: @@ -186,12 +198,16 @@ Options and environment variables scripts for direct access of the chroot. Default directory: /etc/debootstrap/pre-scripts/ -*--scripts* _directory_:: +*-r*, *--release* _releasename_:: + + 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/ +*--remove-configs*:: + + Delete grml-debootstrap configuration files (/etc/debootstrap/*) from installed + system. Useful for reproducible builds or if you don't want to leak information. *-t*, *--target* _target_:: @@ -202,11 +218,20 @@ Options and environment variables Increase verbosity. -*--vmfile*:: +*--vm*:: - Set up a Virtual Machine instead of installing to a partition or directory. + Set up a Virtual Machine on an existing block device, which will be + partitioned. This allows deployment of a Virtual Machine. The options needs to be combined with the --target option. + Usage example: --vm --target /dev/mapper/your-vm-disk + +*--vmfile*:: + + 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 *--vmsize* _size_:: @@ -229,7 +254,7 @@ Usage examples grml-debootstrap --target /dev/sda1 --grub /dev/sda -Install 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. grml-debootstrap --target /dev/sda6 --grub /dev/sda --release sid @@ -240,20 +265,20 @@ Install Debian unstable/sid on /dev/sda6, install bootmanager Grub in MBR mount /dev/sda1 /data/chroot grml-debootstrap --target /data/chroot -Install 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/debian -Install 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://http.debian.net/debian) one. mount /dev/sda1 /mnt/sda1 grml-debootstrap --vmfile --vmsize 3G --target /mnt/sda1/qemu.img -Install 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 grml-debootstrap --target /dev/sda1 --grub /dev/sda --iso file:/mnt/iso/debian/ @@ -328,8 +353,8 @@ Where do you want to install grub to? Usage example: grub=/dev/sda release=... -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=... @@ -367,14 +392,26 @@ include::releasetable.txt[] ================================================================================ [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. +anymore unless you really know what you are doing. Choose Debian 7.0 (wheezy) or +something newer 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. Set the mirror to e.g. http://archive.debian.org/debian/ if you don't have your own lenny mirror. +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. @@ -383,7 +420,7 @@ the advantage of grub-legacy actually being able to boot from it. [NOTE] .unstable and testing releases ================================================================================ -[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. ================================================================================