Re: GGI, EGCS/PGCC, Kernel source

Jason McMullan (jmcc@ontv.com)
Fri, 27 Feb 1998 14:35:28 -0500 (EST)


'Theodore Y. Ts'o wrote with particular insight...'
> A line discpline in itself is *not* clean, since it would require
> replicating the N_TTY code in their line discpline.
>
> Having a filter function that gets called from within the N_TTY line
> discipline (assuming that you would never want to use SLIP or PPP line
> discplines on the console) is a little better, but there's still a
> fundamental mismatch in that by the time you get into a tty line
> discpline, you *know* what tty the input is destined for.

Hmm... Good points... You _do_ realize that this whole
`EvStack on serial lines' is completely off the cuff and hypotheical,
right?

Anyhow, The N_KEYBOARD (hypothetical!) tty line discipline
would basically eat the tty - ie, you could only use it for
keyboard input. Not that this is a bad thing for such items
as Sun keyboards.

For dual input-output (the VT100 example), a better insertion
point would be at the head of a termstack (terminal emulation)
EvStack (there's one per VT) where the termstack has a `scroll-vt-100'
display scroller driver that outputs the currect VT-100 codes to
draw text, regardless of what terminal emulation you have loaded
on your VT....

All of the above, of course, could be run via the /dev/event
kernel<->user event delivery device in userland.

GGI: Display drivers

EvStack: Console subsystem redesign

-- 
Jason McMullan - Linux - GGI - http://pepsi.visus.com/~jmcc
NT 5.0 is the last nail in the Unix coffin. Interestingly, Unix
isn't in the coffin... It's wondering what the heck is sealing 
itself into a wooden box 6 feet underground... 

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu