From owner-freebsd-current Mon Jul 6 09:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07336 for freebsd-current-outgoing; Mon, 6 Jul 1998 09:47:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07327 for ; Mon, 6 Jul 1998 09:46:59 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-138.camalott.com [208.229.74.138]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA32031; Mon, 6 Jul 1998 11:46:55 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06285; Mon, 6 Jul 1998 11:46:33 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Jul 1998 11:46:33 -0500 (CDT) Message-Id: <199807061646.LAA06285@detlev.UUCP> To: smoergrd@oslo.geco-prakla.slb.com CC: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG In-reply-to: (smoergrd@oslo.geco-prakla.slb.com) Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807060816.MAA27917@minas-tirith.pol.ru> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Hmm... WHY X cannot be started with securelevel set? Is it a bug or >> a feature? > I guess it's a feature. 'man 8 init'. Anyway, there are a lot more > things you can't do at securelevel >= 1; installing a new kernel or > world, for instance, since they involve overwriting immutable files. Most things that are disallowed under securelevel 1 are things that aren't frequently done except during rc, a system install, or an attack. But running X is a normal operation. I'd classify it as a bug myself. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message