From owner-freebsd-current  Mon Sep 11 18:23:23 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA14700
          for current-outgoing; Mon, 11 Sep 1995 18:23:23 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA14694
          for <current@freefall.freebsd.org>; Mon, 11 Sep 1995 18:23:19 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA14593; Mon, 11 Sep 1995 18:14:25 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199509120114.SAA14593@phaeton.artisoft.com>
Subject: Re: Is nullfs broken in -current?
To: gary@palmer.demon.co.uk (Gary Palmer)
Date: Mon, 11 Sep 1995 18:14:25 -0700 (MST)
Cc: jkh@time.cdrom.com, current@freefall.freebsd.org
In-Reply-To: <6410.810844646@palmer.demon.co.uk> from "Gary Palmer" at Sep 11, 95 07:37:26 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 467       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> AFAIK, nullfs has always been broken for `writing' - but I used it
> successfully on my machine here for over 2 months read only fine. I
> think that may be your problem...

Document an instance and a mount command line that would cause this to
be useful.

If I agree, and it doesn't just work on the Lite2 code, I'll fix it.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.