Getting the latest source code: Difference between revisions

From xfs.org
git-cvsimport, cvsps linked
Update current XFS kernel source git URL
 
(15 intermediate revisions by 10 users not shown)
Line 1: Line 1:
== <font face="ARIAL NARROW,HELVETICA"> XFS Released/Stable source </font> ==
== <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'''
* '''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 SGI XFS development team.
: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'''
* '''Vendor kernels'''
: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.
:All modern Linux distributions include support for XFS.  


* '''XFS userspace'''
* '''XFS userspace'''
: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.
:[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> ==
== <font face="ARIAL NARROW,HELVETICA"> Development and bleeding edge Development </font> ==
Line 15: Line 16:
* [[XFS git howto]]
* [[XFS git howto]]


Note: there are also [http://git.kernel.org/ XFS git repositories on kernel.org] for external (i.e. non-Sgi) contributers. Sgi periodically pulls those in to [http://oss.sgi.com/cgi-bin/gitweb.cgi oss.sgi.com]. This also means that one or the other may be a bit more current.
=== Current XFS kernel source ===


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


=== Current XFS kernel source ===
  $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=summary xfs]
  $ git clone git://oss.sgi.com/xfs/xfs


=== XFS user space tools ===
=== XFS user space tools ===
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsprogs.git;a=summary xfsprogs]
* [https://git.kernel.org/cgit/fs/xfs/xfsprogs-dev.git/ xfsprogs ]
  $ git clone git://oss.sgi.com/xfs/cmds/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 ===
=== XFS dump ===
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsdump.git;a=summary xfsdump]
* [https://git.kernel.org/cgit/fs/xfs/xfsdump-dev.git/ xfsdump ]
  $ git clone git://oss.sgi.com/xfs/cmds/xfsdump
 
  git clone git://git.kernel.org/pub/scm/fs/xfs/xfsdump-dev.git


=== XFS tests ===
=== XFS tests ===
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=summary xfstests]
* [https://git.kernel.org/cgit/fs/xfs/xfstests-dev.git/ xfstests ]
  $ git clone git://oss.sgi.com/xfs/cmds/xfstests
 
  git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git


=== DMAPI user space tools ===
=== DMAPI user space tools ===
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/dmapi.git;a=summary dmapi]
* [https://git.kernel.org/cgit/fs/xfs/dmapi-dev.git/ dmapi ]
  $ git clone git://oss.sgi.com/xfs/cmds/dmapi
 
  git clone git://git.kernel.org/pub/scm/fs/xfs/dmapi-dev.git


=== git-cvsimport generated trees ===
=== git-cvsimport generated trees ===
Line 62: Line 71:


At this point all new development is being managed by the git trees thus 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.
for reference.


* [[XFS CVS howto]]
* [[XFS CVS howto]]

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]

Current XFS kernel source[edit | edit source]

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

XFS user space tools[edit | edit source]

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]

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

XFS tests[edit | edit source]

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

DMAPI user space tools[edit | edit source]

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.