From owner-freebsd-security Tue Jul 13 21:57:55 1999 Delivered-To: freebsd-security@freebsd.org Received: from srh0710.urh.uiuc.edu (srh0710.urh.uiuc.edu [130.126.76.32]) by hub.freebsd.org (Postfix) with SMTP id 5671014D5F for ; Tue, 13 Jul 1999 21:57:52 -0700 (PDT) (envelope-from ftobin@uiuc.edu) Received: (qmail 95600 invoked by uid 1000); 14 Jul 1999 04:56:10 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Jul 1999 04:56:10 -0000 Date: Tue, 13 Jul 1999 23:56:10 -0500 (CDT) From: Frank Tobin X-Sender: ftobin@srh0710.urh.uiuc.edu To: security@FreeBSD.ORG Subject: Re: Module magic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Tobin, at 12:53 on Tue, 13 Jul 1999, wrote: > However, it seems, the XFree86 wants to open kmem or mem only on startup; > one can start xdm and have it running fine with a functional securelevel. > The only problem arises if one needs to do a server reset with > Ctrl-Alt-Backspace. Erm, I'd like to correct this before anyone gets confused. I meant to say that in order to get xdm (followed by x session) to work correctly with a securelevel > 0, one needs to start xdm, and _then_ raise the securelevel. This worked fine for me, anyways. Really caused me a lot of confusion, though, the first time the machine rebooted. I couldn't figure out why X was bombing upon startup; it was because the securelevel was being raised before X was starting. -- Frank Tobin "To learn what is good and what is to be www.neverending.org/~ftobin valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus FreeBSD: The Power To Serve PGPenvelope = GPG and PGP5 + Pine PGP: 4F86 3BBB A816 6F0A 340F www.neverending.org/~ftobin/resources.html 6003 56FF D10A 260C 4FA3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message