From owner-freebsd-current@FreeBSD.ORG Sun Oct 2 07:50:07 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 D837416A41F for ; Sun, 2 Oct 2005 07:50:07 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: from mail.contexthosting.net (inception.centerfuse.net [209.120.245.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 513C243D46 for ; Sun, 2 Oct 2005 07:50:07 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: (qmail 10149 invoked by uid 89); 2 Oct 2005 07:50:06 -0000 Received: by simscan 1.0.7 ppid: 10145, pid: 10147, t: 0.0470s scanners:none Received: from unknown (HELO ?192.168.1.100?) (jim@contexthosting.net@68.80.252.242) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Oct 2005 07:50:06 -0000 Message-ID: <433F912B.6060308@contexthosting.net> Date: Sun, 02 Oct 2005 03:50:03 -0400 From: Jim Keller User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <433F5AD7.9080705@contexthosting.net> <20051002062012.GA12386@xor.obsecurity.org> In-Reply-To: <20051002062012.GA12386@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 07:50:08 -0000 Hi Kris, Thanks for the response. Are you aware of any bugs in nullfs on FreeBSD 4? I'm still using 4.10/4.11 on a lot of servers. Although, as I mentioned, I've been using nullfs pretty heavily for a ProFTPD chroot for over 2 years now. I just don't want to suddenly get the bum's rush :) -Jim Keller Kris Kennaway wrote: >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 >>beneath chroot jails, and have had no problems. However, the man page >>for mount_null has had a warning (since 1995, apparently) that "IT >>DOESN'T WORK", and I know OpenBSD has removed nullfs support as of >>version 3.7 (per >>http://archives.neohapsis.com/archives/openbsd/2005-09/0198.html). The >>bug listed in that thread doesn't appear to apply to FreeBSD, as I was >>able to successfully null mount /dev and list its contents. So my >>questions are: >> >>1. is nullfs actively supported on FreeBSD? If so, are there plans to >>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 > > Kris Kennaway wrote: >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 >>beneath chroot jails, and have had no problems. However, the man page >>for mount_null has had a warning (since 1995, apparently) that "IT >>DOESN'T WORK", and I know OpenBSD has removed nullfs support as of >>version 3.7 (per >>http://archives.neohapsis.com/archives/openbsd/2005-09/0198.html). The >>bug listed in that thread doesn't appear to apply to FreeBSD, as I was >>able to successfully null mount /dev and list its contents. So my >>questions are: >> >>1. is nullfs actively supported on FreeBSD? If so, are there plans to >>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 > >