mgetty 0.98 - checking modem config
Gert Doering (gert@greenie.muc.de)
Tue, 12 Dec 1995 22:36:04 +0100
Hi,
Jon Lewis wrote:
> > > It makes more sense to me to implement your modem configuration
> > > checker as a separate utility. You could run it when you get a new
> > > modem and also run it from cron to see if things have changes when they
> > > shouldn't have. It would just set the tty lock file like any other
> > > program using the modem and do its thing.
> >
> > Yep. I second that. This would do fine, and not increase mgetty size and
> > complexity (and, as we all now, the number of bugs hidden in there :) ).
>
> The guy from Zyxel (I'm terrible with names) suggested just making the
> init chat at&f1 OK at[mystrings] OK.
Either it was Brent, or Tyrone :) -- but yes, that's what I recommend as
well.
> Am I wrong in thinking that its
> better to have the prefered init string saved in nvram?
Why? You gain nothing, you lose not much (except having to do the effort
of making sure that the NVRAM is always up to date).
> With the modem
> set to reset on dtr loss, my modems currently reload the settings I want
> them to have. Would it make any difference to mgetty if they reset to
> factory defaults and had to be re-initialized with more than just ATZ?
No, since you can have as complex an init string as you like :)
> I guess it probably wouldn't...but I still like the idea of an easy way
> to put my settings in new modems without having to mess with minicom and
> its config files.
It *is* easy for the user, but to get it bulletproof isn't easy.
> Here's another idea...how bad would it be to have mgetty optionaly run chat
> much in the same way pppd uses the external chat program?
Why not run "chat" from cron, the way CDR proposed?
I'm somewhat opposed to "bloating" mgetty with things that can be done
as well in a different way.
gert
--
//www.muc.de/~gert
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-3545980 <---new!!! gert.doering@physik.tu-muenchen.de