Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Dec 2005 12:15:17 +0100
From:      Matthias Andree <matthias.andree@gmx.de>
To:        Craig Rodrigues <rodrigc@crodrigues.org>
Cc:        freebsd-fs@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: XFS (read-only) support committed to CURRENT
Message-ID:  <m37ja59ttm.fsf@merlin.emma.line.org>
In-Reply-To: <20051213151908.GA26821@crodrigues.org> (Craig Rodrigues's message of "Tue, 13 Dec 2005 10:19:08 -0500")
References:  <20051213151908.GA26821@crodrigues.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Craig Rodrigues <rodrigc@crodrigues.org> writes:

> Read-only XFS support has been committed to FreeBSD-CURRENT.
> Write access to XFS is not supported at this time.
> The XFS for FreeBSD source code is based off of GPL'd sources
> provided by SGI.

Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like
ext2fs is? If so, allow me a question why XFS was chosen in preference
to ext3fs?

Ext3fs appears to have some advantages, easy migration from and to
ext2fs, shrinkable, data journalling, data ordering (write data blocks
before the file metadata is written) and so on.

I don't mean this should become an advocacy discussion, as XFS surely
has advantages, too, real-time capability and so on - but ext2fs is
already there and has write support.

Just curious.

-- 
Matthias Andree



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m37ja59ttm.fsf>