From owner-freebsd-hackers Wed Jun 5 13:56:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04147 for hackers-outgoing; Wed, 5 Jun 1996 13:56:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04141 for ; Wed, 5 Jun 1996 13:56:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA29664; Wed, 5 Jun 1996 13:51:09 -0700 From: Terry Lambert Message-Id: <199606052051.NAA29664@phaeton.artisoft.com> Subject: Re: /dev/tty and nits in 2.2-960501-SNAP To: kaleb@x.org (Kaleb S. KEITHLEY) Date: Wed, 5 Jun 1996 13:51:09 -0700 (MST) Cc: hackers@freefall.freebsd.org In-Reply-To: <199606051421.KAA09865@exalt.x.org> from "Kaleb S. KEITHLEY" at Jun 5, 96 10:21:58 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Things I note thus far: > > # ls -l /dev/tty > crw-r--r-- 1 root wheel 1, 0 5 Jun 10:16 /dev/tty > > really wants to be: > > crw-rw-rw- 1 root wheel 1, 0 5 Jun 10:16 /dev/tty > > otherwise xterm cannot open it. Breaking xterm is a Bad Thing (tm). Hmmm... I wonder if this change should wait until the xterm sets the ownership on the pty (ie: maybe it should not happen at all). Specifically, you really don't want someone to be able to open the slave side before the pty is allocated, and has a master -- maybe not even then, until the program that grabbed the master provides the slave process itself? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.