From owner-freebsd-hackers Fri Nov 17 09:45:16 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA18002 for hackers-outgoing; Fri, 17 Nov 1995 09:45:16 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA17977 for ; Fri, 17 Nov 1995 09:44:58 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05728; Fri, 17 Nov 1995 10:35:53 -0700 From: Terry Lambert Message-Id: <199511171735.KAA05728@phaeton.artisoft.com> Subject: Re: pty To: didier@omnix.fr.org (Didier Derny) Date: Fri, 17 Nov 1995 10:35:48 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG In-Reply-To: from "Didier Derny" at Nov 17, 95 10:17:49 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1189 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > the data would be send and received on the pty side as small blocks. > each block would be delimited with STX an ETX > > example: > > STX CODE CHAN DATA ETX > > CODE: indicates the nature of the block > start a new connection, data, or disconnect > > CHAN: ttyp number > > It's a protocol wildely use in france for minitel servers. > (ASM protocol) HEY! I've written Minitel code before, for a contract with your ministry of defense! Big building, looks like an upside-down squared-off "U"! 8-). > either I write a program to control 32 pty and feed them with the data > from the ASM box or I control only one special pty an the driver do the > job... I think that the expensive part of the pty is going to be there whether or not you put in the endpoint. You may save on fd's doing this, but I think overall the increased code complexity in the muxed pty driver will steal back whatever savings you get that way. Something like this will probably be a false economy, unless maybe you will put *all* of your code in the kernel. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.