Hey! Did you see what Brian Willis wrote on Jul 23 ?
BW> I have kernel 2.0.18 and I'm in the process of adding patches to get
BW> my kernel current. Well, I've
BW> downloaded all patches up to 2.2.10 (wow, there were a lot of patches
BW> for 2.1). So, I started
Here's where you went wrong. If you have kernel 2.0.18 you can
only patch that to 2.0.37
2.1.x was the development kernel that later became 2.2.0. Being very new
to Linux like you are you should stay right away from the development
kernels (odd numbered 2.1.x or 2.3.x).
Also, I would forget about trying to upgrade your system from 2.0.x to
2.2.x it is possible, but a whole lot can go wrong. The best piece of
advice I could give you would be to spend a couple of bucks on a current
Linux distribution CD.
BW> Do I only need to recompile the kernel? "Running LINUX" from O'Reilly
BW> says that can create some
BW> problems. I don't want to continue adding patches if I need to
BW> recompile the kernel to fix problems
BW> that will help me down the road. I'd appreciate any advice!!
You actually have to re-compile the kernel for those patches to be
included into it. You are patching the kernel source code not the actual
kernel binary. Once you re-compile the patched source code you get a new
kernel binary that has the updates from the patch. You can apply multiple
patches (2.0.18 apply all patches to 2.0.37) then re-compile the kernel
after that.
Another reason to re-compile the kernel would be to add support for
something you want that isn't there by default or to remove support for
something that you don't need. A smaller kernel is better because you use
less memory.
Regards, Steve Youngs <[EMAIL PROTECTED]> ICQ: 34307457
------------------------------------------------------------
| __ |
| Isn't it good to know that / / __ ___ __ ____ __ |
| There _IS_ an alternative! / /__ / // _ \/ // /\ \/ / |
| /____//_//_//_/\_,_/ /_/\_\ |
------------------------------------------------------------
