Skip site navigation (1)Skip section navigation (2)
Date:      18 Dec 2002 13:40:21 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
To:        "Soup4you2" <soup4you2@blackmarketbabies.com>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   Re: X and kern_securelevel
Message-ID:  <443covrx0q.fsf@be-well.ilk.org>
In-Reply-To: <62125.66.160.16.51.1036593111.squirrel@localhost.blackmarketbabies.com>
References:  <62125.66.160.16.51.1036593111.squirrel@localhost.blackmarketbabies.com>

next in thread | previous in thread | raw e-mail | index | archive | help
"Soup4you2" <soup4you2@blackmarketbabies.com> writes:

> Riddle me this batman..
> 
> Environment
> FreeBSD xxxxxxxxxxxxxx 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Mon Oct 21
> 17:33:06 EST 2002     xxxxxxxxx@xxxxxxxxx.com:/usr/obj/usr/src/sys/SOUPX 
> i386
> 
> Description
> Why is it that if i slap :
> kern_securelevel_enable="YES"
> kern_securelevel="1"
> 
> inside my rc.conf i am no longer able to start X
> i get the following error message
> 
> Fatal server error:
> xf86EnableIO: Failed to open /dev/io for extended I/O
> 
> where as if i disable kern_securelevel it works fine..

This is covered in the FAQ.

The short explanation is that it's a security feature (X writes
directly into memory).

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443covrx0q.fsf>