On Wed, 2018-04-18 at 15:41 -0700, Vagrant Cascadian wrote: > On 2013-12-18, Joey Hess <email@example.com> wrote: > > If debootstrap installed qemu-user-static into the chroot > > when --foreign was used, it could then immediately chroot in > > and run commands (assuming the host system has binfmt-support > > installed). > > > > This would allow debootstrap to go ahead and run the second stage > > itself, under qemu emulation, and leave the user with a foreign chroot > > that could be transparently chrooted into. > > With version 2.12~rc3 (currently in unstable), qemu-user-static doesn't > require copying the qemu-ARCH-static binary into the chroot. > > You can simply call: > > debootstrap --arch=ARCH sid CHROOT > > ... and it just works now, without any debootstrap --foreign or > qemu-debootstrap wrappers! > > You might still want the binary copied into the chroot to make it easier > if moving the chroot to another machine, but that seems well outside the > scope of what debootstrap should worry about. I think this depends on a new feature in binfmt_misc in Linux 4.8, so the copy will also be needed on a jessie or wheezy host. Ben. -- Ben Hutchings It's easier to fight for one's principles than to live up to them.
Description: This is a digitally signed message part