Whole document tree
2. Preparation for XFS Installation
2.1. Downloading the Linux 2.4.x-XFS Kernel Source
Currently the only place to get the source code for the XFS enabled Linux kernel is straight from SGI's Open Source Development site via CVS.
 | Note |
|---|---|
two distinct trees are available:
|
My experience is based on the development tree, but I imagine everything will work the same (probably be more stable) with the beta tree. Here are the steps to download the kernel source tree:
A. Normally the linux kernel source is installed in the /usr/src directory, so you should start off by switching to that directory.
$ cd /usr/src |
B. Next, you should set the CVSROOT environment variable so that it points to the proper cvs server.
If you are running sh, bash, ksh, etc...:
$ export CVSROOT=':pserver:cvs@oss.sgi.com:/cvs'
If you are running csh or tcsh:
$ setenv CVSROOT :pserver:cvs@oss.sgi.com:/cvs
If you plan on updating your kernel often (to keep up with the latest changes) you might want to put this in your login script.
C. Then log in to the cvs server.
$ cvs login (the password is "cvs") |
This needs to be done only ONCE, not everytime you access CVS.
D. Now grab linux-2.4-xfs. The first time you will want to do something like:
$ cvs -z3 co linux-2.4-xfs |
After you have checked the code out, you can use:
$ cvs -z3 update linux-2.4-xfs |
to update your copy to the latest version from the CVS server.
2.2. XFS Support as Modules or Compiled Into the Kernel?
The option to build XFS support for the Linux kernel as modules is available and will work (or so I am told) with the help of an initial RAM disk and a couple of additions to the lilo configuration. I have not tried this (yet), so I will not include documentation on how this is done other than just to qoute from a message to the development mailing list from Russell Cattelan:
Actually running xfs as a module isn't very hard. in the directory cmd/xfs/misc there is a modified mkinitrd the will always generate a ram disk with pagebuf xfs_support and xfs. Once that is done just add the initrd line in lilo.conf AND
The default size is 4096 which isn't nearly large enough to hold xfs. This is from my laptop.
| ||||
| -- Russell Cattelan | ||||
It seems to me that compiling the support into the kernel would be much simpler, so that is how I am doing it at this point. I will try it as a module at a later time and add more detailed instructions then. If anyone has time to document this method before I get around to it please email it to me and I will include it with credit given where credit is due. :-)