Re: Request for access to porterbox
On Wed, Jul 27, 2016 at 11:07:17PM +0200, Christian Seiler wrote:
> m68k and sh4 do work in qmeu-user-static chroots, the setup
> is not quite as trivial however. (I can give you a tarball
> that will work in pbuilder and schroot though.)
No, that's wrong. For these archs, qemu-user setup _is_ trivial. :)
It'd probably be helpful to gather such copypasta in one place, though:
wiki? a package? It gets more complex for qemu-system, though -- only
some archs can do just "toss me a d-i ISO image and next/next/next".
For qemu-user for sh4 it's:
CHROOT=/srv/chroots/sh4 #name the chroot here
apt-get -y install debian-ports-archive-keyring qemu-user-static
btrfs subv create "$CHROOT" || mkdir "$CHROOT"
mkdir -p "$CHROOT/usr/bin"
cp -p /usr/bin/qemu-sh4-static "$CHROOT/usr/bin/"
debootstrap --arch=sh4 \
--keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
unstable "$CHROOT" http://ftp.ports.debian.org/debian-ports/
Same works for all other archs supported by qemu, other than powerpcspe
(needs QEMU_CPU=e500v2). Obviously first-class archs will use the main
archive rather than debian-ports. x32 needs support in host kernel. hppa
is not supported by qemu (nor any other emulator).
Non-linux archs need qemu-system rather than qemu-user. As all of them are
x86, you want -enable-kvm, or, if you're scared by qemu-system, virtualbox.
Meow!
--
An imaginary friend squared is a real enemy.
Reply to: