mgetty 0.98 - checking modem config

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Michael Talbot-Wilson wrote:
> > You get a clean slate for the brand of modem that you have configured 
> > your software to use.  If you change modems, you would need to re-write 
> > NVRAM again.  Also, if you use the modem for more than one purpose 
> 
> I buy three NoName modems and put them on /dev/ttyS[234].  A few months
> later I have seen the light :-) and so I buy two XyXEL modems and put
> them on /dev/ttyS[56].  Soon afterwards a fourth NoName that was on
> another computer becomes redundant there and so I put it on /dev/ttyS7.
> 
> Because the modems differ both in their defaults and in the functions of
> similarly-numbered S registers, as well as the available AT commands,
> compiling in the init string is perhaps not such a terrific idea in these
> circumstances.

Compiling in? What stone age release of mgetty are you using? This hasn't
been necessary anymore since about 1 1/2 years...

The modem init chat can be easily configured on a per-port basis in the
configuration file or on the command line.

[..]
> > (shifting back and forth between various apps for instance), then you run 
> > the risk of having the wrong settings set in the active profile.  
> 
> I don't think you would do this.  You would set the NVRAM for mgetty, 
> which, after all, is sitting on the line all the time.  You configure
> your dial-out program to make whatever changes it needs to the defaults,
> and it makes no difference whether they are the factory defaults or those
> that you stored in NVRAM.  You wouldn't allow every comms program you run 
> to write to the NVRAM.

I wholeheartly agree.

gert

-- 
                                                            //www.muc.de/~gert
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3545980 <---new!!!              gert.doering@physik.tu-muenchen.de