Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxc.cso.uiuc.edu!fthood!egray
From: egray@fthood.UUCP
Newsgroups: comp.unix.i386
Subject: Re: uugetty in 386/ix
Message-ID: <11500001@fthood>
Date: 13 Nov 89 01:40:40 GMT
References: <1324@krafla.rhi.hi.is>
Lines: 35
Nf-ID: #R:krafla.rhi.hi.is:1324:fthood:11500001:000:1361
Nf-From: fthood.UUCP!egray    Nov 11 11:22:00 1989


> Hello netland !
> 
> I am having a *whole* lot of trouble getting uugetty in the 386/ix 
> ver. 2.0.1 to work properly.  I heard that there was a recent discussion 
> about ISC uugetty  on this newsgroup which I  missed.
> 
> If someone out there has an archive of the discussion or a solution,
> I would be thankful if he/she could e-mail me an update.
> 
> Thanks in advance. 

One of the not-quite-so-obvious requirments is that uugetty wants full
modem control on the port.  My version of ISC (actually from Dell) did
come with the devices configured for both "normal" and "modem control",
although the driver supports them both.  To fix, I created the devices
/dev/ttym0 and /dev/ttym1 with minor device numbers 16 for ttym0, and 17
for ttym1

Another misprint in the documentation leads you to beleive that the
line in /etc/inittab should read:

	01:2345:respawn:/usr/lib/uucp/uugetty /dev/ttym01 2400

But uugetty actually uses the first argument to create the lock file,
so that the "/dev/" part of "/dev/ttym01" will screw things up.  I have
mine set as:

	01:2345:respawn:/usr/lib/uucp/uugetty -t 60 ttym01 2400

Emmet P. Gray				US Army, HQ III Corps & Fort Hood
...!uunet!uiucuxc!fthood!egray		Attn: AFZF-DE-ENV
fthood!egray@uxc.cso.uiuc.edu		Directorate of Engineering & Housing
					Environmental Management Office
					Fort Hood, TX 76544-5057