I have two questions:

* What is an easy way to use the 2.6 kernel right from 10.2 CD installation (so that everything works)? Will setup install the module packages and configure initrd for me? If not, what do I need to do?

* Does anyone have a safe (doesn't mess everything up) procedure they use to upgrade Slackware from 10.2 to current using slackpkg?
I've already done the instructions from the section on package management in Slackbasics, making sure to slackpkg install-new everything before upgrading the system and it didn't work.

Thanks in advance.

the safest way to upgrade the kernel packages is manual
i wouldn't let slackpkg, slapt-get, swaret, etc touch anything
related to the kernel or lilo

Just boot from the test26.s kernel and tell the installer to use that as the kernel.

Since it's a testing/ kernel it will NOT install the modules. You have to mount the second CD (either after you reboot, once you're running your brand new system, or unmount the CD1 after the installation is over and mount the CD2), and install the ALSA modules (unless you don't want sound in your system) and the kernel modules. I can't remember for sure the directory it was in... Was it testing/ too?

Before anything make sure to issue "slackpkg update". Note that you'll start following -current after that. Just to be safe, it's recommended to read the ChangeLog (http://www.slackware.com/changelog/current.php?cpu=i386) to know if you have to "install-new" packages. (if you just came from a Slack 10.2 install, you'll have to).

Also IIRC, "install-new" is only available in the lastest Slackpkg versions (2.x).

The recomendation that kodon gave you about not letting slackpkg touch the kernel or lilo is pretty wise. Even if slackpkg should be able to handle a kernel upgrade (I've never actually tried), it's more safe to handle those things on your own, specially if you like to mess up with the kernel .

** After I install the 2.6 kernel and alsa modules, will the modules work automatically? If not, how do I set them up? And what if I'm using reiserfs?

BTW:
* I did slackpkg update.
* What should I be looking for in the changelog?
* Any recommendations as to what else to blacklist besides the usual?

I regularily install using the test26.s kernel. Just pop in CD2, browse to /linux-2.6.* and use upgradepkg on all the ones in there, with the exception of kernel-generic. Reboot, and all should be well. I do this before the initial reboot of the installation (otherwise my USB keyboard will not work - needs the USB module).

I run slackware 10.2 with only a few things at current (Xorg for one). I havent been game enough to run a -current machine, though cwwilson says his runs fine.

I always just mount the 2nd Slackware CD, and in the linux2.6 directory read the INITRD readme file. It will guide you step by step on how to install the 2.6 kernel, modules, source, and alsa and make the initial Ram disk with an example for reiserfs for you to simply copy and paste into a terminal. It also describes what lilo changes need to be made. It never fails. Good luck.

Thanks, everyone!

In case anyone wants to know, this is what I did:

* I just booted the default 2.4 kernel and installed normally. When that was done, I installed all the packages in the linux-2.6.13 dir on the second CD before rebooting. After the reboot, I followed the instructions in README.initrd, deleted the kernel 2.4 packages, and rebooted. This worked perfectly and it wasn't nearly as hard as I thought it'd be.

* For slackpkg, I just edited /etc/slackpkg.conf so that GPG checking is turned off (that was the problem I neglected to mention before) and did the usual stuff (choose a mirror, slackpkg update, slackpkg upgrade-all). When I got the occasional program not working because of missing libraries, all I had to do was slackpkg search <the-missing-file> and install the needed package.

In the last few weeks, in all my fiddling/fumbling with Slackware, I've learned more about Linux than I did using RedHat 9 for over a year (back in the day).

... Now all I have to do is get alsa working.

I've used the official Slackware UPGRADE.TXT method to keep several boxen upgraded to -current.

I also have a link to Darrell Anderson's Updating Slackware guide, where he states:
He has some wisdom in that article.

You should understand that -current is development software, has bugs, and will sometimes break things in your system. You will learn more by fixing them; unless you just wait on Pat V. to fix it in another -current update, in which case you'll learn patience.

If you search these forums, and Google <Linux>, you'll find literally thousands of people who fubar their systems using all those other methods to upgrade Slackware.

If it's a system you need to work, and can't afford to break, just use the latest stable Slackware version, and don't bother keeping "current" afterwards; just try to make the stable release install better over time. But if you have a system that you can use to test, then run -current and help Pat by finding and reporting bugs.

That's what Slackware-current is for, breaking and fixing -- not for people who can't tech their system to have the latest software...

Read Alien Bob's post in this thread.