Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!cybvax0!vcvax1!paul
From: paul@vcvax1.UUCP
Newsgroups: comp.sources.wanted,comp.unix.wizards,comp.unix.questions
Subject: Re: UUCP Port Turnaround
Message-ID: <217@vcvax1.UUCP>
Date: Sun, 15-Feb-87 22:14:41 EST
Article-I.D.: vcvax1.217
Posted: Sun Feb 15 22:14:41 1987
Date-Received: Mon, 16-Feb-87 04:06:27 EST
References: <171@ndmath.UUCP> <4090@nsc.nsc.com> <166@piaget.UUCP> <13135@sun.uucp> <2386@homxb.UUCP>
Organization: VenturCom Inc., Cambridge, MA
Lines: 20
Xref: watmath comp.sources.wanted:525 comp.unix.wizards:973 comp.unix.questions:1046

> > of sync.  I've seen solutions proposed where you have two "devices"
> > associated with a terminal port, one for dialing out and one for
> > other uses.
> 
> Venturcom's VENIX did (still does) have hacks like these in the kernel
> tty driver. 

Actually, we took these hacks out in VENIX System V, since, as Rick
pointed out, they didn't work too well, due to problems that
did not appear easily solvable.  Instead, we added
the "ttystate" command, a shell script which (carefully) manipulates
the inittab and turns off and on getty processes.  (I posted this to the net
a while ago.) A uudemon script can use this to disable
the getty before dialing out.  This approach has proved more reliable.


Paul Kleppner
VenturCom, Inc.
617/661-1230
{seismo!harvard,genrad!mit-eddie}!cybvax0!vcvax1!paul