From owner-freebsd-current@FreeBSD.ORG  Wed Jun 30 01:39:26 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 758)
	id 3B27716A4CF; Wed, 30 Jun 2004 01:39:26 +0000 (GMT)
Date: Wed, 30 Jun 2004 01:39:26 +0000
From: Kris Kennaway <kris@FreeBSD.org>
To: Tim Robbins <tjr@freebsd.org>
Message-ID: <20040630013926.GA97839@hub.freebsd.org>
References: <20040628212811.W658@korben.in.tern>
	<20040628215640.C14935C29@techpc04.okladot.state.ok.us>
	<20040629103724.GA25753@cat.robbins.dropbear.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040629103724.GA25753@cat.robbins.dropbear.id.au>
User-Agent: Mutt/1.4.1i
cc: freebsd-current@FreeBSD.org
Subject: Re: Q's about IBM TSM (was Re: HEADSUP: ibcs2 and svr4 compat
	headedfor history)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2004 01:39:26 -0000

On Tue, Jun 29, 2004 at 08:37:24PM +1000, Tim Robbins wrote:
> On Mon, Jun 28, 2004 at 04:56:40PM -0500, Paul Seniura wrote:
> 
> > I google'd and didn't like what I saw.  Stuff about
> > nullfs not being too kosher on -Current.  :(
> 
> There seems to be a lot of superstition surrounding nullfs, but I only
> know of one outstanding reproducible problem with it in -current (sockets
> and fifos aren't handled correctly and cause panics.) If you can spare the
> time to experiment, I suggest trying it, then filing a PR if you encounter
> any problems. There's no guarantee that these problems will be addressed
> right away, but it will give others more solid information than rumours
> to go by when deciding whether or not to use nullfs, and well-documented
> problems are much more likely to get fixed.

FYI, I use read-only nullfs extensively for package builds (with a
static lower layer, and no sockets or fifos in either layer).  I
haven't had any problems with it.

Kris