[trustees] trustees development method changed, 2.6.24+ compatible

[Andrew R. <an...@ae...>]

Hey all,

You may (or probably not) have noticed that the trustees git repository
has suddenly lost its module/ directory.  This is due to a big change in
how trustees is developed.

Up until a couple days ago, trustees was distributed as a single
repository containing the settrustees tool, a minor patch, and a module
that compiled externally to the main linux source tree.  This method of
development worked well for a long time, that is, until 2.6.24-rc1.  A
commit for 2.6.24-rc1 made the API's I use to make trustees work
unavailable to modules.  Trustees would now have to be compiled *into*
your kernel.

If you've ever thought patches were a pain to apply, they're even more
of a pain to maintain so I've gone with what is hopefully a better
method.  Since linux itself is developed with git and git is very
distributed in nature, it is very easy to maintain a fork of the full
linux kernel while merging in new changes as new kernels are released.

So as of this point on, trustees will be distributed via two
repositories.  One repository will hold the linux kernel code with the
changes for trustees incorporated.  You can build this source code
directly like any other kernel.  Trustees will show up in the make
menuconfig like any other kernel option.  If you are using a custom
kernel, you can pretty easily extract a patch to apply to your custom
kernel.

The new README in your trustees.git repository should fill you in on any
details on getting going with the new setup.  This is available online
at:

http://gitweb.aeruder.net/?p=trustees.git;a=blob_plain;f=README;hb=HEAD

I'm going to plead with people to please use the method described in the
document to clone the trustees kernel repository.  It is a little
complicated, but it pushes 98% of the bandwidth off onto kernel.org
which would be a good thing for my current hosting situation.

If the README is unclear or you can't figure something out, please send
an email to this list to let me know.  I'm not much of a documentation
writer, but let me know if you have issues, and I'll do my best at
fixing the docs.

Thanks all,
Andy



-- 
Andrew Ruder <an...@ae...>
http://www.aeruder.net