Yes.
You can read documentation un download paches from
http://startx.times.lv
or
http://www.schuldei.org/aivils
I have got working real multiple local X servers.
Main idea is from James Simmons.
/dev/tty1-63 is splited. Now we have a multiple
ranges of /dev/tty's
/dev/tty1-7 bounded with 1-st keyboard
/dev/tty8-16 bounded with 2-nd keyboard
and so on.
Also XFree86 server has a parameter vtXX , where
XX is a number of /dev/ttyXX. Now we can choose
right keyboard for right X sever.
Normal X server during initialization search all
video adapters and then disable these all and after
init enable one necessary video adapter. This feature
must be disabled. If You tell xf86 to use /proc
interface for PCI configuration, then is possible
filter xf86 PCI-steering commands with kernel.
In my case patching of XFree86 is not necessary.
Kernel do not allow disable innocent video adapters
and multiple XFree86 servers runs without interference.
Another trouble is with bunch of USB input devices.
After boot USB assing device files randomly - same
mouse may have a various /dev/input/mouseX device file,
because init 1-st 2-nd 3-rd . I use
/etc/hotplug/input.agent
This agent make symbolic links depends from mouse physicaly
location. So i do not use straight /dev/input/mouse0 but
input.agent created /dev/Amouse0 - symlink to right
mouse device file.
Another troble is with sound. Any programm under Linux
will use hers own sound interface. If You have multiple
sound cards, then any starting script must be patched.
Some programms are unconfigurable or i do not know how
to doe it (SUN java plugin for Netscape). My home users
well know this and configure popular apps (xmms) as they
like and create additional chaos.
Zero trobles with GLX hardware acceleration! This is true
for closed source Nvidia drivers :)
IMHO this solution is very usable for home computers with
restricted budget. I never do cost calculations, because i
will not 2-nd box in my home.
Aivils Stoss
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/