PDA

View Full Version : The Complete Fedora Kernel Headers



raoul
9th January 2006, 11:29 AM
As I had not been able to build certain 3rd party kernel modules (lirc_gpio, truecrypt) using the stock kernel-devel package, I wrote a small article about how to use the kernel SRPM to obtain the complete kernel headers for the currently running kernel on the system, without having to compile the kernel itself.
The Complete Fedora Kernel Headers (http://www.g-loaded.eu/2005/12/14/the-complete-fedora-kernel-headers/)
Most of this info exists in the Fedora Release Notes, but here I have added some more explanation and some required extra steps.

A small BASH script that does this job exists at:
Get my kernel headers script (http://www.g-loaded.eu/2005/12/15/get-my-kernel-headers-script/)

What I really wanted to know is if this is an accepted approach to resolve the issue.

RahulSundaram
11th January 2006, 11:37 PM
As I had not been able to build certain 3rd party kernel modules (lirc_gpio, truecrypt) using the stock kernel-devel package, I wrote a small article about how to use the kernel SRPM to obtain the complete kernel headers for the currently running kernel on the system, without having to compile the kernel itself.
The Complete Fedora Kernel Headers (http://www.raoul.shacknet.nu/2005/12/14/the-complete-fedora-kernel-headers/)
Most of this info exists in the Fedora Release Notes, but here I have added some more explanation and some required extra steps.

A small BASH script that does this job exists at:
Get my kernel headers script (http://www.raoul.shacknet.nu/2005/12/15/get-my-kernel-headers-script/)

What I really wanted to know is if this is an accepted approach to resolve the issue.

I think a better resolution is to file a bug report and get this resolved by default. You might consider joining the Fedora Documentation Project. You seem to be do a handy job with it

http://fedoraproject.org/wiki/DocsProject

raoul
12th January 2006, 06:32 PM
Hello Rahul,
A bug report about lirc_gpio has already been filed in the Red Hat Bugzilla by someone else:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176758
the current bug status is: CLOSED UPSTREAM
But, the comments that have been posted there did not help at all in resolving the lirc_gpio issue, so I started experimenting with the fedora kernel sources.

For the truecrypt module, the device mapper header (dm.h) is needed, which is also unavailable in kernel-devel. I do not consider that this worths filing a bug at the moment, since the current linux version of truecrypt is not fully functional as it cannot create any encrypted containers (it can only manage containers that have been created with the Windows version).

Thanks for the good words. I would definitely like to contribute to one or more Fedora Projects, since I use Fedora as my main operating system. The reasons I haven't done so until now are that I have no previous experience and that I do not know if my technical knowledge is enough (my field is far from the Computer Science). Anyway, I intend to participate.

I have one question though (important to me): What kind of a commitment is it to participate in such a project? Is there any timeline/schedule that a participant should follow?

RahulSundaram
13th January 2006, 07:10 AM
Hello Rahul,
A bug report about lirc_gpio has already been filed in the Red Hat Bugzilla by someone else:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176758
the current bug status is: CLOSED UPSTREAM
But, the comments that have been posted there did not help at all in resolving the lirc_gpio issue, so I started experimenting with the fedora kernel sources.

For the truecrypt module, the device mapper header (dm.h) is needed, which is also unavailable in kernel-devel. I do not consider that this worths filing a bug at the moment, since the current linux version of truecrypt is not fully functional as it cannot create any encrypted containers (it can only manage containers that have been created with the Windows version).

Thanks for the good words. I would definitely like to contribute to one or more Fedora Projects, since I use Fedora as my main operating system. The reasons I haven't done so until now are that I have no previous experience and that I do not know if my technical knowledge is enough (my field is far from the Computer Science). Anyway, I intend to participate.

I have one question though (important to me): What kind of a commitment is it to participate in such a project? Is there any timeline/schedule that a participant should follow?

Looks like you are facing a slightly different but related issue. Do file a additional bug report specifying the precise details of the lirc_gpio module and get this fixed if you want to.

There are several different projects and many of them do not require much technical knowledge at all. . You don't need to be a computer specialist. Ambassadors project as a specific example is about promoting Fedora. Documentation is of different types. Release notes and installation guides follow a schedule but other documents but might be more generic. See

http://fedoraproject.org/wiki/DocsProject

You can also help by doing some testing and filing bug reports on the test/development releases. See http://fedoraproject.org/wiki/HelpWanted for all the different means to contribute. The only commitment thats obsolutely required is having a interest in it which you obviously do already.