From owner-freebsd-security  Wed Sep 17 09:55:31 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA24596
          for security-outgoing; Wed, 17 Sep 1997 09:55:31 -0700 (PDT)
Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA24585
          for <freebsd-security@freebsd.org>; Wed, 17 Sep 1997 09:55:25 -0700 (PDT)
Received: from eagle.bigblue.no (eagle.bigblue.no [194.19.68.13])
          by login.bigblue.no (8.8.7/8.8.5) with SMTP id SAA26869;
          Wed, 17 Sep 1997 18:55:09 +0200 (MET DST)
Message-Id: <199709171655.SAA26869@login.bigblue.no>
From: "Frode Nordahl" <froden@bigblue.no>
To: "Sean Kelly" <kelly@fsl.noaa.gov>
Cc: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org>
Date: Wed, 17 Sep 97 18:55:07 +0100
Reply-To: "Frode Nordahl" <froden@bigblue.no>
Priority: Normal
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: schg flag...
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 17 Sep 1997 10:45:31 -0600, Sean Kelly wrote:

>The schg flag can't be changed when the system is running in securelevel
>1 or 2.  See init(1) for more details.
>
>According to that man page, the securelevel is usually set in /etc/rc
>during bootup.  A quick grep through /etc/* doesn't contain any
>reference to securelevel, though.  You could probably add it yourself to
>your own rc files, but it'd be nice if there were an /etc/rc.conf entry
>for it.

Ok... Well then's a question, why is FreeBSD's standard mode to run in leve -1?  Isn't that a bit suicidal?
_____________________________________________________________
Frode Nordahl         | P.B. 2509 Solli | Tel +47 22 20 47 18
Teknisk ansvarlig     | 0202 Oslo       | Fax +47 22 20 39 19
Computer Tjenester AS | Norway          | froden@bigblue.no