From owner-freebsd-hackers Sun Apr 27 01:44:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04493 for hackers-outgoing; Sun, 27 Apr 1997 01:44:31 -0700 (PDT) Received: from fcggsg07.icg.tu-graz.ac.at (fcggsg07.icg.tu-graz.ac.at [129.27.201.16]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04488 for ; Sun, 27 Apr 1997 01:44:25 -0700 (PDT) Received: from lend.tu-graz.ac.at (isdn074.tu-graz.ac.at [129.27.240.74]) by fcggsg07.icg.tu-graz.ac.at (8.8.4/8.8.4) with ESMTP id KAA24409 for ; Sun, 27 Apr 1997 10:44:18 +0200 (MDT) Received: from localhost (lend.tu-graz.ac.at [127.0.0.1]) by lend.tu-graz.ac.at (8.8.5/8.8.5) with SMTP id KAA00420 for ; Sun, 27 Apr 1997 10:42:19 +0200 (CEST) Date: Sun, 27 Apr 1997 10:42:19 +0200 (CEST) From: Martin Kammerhofer To: hackers@hub.freebsd.org Subject: Re: sysctl -A In-Reply-To: <199704270447.VAA27744@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There's a workaround to solve the "X exor securelevel" problem. I use # X must be up and running before setting securelevel to $slev > 0 (sleep $sleep; sysctl -w kern.securelevel=$slev) & in my rc.local right after starting xdm. So securelevel is raised after X got it's write access to VGA memory (which securelevel > 0 would prohibit). The drawbacks are: 1. You have to go single user to restart your X server if it should die (fortunately this never happened to me :). 2. securelevel > 0 prevents you from using modload too (preload all anticipated lkms or go single user again here). NetBSD is said to have a cleaner solution, they're using a special device for X's memory access. Martin