You need to install the 2.6 kernel source. I think it is on the second cd in the extra directory. You install it the way you installed the modules. It will create the soft link /usr/src/linux to your /usr/src/linux-2.6.27.13.

Thanks, that worked. You guys are awsome.

Nah, we just been down the road you are on now.

Ah, so that explains the McDonald's wrappers.

Do I want to remove all the 2.4 stuff, then install the 2.6 stuff (all except the headers)?[/QUOTE]
It is good to save for backup. You can set up your boot to choose a default and allow the other kernel as an option.

So to change kernels, all I have to do is change grub (or lilo) to point to a new kernel? So could I point to say my pclinuxos kernel and boot slackware on that kernel? Not that I would want to, but am just trying to figure out how this works.

You could do that I suppose, and only use 1 kernel for like 5 distributions. You'd have to make sure your kernel is on a partition that is mounted by all the distros though to make sure it can be accessed. My guess is, though I can't say for sure, that even though this is possible its probably not a good idea.

Definatly somehting I'd like you to try so I don't have to

Technically you could but it might not be that simple since you will have to have all of the correct headers and modules to support that kernel. If you're just using a couple installations of Slackware, you could use a /boot partition that each installation mounts and then you could just point to that with lilo or grub.
I'm not completely sure but I think sharing kernels between distros might end up getting messy but you could try it. It won't hurt anything to have a few lilo/grub entries pointing to different kernels.

Ok, thanks. I think I am starting to understand. So when I run makemenuconfig, and then make && make modules. Does it compile a new kernel, and also make all the modules and headers for that kernel? Then all I need to do is copy the new kernel found in /usr/src/linux/arch/i386/boot/bzImage to /boot, and call it vmlinuz-whatever. Then just point grub or lilo to it.

Exactly

Thanks guys. It feels so good to actually start to understand what I am doing.

Have you found the answer by now?

It appears that, even the source, can have two different Slack packages of it installed, onboard? Is this correct?

As far as Slack pkgs go, I didn't know if some of the Slack pkg 2.6 source would overwrite some of the 2.4 source or not (if I were to install 2.6 source in addition to or while the 2.4 source is installed.

I do know that as to the remainder or everything else per your above quoted question, you can have both the 2.4 and the 2.6 stuff installed.

--
Alan.

I left 2.4 for now. I am not sure what would happen if I tried using it again. But I don't think I will, because 2.6 seems to work just fine.

This is what I now have.

If your last step is "make install" the script puts the works in /boot for you. You can have any number of kernels there. The modules are stored in /lib/modules
with the kernel release name. If you use installpkg for the source you can have any number of sources in /usr/src. The last one installed will be symlinked to /usr/src/linux. Upgradepkg cleans everything out but the designated source.

Lilo or grub can have multiple entries so you can switch back and forth from 2.4 to 2.6 with no problem.

If you use an initrd you can name each one distinctly and use that name in the boot entry to keep multiple versions.

I have

2.4.33.3
2.6.16.27
2.6.17.13
2.6.18

all available with individual initrds for the 2.6 kernels.

thanks that is good to know. I am going to have to read up on initrd. I am not sure what it does.