[lug] Redhat doesn't support users that compile their own kernels.

[Nate Duehr]

See inline...

Jeff wrote:
> > It is a mistake to think the kernel is involved. There is a badly
> > misunderstood point here: *ALL* kernels, when they have iptables module
> > loaded, will NOT load ipchains. They are mutually exclusive. The bash
> > scripts seem to fail to check return values. If ipchains module is
> 
> Mr. Stimits is right on this part.  I understand both sides.  One
> *cannot* load ipchains if the iptables modules is loaded.  Period.  One
> possible fix, albeit ugly, is to edit the appropriate init script and
> replace the section that load iptables and load ipchains.  Ugly, but it
> works.  Another suggestion that I've seen here is to write a fix
> independantly.

He not complaining about the kernel's behaviour, he's complaining about
the startup/shutdown scripts that attempt to load ipchains rules not
CHECKING THEIR RETURN CODES.  In addition, I'd add... shouldn't there be
some way for that script to check for the presence of ipchains in the
kernel via /proc somehow?  Why didn't anyone READ his original post?

> >From Red Hat's point of view, this is not a major problem; only an
> inconvience.  I run Mandrake (8.0) and I also had the exact same issue.
> So it's not exclusive to Red Hat.  Since I don't completely understand
> iptables, and have not had time to learn as yet, I simply ensure that
> the init script only loads ipchains.