Date: Sun, 2 Oct 2005 02:20:12 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Jim Keller <freebsd@contexthosting.net> Cc: freebsd-current@freebsd.org Subject: Re: mount --bind equivalent? mount_null broken or not? Message-ID: <20051002062012.GA12386@xor.obsecurity.org> In-Reply-To: <433F5AD7.9080705@contexthosting.net> References: <433F5AD7.9080705@contexthosting.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 01, 2005 at 11:58:15PM -0400, Jim Keller wrote: > I've been using mount_null for quite some time to mount filesystems=20 > beneath chroot jails, and have had no problems. However, the man page=20 > for mount_null has had a warning (since 1995, apparently) that "IT=20 > DOESN'T WORK", and I know OpenBSD has removed nullfs support as of=20 > version 3.7 (per=20 > http://archives.neohapsis.com/archives/openbsd/2005-09/0198.html). The=20 > bug listed in that thread doesn't appear to apply to FreeBSD, as I was=20 > able to successfully null mount /dev and list its contents. So my=20 > questions are: >=20 > 1. is nullfs actively supported on FreeBSD? If so, are there plans to=20 > continue supporting it? Yes and yes. In fact I don't know of any remaining nullfs bugs on FreeBSD 5 and above (although I only stress it on 6 and above), so the warning should just be removed. Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDP3wcWry0BWjoQKURAmIvAKC+WMIZ7hz3r0RDpNGks/9Po29K0QCghhUt AfD3vlw1Fvzw+8Ytlgn4skQ= =mQib -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051002062012.GA12386>