Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!yale!quasi-eli!cs.yale.edu!yarvin-norman
From: yarvin-norman@cs.yale.edu (Norman Yarvin)
Newsgroups: comp.sys.3b1
Subject: Re: problems with graphics under TAM
Message-ID: <28881@cs.yale.edu>
Date: 18 Feb 91 21:40:22 GMT
References: <1991Feb18.190101.22034@uncecs.edu>
Sender: news@cs.yale.edu
Organization: Yale Computer Science Department
Lines: 27
Nntp-Posting-Host: turquoise.systemsx.cs.yale.edu
Originator: yarvin@turquoise.CS.Yale.Edu

tcamp@uncecs.edu (Ted A. Campbell) writes:
>(1) What happened to /dev/tty under TAM?

A call to setpgrp() might fix this.  I think setpgrp() sets the terminal
associated with your device; this in in some way a 'process group'.

>   close( 0 );
>   close( 1 );
>   close( 2 );

Put it here

>   w_id = open( "/dev/window", O_RDWR );
>   dup( w_id );
>   dup( w_id );

or here; see which works.

>Normally I accomplish this by taking hold of /dev/tty
>and altering its parameters so that a read() of the keyboard
>(/dev/tty) will return immediately if it does not succeed.

Why don't you just dup() your file descriptor, and alter the copy?

--
Norman Yarvin					yarvin-norman@cs.yale.edu
 "Obviously crime pays, or there'd be no crime." -- G. Gordon Liddy