NOTICE: /dev/cuaa%d -> /dev/cuad%d renaming
Peter Edwards
peadar.edwards at gmail.com
Thu Oct 14 03:46:20 PDT 2004
On Wed, 13 Oct 2004 23:29:15 -0700, Randy Bush <randy at psg.com> 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.
More information about the freebsd-current
mailing list