> As a asfety measure (an incorrect kernel driver can ruin your system),
> kernel versioning is made available.
> If you recompile your kernel with "kernel version" support off, you can
> load the same binaries.
> Note that this will almost definitely ruin your day if the second number
> in the kernel is different (e.g 2.4 vs 2.4). that number indicates that
> internal interfaces have changed, the first number roughly approximating
> that the whole idea of the kernel has changed, so many user programs will
> need recompiling.
sorry, but imho you are confusing two things : versioning is for modules
and not for programms.
As I said modules needs to be compiled on (almost) every new kernel-build.
But this is not true for binaries like ipchains, ls, pppd .... - for good
reason, cause a new kernel would force me to rebuild my whole system.
But now - with iptables (not the module !! the binary !!) - things seems
being different ...
thnx,
peter
>> just installed a new kernel and iptable stopped working.
>> I get the following error:
>> # iptables -F FORWARD
>> iptables v1.2.4: can't initialize iptables table `filter': Module is
>> wrong version
>> Perhaps iptables or your kernel needs to be upgraded.
>> having kernel2.4.16 and iptables 1.2.4. I check googles and the
>> netfilter-docs and the postings in googles says that this is, if iptables
>> wasnt compiled against the recent kernel and the netfilter-install needs
>> the kernel-sources in every step.
>> somehow this doesnt make sense to me. The netfilter-modules are included
>> with the kernel-sources and therefore change at every new kernel, but why
>> should I be forced to compile a new iptables-binary ever time I update my
>> kernel ?
--
peter pilsl
http://www.goldfisch.at
by