Marcus Brinkmann <[EMAIL PROTECTED]> writes: > If you have the console server and X as the only players, the > mentioned protocol ensures that X can safely grab control over the > graphic card and the keyboard (the console server might in fact act > as an repeater for the keyboard input on /dev/kbd) and hands it back > to the console server, although the console server might have some > hotkeys to reset state in emergency cases (only works if used in > repeater mode of course).
Ok, I understand if that is the current goal, but I think the Right Thing should (1) behave in a sane way if the X server is kill -9:ed (i.e. cleanup bound to a no-senders notification somewhere), and (2) support arbitrary frame buffer applications in a simple and robust way. I.e. the responsibility for sane gfx state should be in some privileged process. A non-privileged user should not be able to shoot it down (but he should still be able to kill his own X server, and certainly his fb applications, and perhaps even his own console). Regards, /Niels _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
