Date: Wed, 14 Jul 1999 04:25:10 -0400 (EDT) From: Robert Watson <robert@cyrus.watson.org> To: Greg Black <gjb-freebsd@gba.oz.au> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, Darren Reed <avalon@coombs.anu.edu.au>, security@FreeBSD.ORG Subject: Re: Module magic Message-ID: <Pine.BSF.3.96.990714042411.20080C-100000@fledge.watson.org> In-Reply-To: <19990713122520.5758.qmail@alice.gba.oz.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jul 1999, Greg Black wrote: > Robert Watson writes: > > > > > > FWIW, I believe NetBSD systems (and OpenBSD systems) ship configured to > > > > > boot with securelevel == 0, as opposed to FreeBSD which appears to default > > > > > to -1. > > > > > > > > We think our users are more concerned about X working. > > > > > > Are you saying that X does not work when securelevel >= 0 under > > > FreeBSD? > > > > If I recall, the XiG Accelerated X product requires direct access to > > memory. vm_mmap.c: > > > > [...] > > > > Their code should probably not do this, as direct memory access violates > > kernel safety. > > Can anybody tell me if this breakage only applies to XiG's > Accelerated X or if it is also an issue with XFree86? I believe only for XiG, but I have not tried it in quite a while. The best thing to do to test this is to bump up the sysctl, and then see if X works. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Computing Laboratory at Cambridge University Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990714042411.20080C-100000>