Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!wonko.mit.edu!nessus
From: nessus@wonko.MIT.EDU (Doug Alan)
Newsgroups: comp.unix.wizards
Subject: Re: Input Line Editing In the Kernel
Message-ID: <9676@eddie.MIT.EDU>
Date: 14 Jul 88 05:15:50 GMT
References: <16456@brl-adm.ARPA> <9666@eddie.MIT.EDU> <249@pigs.UUCP>
Sender: uucp@eddie.MIT.EDU
Reply-To: nessus@athena.MIT.EDU (Doug Alan)
Organization: Kate Bush and Butthole Surfers Fandom Center
Lines: 20

In article <249@pigs.UUCP> haugj@pigs.UUCP (Joe Bob Willie) writes:

> In a previous article Doug Alan expounded on the virtues of kernel support
> for input line editting and virtual terminal output.

> this is possible where the number of terminals which are supported is
> limited to some subset.

Hey, I never said that line editting and virtual terminal support
belong in the kernal!  I don't know how you got this idea.  In fact, I
think they definitely don't!  Where they belong is in a special
process devoted to this task.  This allows an infinite number of
different types of terminals to be supported because the process can
be anything the user wants and can be configurable.

Now, to make this work seamlessly may require a few kernal mods, and
those, I think, should be done.  In any case, I just posted a big
article more precisely saying how I think things should be.  See that.

|>oug /\lan