From owner-freebsd-stable Fri Mar 9 0:26:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id 5ECFE37B71A for ; Fri, 9 Mar 2001 00:26:02 -0800 (PST) (envelope-from greg@snickers.org) Received: from spike (spike [216.126.90.2]) by mail.snickers.org (Postfix) with ESMTP id 2CB273D46 for ; Fri, 9 Mar 2001 03:26:01 -0500 (EST) Date: Fri, 9 Mar 2001 03:26:01 -0500 (EST) From: Greg Prosser X-X-Sender: Reply-To: Greg Prosser To: Subject: installworld / securelevel Message-ID: X-Sysadmin-Nolife: True X-BOFH: Yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now, before anyone spits back the "this shouldn't be done in multiuser, and shouldn't be done remotely" speech to me, remember we all have to sometimes work in not so perfect conditions. Is it possible for the FreeBSD Makefile jedi to put a kern.securelevel check into the installworld procedure? I'm fairly sure that if key files are set as schg, and securelevel as one, causing an installworld to puke mid-make probably isn't the ideal state to leave a box in, hoping it'll come back after reboot with securelevel lowered. Some of us forget to check things occasionally.. *eyes the terminal where ping is running*, I think I'm ok this time, but doing more in-depth system upgrades might pose a larger problem if userland and kernel aren't in sync.. /gnp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message