From owner-freebsd-current Wed Apr 22 09:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18065 for freebsd-current-outgoing; Wed, 22 Apr 1998 09:40:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18040 for ; Wed, 22 Apr 1998 16:40:04 GMT (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA16458; Wed, 22 Apr 1998 10:39:52 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA04130; Wed, 22 Apr 1998 10:39:46 -0600 Date: Wed, 22 Apr 1998 10:39:46 -0600 Message-Id: <199804221639.KAA04130@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: Kazutaka YOKOTA , "Alok K. Dhir" , current@FreeBSD.ORG Subject: Re: Disappearing keyboard In-Reply-To: References: <199804220516.OAA00391@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > AFAIK, there are four ways to start xdm and avoid conflicts with getty. > > > > 1. Specify xdm in /etc/ttys. If you want to run xdm in ttyv3, you write: > > > > ttyv3 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure > > This is evil and should never have been suggested in the docs. Why? I contend this is the best way, and have yet to be proven wrong. (Joerg and I had it out publically/privately already on this, so I'm feeling pretty good about my odds. :) > The Right Way (tm) to start X or xdm is to put a shell script in > /usr/local/etc/rc.d which Does the Deed. It will work, no questions > asked. I have something similar to this: So is doing in /etc/ttys. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message