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?
TIA

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? TIA

I just built a 2.6.6 kernel last night, so it's fresh in my mind.
1) Get the kernel src from kernel.org.
2) The src package has excellent instructions, especially see the
Documentation directory.
3) I did a make defconfig, then modified the resulting config for my
hardware.
4) There are some changes you'll need to make to your 9.1 Slackware
configuration. For example, you won't need the hdc=ide-scsi line in
lilo.conf. That means you'll need to change the /dev/cdrom link as well.
There are other changes as well, but nothing major. Google is your friend.

hth

Sharino <sharino07REMOVE@hotmail.com> 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

The steps are the same except for some differences in how you
prepare the kernel for compile. This is a pretty good kernel
howto that covers 2.6.x:

<http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html>

> 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?

I do not know of any way to patch a 2.4.x to be a 2.6.x - that
would probably be pretty pointless as the patch would be huge.
You should just download the full source and follow the directions
in the above link to build and install it. Also check out
the README in the kerel source.

- Kurt

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

~kurt wrote:
| I do not know of any way to patch a 2.4.x to be a 2.6.x - that
| would probably be pretty pointless as the patch would be huge.
| You should just download the full source and follow the directions
| in the above link to build and install it. Also check out
| the README in the kerel source.
|
| - Kurt

If you were to try and patch 2.4.x to 2.6.x you probably have to get a
bunch of 2.4 patches and back them out until you arrived at the version
that was forked to 2.5, than apply all the 2.5 patches and all the the
2.6 patches as well. I'm not even sure that would work.
You're right, just download the tarball.

Ross
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAw2/z9bR4xmappRARAgDkAJ92ODg97PZfuT2W83dZ5Maj5EPbwQCgl 1Nq
zrRsgU6bRuSydqhiLBqYeBQ=
=KPWn
-----END PGP SIGNATURE-----

"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

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?
> TIA
>
>
This is what I do.

1. Log in as root
2. Download the full kernel source code from
www.kernel.org. The current stable kernel at this time is 2.6.2.
I downloaded the full kernel source code file
linux-2.6.2.tar.bz2 this was downloaded into the /root
directory
3. To avoid possible drama, I never unpack the new
kernel source in the /usr/src. Since I am logged in as root, I
will proceed with unpacking the source in my /root dir. I use
the following command
* bzip2 -cd linux-2.6.2.tar.bz2 | tar -xvf -
This will unpack everything into /root/linux-2.6.2/
4. cd /usr/src/linux & then
* make mrproper this cleans-up old kernel
stuff
5. When compiling the kernel all output files will per
default be stored together with the kernel source code. Using
the option "make O=output/dir" allows you to specify an alternate
place for the output files (including .config). I like this
option. Since my kernel source code is in /root/linux-2.6.2, I
will save my output files to /root/build/kernel. I believe an
added bonus to this option is the next time I run "make mrproper"
in my new /root/linux-2.6.2 kernel source, I believe my .config
file will remain safely in /root/build/kernel for future purposes
I don't want to f-things up, so I make the dir tree
/root/build/kernel in advance. Note: if the O=output/dir is
used, it must be used with each make command.
6. cd /root/linux-2.6.2
7. make O=/root/build/kernel menuconfig
* This starts a menu driven utility to help
config the kernel
8. make O=/root/build/kernel
9. make O=/root/build/kernel bzImage
10. make O=/root/build/kernel modules_install
11. cp /root/build/kernel/arch/i386/boot/bzImage /boot
12. cd /boot
13. mv vmlinuz vmlinuz.old
14. vi /etc/lilo.conf (need to edit lilo for new
kernel, and add an entry for the old 2.4.22 kernel)

#Linux bootable partition config starts
#this will load the new kernel 2.6.2
image = /boot/bzImage
root = /dev/hda3
label = slackware
read-only

#old back-up stock 2.4.22 kernel - old
faithful
image = /boot/vmlinuz.old
root = /dev/hda3
label = slack2422
read-only

# End Config File


15. lilo **don't forget this command **
16. reboot


--
===========================
http://b-o-b.homelinux.com
Long 93:18W Lat 45:09N
===========================

On Mon, 07 Jun 2004 03:07:06 +0000, Robert D. De Mars wrote:
> This is what I do.
>
> 1. Log in as root

Why?!? There is no any need to do typical compiling jobs as root. The
more you use that root account the more potential risks you face:
risk of you typing something wrong, risk of someone else having typed
something wrong, or worse: a deliberate trojan.

> 2. Download the full kernel source code from

If a vulnerability existed in your FTP/HTTP client, a hostile server
could exploit you. This kind of thing happens to Windows/MSIE users
every day.

> www.kernel.org. The current stable kernel at this time is 2.6.2.

?!?!? It's 2.6.6, as the OP noted.

The rest of this is basically good advice, however:

> option. Since my kernel source code is in /root/linux-2.6.2, I
> will save my output files to /root/build/kernel. I believe an
> added bonus to this option is the next time I run "make mrproper"
> in my new /root/linux-2.6.2 kernel source, I believe my .config
> file will remain safely in /root/build/kernel for future purposes

Unless you use the O=/output/dir with that. Also, all your object files
remain, so what you might have wanted from running mrproper in the
first place is not achieved. I'd say that the O=/output/dir benefit is
that you don't need to run make clean or mrproper. If you're doing a
different ARCH or dramatically different configurations, specify a
different output directory.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

/dev/rob0 wrote:

