🚀 go-pugleaf

In article <4go1db$j1m@ghostgum.hunterlink.net.au>,
	fat.man@hunterlink.net.au (Fat Man) writes:

>	I'm having a problem with agetty and uugetty to answer my modem...
>
>    with agetty is dosn't pick-up at all...

Set answer mode on the modem. agetty has no (zero zilch) modem
smarts built-in, so the modem needs to do all that is required.
Make sure you don't enable "local" mode on the modem since you
need agetty to sleep on the line until carrier goes high. It'll
do that automagically if you don't use 'local' mode and make
sure you use the correct port designation (the one with modem
control.. ie. /dev/cua0, /dev/cua1 etc).


>    with uugetty it says it can't find the file "utmp"(this file is
>DEFINATLY THERE)....

. but probably not where it expects it. This was a slackware thing,
where the fsstnd said it went one place, but Slackware pre-3.0 put
it somewhere else. If you compiled with the standard paths.h you
get into trouble.

Make sure there is one file called 'wtmp' in /etc, /var/adm or
/var/log, and symbolic links from the other places pointing at 
the right one. The 'correct' fsstnd location is in /var/log.


> and it can't find some lock files in
>/var/spool/uucp/lock/  called "LCK...ttyS1"

FWIW, uugetty is built to handle both dialin and dialout lines.
If that isn't what you need, then you're complicating the issue
in trying to use it. Use getty instead.

Better yet, use mgetty or stick with the simplistic agetty.
getty is not easy to get right, but works like a dream when
you do. I can't really advise you on how to set it up since
I'm running a fairly hacked version thereof (mainly because
uu/getty has some dangerous bugs in the send/get routines
which are used to handle the modems that were causing panics
and traps under kernel 1.2.13).


-- 
David Nugent: davidn@blaze.net.au, davidn@unique.blaze.net.au
Unix/Linux/DOS/Win/Os2 Microsystem Technical Support [FOR HIRE!]
http://www.blaze.net.au/~davidn