hiya.... lol... looks like a lot of these sorts of questions lately....

well... here are mine (i'll try to keep this quick....)

long story short... i upgraded from 10.0 to 10.2... everything seemed to work out okay.
now i want to upgrade my kernel. i tried to download a 2.6.14 kernel and do it myself using SHILO's help that he put up here... but alas... after a week or so a putzing with the thing it's still not working right and i have a new sound card i want to install ontop of all this.... so i'm thinking of just going out and getting the 2.6.13 kernel pat has in the 'testing' (in the slack current folder) and doing an 'upgradepkg' on it. here are my questions....

1) right now in lilo i got 3 options.....
a) windows... which points to my first hard drive
b) linux.... which point to my old kernel (vmlinuz-ide-2.4.26)
c) slackware... which points to my 'new' kernel (vmlinuz..)

if i just do 'upgradepkg kernel*' will my old kernel still be there? or does the upgrade write over the entire folder? in otherwords... b) should lead to my old kernel and c) will lead to my new kernel if i upgrade using this method... right?

also... i'll probably have to upgradepkg alsa... it should detect my new soundcard afterwords right? just alsaconf, alsamixer, etc.... or is there something special i'm going to have to do? (the sound is a sound blaster live! 24-bit 7.1 ....BTW)

lastly... i see that pat says in the 'testing folder' in slack current not to upgrade the kernel headers... and i've seen a couple of post where people say 'upgrade the headers...' so... should i upgrade my headers or not? (have no clue what it does...lol)

well... i tried to keep it short... anyhow.. thanks

1) No.

If you want to keep your old kernel, do not run upgradepkg, just run installpkg. Also, see the README notes in /testing for Pat's 2.6.13 kernel as you need to set up an initrd for that kernel (especially if you use reiserfs for your hard drives).

You will also need to edit /etc/lilo.conf to add a new entry for the new kernel, and then run /sbin/lilo to update lilo.

2) As with the old kernel, do *not* run installpkg if you want to keep the old kernel and alsa. Just install the alsa-driver-1.0.9b_2.6.13.x from /testing (alsa-lib, oss and utils don't change).

After booting with your new kernel, run 'alsaconf' to update /etc/modprobe.conf (the new file used by 2.6).

3) Do *not* upgrade the kernel headers to 2.6.x - the kernel headers should match that of which glibc was built against. In Slackware's case, as long as glibc is built against 2.4, then kernel headers should be from a 2.4 kernel, not 2.6. The only reason to upgrade is some drivers and software require 2.6 headers to build, but these cases should be fairly rare (I've never come across this problem). Therefore, unless there is some actual need for you to do so, do not upgrade the kernel headers to 2.6

ok... thanks.. i'll give it a whirl