Date: Wed, 18 Jan 2006 15:19:41 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Ensel Sharon <user@dhp.com> Cc: freebsd-hackers@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: tuning to run large (1000+) numbers of null_mounts Message-ID: <20060118201941.GA48904@xor.obsecurity.org> In-Reply-To: <Pine.LNX.4.21.0601181452360.8684-100000@shell.dhp.com> References: <20060118191831.GA47747@xor.obsecurity.org> <Pine.LNX.4.21.0601181452360.8684-100000@shell.dhp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060118201941.GA48904>