From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Newall Subject: Re: New filesystem for Linux kernel Date: Wed, 25 Feb 2009 20:03:21 +1030 Message-ID: <49A51061.2040300@davidnewall.com> References: <7558.1235374266@jrobl> <7769.1235374482@jrobl> <49A268A7.1010708@slax.org> <49A26ACC.90804@slax.org> <49A3AC14.2050107@slax.org> <20090224141548.GB5482@mit.edu> <1235488695.15148.49.camel@moss-terrapins.epoch.ncsc.mil> <49A4F3EC.7060005@slax.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "David P. Quigley" , Theodore Tso , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Tomas M Return-path: In-Reply-To: <49A4F3EC.7060005@slax.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Tomas M wrote: > In general, I need an union filesystem and I do not care if that is unionfs or aufs. Agreed. Well said. > I wish aufs to be mainlined; because the code simply works, since its initial release, for many years. Perhaps; but consider Okajima-san's rationale, "Aufs2 is a refined version of old aufs1: - to be reviewed easily and widely. - to make the source files simpler and smaller by dropping several original features." Do note assume the code being proposed is the same as, or of the same quality as, that from AUFS1. If we really believe in choice, then unless AUFS2 obviously breaks things, it's hard to argue against it's inclusion. Thus can best-of-breed emerge.