Fresh off of burning my fingers with the soldering iron, I had a thought about this.

If I'm running multilib and I upgrade my kernel, is there any reason I would have to roll my own multilib to go with my new kernel? Or could I keep using Alien's (currently from 3.2.29) without problems? Of course the 3.2.29 header files would still be there, but let's say I was running a 3.5.4 kernel?

Or maybe it's just the bacon smell that's getting to me?! :)

You can still use Alien Bob's multilib packages without any problems. They are glibc version-dependent but not kernel version-dependent (though, as you said, make sure you keep the original kernel headers).

I have a question about the kernel headers and glibc.
I am making packages for kernel-source kernel-huge and kernel-modules on my
slackware 14.0 64-bit system. The kernel-source package is done and I'm using
3.0.49 source tree. Nice build scrips from slackware.com will be used to build
renaming pkg. Witch is kernel-huge, kernel-modules and
?? kernel-headers ?? ?? rebuild glibc ??
(there is no builds script for kernel-header,only a slack-desc file?)

If the software is built from glibc that is built from kernel 3.2.29 headers
and now will be running along an older kernel like 3.0.x .

will my software still sync, work and compile correctly with older kernels runing?

I think like this:

software ---> glibc/elf ---> 3.2.29 headers -?-> >>>older kernel running different instructions<<<

Wish Linus was here now. But any answer is better then none.

AFAIK there is no need to rebuild kernel-headers nor (hopefully!) glibc.

the kernel-headers package simply copy headers from the kernel tree to /usr/include, this is why:
(1) There is no need for a SlackBuild for it.
(2) These headers (in /usr/include) won't be overridden if you install a new kernel-source, so there is no need to update them when you install a new kernel-source package.

Oh, and in any case the sanitized kernel headers should be there *before* you re-build glibc (which is hopefully not necessary in your case anyway) as noted in glibc.SlackBuid:
Long story short, just install your kernel 3.0.49, no need to change the kernel-headers nor glibc AFAIK.

what kind of error could show up if there where problems.
or how do I know if I need to downgrade headers and rebuild glibc?
what symptoms do I look for or how to test if I'm not the lucky one?

I mean if my kernel boot and nothing special happens,
can I just go on and forget about it ??

Don't worry, just try and in case something looks weird, come back here.

Only add a new entry for the new (I should say old) kernel in /etc/lilo.conf instead or erasing the old one, just in case.

With Alien Bob instructions and the .config from http://mirrors.slackware.com/slackwa...sting-3.6-rc4/ the 3.6.3 and 3.6.4 kernels works with only one new module not set on .config .
I'm also changed preemptive processor option and hostname, without any problems. On Alien tutorial need to change the x86 or x86_64 part of copying the new bzImage from tree if you're running x86 or x86_64 .config .