Getting the latest source code: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== <font face="ARIAL NARROW,HELVETICA"> XFS Released/Stable source </font> == | |||
== <font face="ARIAL NARROW,HELVETICA"> | |||
* '''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. | |||
* '''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. | |||
* '''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. | |||
== <font face="ARIAL NARROW,HELVETICA"> Development and bleeding edge Development </font> == | |||
[[XFS git howto]] | [[XFS git howto]] | ||
Development git trees | |||
Current XFS kernel source | |||
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=summary xfs] | |||
<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. | The Git trees are automated mirrored copied of the cvs trees using git-cvsimport. | ||
| Line 11: | Line 38: | ||
* [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=linux-2.6-xfs-from-cvs/.git;a=summary linux-2.6-xfs-from-cvs] | * [http://oss.sgi.com/cgi-bin/gitweb.cgi?p=linux-2.6-xfs-from-cvs/.git;a=summary linux-2.6-xfs-from-cvs] | ||
* [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] | ||
== <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font> | == <font face="ARIAL NARROW,HELVETICA">XFS cvs trees </font> == | ||
The cvs trees were created using a script that converted sgi's internal | The cvs trees were created using a script that converted sgi's internal | ||
Revision as of 21:52, 8 January 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 copied 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.
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.