--- Alan Cox <[EMAIL PROTECTED]> wrote:
> On Maw, 2004-05-18 at 21:14, Jon Smirl wrote:
> > So you don't have any problem with pulling VT support out of the kernel?
>
> You need the code to handle video context switches. You also need vt's
> because you have multiple security contexts on the PC console and good
> reason to keep that when using SELinux.
>
> VT switch is easy however. DRI+X already handles that, and we never have
> two people using the VT at once. Its one device, multiple handles only
> one currently active - like many other drivers
Why does VT switch have to be in the kernel? I can have multiple xterms logged
in as different users without kernel support. Why can't VT switching be
implemented as if I was switching between multiple fullscreen xterms? I guess I
don't see why there is a difference between multiple xterms and VT's. I can use
su to set the xterm to any account.
I wanted to get the kernel completely out of the user space console. The only
kernel usage would be the video device driver. On the other hand, the system
console is completely implemented in the kernel.
User space console makes it easier to go multi-user. Stick four cards in, run a
user space console on each of them, and you have a four user system. No need for
kernel support.
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
