Obtaining Unionfs 2.x via Git
 |
Unionfs 2.x is
maintained using Git
— a distributed version control system. This
page gives a
brief description of how to get the latest Unionfs
source code from our Unionfs repository.
|
Requirements
You'll need Git to complete the following
steps (packaged in many distributions). Since you will be cloning the
entire kernel repository you will need about 500MB (about 200MB for the
history, and about 300MB for the checked out working directory). You'll
need a total of up to 3GB if you plan to build a full kernel with every
possible kernel option enabled.
Initial clone
To obtain the full kernel tree with Unionfs, you can get it from our git
server via this command:
$ git clone git://git.fsl.cs.sunysb.edu/unionfs-latest.git
or
$ git clone http://git.fsl.cs.sunysb.edu/unionfs-latest.git
If you are looking for a specific version, you can try as follows:
$ git clone git://git.fsl.cs.sunysb.edu/unionfs-2.6.26.y.git
or
$ git clone http://git.fsl.cs.sunysb.edu/unionfs-2.6.26.y.git
The cloning proecss will take a while as it needs to transfer the repository
history, so please be patient. Once the clone succeeds, you will have a new
directory called 'unionfs', that contains the full kernel source.
Since clone stresses the network a lot, please use 'git pull' (see below) to
obtain new updates to the repository, instead of removing the entire source
tree and re-cloning.
Getting updates
To obtain any new commits, cd into the source tree cloned earlier, and run:
$ git pull
This will automatically get any changes from the Unionfs Git repository you
cloned from. Since only changes are transfered when pulling, it should not
take very long to complete.
Further help
For further Git help, see the Git Web site.
It contains detailed instructions how to use Git. If you have any problems
related to the Unionfs repository, please let us know (via the mailing
list).