From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 25 03:29:35 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 CB94516A4CE for ; Tue, 25 Jan 2005 03:29:35 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9203343D5D for ; Tue, 25 Jan 2005 03:29:35 +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 j0P3TSWi008789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2005 19:29:29 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41F5BD37.8020407@errno.com> Date: Mon, 24 Jan 2005 19:29:59 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20050124083043.GA8729@kukulies.org> <20050124151612.GC628@cicely12.cicely.de> <20050124124250.A27718@pix.net> <20050124.201048.21921498.imp@bsdimp.com> In-Reply-To: <20050124.201048.21921498.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: lidl@pix.net cc: ticso@cicely.de 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: Tue, 25 Jan 2005 03:29:35 -0000 M. Warner Losh wrote: > In message: <20050124124250.A27718@pix.net> > "Kurt J. Lidl" writes: > : Having seperate dialout and dialin devices really are just a kludge > : for having the kernel doing locking that could be done in userland > : code. > > That's not why they are there. Maybe now; that's not why they were added originally. > > : Just because FreeBSD does this the same way it's been done on > : BSD-ish systems for the last 15 years doesn't mean there isn't a > : better way of doing it. > > That's uncalled for. > > The real reason that they are there is that ttyd waits for carrier > detect, while cua doesn't. Non-blocking open followed by block on read/write and/or select dealt with that long ago. Sam