From owner-freebsd-current@FreeBSD.ORG Sat Mar 5 15:19:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0F06016A4CF; Sat, 5 Mar 2005 15:19:03 +0000 (GMT) Date: Sat, 5 Mar 2005 15:19:03 +0000 From: Kris Kennaway To: Denis Shaposhnikov Message-ID: <20050305151903.GC26240@hub.freebsd.org> References: <87is46kzk1.fsf@neva.vlink.ru> <41C26F23F7DF023CB3DF35C5@cc-171.int.t-online.fr> <87sm3ajj8s.fsf@neva.vlink.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sm3ajj8s.fsf@neva.vlink.ru> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Mathieu Arnold Subject: Re: unionfs 5.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 05 Mar 2005 15:19:03 -0000 On Sat, Mar 05, 2005 at 04:49:07PM +0300, Denis Shaposhnikov wrote: > >>>>> "Mathieu" == Mathieu Arnold writes: > > Mathieu> I'm not answering to your question, but what's the need of a > Mathieu> ro unionfs, a ro nullfs would do the same, no ? > > It seems that nullfs much slower. But it works, and doesn't panic the system. unionfs is well-documented to be broken, and this is unlikely to change in the near future. Kris