"FS"? I thought that usually meant "for sale" in Usenet subjects? I was
interested in buying an upgrade kernel.
On Sun, 06 Jun 2004 16:50:48 +0000, Sharino wrote:
> Can anybody direct me to a how to site on update the
> kernel, I found the steps on rebuilding the current kernel
> but no on how to change it to 2.6.6. I did a fresh install of
> Slack 9.1 and would like to change the kernel. Do I need
> the patch of 2.6.6 or the source to accomplish this?
There are dozens of ways to get from where you are to where you want to
be, but they all require some knowledge, which is generally available
by reading the instructions, but possibly not always. For example, you
have to know something about your hardware in order to properly
configure a new kernel.
Your post doesn't give any direct indication of what you know or don't
know, which I will take as an indirect indication that you don't know
much at all. In that case the best question for you is ... WHY? Why do
you think you need a 2.6.6 kernel?
<you tell me what you expect to gain>
Whether or not those gains are real or imaginary, you would probably
gain more from learning some basic skills. In general the skill of
configuring a kernel is not that important. I suspect that a lot of
people who get caught up in that before they understand anything about
GNU/Linux are the ones who get burned out and go back to Windows in
anger or frustration.
<assuming you're going to disregard my advice, everyone does

>
As others have told you already, there is no major difference between a
2.4.x and 2.6.x kernel. Go forth and follow the instructions you found.
If you were fortunate enough to land on some clueful instructions, you
will soon enjoy your shiny new 2.6.6 kernel.
Slackware-current has a generic 2.6.6 kernel and modules in its
testing/ directory. That one might be tricky to use, because unlike its
predecessor Slackware kernels, it's stripped down. You'll probably need
to use the new mkinitrd package (also in testing/) to build an initrd
which contains all the modules you need to get to your root filesystem.
(The idea is that once your root filesystem is mounted, you can load
all the modules you need.)
I can't advise you on the mkinitrd thing, not having done it myself.
But if you try it and run into problems I'm sure I/we here in a.o.l.s.
can help.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply