From owner-freebsd-current Wed Mar 26 02:33:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA01729 for current-outgoing; Wed, 26 Mar 1997 02:33:59 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01724 for ; Wed, 26 Mar 1997 02:33:53 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id KAA20630; Wed, 26 Mar 1997 10:31:03 GMT Date: Wed, 26 Mar 1997 10:25:05 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 26 Mar 1997 10:25:05 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199703252328.QAA26225@phaeton.artisoft.com> References: from "Bob Bishop" at Mar 25, 97 11:00:54 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: Bob Bishop Subject: Re: 2.2R (src 2.2 211): == dialing Cc: bde@zeta.org.au, freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 11:28 pm -0000 25/3/97, Terry Lambert wrote: >[...] >It should be possible to >distinguish a process which has made a tty it's controlling tty >in order to get device events as signals, and a process which >has a controlling tty because it is interactive. Do you mean "a process which has no controlling tty should be able to open a tty without that automatically becoming its controlling tty"? If not, please explain. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK