Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Testing for power at modem port.
Message-ID: <465@toaster.SFSU.EDU>
Date: 9 Apr 90 16:07:49 GMT
References: <2518@sunset.MATH.UCLA.EDU>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 27

In article <2518@sunset.MATH.UCLA.EDU> dgc@euphemia.math.ucla.edu
	(David G. Cantor) writes:
>The problem with this is (it appears) that this will be the only use I
>can make of this port, because of the @#$%!! NON-STANDARD, NON-UNIX
>interlocks on /dev/ttya, /dev/cua, and /dev/ttyda.  These interlocks
>prevent two programs from simultaneously opening this port (under any
>combination of names).

>Is there any hope that, in some future revision of its OS, the NeXT tty
>ports, under one of their aliases, will obey the usual Unix semantics?

"Render unto me a f---ing break."  You don't know how much grief
the `usual' UNIX semantics caused me until I got my hands on a
System V implementation that had intrinsicly interlocking tty
devices, and I'm really sick of BSD claiming to be so "advanced"
when it's still forcing me into 7th edition's limitations.

My commendations to SunOS and NeXT Mach; they're the only BSD-
derived systems I've used that don't have their heads in the sand
on this.  (Now if Mach would only adopt termio...)

I share your concerns (and I've criticized NeXT's handling of
power outages more than once in this forum).  I would like to see
a clean solution, not a kludge, and certainly not at the expense
of essential functionality.

					-=EPS=-