* frm crispinat_private "04/08/2002 01:51:56 PM -0700" | sed '1,$s/^/* /' * * * LSM (technology and project) was designed to solve the opposite problem: * allowing people with non-standard security toys to distribute modules * that will work with standard kernels, e.g. so that SELinux can build a * module that "just works" with whatever kernel Red Hat is shipping at the * time. "just works" will include compiling the module for every kernel that RedHat ships... For just the IA32 platforms, that means... athlon: kernel-2.4.9-31.athlon.rpm kernel-smp-2.4.9-31.athlon.rpm i386: kernel-2.4.9-31.i386.rpm kernel-BOOT-2.4.9-31.i386.rpm (probably get away without this one) i586: kernel-2.4.9-31.i586.rpm kernel-smp-2.4.9-31.i586.rpm i686: kernel-2.4.9-31.i686.rpm kernel-smp-2.4.9-31.i686.rpm kernel-enterprise-2.4.9-31.i686.rpm kernel-debug-2.4.9-31.i686.rpm (probably get away without this one) So while the source code should be okay, that doesn't remove the hassle of building and supporting multiple kernels (if what you want to do is to provide a binary distribution) While you may be able to get away with fewer than these, in some respects its easier to take the build hit rather than worry about trying to support something that may (or may not) work. Of course if all you're intersted in is shipping source, the all you've got to worry about is SMP locking (and PPC/IA64/Alpha/SPARC...) * * Crispin * richard. -- ----------------------------------------------------------------------- Richard Offer Technical Lead, Trust Technology, SGI "Specialization is for insects" _______________________________________________________________________ _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Tue Apr 09 2002 - 08:22:39 PDT