[SOLVED] Problems with setting up 32-bit chroot environment

Question

Recently I've moved to Arch64 and decided to build chroot environment in order to have a working flashplugin, Java and some other applications without messing up system libraries of two different architectures. I've followed directly instrucions from the wiki, but unfortunately still can't make it work. I'm stuck with
Kod:
bash-3.2# /etc/rc.d/arch32 start
:: Starting Arch32 chroot [DONE]
bash-3.2# xhost +local:
No protocol specified
xhost: unable to open display ":0.0"
bash-3.2# chroot /opt/arch32
I've googled a lot, asked on Polish Arch Linux forum, but so far I wasn't able to find a working solution. Can someone more experienced give me a hand with this?
Last edited by Zibi1981 (2008-11-14 22:35:48)

Answer 1

I have a working 32 bits chroot on a 64 bits system. My /etc/rc.d/arch32:
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
case $1 in
start)
stat_busy "Starting Arch32 chroot"
mount --bind /proc /opt/arch32/proc
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb
mount --bind /dev /opt/arch32/dev
mount --bind /dev/pts /opt/arch32/dev/pts
mount --bind /dev/shm /opt/arch32/dev/shm
mount --bind /sys /opt/arch32/sys
mount --bind /tmp /opt/arch32/tmp
mount --bind /home /opt/arch32/home
add_daemon arch32
stat_done
stop)
stat_busy "Stopping Arch32 chroot"
umount /opt/arch32/proc/bus/usb
umount /opt/arch32/proc
umount /opt/arch32/dev/pts
umount /opt/arch32/dev/shm
umount /opt/arch32/dev
umount /opt/arch32/sys
umount /opt/arch32/tmp
umount /opt/arch32/home
rm_daemon arch32
stat_done
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
I have the arch32 daemon in my /etc/rc.conf and I run this when I want to use the chroot:
#!/bin/sh
/etc/rc.d/arch32 start
xhost +local:
chroot /opt/arch32 su -l username -c "linux32 zsh"
Is it similar to your setup?