--nextPart1497178.zgjlSUyPsS
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wed, 14 Nov 2007, Girish Venkatachalam wrote:
> On 14:20:51 Nov 14, Daniel O'Connor wrote:
> > Couldn't you just run N copies of X (one for each head) and tell
> > them which mouse & keyboard device to use in each config file?
> >
> > ie don't use sysmouse or kbdmux.

>
> Try it. If it works let us know.
>
> Very unlikely.


Why?

> Nowadays all X display managers supply multiseat. So this might not
> be too much of a problem if the mouse and keyboard events are kept
> separated at the kernel level.


Keyboard data would not be MUX'd if you didn't use kbdmux. Unless you=20
use moused mouse events wouldn't be MUX'd.

I haven't tried it since I lack the hardware ATM but.. why not?

=2D-=20
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

--nextPart1497178.zgjlSUyPsS
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQBHOuX45ZPcIHs/zowRAkMuAJwO5N4ZmISWs6kQRjAy+HUnMJF1/QCfWeL+
MKMk/LJjsmCcXm5ONi0P8WA=
=zagj
-----END PGP SIGNATURE-----

--nextPart1497178.zgjlSUyPsS--