From owner-freebsd-stable Wed Jan 27 03:43:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02543 for freebsd-stable-outgoing; Wed, 27 Jan 1999 03:43:49 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA02523 for ; Wed, 27 Jan 1999 03:43:46 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Jan 99 11:43:41 +0000 (GMT) To: freebsd-stable@FreeBSD.ORG Subject: Re: Keyboard Not Responding With X startup In-reply-to: Your message of "Wed, 27 Jan 1999 02:57:29 +0100." <199901270157.CAA06301@dorifer.heim3.tu-clausthal.de> Date: Wed, 27 Jan 1999 11:43:41 +0000 From: David Malone Message-ID: <9901271143.aa23872@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You should not start X before init has finished running /etc/rc > and starting all of its gettys (according to /etc/ttys). > Otherwise init will try to start a getty on the same vty on > which X is running, which is a Bad Thing. > > The easiest way to avoid all of those problems would be to > run xdm from /etc/ttys. I think there's even a (disabled) > example entry in that file. This is a really bad idea - "xdm -nodaemon" seems to have weird bugs which can result in thousands of xdm's being spawned if someone does an X -indirect to your machine. Besides rc.local is the right sort of place for this to happen. I'm suffering from the same problem, but putting sshd before xdm in rc.local seems to provide enough of a delay. Could this be related to the new console driver stuff? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message