From owner-freebsd-stable Sat Mar 10 17: 0:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from enigma.crypt-net.org (enigma.crypt-net.org [216.254.75.169]) by hub.freebsd.org (Postfix) with ESMTP id 6217B37B718 for ; Sat, 10 Mar 2001 17:00:53 -0800 (PST) (envelope-from mjw@crypt-net.org) Received: from indigo.crypt-net.org (indigo.crypt-net.org [216.254.75.170]) by enigma.crypt-net.org (Postfix) with ESMTP id 08994202E for ; Sat, 10 Mar 2001 20:00:46 -0500 (EST) Date: Sat, 10 Mar 2001 19:56:33 -0500 From: Matt White To: stable@freebsd.org Subject: Read-only UnionFS Message-ID: <22480000.984272193@indigo.crypt-net.org> X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have need of a union like filesystem but do not need that filesystem to be read-write. My understanding is that the main broken-ness of the union filesystem is that whiteouts are likely to cause my system to panic. Since I'm mounting my unions read-only, this particular problem shouldn't bother me. I'm wondering if there is any other major brokeness with the union filesystem. Anyone else out there play with this? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message