From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 24 21:35:52 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC40216A4CE for ; Mon, 24 Jan 2005 21:35:52 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6414443D39 for ; Mon, 24 Jan 2005 21:35:52 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] (sam@[66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j0OLZlWi006769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2005 13:35:47 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41F56A52.1040804@errno.com> Date: Mon, 24 Jan 2005 13:36:18 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ticso@cicely.de References: <20050124083043.GA8729@kukulies.org> <20050124151612.GC628@cicely12.cicely.de> <20050124124250.A27718@pix.net> <20050124180840.GH628@cicely12.cicely.de> <41F548D6.9060409@errno.com> <20050124194800.GI628@cicely12.cicely.de> In-Reply-To: <20050124194800.GI628@cicely12.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: "Kurt J. Lidl" Subject: Re: ttyd0/cuad0 - why is there still this duality ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 21:35:52 -0000 Bernd Walter wrote: > On Mon, Jan 24, 2005 at 11:13:26AM -0800, Sam Leffler wrote: > >>Bernd Walter wrote: >> >>>On Mon, Jan 24, 2005 at 12:42:50PM -0500, Kurt J. Lidl wrote: >>> >>> >>>>On Mon, Jan 24, 2005 at 04:16:13PM +0100, Bernd Walter wrote: >>>> >>>> >>>>>On Mon, Jan 24, 2005 at 09:30:43AM +0100, Christoph P. Kukulies wrote: >>> >>>Yes, but this way it just works and applications used it for many >>>years. >>> >> >>Portable modem-aware applications have never used it (speaking as >>someone that wrote many modem-oriented applications like tip and >>hylafax). I've never found a case where you cannot implement the >>equivalent functionality outside the kernel. > > > The following scenario: > Null modem cable and getty on both sides. > Works fine with any outdialin software in both directions and with > automatic disconnect on DCD (issued by remote DTR) loss. > How would you handle this without dual mechanism? > I don't consider this a meaningful setup. The split device arrangement was originally created to do transparent interlock between getty and outbound applications. It's been shown that this can be done well using only lock files. Note that I'm not suggesting one remove the functionality from the system though I consider it's value minimal at best. Sam