From: Lars Marowsky-Bree Subject: Re: GFS, what's remaining Date: Thu, 1 Sep 2005 17:11:18 +0200 Message-ID: <20050901151118.GV28276@marowsky-bree.de> References: <20050901104620.GA22482@redhat.com> <20050901035939.435768f3.akpm@osdl.org> <1125586158.15768.42.camel@localhost.localdomain> <20050901142708.GA24933@infradead.org> <1125588511.15768.52.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andrew Morton , David Teigland , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-cluster@redhat.com Return-path: To: Alan Cox , Christoph Hellwig Content-Disposition: inline In-Reply-To: <1125588511.15768.52.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 2005-09-01T16:28:30, Alan Cox wrote: > Competition will decide if OCFS or GFS is better, or indeed if someon= e > comes along with another contender that is better still. And competit= ion > will probably get the answer right. Competition will come up with the same situation like reiserfs and ext3 and XFS, namely that they'll all be maintained going forward because of= , uhm, political constraints ;-) But then, as long as they _are_ maintained and play along nicely with eachother (which, btw, is needed already so that at least data can be migrated...), I don't really see a problem of having two or three. > The only thing that is important is we don't end up with each cluster= fs > wanting different core VFS interfaces added. Indeed. Sincerely, Lars Marowsky-Br=E9e --=20 High Availability & Clustering SUSE Labs, Research and Development SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin "Ignorance more frequently begets confidence than does knowledge"