Date: Thu, 14 Oct 2004 10:16:43 -0700 From: Randy Bush <randy@psg.com> To: Peter Edwards <peadar.edwards@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: NOTICE: /dev/cuaa%d -> /dev/cuad%d renaming Message-ID: <16750.46203.217249.805105@ran.psg.com> 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> <34cb7c84041014034649c63c3b@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> 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. it's the getty that is the problem. this is out of band access to the console, i.e. getty. randyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16750.46203.217249.805105>