Xref: utzoo unix-pc.general:1010 unix-pc.uucp:39
Path: utzoo!utgpu!water!watmath!uunet!lll-winken!pacbell!att!gladys!rbdc!andy
From: andy@rbdc.UUCP (Andy Pitts)
Newsgroups: unix-pc.general,unix-pc.uucp
Subject: Re: 3.51a keeps dying; even HDB is a mess; any ideas out there?
Summary: Have you tried the standard things?
Message-ID: <531@rbdc.UUCP>
Date: 5 Jul 88 21:54:36 GMT
References: <422@kosman.UUCP> <1041@flatline.UUCP>
Reply-To: andy@rbdc.UUCP (Andy Pitts)
Organization: Red Barn Data Center, Winston-Salem, NC.
Lines: 25

This has all been said before but I'll post it again for any new people
who may have missed it.  The standard things that screw up uucp are:

1) The inittab entry.  There MUST be a space preceding the entry for
the tty line in inittab. example:
 ph1:2:respawn:....
^ must have leading space.  If the space is missing setgetty will lock.

2) There is a bug on some versions of the eia/ram cards that causes the
system to crash.  The fix is simple, you just replace a chip.  If you are
using an eia card call the hotline and ask about it.  This bug only affected
V3.50 and later if my memory serves.

3) Also I seem to remember reading that the device driver for tty000 was
brain damaged.  As I recall it will not pass a null (so break won't change
speed) and hardware flow control did not work.  Some or all of this may
have been fixed with the fixdisk, but I don't know.  Perhaps someone else
out there can tell us.  The drivers for the eia cards seem to work however
(if you change the chip).

I hope this helps.
-- 
Andy Pitts andy@rbdc.UUCP  : "The giant Gorf was hit in  one eye  by a stone,
att    \                   : and that eye  turned  inward  so  that it looked
kd4nc   !gladys!rbdc!andy  : into his mind and he died of what he saw there."
pacbell/                   :   --_The Forgotten Beast of Eld_, McKillip--