From owner-freebsd-questions@FreeBSD.ORG Tue Aug 14 19:26:31 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97E3516A46B for ; Tue, 14 Aug 2007 19:26:31 +0000 (UTC) (envelope-from gao@schrodinger.com) Received: from schrodinger.com (thermidore.schrodinger.com [192.156.98.99]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0CD13C478 for ; Tue, 14 Aug 2007 19:26:31 +0000 (UTC) (envelope-from gao@schrodinger.com) Received: from [192.156.98.12] (ithi.schrodinger.com [192.156.98.12]) by schrodinger.com (8.13.4/8.13.4) with ESMTP id l7EJQUfd096940; Tue, 14 Aug 2007 12:26:31 -0700 (PDT) (envelope-from gao@schrodinger.com) Message-ID: <46C201E6.8020805@schrodinger.com> Date: Tue, 14 Aug 2007 12:26:30 -0700 From: Simon Gao User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: Jerry McAllister References: <46C0F96C.3060600@schrodinger.com> <46C1F8FD.6090406@schrodinger.com> <20070814190905.GA9655@gizmo.acns.msu.edu> In-Reply-To: <20070814190905.GA9655@gizmo.acns.msu.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (schrodinger.com [192.156.98.99]); Tue, 14 Aug 2007 12:26:31 -0700 (PDT) Cc: questions@freebsd.org, "illoai@gmail.com" Subject: Re: Can't fdisk newly installed disks X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2007 19:26:31 -0000 Jerry McAllister wrote: > On Tue, Aug 14, 2007 at 11:48:29AM -0700, Simon Gao wrote: > > >> illoai@gmail.com wrote: >> >>> On 13/08/07, Simon Gao wrote: >>> >>> >>>> Hi, >>>> >>>> I am running into some problem with fdisk newly installed drives. >>>> >>>> >>> . . . >>> >>> >>>> # fdisk -BI da5 >>>> fdisk: cannot open disk /dev/da5: No such file or directory >>>> >>>> >>> What is your securelevel? >>> >>> For example: >>> % sysctl kern.securelevel >>> kern.securelevel: -1 >>> >>> man init for more about securelevels. >>> >>> >>> >> # sysctl kern.securelevel >> kern.securelevel: 3 >> >> Does higher security level prevent one from adding new file system? >> > > It can prevent you from making almost any changes. A secure level of 3 > is very high and may be what you want for your production - depending > on what you are doing, but will make any installation or development > very difficult or impossible. > > ////jerry > > Thanks, Jerry. I tried to lower secure level, but still run into similar error: # sysctl kern.securelevel=-1 kern.securelevel: 3 sysctl: kern.securelevel: Operation not permitted Is there other way to reduce secure level to -1 without reboot the machine or drop into single user mode? Simon