From owner-freebsd-current  Mon Apr  3 16:05:15 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA22858 for current-outgoing; Mon, 3 Apr 1995 16:05:15 -0700
Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA22850 for <current@freebsd.org>; Mon, 3 Apr 1995 16:05:12 -0700
Received: from metal.ops.neosoft.com (root@glenn-slip55.nmt.edu [129.138.5.155]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id SAA09018 for <current@freebsd.org>; Mon, 3 Apr 1995 18:04:51 -0500
Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id RAA00336 for current@freebsd.org; Mon, 3 Apr 1995 17:04:47 -0600
Date: Mon, 3 Apr 1995 17:04:47 -0600
From: Scott Mace <smace@metal-mail.neosoft.com>
Message-Id: <199504032304.RAA00336@metal.ops.neosoft.com>
To: current@FreeBSD.org
Subject: a few patches...
Sender: current-owner@FreeBSD.org
Precedence: bulk



I would like to add a config option to enable as disable securelevel.
the securelevel and chflags features are a major security helper IMHO.

Also, on a totally unrelated note, I've found on at least 2 scsi drives
I've used I need a pause right before the extended probe kicks off.
(bt_inquire_setup_information) The minimal pause I've experimentally 
found is DELAY(450000).  This is with the bt driver.  I've had this patch
in my set of "local" patches forever, but when I brought it up before, 
noone wanted it committed.  Oh the horrors of yet another pause (which
is nothing compared the the SCSI_WAIT stuff).  The reason I'm bringing
this up again is because I found _another_ drive that needs this little
pause.  

So, what does everyone think?

        Scott