From owner-freebsd-questions@FreeBSD.ORG Mon Oct 20 06:30:12 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3A9D16A4B3 for ; Mon, 20 Oct 2003 06:30:12 -0700 (PDT) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3E1343FBD for ; Mon, 20 Oct 2003 06:30:11 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id A362D3B04; Mon, 20 Oct 2003 09:30:11 -0400 (EDT) Sender: lowell@be-well.ilk.org To: mrb@bmyster.com References: <2776.192.168.25.10.1066606958.squirrel@bmyster.com> From: Lowell Gilbert Date: 20 Oct 2003 09:30:11 -0400 In-Reply-To: <2776.192.168.25.10.1066606958.squirrel@bmyster.com> Message-ID: <44ismkjau4.fsf@be-well.ilk.org> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: questions@freebsd.org Subject: Re: buildingworld & sysctl -w kern.securelevel=2 help?? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 13:30:12 -0000 "Brent Bailey" writes: > After i started my > make buildworld > while it was building .. i noticed that the kernel sysctl was set to > sysctl -w kern.securelevel=2 That's fine. > i tried set it back to 0 or -1 ..but it wouldnt let me. Right. That's the point of securelevels. If it could be changed without rebooting, it wouldn't be much use for security. > is it safe to reboot the system with the sysctl -w kern.securelevel > variable set to -1 ..AFTER the OS has just done a make buildworld ? and > then just pickup where i left off ?? The buildworld should work fine in raised securelevels. Installing (kernels or the rest of the "world") won't, but that's one of the reasons you usually want to do those things in single-user mode. It's quite acceptable (and common) to do the buildworld with the high securelevel and then reboot to continue with the installation.