Date: Thu, 27 Apr 1995 23:50:27 +0200 (MET DST) From: J Wunsch <j@jette.heep.sax.de> To: agl@redline.ru (Anthony Graphics) Cc: hackers@FreeBSD.org Subject: Re: Is there any FAQ on thge serial in FreeBSD? Message-ID: <199504272150.XAA01633@jette.heep.sax.de> In-Reply-To: <m0s4Vm9-000FJ6C@redline.ru> from "Anthony Graphics" at Apr 27, 95 07:46:00 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > I'm spending the second day trying to setup a dialin. > One simple question: should the /usr/libexec/getty be used for that > purpose? Where are the modem init strings are located? > Any entries I should add into /etc/gettytab? I think there is a FAQ somewhere in the Web page. Yes, /usr/libexec/getty is the way to go. You normally don't need to add anything in gettytab, just edit /etc/ttys, and "kill -HUP 1" to get the change in effect. Modem init string? Huh, "ats0=1&w", and let the modem do the rest. Remember, the normal way to share a line for dialin/dialout is to access it via /dev/cuaa* (dialout) and /dev/ttyd* (dialin). The open(2) call on the dialin device will block until the carrier appears, and if you think more about this, there is not even a chance to have the getty talking to the modem at this time. Of course, you're free to use mgetty, which must use the dialout device in order to work. Anyway, the device sharing must be done via those ***ing lock files then, which can cause serious race conditions. (Believe me, i do use mgetty, since my modem is too braindead to do what it's expected to do. My slip dial script is full of hacks which are only needed for that lock file crap, and there are still race conditions, but i'm tired to try even more hackery on this. I wish i had the money for a really working modem right now, and could go back to the regular getty instead of all those hacks.) Jörg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504272150.XAA01633>