Running X chroot?
-----BEGIN PGP SIGNED MESSAGE-----
With the (current in unstable) binary incompatibility in libc, I'm
having trouble getting my old commercial X server running. One
suggestion was to run it chroot with the old libc libraries. I can see
how this would theoretically allow me to update the rest of the
So I gave it a try, I setup an /AccelX directory with the commercial
binaries and configuration files and the necessary libraries. It took
a little fiddling to get /proc mounted under /AccelX and to recreate
the obviously necessary devices under /AccelX/dev (console, mem, null,
psaux, tty0, tty7, and xsvc) but I figured it out eventually.
Now if I run
chroot /AccelX /usr/X11R6/bin/Xaccel
The server starts. Progress.
My next step was to attempt to get the server running chroot as part of
the normal init process.
Observing that /usr/X11R6/bin/X was a symlink to /usr/X11R6/bin/Xaccel,
I replaced it with a small shell script that contains:
exec chroot /AccelX /usr/X11R6/bin/Xaccel "$@"
Now if I run, for example, 'startx' the server starts but nothing happens.
When I kill off the server, I get
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
So clearly applications can't talk to the X server. Because I didn't create
some necessary device? Because I've overlooked something obvious? Clues
Be seeing you,
Norman Walsh <email@example.com> | We have fewer friends than we imagine,
http://nwalsh.com/ | but more than we know.--Hugo Von
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
-----END PGP SIGNATURE-----