|Line 10:||Line 10:|
Revision as of 14:07, 2 May 2013
Assorted information related to the Fedora Linux kernel.
|F17||3.8.x||jforbes||soon to be rebased to 3.9.|
|F18||3.8.x||davej||soon to be rebased to 3.9.|
|F19||3.9||jwb||F19 GA kernel will be 3.9.|
|Rawhide||Latest mainline (3.10-rcX)||jwb||Pretty much always the latest mainline tree.|
Each branches maintainer rotates each month. The MotM field above refers to the current months active maintainer. If in doubt, send mail to the kernel list (info below) rather than individuals.
Fedora kernel mailing list
For discussion about Fedora related kernel package issues only. For "my kernel module doesn't work" type messages, see the http://kernelnewbies.org list, or linux-kernel.
Join thechannel on freenode.net.
Every two weeks, the fedora kernel team meets in the Meeting_channel)channel on freenode.net for a one hour meeting. (Details on times at
Source checkout info
fedpkg co -B kernel
This gets you the git checkout and sets up branches for f13, f14, and master (devel). Once you have switched to the branch you care about (with git checkout branchname), fedpkg prep will create a tree.
You'll then be left with a kernel-2.6.? directory, containing both an unpatched 'vanilla-2.6.?' dir, and a linux-2.6.?-noarch hardlinked dir which has the Fedora patches applied.
The above command will require you to have SSH access to the Fedora pkg-git archives. If you want to do an anonymous checkout of the sources, you can use:
fedpkg co -Ba kernel
Contributing to the Fedora kernel
- For one-off fixes, send them to the fedora-kernel mailing list, or if they are relevant upstream, send them directly to email@example.com and Fedora will inherit them on the next rebase
- If you are sending lots of changes to the Fedora kernel, then it may make more sense for you to get commit access. (Note, for most things, sending them upstream is far more preferable).
- To request commit access to the Fedora kernel:
- Get a fedora account if you don't already have one
- Visit the package db entry for the kernel and request access for the branch(es) which interest you.
- Please subscribe to the mailing list above. Important announcements regarding rebases, builds, patches being disabled, and much more happen there.
- If you're interested in adding an out-of-tree driver or similar to the Fedora kernel, please read KernelDriverPolicy first. See KernelStagingPolicy also.
Commit access also gives you the ability to build kernels that go out to end-users when you 'make build'. Please note the caveats.
- The kernel package currently builds many rpms, which means it ties up the build system for hours at a time. For this reason, coordinate with other developers on irc/fedora-kernel-list to be sure there isn't more than one build happening at once.
- Rawhide gets pushed once a day. If you think a build may occur later in the day for some reason, hold off on building. If in doubt, ask.
- If you are checking in patches for any branch other than rawhide, the build won't automatically go out to users, it needs to be processed through bodhi . Consider the negative effect of flooding end-users with too many updates, and coordinate your builds with others so that we push updates containing more than one fix.
- For the end-user who wants to build a custom kernel, we offer a separate wiki page with complete instructions.
Below are some of the policies we use when it comes to various aspects of the Fedora kernel
- Information on the various debugging options used in Fedora kernels can be found at KernelDebugStrategy
- Building a custom kernel
- Building a non-debugging kernel
- How to use kdump to debug kernel crashes
- Information on building upstream kernels by hand for testing can be found at BuildingUpstreamKernel
- Kernel Updates
- RawhideKernelNodebug The repository for rawhide kernels built without debugging enabled.