Joined: 02 Mar 2013
|Posted: Sat Mar 02, 2013 5:07 pm Post subject: DBUS socket not readable from within chroot, help (NOT UDEV)
|Hello, I am on a no-multilib amd64 hardened selinux build, x works, udev functions perfectly.
Unfortunatly wine and skype do not work on no-multilib platforms, and so I created a subsystem for this kind of
ia32 bit application.
The chroot lies at /32/ on my root drive.
Every time I want to log into this system I go to a TTY and run this script
cp -L /etc/resolv.conf /32/etc/
mount -t proc none /32/proc
mount --rbind /sys /32/sys
mount --rbind /dev /32/dev
mount -o bind /dev/pts /32/dev/pts
mount -o bind /dev/shm /32/dev/shm
mount -o bind /proc/bus/usb /32/proc/bus/usb
mount -o bind /tmp /32/tmp
#mount -o bind /var/run /32/var/run
mount -o bind /home/kaylee /32/home/kaylee
mount -o bind /root /32/root/oldroot
mount -o bind /etc /32/etc/etcOLD
mount -o bind /etc/init.d /32/etc/init.dOLD
mount -o bind / /32/oldroot/
#ln -s /var/run/dbus/system_bus_socket /32/var/run/dbus/
#ln -s /32/var/run/
chroot /32/ /bin/bash --login &&
echo "cleaning up..."
After that I run this from inside the chroot
env-update && source /etc/profile
cd /home/kaylee/ && su kaylee
To fix up things to make it like a standard login so I can startx...
I had to build xorg-server with -dbus use so that it would run, but I would perfer to use dbus...
however I cannot run ANY applications inside the chroot that need dbus... so now I have to fix this!
*Note that I have tried several options and have not had success...
What happens is from outside the chroot, the socket file at /32/var/run/dbus/ is visable and has all the right permissions, but inside the chroot, the dbus socket folder is EMPTY
I have even tried changing the udev config file to make it store the default file in /32/var/run/ but even THAT didn't work, I edited /etc/dbus-1/system.conf, maybe I needed to edit other stufff?
Why can I not access the socket from inside the chroot, and HOW can I pipe the socket into my enviornment so I can make everything work??
EDIT: for some reason Udev got stuck in my head, I meant dbus, sorry for the confusion....