Hello, Slackers

I have installed and configured Slackware 13.1 and it works perfectly. Now I'm going(actually forced) to downgrade kernel version down to 2.6.32. Is there any caveats? Do I need rebuild any other packages from sources?
(In case of 13.37 the same questions)

Build a new kernel and leave a symlink to your present kernel.

Even running custom kernels the install kernel is always present
on my Slackware boxen. This kernel rebuild guide has proper steps.

NB: Using your present kernel .config file is probably not a good
idea, as many options have changed or been added since 2.6.32.

Can you share why you are forced to downgrade your kernel?

Many thing will work, some things might not...

Especially non-standard kernel modules you will need to rebuild for each kernel.
Also the nvidia driver, if you use that.

Now, out of curiosity, what forces you to go back to 2.6.32?

All you have to do is install the kernel modules for that version.

Thanks, but I know how to build kernels(have 20-30 installations with successfully updated kernels). I do not fair kernel upgrade because of positive experience, but have not downgrade experience.

For now I do not care about video drivers and other stuff targeted for Desktop uses of Linux.

Because of OpenVZ. I did not found any ready-made solutions based on Slackware so decided to create my own(or to try). It requires to install their own patched kernel. Latest one they have which is closest to kernel in Slackware is 2.6.32 and it is in development branch. So I want be sure if my system fails, it fails only because of kernel, but not incorrect work of other stuff(like glibc) with it.

If you like to play with Slackware and that type of virtualization, how about Linux Containers, which is the native Slackware (13.37) solution?

Darth Vader
Thanks for tip, I shall try it a bit letter.
I wonder if it stable enough? I have read linked article, and found some configuration options which must be turned on are marked as Experimental. In my experience systems which intensively use experimental stuff are offten crashed.

Ummm... I have no idea. Probably, yes.

But, because that Linux Containers, aka LXC, are shipped by Slackware 13.37, I think we could raise this question to the First Slacker ...

Then, it's an experimental stuff for geeks or a production ready solution?

Don't forget about linux-vserver -> http://linux-vserver.org
always served me well, but maybe this LXC thing is cooler because it is shipped with slack

Just checked source/k/config-generic-2.6.37.4 and found some options needed by LXC(from list in LXC HOWTO) are not enabled, and there is no userspace tools to manage LXC shipped in current. So you was a bit hasty stating "the native Slackware (13.37) solution".


hotchili
As far as I understood, LVS is more like openvz. For now I have configured openvz successfully(there some boot tunings left).

But we a bit offtopic.

ap/lxc-0.7.4-i486-2.txz

And if we talk about a possible incorrect kernel configuration, from LXC p.o.v., how about a little bug report to Mr. Volkerding (known as volkerdi in our little forum)?

Darth Vader, oops, I have missed it(buggy search or I probably viewed list of packages from 13.1).
I think I will hold any bug-report until I try it(for now I have only one 13.37 installation updated from 13.1 and I do not trust myself enough to be sure I did not broke anything).

From the 13.1 RELEASE_NOTES file:

So I think you'll be OK.

It seems I made mistake again. Configuration seems to be ok. But still, it is easier to use openvz than lxc.