From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 20:19:42 2006 Return-Path: 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 E431716A41F for ; Wed, 18 Jan 2006 20:19:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC1943D53 for ; Wed, 18 Jan 2006 20:19:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6B1201A3C22; Wed, 18 Jan 2006 12:19:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 92B8A5154A; Wed, 18 Jan 2006 15:19:41 -0500 (EST) Date: Wed, 18 Jan 2006 15:19:41 -0500 From: Kris Kennaway To: Ensel Sharon Message-ID: <20060118201941.GA48904@xor.obsecurity.org> References: <20060118191831.GA47747@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 20:19:43 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 18, 2006 at 02:54:04PM -0500, Ensel Sharon wrote: >=20 >=20 > On Wed, 18 Jan 2006, Kris Kennaway wrote: >=20 > > > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. > > >=20 > > > So, based on this, all of my null_mounts are actually mounted read-on= ly. > >=20 > > As others have said, this is no longer applicable to FreeBSD 6.0, and > > it's been removed from HEAD. >=20 >=20 > 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 ? >=20 > Or is 6.0-RELEASE safe ? (re: null_mount) >=20 > Thanks a lot. 6.0-RELEASE is also safe. I only just removed the warning the other day, but I'll also be merging it to 6.0-STABLE. Kris --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDzqLdWry0BWjoQKURAmkyAJ0RZAw/6wUQBijIdmYvsnK+cRu3fwCfdpAG c+FgryPADAnqFcHAkyvsous= =HqKo -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--