Menu
▾
▴
trustees-general
|
From: Andrew R. <an...@ae...> - 2007-06-10 20:55:44
|
Hey all, I've spent the last few weeks familiarizing myself with git with the idea it would lend itself a bit more to trying to maintain trustees against several different kernel revisions. For now, I'm only doing 2.6.21, but hopefully on future kernel releases I will maintain separate branches for multiple stable kernels. I'll let you know more about that when 2.6.22 comes out I guess. :) Important changes in the git repository (more about accessing git below): * trustees bumped for kernel 2.6.21 trustees will no longer build on older kernel revisions, sorry, unless someone has some compelling reason not to use 2.6.21... * trusteesfs removed in favor of securityfs securityfs is a builtin filesystem that was made for security modules, it allowed me to remove some code and you no longer have to mount/unmount your trusteesfs to unload/reload the trustees module. You will need to add something like this to your /etc/fstab: none /sys/kernel/security securityfs defaults 0 0 When trustees is loaded, it will create /sys/kernel/security/trustees and associated files. * Added NEWS file This will include the major changes like dropping of securityfs from now on. If you see this file being updated, there's a good chance you should take a look at it. * Removed -t option on settrustees If settrustees can't automagically determine your securityfs mount, let me know. I've got some ideas for making a good testsuite that'll test various trustees configurations, I'll play with that more later on and let you know when its committed. ======== How to access the git repository ======== Firstly, get git installed. I would *very* highly recommend installing at *least* git 1.5, you can't go wrong with the latest 1.5.2.1 or even the git repository of git itself. Get this at http://git.or.cz Afterwards: * Clone the repository git clone git://git.aeruder.net/trustees.git At this point, you have the *full* trustees repository. Your copy of trustees.git has all the development history, so feel free to do things like 'git log', or 'git blame', or otherwise. * Pull additional changes git pull origin This is somewhat analogous to 'svn update' That should sum up the very very basics for what is needed to stay up to date with the latest trustees. There is some good tutorials and user manuals at http://git.or.cz or you can send me questions (on list) if you run into some git problems related to trustees. ======= Grabbing a trustees snapshot ======= These are available from the web interface at: http://gitweb.aeruder.net/?p=trustees.git;a=summary This is the URL you'd use for a tar.gz snapshot of the latest trustees: http://gitweb.aeruder.net/?p=trustees.git;a=snapshot;h=HEAD ======= I would appreciate it if some people could do a bit of testing against the new trustees, I need to do more testing myself, but at first glance it appears that everything is working alright. If there are problems, revert to the svn repository or do a: git checkout 8c97c92e in your cloned git repository. Thanks all, Andy -- Andrew Ruder <an...@ae...> http://www.aeruder.net |
|
From: Andrew R. <an...@ae...> - 2007-06-12 04:01:13
|
Sorry if people got this two times, I never saw it come through... Hey all, I've spent the last few weeks familiarizing myself with git with the idea it would lend itself a bit more to trying to maintain trustees against several different kernel revisions. For now, I'm only doing 2.6.21, but hopefully on future kernel releases I will maintain separate branches for multiple stable kernels. I'll let you know more about that when 2.6.22 comes out I guess. :) Important changes in the git repository (more about accessing git below): * trustees bumped for kernel 2.6.21 trustees will no longer build on older kernel revisions, sorry, unless someone has some compelling reason not to use 2.6.21... * trusteesfs removed in favor of securityfs securityfs is a builtin filesystem that was made for security modules, it allowed me to remove some code and you no longer have to mount/unmount your trusteesfs to unload/reload the trustees module. You will need to add something like this to your /etc/fstab: none /sys/kernel/security securityfs defaults 0 0 When trustees is loaded, it will create /sys/kernel/security/trustees and associated files. * Added NEWS file This will include the major changes like dropping of securityfs from now on. If you see this file being updated, there's a good chance you should take a look at it. * Removed -t option on settrustees If settrustees can't automagically determine your securityfs mount, let me know. I've got some ideas for making a good testsuite that'll test various trustees configurations, I'll play with that more later on and let you know when its committed. ======== How to access the git repository ======== Firstly, get git installed. I would *very* highly recommend installing at *least* git 1.5, you can't go wrong with the latest 1.5.2.1 or even the git repository of git itself. Get this at http://git.or.cz Afterwards: * Clone the repository git clone git://git.aeruder.net/trustees.git At this point, you have the *full* trustees repository. Your copy of trustees.git has all the development history, so feel free to do things like 'git log', or 'git blame', or otherwise. * Pull additional changes git pull origin This is somewhat analogous to 'svn update' That should sum up the very very basics for what is needed to stay up to date with the latest trustees. There is some good tutorials and user manuals at http://git.or.cz or you can send me questions (on list) if you run into some git problems related to trustees. ======= Grabbing a trustees snapshot ======= These are available from the web interface at: http://gitweb.aeruder.net/?p=trustees.git;a=summary This is the URL you'd use for a tar.gz snapshot of the latest trustees: http://gitweb.aeruder.net/?p=trustees.git;a=snapshot;h=HEAD ======= I would appreciate it if some people could do a bit of testing against the new trustees, I need to do more testing myself, but at first glance it appears that everything is working alright. If there are problems, revert to the svn repository or do a: git checkout 8c97c92e in your cloned git repository. Thanks all, Andy -- Andrew Ruder <an...@ae...> http://www.aeruder.net |
Thanks for helping keep SourceForge clean.
X