> I get a little bit confused.
I do not blame you, I really wish there were at least more README files out
there on the web/ftp site.
There are really two legs of xfs development right now, the 'development'
tree, only truly accessable via cvs which is where the latest code can be
found, and the 'release' tree which is a more slow moving tree were only
bug fixes are going in.
> I have 2.4.3 kernel, and I applied:
> And, for now, it works.
This is correct, however, the intent of this patch is to seed a cvs tree
so that you can do cvs updates from our cvs repository. The patch gets
regenerated periodically, I cannot remember how often, but this one is 3
weeks old, the cvs tree is updated every hour from our internal development
tree. I would recommend doing a cvs update, see this web page for details:
You should use the linux-2.4-xfs cvs tree
I suspect you will see a lot of changes since the April 2nd patch, this is
the development tree and a lot of changes have gone in recently, nothing
earth shattering though, a few bug fixes, and a lot of code cleanup.
> But in directory Release-1.0-test3 are other patches:
These are patches being used in the generation of rpm packages for the
'release' of xfs. The core-xfs patches represent changes to the base
linux kernel, the -xfs- patch is the xfs code itself, the same patch
being usable with different base kernel patches. These patches and
the associated cvs tree (currently linux-2.4-xfs-beta I think) are 2.4.2
based and are only getting bug fixes.
> In other directories is also a loop patch.
This should make the loop device work in a 2.4.2 based kernel.
> So, what is the linux-xfs patch, and linux-xfs-core patch?
> What is the difference between RHlinux-core-xfs patch and linux-core-xfs
> And, are all these patches contained in xfs-cvs patch!?
The 2.4.3 patch is getting a bit dated when it comes to bug fixes, hopefully,
after applying the patch you do not need too much internet bandwidth to
do a cvs update.