From owner-freebsd-current@FreeBSD.ORG Sun Jul 20 09:40:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BFCC37B401 for ; Sun, 20 Jul 2003 09:40:27 -0700 (PDT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id A489743FAF for ; Sun, 20 Jul 2003 09:40:25 -0700 (PDT) (envelope-from me@farid-hajji.de) Received: (qmail 24592 invoked by uid 505); 20 Jul 2003 16:40:29 -0000 Received: from me@farid-hajji.de by dsl-mail by uid 502 with qmail-scanner-1.14 (spamassassin: 2.43. Clear:. Processed in 0.179227 secs); 20 Jul 2003 16:40:29 -0000 Received: from unknown (HELO reverse-213-146-116-200.dialin.kamp-dsl.de) (213.146.116.200) by dsl-mail.kamp.net with SMTP; 20 Jul 2003 16:40:28 -0000 From: Farid Hajji To: Bill Moran , root@bofh.bg Date: Sun, 20 Jul 2003 18:40:28 +0200 User-Agent: KMail/1.5.2 References: <1058624617.3f1954691cbfc@mail.orbitel.bg> <3F1AB481.5010600@potentialtech.com> In-Reply-To: <3F1AB481.5010600@potentialtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307201840.28680.me@farid-hajji.de> cc: freebsd-current@freebsd.org Subject: Re: OT:escaping X barfings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: me@farid-hajji.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 16:40:27 -0000 > > 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