Subject: Re: rc.d: securelevel and kern.securelevel behavior in 1.5S/macppc
To: Chris Tribo <firstname.lastname@example.org>
From: Manuel Bouyer <email@example.com>
Date: 03/31/2001 17:19:50
On Fri, Mar 30, 2001 at 02:27:50PM -0500, Chris Tribo wrote:
> I changed my rc.conf and added the line securelevel=NO, used 'shutdown
> now' and then exited to reload the rc's. In the rc script I got "Kernel
> securelevel 0 -> 0" but then as soon as the rc finished, and the Login
> prompt popped up on the console, I got init: kernel securelevel changed from
> 0 -> 1. There's apparently no man page for securelevel and sysctl -w
> kern.securelevel=0 is denied, for obvious reasons. Is this the expected
> behavior? This is just the standard GENERIC kernel config, do I need
> options=insecure in my kernel config to get securelevel 0 in multi-user?
yes, you need 'options INSECURE'.
Hum, maybe we could now remove code from init which bumps the securelevel,
as it's done in the rc script ...
Manuel Bouyer <firstname.lastname@example.org>