From owner-freebsd-fs  Fri Jun 18 10: 1:45 1999
Delivered-To: freebsd-fs@freebsd.org
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
	by hub.freebsd.org (Postfix) with ESMTP id 4DF5414CA4
	for <freebsd-fs@FreeBSD.ORG>; Fri, 18 Jun 1999 10:01:40 -0700 (PDT)
	(envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
	by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA23314;
	Fri, 18 Jun 1999 19:01:39 +0200 (CEST)
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.8/8.8.6) id TAA62776;
	Fri, 18 Jun 1999 19:01:38 +0200 (MET DST)
Date: Fri, 18 Jun 1999 19:01:38 +0200
From: Eivind Eklund <eivind@FreeBSD.ORG>
To: James Pace <jepace@pobox.com>
Cc: freebsd-fs@FreeBSD.ORG
Subject: Re: nullfs?
Message-ID: <19990618190138.F62123@bitbox.follo.net>
References: <Pine.GSO.4.05.9906161310290.10921-100000@shell1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <Pine.GSO.4.05.9906161310290.10921-100000@shell1>; from James Pace on Wed, Jun 16, 1999 at 01:12:16PM -0700
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Wed, Jun 16, 1999 at 01:12:16PM -0700, James Pace wrote:
> 
> The man page for mount_null(8) warns me:
> 
> THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T
> WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM.  USE AT
> YOUR OWN RISK.  BEWARE OF DOG.  SLIPPERY WHEN WET.
> 
> What are the known problems with it?

Incorrect alias handling (read: your data may or may not reach disk)
and extreme locking problems, mostly.

Eivind.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message