> > > >> On another note, can you still change to version 1.3.6? > > What does that give us, that 1.3.5 doesn't?
Just some extra extensions (that I happen to use). In my case match and target support for 'SET', but there's a couple of others as well. I've heard back about the problem I was having with 1.3.7. Looks like it throws up a spurious error message when iptables is compiled into the kernel, but still works (which I didn't realise at the time) > > > Not sure what to do here. > > Okay, how does this sound (in the IPTables instructions in a note > right before the compilation commands): > > "IPTables can use the raw kernel headers from the Linux package > to build additional modules and extensions. This could result > in IPTables becoming broken if you update to a more recent > kernel version later on." > > I'm not thrilled with that, especially the fact that the "additional > modules and extensions" aren't described as to what they would do > (what additional functionality is provided) if you *did* build them. For the sake of brevity and speed, how about a few examples such as the ones that you found to be built when you specified the kernel dir? To be honest, just reading the above paragraph would have been enough to send me off in the right direction. The problem I had was that I had always followed BLFS instructions to the letter, even when they are different to those contained in the particular application. Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
