From owner-freebsd-hackers@FreeBSD.ORG  Wed Jan 18 19:54:07 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2771716A41F
	for <freebsd-hackers@freebsd.org>; Wed, 18 Jan 2006 19:54:07 +0000 (GMT)
	(envelope-from user@dhp.com)
Received: from shell.dhp.com (shell.dhp.com [199.245.105.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D0C9F43D49
	for <freebsd-hackers@freebsd.org>; Wed, 18 Jan 2006 19:54:06 +0000 (GMT)
	(envelope-from user@dhp.com)
Received: by shell.dhp.com (Postfix, from userid 896)
	id 7321A3133D; Wed, 18 Jan 2006 14:54:04 -0500 (EST)
Date: Wed, 18 Jan 2006 14:54:04 -0500 (EST)
From: Ensel Sharon <user@dhp.com>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20060118191831.GA47747@xor.obsecurity.org>
Message-ID: <Pine.LNX.4.21.0601181452360.8684-100000@shell.dhp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 18 Jan 2006 20:01:33 +0000
Cc: freebsd-hackers@freebsd.org
Subject: Re: tuning to run large (1000+) numbers of null_mounts
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2006 19:54:07 -0000



On Wed, 18 Jan 2006, Kris Kennaway wrote:

> >      RISK.  BEWARE OF DOG.  SLIPPERY WHEN WET.
> > 
> > So, based on this, all of my null_mounts are actually mounted read-only.
> 
> As others have said, this is no longer applicable to FreeBSD 6.0, and
> it's been removed from HEAD.


hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE man
page ... if I need to be CURRENT to get the updated man page, do I also
need to be CURRENT to get the safe null_mount code itself ?

Or is 6.0-RELEASE safe ? (re: null_mount)

Thanks a lot.