From owner-freebsd-hackers Sat Jun 3 10:04:50 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA04103 for hackers-outgoing; Sat, 3 Jun 1995 10:04:50 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA04097 for ; Sat, 3 Jun 1995 10:04:48 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id KAA13340; Sat, 3 Jun 1995 10:03:32 -0700 From: Poul-Henning Kamp Message-Id: <199506031703.KAA13340@ref.tfs.com> Subject: Re: Anyone interested in a STREAMS port? To: matt@lkg.dec.com (Matt Thomas) Date: Sat, 3 Jun 1995 10:03:32 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199506031245.MAA12536@whydos.lkg.dec.com> from "Matt Thomas" at Jun 3, 95 12:45:08 pm Content-Type: text Content-Length: 1040 Sender: hackers-owner@freebsd.org Precedence: bulk > 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 -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'