From owner-freebsd-questions Tue Jul 21 16:59:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15369 for freebsd-questions-outgoing; Tue, 21 Jul 1998 16:59:35 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-17.ix.netcom.com [206.214.137.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15285 for ; Tue, 21 Jul 1998 16:59:01 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id QAA01833; Tue, 21 Jul 1998 16:58:31 -0700 (PDT) (envelope-from tomdean) Date: Tue, 21 Jul 1998 16:58:31 -0700 (PDT) Message-Id: <199807212358.QAA01833@ix.netcom.com> From: Thomas Dean To: ron@dc.infi.net CC: freebsd-questions@FreeBSD.ORG In-reply-to: <9807211702.AA05774@ara.office.aol.com> (message from Ron Steele on Wed, 22 Jul 1998 01:04:40 -0400) Subject: Re: Why is XDM in /etc/ttys a Bad Thing? Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reformatting, ron@shellhost.dc.infi.net said: > It's a control issue. As long as everything is working perfectly, XDM > is just fine. If trouble starts to rear it's ugly head, XDM can make > it less apparent and/or harder to fix. I guess I am a control freak, > but I like to see the messages printed on the console when the system > boots, and I don't mind typing xinit at all. Also, if X crashs you > still have a login. If you change video hardware, you can boot into > your normal shell and fix things up so X works again. etc. If xdm is in /etc/ttys, it does not start until just after login on vty0 is allowed. You see all the messages from boot. You can still login on the vty's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message