Date: Sun, 22 Jun 1997 07:20:41 +0000 (GMT) From: Adam David <adam@veda.is> To: davidn@labs.usn.blaze.net.au (David Nugent) Cc: freebsd-current@freebsd.org Subject: Re: getty modem control Message-ID: <199706220720.HAA21918@veda.is> In-Reply-To: <199706220523.PAA00550@labs.usn.blaze.net.au> from David Nugent at "Jun 22, 97 03:23:07 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
[David Nugent] > Actually, CID should be trivial to add. The support functionality > is already there. Instead of flushing the modem input with wait/flush > after the connect, use the functions in chat.c to grab each line > output from the modem and log the data. I have reordered the flow of the chat support in main() and added :nb: to enable non-blocking use. If no-one among the non-blocking crowd objects, I will commit the changes so that blocking use of the answer chat facilities is available by default. Yes, it would definitely be nice to log the report strings. Is there a chance that CID will be available on broken implementations (such as Rockwell) when blocking on open() is used? To generify the question, if the serial input is not flushed on successful open, is that input available for reading if it originally occured after open() was first invoked but before the open() completed? > I *hate* mgetty with a vengence - it is far too bloated and > difficult to configure. ... and still assumes primitive modem technology. It's fine to support older equipment, but too limiting when this is assumed. > getty works for me, and very well, using a wide range of modems. > Its only problem is having to use cua* devices rather than tty* > devices, which I am fairly certain has to do with termios settings, > and in particular CLOCAL handling. It is in my todo list to fix. Ah, this is where I took a wrong turn. I was trying to use it with ttyd? devices. CLOCAL looks a likely culprit under the circumstances. However, when trying cuaa0 I found something had set /dev/cuaa0 to root.wheel 600 and I don't remember any other program than getty getting near it, so I went back to being stuck at getty chat on ttyd0 not working. Since people are using it with some success, I sat back to hear how this was done. -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706220720.HAA21918>