I am using the 3.4.x kernels, but may move to 3.6.x soon. I don't like 3.2.x because of bad nouveau drivers and a few other issues. If you don't have problems with it, you can stay with it.

I went to 3.4 based on Pat's configuration in /testing because I wanted to try a kernel with EFI stub enabled. It is working fine for me.

I tried 3.6 but it introduced some ACPI Conflict warnings on my box (Actually, googling, it looks like it was 3.5 that introduced them, but I never tried that one so I can't say for certain). I believe 3.7 contains a fix, so I'll be waiting for that one. In the mean time, it's nice being able to fallback to the 3.2 branch and I'm glad Pat chose to base the release on a long-term kernel.

I have been upgrading to the latest kernel the day they appear on kernel.org since around 1999 using slackware. It is easy. I have only run into one small problem. That was with vmware when the 'tickless kernel' was introduced. That problem only effected vmware and was quickly fixed by the developers.
My reasoning has always been if the kernel developers think the kernel should be constantly upgraded why shouldn't I. After all it is their kernel.
I always start with Pat's latest config.
John

As a note 3.4.x is also long-term.

I just finished upgrading the kernel, after a long strenuous figuring things out, to 3.7.0-rc. Took awhile to figure out what should be turned on in /usr/src/linux/.config. One of the problems that I encountered building the new kernel was that the .config, by default, did not have CONFIG_TMPFS and CONFIG_TMPFS_MOUNT turned on. had to look at GENTOO forums for that :P

Anyways, my question is what are the primary difference between mainline and stable in www.kernel.org ? their FAQ do not explain what the mainline is, at least i think not ;D

I think that's the official position: no explanation. From my personal experience, "stable" kernels do tend to be more stable, and the higher is the 3rd version number, the more stable they are. But the newer ones support more devices, or support them more fully.

Edit: I am running linux-libre 3.6.6 on my lappy now, used Pat's 3.6 config and it just worked (TM). Feels great, with more than a week uptime now. I upgraded to support Ivy Bridge and to purge the kernel blobs.

I have upgraded to very bleeding edge 3.7rc3 with some other patches to solve my macbook pro 8,1 internal mic problem. All is fine.

I'm using 3.7.0-rc7 with .config from http://slackbuilds.org/mirror/slackw...ic-3.6-rc4.x64 Slackware testing file tree. All new modules i'd assumed with the default option.
In mounting USB external disks, i'm having troubles with it dismounting itself, but it seems to be a new approach of udev of newer kernels, not sure yet, anyway i'm trying to solve it...
I also had three reboots with this kernel config, but i was not watching it so not sure too what happened.
I builded a new kernel because i had same troubles of this post http://www.linuxquestions.org/questi...30-4175426269/

By that logic, you should go with a bleeding edge rolling release distribution. Get the "latest and greatest" from everyone.

I haven't compiled a custom kernel for about 5-6 years I reckon; the generic pretty much just works for me. Might even be longer, from memory the last time I did was before the video4linux stuff was integrated.

The only time I upgrade a kernel outside of what comes with Slackware is if I need too. The last time I needed to upgrade a kernel was ages ago.

Actually I do. I upgrade everything that Pat says I need to upgrade. After all its his distribution.
You have a problem with that?
John

It really depends on your needs. For a while I used bleeding edge kernels because I wanted good nouveau support. Now I use the long term 3.4.x, because it has a good nouveau driver, is stable, and is long term support. You may have different requirements and probably can use the default kernel. In fact, for a long time I also used the default kernel version, but still a custom kernel for performance reasons.

This is one of the great things about slackware imo. When we were still at 13.37 and the release candidates i was keeping up with the latest kernel and had no trouble. Since 14 was officially released i have been using the stock kernel.
But to address the op, just back up your boot dir/partition and lilo.conf and create a new menu entry in lilo for the new kernel, dont delete the old one, this way you have a way back and can boot to either kernel when you want to.