Getting the latest source code: Difference between revisions

Latest revision as of 09:20, 19 May 2022

XFS Released/Stable source [edit | edit source]

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 kernel trees starting with 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

source code tarballs of the xfs userspace tools. These tarballs form the basis of the xfsprogs packages found in Linux distributions.

Development and bleeding edge Development [edit | edit source]

XFS git howto

Current XFS kernel source[edit | edit source]

xfs

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

XFS user space tools[edit | edit source]

xfsprogs

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

A few packages are needed to compile xfsprogs, 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[edit | edit source]

xfsdump

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

XFS tests[edit | edit source]

xfstests

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

DMAPI user space tools[edit | edit source]

dmapi

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

git-cvsimport generated trees[edit | edit source]

The Git trees are automated mirrored copies of the CVS trees using git-cvsimport. Since git-cvsimport utilized the tool cvsps to recreate the atomic commits of ptools or "mod" it is easier to see the entire change that was committed using git.

Before building in the xfsdump or dmapi directories (after building xfsprogs), you will need to run:

 # cd xfsprogs
 # make install-dev

to create /usr/include/xfs 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 /usr/include/xfs.

XFS cvs trees [edit | edit source]

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

@@ Line 1: / Line 1: @@
 == <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'''<br /> XFS has been maintained in the official Linux kernel [http://www.kernel.org/ kernel trees] starting with Linux 2.4 and is frequently updated with the latest stable fixes and features from the SGI XFS development team.
+* '''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'''<br /> All modern Linux distributions include support for XFS. SGI actively works with [http://www.suse.com/  SUSE] to provide a supported version of XFS in that distribution.
+* '''Vendor kernels'''
+:All modern Linux distributions include support for XFS.
-* '''XFS userspace'''<br /> Sgi also provides [ftp://oss.sgi.com/projects/xfs source code taballs] of the xfs userspace tools. These tarballs form the basis of the xfsprogs packages found in Linux distributions.
+* '''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 ]
-== <font face="ARIAL NARROW,HELVETICA"> Development and bleeding edge Development </font> ==
+ 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 ]
-[[XFS git howto]]
+ git clone git://git.kernel.org/pub/scm/fs/xfs/dmapi-dev.git
-Development git trees
+=== git-cvsimport generated trees ===
-Current XFS kernel source
+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].
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=summary xfs]
+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.
-<pre>$ git clone git://oss.sgi.com/xfs/xfs</pre>
-XFS user space tools
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsprogs.git;a=summary xfsprogs]
-<pre>$ git clone git://oss.sgi.com/xfs/cmds/xfsprogs</pre>
-XFS dump
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsdump.git;a=summary xfsdump]
-<pre>$ git clone git://oss.sgi.com/xfs/cmds/xfsdump</pre>
-XFS tests
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=summary xfstests]
-<pre>$ git clone git://oss.sgi.com/xfs/cmds/xfstests</pre>
-DMAPI user space tools
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/dmapi.git;a=summary dmapi]
-<pre>$ git clone git://oss.sgi.com/xfs/cmds/dmapi</pre>
-The Git trees are automated mirrored copied of the cvs trees using git-cvsimport.
+* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-import.git;a=summary linux-2.6-xfs-from-cvs]
-Since git-cvsimport utilized the tool cvsps to recreate the atomic commits of ptools
+* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-cmds.git;a=summary xfs-cmds]
-or "mod" it is easier to see the entire change that was committed using git.
-git-cvsimport generated trees.
+Before building in the <tt>xfsdump</tt> or <tt>dmapi</tt> directories (after building <tt>xfsprogs</tt>), you will need to run:
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=linux-2.6-xfs-from-cvs/.git;a=summary linux-2.6-xfs-from-cvs]
+  # cd xfsprogs
-* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs-cmds/.git;a=summary xfs-cmds]
+  # 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> ==
@@ Line 45: / Line 70: @@
 ptools repository to a cvs repository, so the cvs trees were considered read only.
-At this point a new development is being managed by the git trees so the cvs trees
+At this point all new development is being managed by the git trees thus the cvs trees
-are not longer active in terms of current development and should only be used
+are no longer active in terms of current development and should only be used
 for reference.
-[[XFS CVS howto]]
+* [[XFS CVS howto]]