On Mon, Jun 16, 2008 at 5:49 AM, Darren Reed <[EMAIL PROTECTED]> wrote:
> > How best can I assist the IPFilter team to ensure that you're rather >> exceptional firewall code is easier to compile for whatever the latest >> stable version of the Linux kernel is on kernel.org <http://kernel.org>? >> (I always work from pristine source and avoid custom patching at all cost.) >> > > Hmm, so you want to use the Linux kernel from kernel.org withut patching? > > That might be an achievable goal... > > The problem I usually have is that the kernels bundled up by SuSE, RedHat, > etc, etc, can be quite a pain in the a** to build from source code and that > ability is needed to compile a kernel module. Agreed the custom patched kernel's from SUSE/Novell, RedHat/Fedora, et al are generally a pain in my rump. My thought pattern being that if we make an effort to support the upstream vanilla code from Linus then its more likely that we'd get people that will put in the time to write the patches needed to work on the various binary distro's. After all they all generally start out with the vanilla release from Linus and patch it to wherever it is they want the code to be. Reason being is after spending far too many years working on different embedded projects the one thing thats ALWAYS a thorn in my side is the firewalling code is almost always different from project to project. I'd LOVE to be able to start standardizing! How can I assist in achieving this aim? I'd be more than happy to do all the testing whenever Linus and friends release a new stable version of 2.6.x (kinda needed any way by my project(s) ). And depending on how severe the breakage is I might be able to fix it (not the world's best kernel hacker - but willing to give it a bash while I'm learning ).
