You can remove modules with then reinsert it with Kernel headers use same versioning convention as their kernel, however there are some BIG CAVEATS involved here. What the error is really talking abut is making sure you're compiling madwifi with the same headers that your kernel was compiled with. The difference is subtle, but important, and best illustrated with an example:

Slack 10.1 came with the 2.4.29 kernel as the default. All the binaries making up Slack 10.1 were compiled with the 2.4.29 kernel headers. When I upgraded to the 2.6.x kernel, I did not install the 2.6.x headers (long story short, because doing so will break gcc. Google or search this site for more information about headers if you want to know why.), so I'm using the 2.4.29 headers with the 2.6.13 kernel. We know you're ok there, unless you've installed new headers, in which case, remove them and put the old ones back in, as you won't be able to compile until you do.

BTW, was referring to journalistic scare tactics; specifically, their tendency to imply that we're all in IMMINANT danger of being cracked by the kid down the street, and not a criticism of your decision to try to test the security of your networks. I believe in knowing AS MUCH AS POSSIBLE about your system, especially security. My in-law's XP box has been cracked twice ("But Windows XP has a firewall built in!" ), and it's caused no end of trouble for them (and, by extension, my brother-in-law and me, as we're the ones who get to clean up the mess).

I did a kernel upgrade from 2.4.21-27 to 2.4.21-32. I just downloaded the RPM from Red Hat and ran RPM -Uvh kernel-2.4.21-32.rpm

I didn't update anything else. Are the kernel headers different between .27 and .32??

I've tried to upgrade other rpm packages but I get a lot of dependency errors. I don't use Yum. (not sure how to install/use it). I've downloaded the tarball and the rpm files but I haven't played around with it yet.

Yes, they are. I don't know HOW different, but they WILL be different.

One problem leads to another....

I've downloaded the RPM update packages from Red Hat and I was getting lots of dependency errors. I was told in another forum to use YUM as it will solve that problem. So that brings me to the Yum installation.

I've done numerous google searches to try and get a step by step on how to INSTALL and USE it.

I'm getting errors when trying to install it. I've downloaded different packages:

yum-2.4.0.tar, yum-2.4.0-1.src.rpm, yum-2.2.0.tar, yum-2-2.2.0-1.src.rpm,
yum-2.2.0-1.noarch.rpm

I finally got the noarch rpm to kind of install. I don't think it's installed properly though.

I get this when I type YUM:

Traceback (most recent call last):
File "/usr/bin/yum", line 6, in ?
import yummain
File "/usr/share/yum-cli/yummain.py", line 23, in ?
import yum
ImportError: No module named Yum

When I typed:

rpm -ivh yum-2.2.0-1.src.rpm I get:

warning: yum-2.2.0-1.src.rpm: V3 DSA Signature: NOKEY, key id 69886cc7
1: yum warning: user skvidal does not exist - using root
warning: group skvidal does not exist - using root
warning: user skvidal does not exist - using root
warning: group skvidal does not exist - using root
##################################[100%]



What am I doing wrong???

Hmmm...
I don't know, as I don't use RPM or yum. I suspect it's a syntax error. Lemme look around a bit, or perhaps someone who does use yum could offer an opinion.

I see you've downloaded a couple of yum source files (*.src.rpm). Have you considered compiling from source?

Edit:
should produce a list of options and a syntax guide.

It could also be a permissions problem. Are you trying to run yum as root or as a user?