Date: Tue, 14 Aug 2007 12:26:30 -0700 From: Simon Gao <gao@schrodinger.com> To: Jerry McAllister <jerrymc@msu.edu> Cc: questions@freebsd.org, "illoai@gmail.com" <illoai@gmail.com> Subject: Re: Can't fdisk newly installed disks Message-ID: <46C201E6.8020805@schrodinger.com> In-Reply-To: <20070814190905.GA9655@gizmo.acns.msu.edu> References: <46C0F96C.3060600@schrodinger.com> <d7195cff0708140207i39be4fcbvc0172673fc5a77b4@mail.gmail.com> <46C1F8FD.6090406@schrodinger.com> <20070814190905.GA9655@gizmo.acns.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <gao@schrodinger.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46C201E6.8020805>