From owner-freebsd-current@FreeBSD.ORG Sun Oct 2 06:20:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5911816A41F for ; Sun, 2 Oct 2005 06:20:20 +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 1567843D46 for ; Sun, 2 Oct 2005 06:20:20 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [70.30.70.180]) by elvis.mu.org (Postfix) with ESMTP id CD1261A3C1B; Sat, 1 Oct 2005 23:20:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B54F951416; Sun, 2 Oct 2005 02:20:12 -0400 (EDT) Date: Sun, 2 Oct 2005 02:20:12 -0400 From: Kris Kennaway To: Jim Keller Message-ID: <20051002062012.GA12386@xor.obsecurity.org> References: <433F5AD7.9080705@contexthosting.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <433F5AD7.9080705@contexthosting.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: mount --bind equivalent? mount_null broken or not? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 06:20:20 -0000 --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--