Date: Sat, 3 Jun 1995 10:03:32 -0700 (PDT) From: Poul-Henning Kamp <phk@ref.tfs.com> To: matt@lkg.dec.com (Matt Thomas) Cc: freebsd-hackers@freebsd.org Subject: Re: Anyone interested in a STREAMS port? Message-ID: <199506031703.KAA13340@ref.tfs.com> In-Reply-To: <199506031245.MAA12536@whydos.lkg.dec.com> from "Matt Thomas" at Jun 3, 95 12:45:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> On top of the TCP interface (using XTI in user mode) I have a > XTI/streams based rlogind/telnetd daemon which takes incoming > connections, forks to handle the incoming connection, performs > the initial protocol work, and then pushes on either a rlogind or > telnetd streams module, and execs login right over itself. > > This module converts talks TPI to TCP on the bottom and talks to > ldterm (the streams terminal line discipline module) on the top. > Hence the network connection is now a terminal. Even better there > are no context switches when doing I/O, no extra processes, less CPU > utilization, ... As I said: good for terminal work, as it is primarily suited for character based stuff. I'm all for the stuff you did. I just don't want anybody to even think about the tcp/ip becoming streams based... Streams aware maybe, but not -based. -- Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506031703.KAA13340>