From owner-freebsd-stable Wed Nov 12 06:44:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA07722 for stable-outgoing; Wed, 12 Nov 1997 06:44:59 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA07716 for ; Wed, 12 Nov 1997 06:44:56 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id JAA17931; Wed, 12 Nov 1997 09:44:32 -0500 (EST) Date: Wed, 12 Nov 1997 09:44:32 -0500 (EST) From: John Fieber To: Michael Knoll cc: Ted Spradley , stable@FreeBSD.ORG Subject: Re: X11 and /tmp In-Reply-To: <3.0.32.19971112020937.00a15400@lafcol.lafayette.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Nov 1997, Michael Knoll wrote: > >Bad Thing. I *hate* that. In defiance, I've been starting xdm by listing it > >in my /etc/ttys file for years with no noticeable ill effect. Can anyone > >tell me *why* it's a Bad Thing? > > Loading XDM like this does not allow network XDM connections. How can I > load it to get both local and network XDM logins. For what its worth, I've never observed this behavior. I've always started xdm in /etc/ttys and frequntly log in from remote X terminals using XDMCP without any problem. -john