Roger Leigh <rle...@codelibre.net> writes: > Is this with or without your fork patch?
Without. With the patch it exec()s Xorg and of course does not execute any schroot code after that. > Right. From the console, I can start X with > schroot -c sid -p -q -- X :1 > or > schroot -c sid -p -q -- xinit :1 > > and then run X applications in both directly from the console without > any trouble, or from with the X session. Yes that works fine. As I described also using xdm works. But gdm just somehow detects the extra fork. > Now, when you start X, it creates a socket in /tmp/.X11-unix/Xn, where > n is the display number. Do you have the same /tmp inside and outside > the chroot (i.e. is it bind mounted)? If not, you'll need to do that. Yes sure that is bind mounted. > Note that in your config: > [sid2] > description=Debian sid2 (unstable) > location=/local/chroot/sid2 > aliases=unstable2 > users=root,lindi > > I don't see a type= line. If this is the complete configuration, That is the complete schroot.conf > you are running with type=plain and not type=directory which would > have done this setup for you. Please see the "should I use the > plain or directory chroot type?" section in the attached FAQ. I prefer not using setup or exec scripts since I don't fully understand how they work. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
