According to Darren Reed:
>
> add a new option, "SECURELEVEL" which is the default value
>for securelevel - and that only.  Yes, this will `break' config files but
>that would happen anyway, for someone.
>

It would break more than config files unless you are going to do some
careful coding that will allow certain operations such as mounting
disks, accessing the raw devs (fsck) and so forth before SECURELEVEL
came into effect.  Otherwise you will end up with a broken system due
to the securelevel blocking operations that need to happen to get the
system up and running.

-- 
===============================================================================
Brett Lymn, Computer Systems Administrator, British Aerospace Australia
===============================================================================