Getting the latest source code: Difference between revisions
No edit summary |
|||
| Line 31: | Line 31: | ||
<pre>$ git clone git://oss.sgi.com/xfs/cmds/dmapi</pre> | <pre>$ git clone git://oss.sgi.com/xfs/cmds/dmapi</pre> | ||
The Git trees are automated mirrored | 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 | 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. | or "mod" it is easier to see the entire change that was committed using git. | ||
| Line 39: | Line 39: | ||
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs-cmds/.git;a=summary xfs-cmds] | * [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs-cmds/.git;a=summary xfs-cmds] | ||
Before building in the xfsdump or dmapi directories (after building xfsprogs), you will need to run: | |||
<pre># cd xfsprogs | |||
# make install-dev</pre> | |||
to create /usr/include/xfs and install appropriate files there. | |||
Before building in the xfstests directory, you will need to run: | |||
<pre># cd xfsprogs | |||
# make install-qa</pre> | |||
to install a somewhat larger set of files in /usr/include/xfs. | |||
== <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font> == | == <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font> == | ||
Revision as of 20:30, 15 April 2009
XFS Released/Stable source
- 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 SGI XFS development team.
- Vendor kernels
All modern Linux distributions include support for XFS. SGI actively works with SUSE to provide a supported version of XFS in that distribution.
- XFS userspace
Sgi also provides source code taballs of the xfs userspace tools. These tarballs form the basis of the xfsprogs packages found in Linux distributions.
Development and bleeding edge Development
Development git trees
Current XFS kernel source
$ git clone git://oss.sgi.com/xfs/xfs
XFS user space tools
$ git clone git://oss.sgi.com/xfs/cmds/xfsprogs
XFS dump
$ git clone git://oss.sgi.com/xfs/cmds/xfsdump
XFS tests
$ git clone git://oss.sgi.com/xfs/cmds/xfstests
DMAPI user space tools
$ git clone git://oss.sgi.com/xfs/cmds/dmapi
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.
git-cvsimport generated trees.
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
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 a new development is being managed by the git trees so the cvs trees are not longer active in terms of current development and should only be used for reference.