[comp.unix.questions] Bidirectional tty port for 386ix

fiasco@infoserv.com (Rich Gircys) (11/09/90)

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

tin@smsc.sony.com (Tin Le) (11/10/90)

In article <12.26746@infoserv.com> fiasco@infoserv.com (Rich Gircys) writes:
> .............
>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)

  You need to use /usr/lib/uucp/uugetty.  That version of getty will leave
  the port under uucp ownership (and work better too with cu/uucico).

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

  Don't do that.  It'll just open up one more security hole in your system.

-- Tin

-- 
.----------------------------------------------------------------------
. Tin Le                    Work Internet: tin@smsc.Sony.COM
. Sony Microsystems              UUCP: {uunet,mips}!sonyusa!tin
. Work: (408) 944-4157      Home Internet: tin@szebra.uu.net

alex@am.sublink.org (Alex Martelli) (11/13/90)

tin@smsc.sony.com (Tin Le) writes:
>In article <12.26746@infoserv.com> fiasco@infoserv.com (Rich Gircys) writes:
>> .............
>>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)

>  You need to use /usr/lib/uucp/uugetty.  That version of getty will leave
>  the port under uucp ownership (and work better too with cu/uucico).

Under Interactive 2.2's tty driver, there's an alternative - put a
normal getty on ttyd0, and use acu0 for dial-out - the *driver* will
handle the necessary handshaking.  The freely available FAS driver,
I believe, implements a similar philosophy on many Unices.
-- 
Alex Martelli - (home snailmail:) v. Barontini 27, 40138 Bologna, ITALIA
Email: (work:) staff@cadlab.sublink.org, (home:) alex@am.sublink.org
Phone: (work:) ++39 (51) 371099, (home:) ++39 (51) 250434; 
Fax: ++39 (51) 366964 (work only), Fidonet: 332/401.3 (home only).