Date: Wed, 19 May 2004 19:01:06 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: wsk <wsk@gddsn.org.cn> Cc: net@freebsd.org Subject: Re: cuaa0&ttyd0's bug? Message-ID: <20040519170105.GZ70900@cicely12.cicely.de> In-Reply-To: <40AA0A30.3020102@gddsn.org.cn> References: <40AA0A30.3020102@gddsn.org.cn>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040519170105.GZ70900>