> On Mon, 07 Jun 2004 03:07:06 +0000, Robert D. De Mars wrote:
>
>>This is what I do.
>>
>> 1. Log in as root
>
>
> Why?!? There is no any need to do typical compiling jobs as root. The
> more you use that root account the more potential risks you face:
> risk of you typing something wrong, risk of someone else having typed
> something wrong, or worse: a deliberate trojan.
>

Noted.

>
>> 2. Download the full kernel source code from
>
>
> If a vulnerability existed in your FTP/HTTP client, a hostile server
> could exploit you. This kind of thing happens to Windows/MSIE users
> every day.
>
>
>>www.kernel.org. The current stable kernel at this time is 2.6.2.
>
>
> ?!?!? It's 2.6.6, as the OP noted.
>

Yeah, sorry. These were the notes I made back when 2.6.2 was fresh.

> The rest of this is basically good advice, however:
>
>
>>option. Since my kernel source code is in /root/linux-2.6.2, I
>>will save my output files to /root/build/kernel. I believe an
>>added bonus to this option is the next time I run "make mrproper"
>>in my new /root/linux-2.6.2 kernel source, I believe my .config
>>file will remain safely in /root/build/kernel for future purposes
>
>
> Unless you use the O=/output/dir with that. Also, all your object files
> remain, so what you might have wanted from running mrproper in the
> first place is not achieved. I'd say that the O=/output/dir benefit is
> that you don't need to run make clean or mrproper. If you're doing a
> different ARCH or dramatically different configurations, specify a
> different output directory.

Thank you for the advice/correction.

Robert De Mars

--
===========================
http://b-o-b.homelinux.com
Long 93:18W Lat 45:09N
===========================

"Robert D. De Mars" <bob-news@b-o-b.homelinux.com> wrote in message
news:uZQwc.3832$Fd.2227@twister.rdc-kc.rr.com...
> 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?
> > TIA
> >
> >
> This is what I do.
>
> 1. Log in as root
> 2. Download the full kernel source code from
> www.kernel.org. The current stable kernel at this time is 2.6.2.
> I downloaded the full kernel source code file
> linux-2.6.2.tar.bz2 this was downloaded into the /root
> directory
> 3. To avoid possible drama, I never unpack the new
> kernel source in the /usr/src. Since I am logged in as root, I
> will proceed with unpacking the source in my /root dir. I use
> the following command
> * bzip2 -cd linux-2.6.2.tar.bz2 | tar -xvf -
> This will unpack everything into /root/linux-2.6.2/
> 4. cd /usr/src/linux & then
> * make mrproper this cleans-up old kernel
> stuff
> 5. When compiling the kernel all output files will per
> default be stored together with the kernel source code. Using
> the option "make O=output/dir" allows you to specify an alternate
> place for the output files (including .config). I like this
> option. Since my kernel source code is in /root/linux-2.6.2, I
> will save my output files to /root/build/kernel. I believe an
> added bonus to this option is the next time I run "make mrproper"
> in my new /root/linux-2.6.2 kernel source, I believe my .config
> file will remain safely in /root/build/kernel for future purposes
> I don't want to f-things up, so I make the dir tree
> /root/build/kernel in advance. Note: if the O=output/dir is
> used, it must be used with each make command.
> 6. cd /root/linux-2.6.2
> 7. make O=/root/build/kernel menuconfig
> * This starts a menu driven utility to help
> config the kernel
> 8. make O=/root/build/kernel
> 9. make O=/root/build/kernel bzImage
> 10. make O=/root/build/kernel modules_install
> 11. cp /root/build/kernel/arch/i386/boot/bzImage /boot
> 12. cd /boot
> 13. mv vmlinuz vmlinuz.old
> 14. vi /etc/lilo.conf (need to edit lilo for new
> kernel, and add an entry for the old 2.4.22 kernel)
>
> #Linux bootable partition config starts
> #this will load the new kernel 2.6.2
> image = /boot/bzImage
> root = /dev/hda3
> label = slackware
> read-only
>
> #old back-up stock 2.4.22 kernel - old
> faithful
> image = /boot/vmlinuz.old
> root = /dev/hda3
> label = slack2422
> read-only
>
> # End Config File
>
>
> 15. lilo **don't forget this command **
> 16. reboot
>
>
> --
> ===========================
> http://b-o-b.homelinux.com
> Long 93:18W Lat 45:09N
> ===========================
Thanks for the directions, this is exactly what I needed,
I know have Slackware 9.1 running on 2.6.6
Thanks again

On 2004-06-07, Robert D. De Mars <bob-news@b-o-b.homelinux.com> wrote:
> 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?
>> TIA
>>
>>
> This is what I do.

> 3. To avoid possible drama, I never unpack the new
> kernel source in the /usr/src.
I always do, and never get any drama. Maybe I'm missing something :-(
As others pointed out, being root for this is a Bad Thing, so I usually
do something like (as root)
cd /usr/src
mkdir linux-2.6.6
chown <my-userid> linux-2.6.6
and then proceed up until the install phase as just plain old me.

> Since I am logged in as root, I will proceed with unpacking the
> source in my /root dir. I use the following command * bzip2 -cd
> linux-2.6.2.tar.bz2 | tar -xvf -

Much easier:
tar xfvj linux-2.6.6.tar.bz2

> This will unpack everything into /root/linux-2.6.2/
> 4. cd /usr/src/linux & then
> * make mrproper this cleans-up old kernel
> stuff

Ummm.... what does that have to do with the new kernel you are compiling?
If you were re-compiling the old source in the same tree, you would
want to do that, but otherwise I don't see the point.

Cheers.

Jim