Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Jul 2003 18:40:28 +0200
From:      Farid Hajji <me@farid-hajji.de>
To:        Bill Moran <wmoran@potentialtech.com>, root@bofh.bg
Cc:        freebsd-current@freebsd.org
Subject:   Re: OT:escaping X barfings
Message-ID:  <200307201840.28680.me@farid-hajji.de>
In-Reply-To: <3F1AB481.5010600@potentialtech.com>
References:  <1058624617.3f1954691cbfc@mail.orbitel.bg> <3F1AB481.5010600@potentialtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> > CAn you tell me how a procedure how to patch X and kernel
> > to avoid X barfings from securelevel? My release is a FreeBSD 5.1.
> >                  2) adding `options APERTURE` to my kernel
> >                  3) make buildkernel && make install kernel && make
> > buildworld 4) reboot and face the music
>
> Do as you feel you must, but I installed 5.1-RELEASE and X from ports and
> it's running fine.  Are you starting from a terminal with 'startx' or do
> you start xdm at boot?  If you use startx, I believe you need to install
> x-wrapper to get around permission issues.

This is a FAQ. X needs to access /dev/io, which is not possible if
securelevel is raised. You need to startx/gdm and _then_ raise
securelevel. This is not flexible, because if X server crashes, you
can't start it again without rebooting.

OpenBSD provides an option 'APERTURE' which allows X to start
even when securelevel is >0. I wish we would have that as well...

-- 
Farid Hajji. http://www.farid-hajji.net/address.html 



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