From owner-freebsd-current@FreeBSD.ORG Wed May 19 12:55:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D8B16A4CE; Wed, 19 May 2004 12:55:49 -0700 (PDT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D245343D2F; Wed, 19 May 2004 12:55:48 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i4JJqO7f019354; Wed, 19 May 2004 13:52:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 19 May 2004 13:53:38 -0600 (MDT) Message-Id: <20040519.135338.08457763.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: "M. Warner Losh" In-Reply-To: <20040519170105.GZ70900@cicely12.cicely.de> References: <40AA0A30.3020102@gddsn.org.cn> <20040519170105.GZ70900@cicely12.cicely.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: wsk@gddsn.org.cn cc: net@freebsd.org Subject: Re: cuaa0&ttyd0's bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2004 19:55:49 -0000 In message: <20040519170105.GZ70900@cicely12.cicely.de> Bernd Walter writes: : On Tue, May 18, 2004 at 09:05:52PM +0800, wsk wrote: : > hi,folks: : > It seems that the ttyd0 isn't the dialin line to login , and : > the cuaa0 like is both the dialin/out device!under 4.9 above : > and 5.X .but the ttyd0 work well under 4.8. : > here is my test: : > I wanna direct connected two bsd box via a null-modem cable,on : > a box ,I congfiured the ttys as follow: : > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. : > ttyd0 "/usr/libexec/getty std.9600" dialup on secure : > ttyd1 "/usr/libexec/getty std.9600" dialup off secure : > and kill -HUP 1 : > on the other box , I use cu connenct the box: : > cu -l /dev/cuaa0 : > connected : > and then , nothing more i could recv! : > but if I confirgure the ttys as below: : > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. : > cuaa0 "/usr/libexec/getty std.9600" dialup on secure : > ttyd1 "/usr/libexec/getty std.9600" dialup off secure : > and do it like before i do , it worked! : > why???? It's a bug??? : : The behavour is intentional. : Your cable doesn't supply DCD signal. : Either use a cable with DCD suport or stay with cuaa. : It's OK to use cuaa if you don't need dialout support. or turn off modem flow control in the lock device... Warner