Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!husc6!seismo!mimsy!chris
From: chris@mimsy.UUCP
Newsgroups: comp.sources.wanted,comp.unix.wizards,comp.unix.questions
Subject: Re: UUCP Port Turnaround
Message-ID: <5439@mimsy.UUCP>
Date: Sun, 15-Feb-87 10:34:22 EST
Article-I.D.: mimsy.5439
Posted: Sun Feb 15 10:34:22 1987
Date-Received: Mon, 16-Feb-87 03:46:45 EST
References: <171@ndmath.UUCP> <4090@nsc.nsc.com> <166@piaget.UUCP> <2388@homxb.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 23
Keywords: uucp
Xref: watmath comp.sources.wanted:523 comp.unix.wizards:971 comp.unix.questions:1044

>In article <43099@beno.seismo.CSS.GOV> rick@seismo.CSS.GOV (Rick Adams) writes:
>>You should try the kernel hack on a decent system before dismissing it.

In article <2388@homxb.UUCP> gemini@homxb.UUCP (Rick Richardson) writes:
>I guess it's just the Berkeley philosophy to do things in the kernel
>whenever possible, even when it's not necessary.

No, and that was a cheap shot.  A few points:

	- Berkeley does not have the line turnaround in the kernel.
	- It *is* necessary, for security if nothing else.

The first is unarguable.  As to the second, think about all the
ways to confuse people dialing in.  You will wind up with only root
being able to do certain things to modem lines.  The kernel does
not now enforce that, so you will have to change it somehow.
(vhangup() almost works, but one can get around it.)  Why not make
the (trivial) changes required to do line turnaround there too?
It costs a few bytes of code, and one extra cdevsw[] entry, per
kind of terminal multiplexor, and two extra bits of data per line.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
UUCP:	seismo!mimsy!chris	ARPA/CSNet:	chris@mimsy.umd.edu