Am 30.06.2011 23:15, schrieb Geert Stappers:
For What it's Worth: In the file debian/qemu-user-static.README.Debian is this text * Configuring qemu-user-static to use in a foreign chroot When used with binfmt, qemu-user-ARCH-static can be configured to run a foreign chroot. The qemu-user-ARCH-static binary should be copied (or better hard linked) into the chroot in /usr/bin. Then the chroot can be entered and used like a normal chroot. I haven't played with it, but it seems to help for "polystrap"
Am I missing something? That was already done in polystrap: <36073d0c9a389048a7f6a4cd4e9cd28ed1bc32a9> # copy qemu usermode binary if [ $ARCH != "`dpkg --print-architecture`" ]; then case $ARCH in alpha|arm|armeb|i386|m68k|mips|mipsel|ppc64|sh4|sh4eb|sparc|sparc64) cp `which qemu-$ARCH-static` $ROOTDIR/usr/bin;; amd64) cp `which qemu-x86_64-static` $ROOTDIR/usr/bin;; armel) cp `which qemu-arm-static` $ROOTDIR/usr/bin;; lpia) cp `which qemu-i386-static` $ROOTDIR/usr/bin;; powerpc) cp `which qemu-ppc-static` $ROOTDIR/usr/bin;; *) echo "unknown architecture: $ARCH"; exit 1;; esac fi </36073d0c9a389048a7f6a4cd4e9cd28ed1bc32a9>I do this to in my multistrap wrapper, but it needs super user rights to get it work. I think, polystraps goal was to run in user space.