Xref: utzoo comp.unix.sysv386:1957 comp.unix.questions:26789
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!mips!infoserv!fiasco
From: fiasco@infoserv.com (Rich Gircys)
Newsgroups: comp.unix.sysv386,comp.unix.questions
Subject: Bidirectional tty port for 386ix
Keywords: bidirectional tty, Interactive, Esix, dialin dialout
Message-ID: <12.26746@infoserv.com>
Date: 8 Nov 90 17:08:57 GMT
Followup-To: poster
Organization: InfoServ Connections, Corralitos, CA. U.S.A.
Lines: 29


I have been working on setting up a bi-directional tty line (for use
as dial-in and dial-out) on a 386 running Interactive Unix, and have run 
into a number of problems. The problems/resulting questions might be
Interactive specific since I'm following the same bi-dir setup I use
on a 386 machine with Esix Unix (which as an aside, if anyone wants to
know how to do this for Esix, send me mail).

Basically, here's what happens:

o dial-out works OK as long as there's no getty on the line

o however, as soon as a getty is started on that line, a dial-out attempt
  (Uutry) will fail because the getty changes the /dev/tty permissions; Uutry
  fails errno=13 (permissions problem)

I have tried making uucico setuid root (which usually solves all permission
problems) but the failure is the same.

What's really perplexing is that On my Esix system, getty changes /dev/tty
permissions also, but uucico works none the less.

If anyone has had the same experience with Interactive Unix and has hints/
insight into what's going on please let me know (preferably by email).

P.S. If you're thinking of Unix for 386, get Esix. Price/performance/service
wise they are the best value.

thanks, Gintaras Gircys { uunet | ...motcsd | ...apple}!infoserv!fiasco