ClearFoundation

I installed clearos-devel which pulled in:

(62/167): kernel-devel-2.6.32-279.2.1.v6.x86_64.rpm
(63/167): kernel-headers-2.6.32-279.2.1.v6.x86_64.rpm

ls /usr/src/kernels/
2.6.32-279.2.1.v6.x86_64

Went to compile some new modules and:



When I look around for "No rule to make target `missing-syscalls'" I see most folks are trying to compile headers alone, but according to yum I have BOTH headers and source code.

Unfortunately, contrary to this guide www.clearfoundation.com/docs/howtos/buil...ustom_kernel_modules the "kernel-sourcecode" package is no longer available. Does anyone know if I should have more than kernel-devel installed?

I think 7odd megs may be a wee bit light for a kernel source code package?

So here's how to do it the hard way:

Hi kfox, you would be one person I thought I could ask about it but I am looking at making a good attempt to build a xen enabled kernel for clear for 6x

I figure you might be able to point me in the right direction

Have you tried with the default kernel? Looking at the default .config in this SRPM xen PV guest support is already enabled. If the binary doesn't support it try compiling a new one like I'm in the middle of doing and give that a shot.

I've had a lot of nasty things to say about 6.x that I think need to be addressed (or better addressed) before I start rolling it out in production and consequentially on Xen platforms. When I do, you can be sure I'll post an update to my old PV image since the foundies seem to have provided an image for every virtualization platform but the one that should theoretically do routing best

Its mostly an effort to get xentools to install as I am running citirx xenserver. I agree that there are bunch of things I don't in the 6.x series. But the good thing is that just because we don't like whats there doesn't mean we can't make changes ourselves an release it to the community. I am thinking of using a 3x bog standard kernel and going from there.

Also cheers for your 5.x xen release btw

Its mostly an effort to get xentools to install
Should be a simple matter of finding and installing the RPM for the corresponding CentOS/RHEL version, from repo or distributor.

But the good thing is that just because we don't like whats there doesn't mean we can't make changes ourselves an release it to the community.
Very true.

I am thinking of using a 3x bog standard kernel and going from there.
You could do that but I try to operate on the assumption that Clear might have some particular patches or configurations suited to or expected by it so wherever possible I try to stay close to the original.

I think you might have problems with things like udev or glibc if you use too new a kernel without updating Clear's versions accordingly.

Also cheers for your 5.x xen release btw
Glad some folks have found it useful

The default .config will run you into this little beauty:



Which can be avoided by:

1) Select "Enable loadable module support", then "Module signature verification (EXPERIMENTAL)". Disable it.
2) Then go back to the main menu, select "Cryptographic API" then "In-kernel signature checker (EXPERIMENTAL)" and disable that one too.

Kudos to pascalB @ scientificlinuxforum.org/index.php?showtopic=1324

Now I just have to hope this doesn't affect the ability of the produced modules to be inserted into the distributed kernel; maybe it's safe to say if the Foundies got it to compile they didn't have this enabled to begin with.

The reason I'm doing a full build is simply running make modules doesn't provide any dependency information to the module, which is then rejected when you try to load it. Hopefully this isn't going to require a full kernel swap.

Hi Kfox, its normal for kernel-devel only to include the required headers and makefiles to build specific compatible kernel modules (think kmod RPM's, or manual module compilation using configure && make && make install). From experience I don't think you can rebuild the whole kernel module tree using this RPM

This RPM normally prevents you having to install the whole kernel source code. As you have found kernel-sourcecode as a package does not exist anymore (as per upstream packaging)...rather the source is shipped as per other RPMs in the SRPM or src.rpm found in the clearos-dev repo

Note also that rhel also distribute prepatched tar balls...rather than the vanilla source code, and subsequent patches (as was the case in el5)

If you just install the kernel-xxx.src.rpm using 'rpm -ivh' it would have put the patches, spec, source and configs all within your local users dev environment (~rpmbuild/SOURCES or ~/rpmbuild/SPECS etc). From here you can then patch or rebuild it as you need from the spec file...

If you're interested in a newer 3.x kernel, check out the kernel-ml el6 builds over at elrepo.org If I had time i'd consider patching it for ClearOS (IMQ bandwidth shaping) to see how it worked...

So what is the purpose of kernel-headers-2.6.32-279.2.1.v6.x86_64?


It looks like you're right; I just looked at my 5.2 VMs and their kernel-devel is tiny as well.

If you're interested in a newer 3.x kernel, check out the kernel-ml el6 builds over at elrepo.org If I had time i'd consider patching it for ClearOS (IMQ bandwidth shaping) to see how it worked...
Where's the patch for that? I might get drunk and try one day.

I just posted information about the "kernel-sourcecode" in another thread:

www.clearfoundation.com/component/option...view/id,45413/#45436

That information should really be used to update the existing Howto:

www.clearfoundation.com/docs/howtos/buil...ustom_kernel_modules

I didn't even know that doc existed... and I wrote it