[svlug] New kernel won't boot

[Rick Moen]

begin Shija Alpheraz quotation:

> I'm trying to install a 2.0.38 kernel on my home firewall machine.
> (the 2.2.10 got hacked, so I'm going back to the 2.0 lineage)

Just a comment:  I doubt that it's a good idea to use a 2.0.x kernel on
a firewall machine.  The 2.0 branch is barely maintained at all, these
days, so you're likely to end up with a less secure system, rather than
more.  That's not to mention all the related parts of your former
2.2.x-oriented system that are likely to break.  The fact that you'll
have to use ipfwadm filtering rules instead of ipchains ones is only the 
start of your difficulties.

You may find that some libs, binutils, the development toolchain, and so
on work poorly if at all, because they were designed for
2.2-kernel-based systems.

A better solution, in my opinion, than switching to 2.0.38, would be to
stick with current production kernels and harden your system in various
ways.  You _might_ have some specific reason why you need 2.0.x, but I
don't know of it.

> The 2.0.30 came from the plain RedHat 4.2 install, and
> I don't know what config options it used. 

Is this firewall machine, by some chance, a Red Hat 4.2 system that
you've managed to incrementally upgrade to the present day, including
the 2.2.10 kernel?  If so, I'm impressed, and take my hat off to you.
You may find, however, that it's time to reimplement your firewall
concepts on a fresh system build, and may want to pick some modern
distribution release as a starting point.

-- 
Cheers,                   "Teach a man to make fire, and he will be warm 
Rick Moen                 for a day.  Set a man on fire, and he will be warm
rick at linuxmafia.com       for the rest of his life."   -- John A. Hrastar