RECONFIGURE setting for debootstrap/config

[AntonioSun]

https://www.apt-browse.org/browse/debian/wheezy/main/all/grml-debootstrap/0.54/file/etc/debootstrap/config

# Packages that should be 'dpkg-reconfigure'-ed while installation.
# Default: 'console-data'.
# RECONFIGURE='console-data'

What's the format for the RECONFIGURE setting for debootstrap/config? comma separated?

It might be a good idea to list 2+ packages in the last line to make it clearer. E.g.,

# RECONFIGURE='console-data,tzdata'

cheers

[mika]

That needs to be something like RECONFIGURE='console-data tzdata', please let me know if that works for you and I'll provide a pull request

[AntonioSun]

Sure, I'm in the process of setting up my new machine, will do asap when it is done.

[AntonioSun]

OK, I tried to grml-debootstrap into a VM image (as per the command found in https://michael-prokop.at/blog/page/2/, ), and it finished fine:

% grml-debootstrap --vmfile --vmsize 3G --target debian.img
. . .
Finished chroot installation, exiting.
 * Removing chroot-script again
 * Removing configuration files from installed system as requested via --remove-configs / REMOVE_CONFIGS.
 * Unmounting bind-mount /run/udev
 * Unmount /mnt/debootstrap.5258
 * Installing Grub as bootloader.
1+0 records in
1+0 records out
440 bytes copied, 1.5154e-05 s, 29.0 MB/s
51+1 records in
51+1 records out
26530 bytes (27 kB, 26 KiB) copied, 4.2169e-05 s, 629 MB/s
 * Setting up bind-mount /run/udev
 * Updating grub configuration file.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
done
 * Adjusting grub.cfg for successful boot sequence.
 * Unmounting bind-mount /run/udev
loop deleted : /dev/loop1
 * Skipping filesystem check because we deploy a virtual machine.
 * Removing /var/cache/grml-debootstrap/variables_debian.img
 * Removing /var/cache/grml-debootstrap/stages_debian.img
 * Removing loopback mount of file /dev/shm/debian.img.
 * Finished execution of grml-debootstrap. Enjoy your Debian system.

And now how can I chroot into it to verify?

I tried:

root@grml:~# mount -o loop /dev/shm/debian.img /mnt/tmp1
mount.nilfs2: Error while mounting /dev/loop1 on /mnt/tmp1: Invalid argument

root@grml:~# mount -o loop,offset=32256 /dev/shm/debian.img /mnt/tmp1
mount.nilfs2: Error while mounting /dev/loop1 on /mnt/tmp1: Invalid argument

root@grml:~# mount -o loop -t ext2 /dev/shm/debian.img /mnt/tmp1
mount: /mnt/tmp1: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.

root@grml:~# mount -o loop,offset=32256 -t ext2 /dev/shm/debian.img /mnt/tmp1
mount: /mnt/tmp1: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.

thx