From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 10:46:20 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 055E116A4CE for ; Thu, 14 Oct 2004 10:46:20 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F76A43D48 for ; Thu, 14 Oct 2004 10:46:19 +0000 (GMT) (envelope-from peadar.edwards@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so12666rnk for ; Thu, 14 Oct 2004 03:46:18 -0700 (PDT) Received: by 10.38.102.60 with SMTP id z60mr2928205rnb; Thu, 14 Oct 2004 03:46:18 -0700 (PDT) Received: by 10.38.149.43 with HTTP; Thu, 14 Oct 2004 03:46:18 -0700 (PDT) Message-ID: <34cb7c84041014034649c63c3b@mail.gmail.com> Date: Thu, 14 Oct 2004 11:46:18 +0100 From: Peter Edwards To: Randy Bush In-Reply-To: <16750.7355.130098.892269@ran.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <16749.52145.110218.317549@ran.psg.com> <200410140048.i9E0mjjM015658@realtime.exit.com> <16749.58484.912537.379555@ran.psg.com> <200410141537.11242.doconnor@gsoft.com.au> <16750.7355.130098.892269@ran.psg.com> X-Mailman-Approved-At: Thu, 14 Oct 2004 12:10:41 +0000 cc: freebsd-current@freebsd.org Subject: Re: NOTICE: /dev/cuaa%d -> /dev/cuad%d renaming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Edwards List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 10:46:20 -0000 On Wed, 13 Oct 2004 23:29:15 -0700, Randy Bush wrote: > > Tie DCD to DTR. (I think) > > i was not clear. this affects production racks in strange > bunker-like facilities. > All this talk of soldering irons and 12v batteries is making me queasy. Can I suggest something? The problem is that your serial setup doesn't provide DCD, but you're using a device that requires it to be available before completing the open(2). Think of DCD as indicating that a "connection is established" with the other side. The ttyd device is _supposed_ to block until a remote connection is established. If you can't provide a DCD signal, then just use "cuad" instead of "ttyd": The intention is that's for making outgoing calls you use cuad, so a getty waiting to open ttyd won't stop the open on cuad. In your case, it's probably ok for the getty to just hog the modem itself, so using /dev/cuad0 sounds like the right thing to do. I've no idea why it was working with ttyd before: it sounds like its working correctly now: maybe phk has fixed a bug in whatever was driving your serial hardware. Cheers, Peadar.