UUCP on SCO Xenix '386 2.2.2 (bad boy)

[Greg Woods]

This was supposed to be sent by mail, but I can't seem to convince uunet
that it knows about "fozzy" even though uupath shows it does :-)
	$ uupath mjbtn
	ai.toronto.edu!uunet.uu.net!fozzy!killer!mjbtn

   ----- Transcript of session follows -----
550 killer:root.tcp... 550 Host unknown
550 <@uunet.uu.net, at fozzy.uucp, at killer:root at mjbtn>... Host unknown: Inappropriate ioctl for device

   ----- Unsent message follows -----
> Date: Tue, 24 May 88 22:57:34 EDT
> To: mjbtn!root
> In-Reply-To: <260 at mjbtn.UUCP>

I'm running 2.2.1 Update B on 286's and 386's.  Besides the other bugs in
the Kernel, I've come across the same bug you mention with ungetty.

I've written a script that surrounds uucico, and checks the port status
after each run.  The only problem is that all it can do is complain,
since it can't kill the DIALOUT getty when it gets stuck.  I don't want
to do my polling as root, and su to run uucico.  When I get the time, I'll
write an suid program to do the assasination.

I think the bug is in getty, as it happens to me with successfull calls,
and not allways on bad calls.  SCO don't seem interested in fixing it.

SCO Xenix V 2.x.x uucp is based on a port of a VERY old V7 version.  I
doubt we will see anything new for the 286, unless from Microport, or
Interactive, for quite some time (Maybe after System V Rel. 4.0 hits the
bricks, though I hope the 286 is dead and gone by then!)

						Greg Woods.

UUCP: utgpu!woods, utgpu!{cpcc, ontmoh, ontmoh!cpcc, tmsoft!cpcc}!woods
VOICE: (416) 242-7572 [h]		LOCATION: Toronto, Ontario, Canada


-- 
						Greg Woods.

UUCP: utgpu!woods, utgpu!{cpcc, ontmoh, ontmoh!cpcc, tmsoft!cpcc}!woods
VOICE: (416) 242-7572 [h]		LOCATION: Toronto, Ontario, Canada