Editing Getting the latest source code

== <font face="ARIAL NARROW,HELVETICA"> XFS Released/Stable source </font> ==

Note: as of September 2016, the XFS project is moving away from oss.sgi.com infrastructure. As we move to other infrastructure the links below will be updated to point to the new locations.

* '''Mainline kernels'''
:XFS has been maintained in the official Linux kernel [http://www.kernel.org/ kernel trees] starting with [http://lkml.org/lkml/2003/12/8/35 Linux 2.4] and is frequently updated with the latest stable fixes and features from the XFS development team.

* '''Vendor kernels'''
:All modern Linux distributions include support for XFS. 

* '''XFS userspace'''
:[https://kernel.org/pub/linux/utils/fs/xfs source code tarballs] of the xfs userspace tools. These tarballs form the basis of the xfsprogs packages found in Linux distributions.

== <font face="ARIAL NARROW,HELVETICA"> Development and bleeding edge Development </font> ==

* [[XFS git howto]]

=== Current XFS kernel source ===

* [https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs]

 $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

=== XFS user space tools ===
* [https://git.kernel.org/cgit/fs/xfs/xfsprogs-dev.git/ xfsprogs ]

 git clone git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git

A few packages are needed to compile <tt>xfsprogs</tt>, depending on your package manager:

 apt-get install libtool automake gettext libblkid-dev uuid-dev pkg-config
 yum     install libtool automake gettext libblkid-devel libuuid-devel

=== XFS dump ===
* [https://git.kernel.org/cgit/fs/xfs/xfsdump-dev.git/ xfsdump ]

 git clone git://git.kernel.org/pub/scm/fs/xfs/xfsdump-dev.git

=== XFS tests ===
* [https://git.kernel.org/cgit/fs/xfs/xfstests-dev.git/ xfstests ]

 git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

=== DMAPI user space tools ===
* [https://git.kernel.org/cgit/fs/xfs/dmapi-dev.git/ dmapi ]

 git clone git://git.kernel.org/pub/scm/fs/xfs/dmapi-dev.git

=== git-cvsimport generated trees ===

The Git trees are automated mirrored copies of the CVS trees using [http://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html git-cvsimport].
Since git-cvsimport utilized the tool [http://www.cobite.com/cvsps/ cvsps] to recreate the atomic commits of ptools or "mod" it is easier to see the entire change that was committed using git.

* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-import.git;a=summary linux-2.6-xfs-from-cvs]
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-cmds.git;a=summary xfs-cmds]

Before building in the <tt>xfsdump</tt> or <tt>dmapi</tt> directories (after building <tt>xfsprogs</tt>), you will need to run:
  # cd xfsprogs
  # make install-dev
to create <tt>/usr/include/xfs</tt> and install appropriate files there.

Before building in the xfstests directory, you will need to run:
  # cd xfsprogs
  # make install-qa
to install a somewhat larger set of files in <tt>/usr/include/xfs</tt>.

== <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font> ==

The cvs trees were created using a script that converted sgi's internal
ptools repository to a cvs repository, so the cvs trees were considered read only.

At this point all new development is being managed by the git trees thus the cvs trees
are no longer active in terms of current development and should only be used
for reference.

* [[XFS CVS howto]]