On Wed, Oct 24, 2007 at 07:11:17PM +0100, Simon Arlott wrote:Generally, the goal is to get external modules included into the kernel. You want to be able to have this functionality and you do not want to use SELinux for it. But instead of working on getting your code into the kernel you are requesting that an API making it easier for you to maintain it externally comes back. There are other points in this thread that might or might not warrant making LSM modular again, but even though it might sound harsh breaking external modules and thereby making people aware that their code should get into the kernel is IMHO a positive point. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -
| Ingo Molnar | Re: x86: 4kstacks default |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Rafael J. Wysocki | [Bug #10919] [regression] display dimming is slow and laggy - Acer Travelmate 661lci |
git: | |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
