{"title":"The Linux Kernel Archives","link":[{"@attributes":{"href":"https:\/\/www.kernel.org\/","rel":"alternate"}},{"@attributes":{"href":"https:\/\/www.kernel.org\/feeds\/all.atom.xml","rel":"self"}}],"id":"https:\/\/www.kernel.org\/","updated":"2026-02-25T18:15:52+00:00","entry":[{"title":"Active kernel releases","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/releases.html","rel":"alternate"}},"published":"2026-02-25T18:15:52+00:00","updated":"2026-02-25T18:15:52+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2026-02-25:\/releases.html","summary":"<p>There are several main categories into which kernel releases may fall:<\/p>\n<dl class=\"docutils\">\n<dt>Prepatch<\/dt>\n<dd>Prepatch or &quot;RC&quot; kernels are mainline kernel pre-releases that are\nmostly aimed at other kernel developers and Linux enthusiasts. They\nmust be compiled from source and usually contain new features that\nmust be tested before they can be \u2026<\/dd><\/dl>","content":"<p>There are several main categories into which kernel releases may fall:<\/p>\n<dl class=\"docutils\">\n<dt>Prepatch<\/dt>\n<dd>Prepatch or &quot;RC&quot; kernels are mainline kernel pre-releases that are\nmostly aimed at other kernel developers and Linux enthusiasts. They\nmust be compiled from source and usually contain new features that\nmust be tested before they can be put into a stable release.\nPrepatch kernels are maintained and released by Linus Torvalds.<\/dd>\n<dt>Mainline<\/dt>\n<dd>Mainline tree is maintained by Linus Torvalds. It's the tree where\nall new features are introduced and where all the exciting new\ndevelopment happens. New mainline kernels are released every 9-10\nweeks.<\/dd>\n<dt>Stable<\/dt>\n<dd>After each mainline kernel is released, it is considered &quot;stable.&quot;\nAny bug fixes for a stable kernel are backported from the mainline\ntree and applied by a designated stable kernel maintainer. There are\nusually only a few bugfix kernel releases until next mainline kernel\nbecomes available -- unless it is designated a &quot;longterm maintenance\nkernel.&quot; Stable kernel updates are released on as-needed basis,\nusually once a week.<\/dd>\n<dt>Longterm<\/dt>\n<dd>There are usually several &quot;longterm maintenance&quot; kernel releases\nprovided for the purposes of backporting bugfixes for older kernel\ntrees. Only important bugfixes are applied to such kernels and they\ndon't usually see very frequent releases, especially for older\ntrees.<\/dd>\n<\/dl>\n<table border=\"1\" class=\"docutils\">\n<caption>Longterm release kernels<\/caption>\n<colgroup>\n<col width=\"11%\" \/>\n<col width=\"46%\" \/>\n<col width=\"17%\" \/>\n<col width=\"26%\" \/>\n<\/colgroup>\n<thead valign=\"bottom\">\n<tr><th class=\"head\">Version<\/th>\n<th class=\"head\">Maintainer<\/th>\n<th class=\"head\">Released<\/th>\n<th class=\"head\">Projected EOL<\/th>\n<\/tr>\n<\/thead>\n<tbody valign=\"top\">\n<tr><td>6.18<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2025-11-30<\/td>\n<td>Dec, 2028<\/td>\n<\/tr>\n<tr><td>6.12<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2024-11-17<\/td>\n<td>Dec, 2028<\/td>\n<\/tr>\n<tr><td>6.6<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2023-10-29<\/td>\n<td>Dec, 2027<\/td>\n<\/tr>\n<tr><td>6.1<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2022-12-11<\/td>\n<td>Dec, 2027<\/td>\n<\/tr>\n<tr><td>5.15<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2021-10-31<\/td>\n<td>Dec, 2026<\/td>\n<\/tr>\n<tr><td>5.10<\/td>\n<td>Greg Kroah-Hartman &amp; Sasha Levin<\/td>\n<td>2020-12-13<\/td>\n<td>Dec, 2026<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"section\" id=\"distribution-kernels\">\n<h2>Distribution kernels<\/h2>\n<p>Many Linux distributions provide their own &quot;longterm maintenance&quot;\nkernels that may or may not be based on those maintained by kernel\ndevelopers. These kernel releases are not hosted at kernel.org and\nkernel developers can provide no support for them.<\/p>\n<p>It is easy to tell if you are running a distribution kernel. Unless you\ndownloaded, compiled and installed your own version of kernel from\nkernel.org, you are running a distribution kernel. To find out the\nversion of your kernel, run <cite>uname -r<\/cite>:<\/p>\n<pre class=\"literal-block\">\n# uname -r\n5.6.19-300.fc32.x86_64\n<\/pre>\n<p>If you see anything at all after the dash, you are running a distribution\nkernel. Please use the support channels offered by your distribution\nvendor to obtain kernel support.<\/p>\n<\/div>\n<div class=\"section\" id=\"releases-faq\">\n<h2>Releases FAQ<\/h2>\n<p>Here are some questions we routinely receive about kernel release\nversions. See also the main &quot;FAQ&quot; section for some other topics.<\/p>\n<div class=\"section\" id=\"when-is-the-next-mainline-kernel-version-going-to-be-released\">\n<h3>When is the next mainline kernel version going to be released?<\/h3>\n<p>Linux kernel follows a simple release cadence:<\/p>\n<ul class=\"simple\">\n<li>after each mainline release, there is a 2-week &quot;merge window&quot; period\nduring which new major features are introduced into the kernel<\/li>\n<li>after the merge window closes, there is a 7-week bugfix and\nstabilization period with weekly &quot;release candidate&quot; snapshots<\/li>\n<li>rc7 is usually the last release candidate, though occasionally there\nmay be additional rc8+ releases if that is deemed necessary<\/li>\n<\/ul>\n<p>So, to find the approximate date of the next mainline kernel release,\ntake the date of the previous mainline release and add 9-10 weeks.<\/p>\n<p>You can also subscribe to the releases calendar that forecasts key\ndevelopment dates for the upcoming kernels:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases-calendar.ics\">https:\/\/www.kernel.org\/releases-calendar.ics<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"section\" id=\"what-is-the-next-longterm-release-going-to-be\">\n<h3>What is the next longterm release going to be?<\/h3>\n<p>Longterm kernels are picked based on various factors -- major new\nfeatures, popular commercial distribution needs, device manufacturer\ndemand, maintainer workload and availability, etc. You can roughly\nestimate when the new longterm version will become available based on\nhow much time has elapsed since the last longterm version was chosen.<\/p>\n<\/div>\n<div class=\"section\" id=\"why-are-some-longterm-versions-supported-longer-than-others\">\n<h3>Why are some longterm versions supported longer than others?<\/h3>\n<p>The &quot;projected EOL&quot; dates are not set in stone. Each new longterm kernel\nusually starts with only a 2-year projected EOL that can be extended\nfurther if there is enough interest from the industry at large to help\nsupport it for a longer period of time.<\/p>\n<\/div>\n<div class=\"section\" id=\"does-the-major-version-number-4-x-vs-5-x-mean-anything\">\n<h3>Does the major version number (4.x vs 5.x) mean anything?<\/h3>\n<p>No. The major version number is incremented when the number after the\ndot starts looking &quot;too big.&quot; There is literally no other reason.<\/p>\n<\/div>\n<div class=\"section\" id=\"does-the-odd-even-number-still-mean-anything\">\n<h3>Does the odd-even number still mean anything?<\/h3>\n<p>A long time ago Linux used a system where odd numbers after the first\ndot indicated pre-release, development kernels (e.g. 2.1, 2.3, 2.5).\nThis scheme was abandoned after the release of kernel 2.6 and these days\npre-release kernels are indicated with &quot;-rc&quot;.<\/p>\n<\/div>\n<\/div>\n","category":{"@attributes":{"term":"Releases"}}},{"title":"The Linux Kernel Organization","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/nonprofit.html","rel":"alternate"}},"published":"2024-08-06T19:40:29+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2024-08-06:\/nonprofit.html","summary":"<p>The Linux Kernel Organization is a California Public Benefit Corporation\nestablished in 2002 to distribute the Linux kernel and other Open Source\nsoftware to the public without charge. We are recognized by the IRS as a\n501(c)3 private operating foundation.<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/corporate\/irs-nonprofit-ok-redacted.pdf\">IRS determination letter<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/corporate\/state-nonprofit-ok-redacted.pdf\">California determination letter<\/a><\/li>\n<\/ul>\n<p>The Linux \u2026<\/p>","content":"<p>The Linux Kernel Organization is a California Public Benefit Corporation\nestablished in 2002 to distribute the Linux kernel and other Open Source\nsoftware to the public without charge. We are recognized by the IRS as a\n501(c)3 private operating foundation.<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/corporate\/irs-nonprofit-ok-redacted.pdf\">IRS determination letter<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/corporate\/state-nonprofit-ok-redacted.pdf\">California determination letter<\/a><\/li>\n<\/ul>\n<p>The Linux Kernel Organization is managed by <a class=\"reference external\" href=\"http:\/\/linuxfoundation.org\/\">The Linux Foundation<\/a>, which\nprovides full technical, financial and staffing support for running and\nmaintaining the kernel.org infrastructure.<\/p>\n<div class=\"section\" id=\"legal-information\">\n<h2>Legal information<\/h2>\n<p>Due to U.S. Exports Regulations, all cryptographic software on this site\nis subject to the following legal notice:<\/p>\n<blockquote>\n<strong>This site includes publicly available encryption source code which,\ntogether with object code resulting from the compiling of publicly\navailable source code, may be exported from the United States under\nLicense Exception &quot;TSU&quot; pursuant to 15 C.F.R. Section 740.13(e).<\/strong><\/blockquote>\n<p>This legal notice applies to cryptographic software only. Please see the\n<a class=\"reference external\" href=\"https:\/\/www.bis.doc.gov\/\">Bureau of Industry and Security<\/a> for more information about current U.S.\nregulations.<\/p>\n<p>Our servers are located in Corvallis, Oregon, USA; Palo Alto and San\nFrancisco, California, USA; Portland, Oregon, USA; and Montr\u00e9al, Qu\u00e9bec,\nCanada.<\/p>\n<p>Use in violation of any applicable laws is prohibited.<\/p>\n<p>Linux is a Registered Trademark of Linus Torvalds. All trademarks are\nproperty of their respective owners.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"About"}}},{"title":"About Linux Kernel","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/linux.html","rel":"alternate"}},"published":"2024-08-06T19:40:29+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2024-08-06:\/linux.html","summary":"<div class=\"section\" id=\"what-is-linux\">\n<h2>What is Linux?<\/h2>\n<p>Linux is a clone of the operating system Unix, written from scratch by\nLinus Torvalds with assistance from a loosely-knit team of hackers\nacross the Net. It aims towards POSIX and <a class=\"reference external\" href=\"http:\/\/www.unix.org\/\">Single UNIX Specification<\/a>\ncompliance.<\/p>\n<p>It has all the features you would expect in a modern fully-fledged \u2026<\/p><\/div>","content":"<div class=\"section\" id=\"what-is-linux\">\n<h2>What is Linux?<\/h2>\n<p>Linux is a clone of the operating system Unix, written from scratch by\nLinus Torvalds with assistance from a loosely-knit team of hackers\nacross the Net. It aims towards POSIX and <a class=\"reference external\" href=\"http:\/\/www.unix.org\/\">Single UNIX Specification<\/a>\ncompliance.<\/p>\n<p>It has all the features you would expect in a modern fully-fledged Unix,\nincluding true multitasking, virtual memory, shared libraries, demand\nloading, shared copy-on-write executables, proper memory management, and\nmultistack networking including IPv4 and IPv6.<\/p>\n<p>Although originally developed first for 32-bit x86-based PCs (386 or\nhigher), today Linux also runs on a multitude of other processor\narchitectures, in both 32- and 64-bit variants.<\/p>\n<\/div>\n<div class=\"section\" id=\"new-to-linux\">\n<h2>New to Linux?<\/h2>\n<p>If you're new to Linux, you don't want to download the kernel, which is\njust a component in a working Linux system. Instead, you want what is\ncalled a distribution of Linux, which is a complete Linux system. There\nare numerous distributions available for download on the Internet as\nwell as for purchase from various vendors; some are general-purpose, and\nsome are optimized for specific uses. We currently have mirrors of\nseveral distributions available at <a class=\"reference external\" href=\"https:\/\/mirrors.kernel.org\/\">https:\/\/mirrors.kernel.org\/<\/a>.<\/p>\n<p>Note, however, that most distributions are very large (several\ngigabytes), so unless you have a fast Internet link you may want to save\nyourself some hassle and purchase a CD-ROM with a distribution; such\nCD-ROMs are available from a number of vendors.<\/p>\n<\/div>\n<div class=\"section\" id=\"mailing-lists\">\n<h2>Mailing lists<\/h2>\n<p>The Linux kernel is discussed on the linux-kernel mailing list at\n<a class=\"reference external\" href=\"http:\/\/vger.kernel.org\/\">vger.kernel.org<\/a>. Please read the <a class=\"reference external\" href=\"http:\/\/www.tux.org\/lkml\/\">FAQ<\/a> before subscribing.<\/p>\n<p>Although there is no official archive site, unofficial archives of the list can be found at:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/lkml.org\/\">https:\/\/lkml.org\/<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/marc.info\/?l=linux-kernel\">https:\/\/marc.info\/?l=linux-kernel<\/a><\/li>\n<\/ul>\n<\/div>\n","category":{"@attributes":{"term":"About"}}},{"title":"Frequently asked questions","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/faq.html","rel":"alternate"}},"published":"2024-08-06T19:40:29+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2024-08-06:\/faq.html","summary":"<p>If you have questions, comments or concerns about the F.A.Q. please\ncontact us at <a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>.<\/p>\n<div class=\"section\" id=\"is-linux-kernel-free-software\">\n<h2>Is Linux Kernel Free Software?<\/h2>\n<p>Linux kernel is released under the terms of GNU GPL version 2 and is\ntherefore Free Software as defined by the <a class=\"reference external\" href=\"https:\/\/www.fsf.org\/\">Free Software Foundation<\/a>.<\/p>\n<p>For more \u2026<\/p><\/div>","content":"<p>If you have questions, comments or concerns about the F.A.Q. please\ncontact us at <a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>.<\/p>\n<div class=\"section\" id=\"is-linux-kernel-free-software\">\n<h2>Is Linux Kernel Free Software?<\/h2>\n<p>Linux kernel is released under the terms of GNU GPL version 2 and is\ntherefore Free Software as defined by the <a class=\"reference external\" href=\"https:\/\/www.fsf.org\/\">Free Software Foundation<\/a>.<\/p>\n<p>For more information, please consult the documentation:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/docs.kernel.org\/process\/license-rules.html\">Linux kernel licensing rules<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"section\" id=\"i-heard-that-linux-ships-with-non-free-blobs\">\n<h2>I heard that Linux ships with non-free &quot;blobs&quot;<\/h2>\n<p>Before many devices are able to communicate with the OS, they must first\nbe initialized with the &quot;firmware&quot; provided by the device manufacturer.\nThis firmware is not part of Linux and isn't &quot;executed&quot; by the kernel --\nit is merely uploaded to the device during the driver initialization\nstage.<\/p>\n<p>While some firmware images are built from free software, a large subset\nof it is only available for redistribution in binary-only form. To\navoid any licensing confusion, firmware blobs were moved from the main\nLinux tree into a separate repository called <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/firmware\/linux-firmware.git\/\">linux-firmware<\/a>.<\/p>\n<p>It is possible to use Linux without any non-free firmware binaries, but\nusually at the cost of rendering a lot of hardware inoperable.\nFurthermore, many devices that do not require a firmware blob during\ndriver initialization simply already come with non-free firmware\npreinstalled on them. If your goal is to run a 100% free-as-in-freedom\nsetup, you will often need to go a lot further than just avoiding\nloadable binary-only firmware blobs.<\/p>\n<\/div>\n<div class=\"section\" id=\"can-i-use-the-word-linux-or-the-tux-logo\">\n<h2>Can I use the word &quot;Linux&quot; or the Tux logo?<\/h2>\n<p>Linux is a registered trademark of Linus Torvalds and its use is\ngoverned by the Linux Trademark Institute. Please consult the following\npage for further information:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.linuxfoundation.org\/trademark-usage\/\">Trademark Usage<\/a><\/li>\n<\/ul>\n<p>The Tux penguin logo was created by Larry Ewing using Gimp software. It\nis free to use, including commercially, as long as you give Larry Ewing\nproper credit (&quot;if someone asks&quot;). For any other permissions, please\nreach out to Mr. Larry Ewing directly.<\/p>\n<\/div>\n<div class=\"section\" id=\"what-does-stable-eol-and-longterm-mean\">\n<h2>What does &quot;stable\/EOL&quot; and &quot;longterm&quot; mean?<\/h2>\n<p>As kernels move from the &quot;mainline&quot; into the &quot;stable&quot; category, two\nthings can happen:<\/p>\n<ol class=\"arabic simple\">\n<li>They can reach &quot;End of Life&quot; after a few bugfix revisions, which\nmeans that kernel maintainers will release no more bugfixes for this\nkernel version, or<\/li>\n<li>They can be put into &quot;longterm&quot; maintenance, which means that\nmaintainers will provide bugfixes for this kernel revision for a\nmuch longer period of time.<\/li>\n<\/ol>\n<p>If the kernel version you are using is marked &quot;EOL,&quot; you should consider\nupgrading to the next major version as there will be no more bugfixes\nprovided for the kernel version you are using.<\/p>\n<p>Please check the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.html\">Releases<\/a> page for more info.<\/p>\n<\/div>\n<div class=\"section\" id=\"why-is-an-lts-kernel-marked-as-stable-on-the-front-page\">\n<h2>Why is an LTS kernel marked as &quot;stable&quot; on the front page?<\/h2>\n<p>Long-term support (&quot;LTS&quot;) kernels announced on the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.html\">Releases<\/a> page will\nbe marked as &quot;stable&quot; on the front page if there are no other current\nstable kernel releases. This is done to avoid breaking automated parsers\nmonitoring kernel.org with an expectation that there will always be a\nkernel release marked as &quot;stable.&quot;<\/p>\n<\/div>\n<div class=\"section\" id=\"linus-has-tagged-a-new-release-but-it-s-not-listed-on-the-front-page\">\n<h2>Linus has tagged a new release, but it's not listed on the front page!<\/h2>\n<p>Linus Torvalds PGP-signs git repository tags for all new mainline kernel\nreleases, however a separate set of PGP signatures needs to be generated\nby the stable release team in order to create downloadable tarballs. Due\nto timezone differences between Linus and the members of the stable\nteam, there is usually a delay of several hours between when the new\nmainline release is tagged and when PGP-signed tarballs become\navailable. The front page is updated once that process is completed.<\/p>\n<\/div>\n<div class=\"section\" id=\"is-there-an-rss-feed-for-the-latest-kernel-version\">\n<h2>Is there an RSS feed for the latest kernel version?<\/h2>\n<p>Yes, and you can find it at <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/feeds\/kdist.xml\">https:\/\/www.kernel.org\/feeds\/kdist.xml<\/a>.<\/p>\n<p>We also publish a .json file with the latest release information, which\nyou can pull from here: <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.json\">https:\/\/www.kernel.org\/releases.json<\/a>.<\/p>\n<\/div>\n<div class=\"section\" id=\"where-can-i-find-kernel-3-10-0-1160-45-1-foo\">\n<h2>Where can I find kernel 3.10.0-1160.45.1.foo?<\/h2>\n<p>Kernel versions that have a dash in them are packaged by distributions\nand are often extensively modified. Please contact the relevant\ndistribution to obtain the exact kernel source.<\/p>\n<p>See the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.html\">Releases<\/a> page for more info on distribution kernels.<\/p>\n<\/div>\n<div class=\"section\" id=\"how-do-i-report-a-problem-with-the-kernel\">\n<h2>How do I report a problem with the kernel?<\/h2>\n<p>If you are running a kernel that came with your Linux distribution, then\nthe right place to start is by reporting the problem through your\ndistribution support channels. Here are a few popular choices:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/help.ubuntu.com\/stable\/ubuntu-help\/report-ubuntu-bug.html.en\">Ubuntu<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/docs.fedoraproject.org\/en-US\/quick-docs\/howto-file-a-bug\/\">Fedora Project<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/bugs.archlinux.org\/\">Arch Linux<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/projects.linuxmint.com\/reporting-an-issue.html\">Linux Mint<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/www.debian.org\/Bugs\/Reporting\">Debian GNU\/Linux<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/bugzilla.redhat.com\/\">Red Hat<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/bugzilla.opensuse.org\/\">OpenSUSE<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/bugzilla.suse.com\/\">SUSE<\/a><\/li>\n<\/ul>\n<p>If you are sure that the problem is with the upstream kernel, please\nrefer to the following document that describes how to report bugs and\nregressions to the developers:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/docs.kernel.org\/admin-guide\/reporting-issues.html\">Reporting issues<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"section\" id=\"how-do-i-get-involved-with-linux-kernel-development\">\n<h2>How do I get involved with Linux Kernel development?<\/h2>\n<p>A good place to start is the <a class=\"reference external\" href=\"http:\/\/kernelnewbies.org\/\">Kernel Newbies<\/a> website.<\/p>\n<\/div>\n<div class=\"section\" id=\"can-i-get-an-account-on-kernel-org\">\n<h2>Can I get an account on kernel.org?<\/h2>\n<p>Kernel.org accounts are usually reserved for subsystem maintainers or\nhigh-profile developers. It is absolutely not necessary to have an\naccount on kernel.org to contribute to the development of the Linux\nkernel, unless you submit pull requests directly to Linus Torvalds.<\/p>\n<p>If you are listed in the MAINTAINERS file or have reasons to believe you\nshould have an account on kernel.org because of the amount of your\ncontributions, please refer to the <a class=\"reference external\" href=\"https:\/\/korg.docs.kernel.org\/accounts.html\">accounts page<\/a> for the\nprocedure to follow.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"FAQ"}}},{"title":"Contacts","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/contact.html","rel":"alternate"}},"published":"2024-08-06T19:40:29+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2024-08-06:\/contact.html","summary":"<p>Email is the only reliable way of contacting Kernel.org administrators.<\/p>\n<div class=\"section\" id=\"general-contacts\">\n<h2>General contacts<\/h2>\n<dl class=\"docutils\">\n<dt><a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>:<\/dt>\n<dd>All questions about kernel.org infrastructure.<\/dd>\n<\/dl>\n<p><strong>Please do not send general Linux questions or bug reports to these\naddresses. We do not have the resources to reply to them.<\/strong><\/p>\n<p>Please try the following sites \u2026<\/p><\/div>","content":"<p>Email is the only reliable way of contacting Kernel.org administrators.<\/p>\n<div class=\"section\" id=\"general-contacts\">\n<h2>General contacts<\/h2>\n<dl class=\"docutils\">\n<dt><a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>:<\/dt>\n<dd>All questions about kernel.org infrastructure.<\/dd>\n<\/dl>\n<p><strong>Please do not send general Linux questions or bug reports to these\naddresses. We do not have the resources to reply to them.<\/strong><\/p>\n<p>Please try the following sites for general Linux help:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/superuser.com\/\">https:\/\/superuser.com\/<\/a> - for computer enthusiasts and power users<\/li>\n<li><a class=\"reference external\" href=\"https:\/\/serverfault.com\/\">https:\/\/serverfault.com\/<\/a> - for systems administrators<\/li>\n<li><a class=\"reference external\" href=\"https:\/\/askubuntu.com\/\">https:\/\/askubuntu.com\/<\/a> - for users of Ubuntu Linux<\/li>\n<\/ul>\n<p>Linux Foundation also offers training opportunities if you are\ninterested in learning more about Linux, want to become a more\nproficient Linux systems administrator, or want to know more about how\nLinux can help your company succeed.<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/training.linuxfoundation.org\/\">https:\/\/training.linuxfoundation.org\/<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"section\" id=\"mailing-address\">\n<h2>Mailing address<\/h2>\n<p>Please send any mail correspondence to the Linux Foundation:<\/p>\n<blockquote>\n<div class=\"line-block\">\n<div class=\"line\">The Linux Foundation<\/div>\n<div class=\"line\">1 Letterman Drive<\/div>\n<div class=\"line\">Building D, Suite D4700<\/div>\n<div class=\"line\">San Francisco, CA 94129<\/div>\n<div class=\"line\">Phone\/Fax: +1 415 723 9709<\/div>\n<\/div>\n<\/blockquote>\n<\/div>\n","category":{"@attributes":{"term":"Contact us"}}},{"title":"Linux.dev mailing list service","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/lists-linux-dev.html","rel":"alternate"}},"published":"2021-03-15T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2021-03-15:\/lists-linux-dev.html","summary":"<p>We are pleased to announce the availability of a new mailing list\nservice running under the new <a class=\"reference external\" href=\"https:\/\/lists.linux.dev\">lists.linux.dev<\/a> domain. The goal of this deployment is to\noffer a subscription service that:<\/p>\n<ul class=\"simple\">\n<li>prioritizes mail delivery to public-inbox archives available\nvia <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\">lore.kernel.org<\/a><\/li>\n<li>conforms to DMARC requirements to ensure \u2026<\/li><\/ul>","content":"<p>We are pleased to announce the availability of a new mailing list\nservice running under the new <a class=\"reference external\" href=\"https:\/\/lists.linux.dev\">lists.linux.dev<\/a> domain. The goal of this deployment is to\noffer a subscription service that:<\/p>\n<ul class=\"simple\">\n<li>prioritizes mail delivery to public-inbox archives available\nvia <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\">lore.kernel.org<\/a><\/li>\n<li>conforms to DMARC requirements to ensure subscriber delivery<\/li>\n<li>makes minimal changes to email headers and no changes to the message\nbody content for the purposes of preserving patch attestation<\/li>\n<\/ul>\n<p>If you would like to host a Linux development mailing list on this\nplatform, please see further details on the <a class=\"reference external\" href=\"https:\/\/subspace.kernel.org\">subspace.kernel.org<\/a> site.<\/p>\n<div class=\"section\" id=\"why-another-mailing-list-service\">\n<h2>Why another mailing list service?<\/h2>\n<p>Linux development started in 1991 and has been ongoing for the past 30\nyears at an ever-increasing pace. Many popular code collaboration\nplatforms have risen throughout these three decades -- and while some of\nthem are still around, many others have shut down and disappeared\nwithout offering any way to preserve the history of the projects they\nused to host.<\/p>\n<p>Development via mailed-in patches remains the only widely used mechanism\nfor code collaboration that does not rely on centralized infrastructure\nmaintained by any single entity. The Linux developer community sees\ntransparency, independence and decentralization as core guiding\nprinciples behind Linux development, so it has deliberately chosen to\ncontinue using email for all its past and ongoing collaboration efforts.<\/p>\n<\/div>\n<div class=\"section\" id=\"what-about-vger-kernel-org\">\n<h2>What about vger.kernel.org?<\/h2>\n<p>The infrastructure behind lists.linux.dev supports multiple domains, so\nall mailing lists hosted on vger.kernel.org will be carefully migrated\nto the same platform while preserving current addresses, subscribers,\nand list ids. The only thing that will noticeably change is the\nprocedure to subscribe and unsubscribe from individual lists. As\nmajordomo is no longer maintained, we will instead switch to using\nseparate subscribe\/unsusbscribe addresses per each list.<\/p>\n<p>There are no firm ETAs for this migration, but if you are currently\nsubscribed to any mailing list hosted on vger.kernel.org, you will\nreceive a message when the migration date is approaching.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Git mirror available in Beijing","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/beijing-git-mirror.html","rel":"alternate"}},"published":"2020-01-11T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2020-01-11:\/beijing-git-mirror.html","summary":"<p>If you are a developer located around Beijing, or if your connection to\nBeijing is faster and more reliable than to locations outside of China,\nthen you may benefit from the new git.kernel.org mirror kindly provided\nby <a class=\"reference external\" href=\"https:\/\/www.codeaurora.org\/\">Code Aurora Forum<\/a> at <a class=\"reference external\" href=\"https:\/\/kernel.source.codeaurora.cn\/\">https:\/\/kernel.source.codeaurora.cn\/<\/a>. This is \u2026<\/p>","content":"<p>If you are a developer located around Beijing, or if your connection to\nBeijing is faster and more reliable than to locations outside of China,\nthen you may benefit from the new git.kernel.org mirror kindly provided\nby <a class=\"reference external\" href=\"https:\/\/www.codeaurora.org\/\">Code Aurora Forum<\/a> at <a class=\"reference external\" href=\"https:\/\/kernel.source.codeaurora.cn\/\">https:\/\/kernel.source.codeaurora.cn\/<\/a>. This is\na full mirror that is updated just as frequently as other git.kernel.org\nnodes (in fact, it is managed by the same team as the rest of kernel.org\ninfrastructure, since CAF is part of Linux Foundation IT projects).<\/p>\n<p>To start using the Beijing mirror, simply clone from that location or\nadd a separate remote to your existing checkouts, e.g.:<\/p>\n<pre class=\"literal-block\">\ngit remote add beijing git:\/\/kernel.source.codeaurora.cn\/pub\/scm\/...\/linux.git\ngit fetch beijing master\n<\/pre>\n<p>You may also use <a class=\"reference external\" href=\"http:\/\/\">http:\/\/<\/a> and <a class=\"reference external\" href=\"https:\/\/\">https:\/\/<\/a> protocols if that makes it easier\nbehind corporate firewalls.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Code of Conduct","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/code-of-conduct.html","rel":"alternate"}},"published":"2020-01-02T00:00:00+00:00","updated":"2025-12-03T11:56:10+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2020-01-02:\/code-of-conduct.html","summary":"<p>The Linux kernel community operates a <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct.html\">Code of Conduct<\/a> based on the\n<a class=\"reference external\" href=\"https:\/\/www.contributor-covenant.org\/version\/1\/4\/code-of-conduct.html\">Contributor Covenant Code of Conduct<\/a> with a <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct-interpretation.html\">Linux Kernel Contributor Covenant Code of Conduct Interpretation<\/a>.<\/p>\n<div class=\"section\" id=\"code-of-conduct-committee\">\n<h2>Code of Conduct Committee<\/h2>\n<p>The Linux kernel Code of Conduct Committee is currently made up of the\nfollowing people:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Kristen Accardi &lt;<a class=\"reference external\" href=\"mailto:kristen.c.accardi&#64;intel.com\">kristen.c \u2026<\/a><\/li><\/ul><\/blockquote><\/div>","content":"<p>The Linux kernel community operates a <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct.html\">Code of Conduct<\/a> based on the\n<a class=\"reference external\" href=\"https:\/\/www.contributor-covenant.org\/version\/1\/4\/code-of-conduct.html\">Contributor Covenant Code of Conduct<\/a> with a <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct-interpretation.html\">Linux Kernel Contributor Covenant Code of Conduct Interpretation<\/a>.<\/p>\n<div class=\"section\" id=\"code-of-conduct-committee\">\n<h2>Code of Conduct Committee<\/h2>\n<p>The Linux kernel Code of Conduct Committee is currently made up of the\nfollowing people:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Kristen Accardi &lt;<a class=\"reference external\" href=\"mailto:kristen.c.accardi&#64;intel.com\">kristen.c.accardi&#64;intel.com<\/a>&gt;<\/li>\n<li>Shuah Khan &lt;<a class=\"reference external\" href=\"mailto:skhan&#64;linuxfoundation.org\">skhan&#64;linuxfoundation.org<\/a>&gt;<\/li>\n<li>Greg Kroah-Hartman &lt;<a class=\"reference external\" href=\"mailto:gregkh&#64;linuxfoundation.org\">gregkh&#64;linuxfoundation.org<\/a>&gt;<\/li>\n<li>Joanna Lee &lt;<a class=\"reference external\" href=\"mailto:jlee&#64;linuxfoundation.org\">jlee&#64;linuxfoundation.org<\/a>&gt;<\/li>\n<\/ul>\n<\/blockquote>\n<p>Committee members can be reached all at once by writing to\n&lt;<a class=\"reference external\" href=\"mailto:conduct&#64;kernel.org\">conduct&#64;kernel.org<\/a>&gt;.<\/p>\n<\/div>\n<div class=\"section\" id=\"committee-reports\">\n<h2>Committee Reports<\/h2>\n<p>We would like to thank the Linux kernel community members who have supported\nthe adoption of the Code of Conduct and who continue to uphold the professional\nstandards of our community. If you have any questions about these reports,\nplease write to &lt;<a class=\"reference external\" href=\"mailto:conduct&#64;kernel.org\">conduct&#64;kernel.org<\/a>&gt;.<\/p>\n<div class=\"section\" id=\"march-2025\">\n<h3>March 2025<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/all\/2025043021-reprogram-gloss-acb5&#64;gregkh\/\">https:\/\/lore.kernel.org\/all\/2025043021-reprogram-gloss-acb5&#64;gregkh\/<\/a><\/p>\n<p>Updates to the Code of Conduct documents:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>The Code of Conduct documentation has been updated to clearly\noutline the enforcement when Unacceptable Behavior Code\nof Conduct Violations take place, and outline the Technical\nAdvisory Board's role in approving remedial actions recommended\nby the Code of Conduct Committee.<\/li>\n<\/ul>\n<\/blockquote>\n<dl class=\"docutils\">\n<dt>Reference:<\/dt>\n<dd><a class=\"reference external\" href=\"https:\/\/docs.kernel.org\/process\/code-of-conduct-interpretation.html#code-of-conduct-interpretation\">https:\/\/docs.kernel.org\/process\/code-of-conduct-interpretation.html#code-of-conduct-interpretation<\/a><\/dd>\n<\/dl>\n<p>In the period of April 1, 2024 through March 31, 2025, the Code of\nConduct Committee received the following reports:<\/p>\n<p>Reports received: 17<\/p>\n<p>Development process related reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching on maintainers' right to accept or reject\npatches. Clarifying the expectations that developers can't demand\ntheir patches to be reviewed and\/or accepted by the community.\nThese reports were about a developer demanding their patch to be\naccepted even after repeated attempts by maintainers advising the\ndevelopers to understand the development process.<\/li>\n<\/ul>\n<\/blockquote>\n<p>Code of Conduct scope and enforcement related reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching on the role and scope of the Code of Conduct.\nSeveral reports from people outside the kernel community reporting\npast incidents before the Code of Conduct was adopted. Reports\nresolved clarifying the scope and validity of reports about past\nincidents before adopting the Code of Conduct.<\/li>\n<\/ul>\n<\/blockquote>\n<p>Insensitive comments reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching on the role and scope of the Code of Conduct.\nReports about Office of Foreign Assets Control (OFAC) related actions\nand offhand comments in technical discussions that do not rise to the\nlevel of violations.<\/li>\n<\/ul>\n<\/blockquote>\n<p>Unacceptable behavior or comments in email: 6<\/p>\n<ul>\n<li><p class=\"first\">4 reports resolved instituting remedial measures on two individuals\nrestricting their participation in development process.<\/p>\n<dl class=\"docutils\">\n<dt>-- Rejecting pull requests from an individual for a full release cycle.<\/dt>\n<dd><p class=\"first last\">Reference: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/all\/6740fc3aabec0_5eb129497&#64;dwillia2-xfh.jf.intel.com.notmuch\/\">https:\/\/lore.kernel.org\/all\/6740fc3aabec0_5eb129497&#64;dwillia2-xfh.jf.intel.com.notmuch\/<\/a><\/p>\n<\/dd>\n<dt>-- Banning an individual for 3 months from Linux kernel mailing lists.<\/dt>\n<dd><p class=\"first last\">Reference: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/all\/67cf7499597e9_1198729450&#64;dwillia2-xfh.jf.intel.com.notmuch\/\">https:\/\/lore.kernel.org\/all\/67cf7499597e9_1198729450&#64;dwillia2-xfh.jf.intel.com.notmuch\/<\/a><\/p>\n<\/dd>\n<\/dl>\n<\/li>\n<li><p class=\"first\">Others\n- Resolved with the individuals making amends for their behaviors.<\/p>\n<\/li>\n<\/ul>\n<p>We would like to thank the Linux kernel community members who have\nsupported the adoption of the Code of Conduct and who continue to\nuphold the professional standards of our community. If you have\nquestions about this report, please write to &lt;<a class=\"reference external\" href=\"mailto:conduct&#64;kernel.org\">conduct&#64;kernel.org<\/a>&gt;.<\/p>\n<\/div>\n<div class=\"section\" id=\"march-2024\">\n<h3>March 2024<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/355aee5f-13ce-4e20-9ce8-e5bcddd14bc2&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/355aee5f-13ce-4e20-9ce8-e5bcddd14bc2&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of October 1, 2023 through March 31, 2024, the Code of\nConduct Committee received the following reports:<\/p>\n<ul class=\"simple\">\n<li>Unprofessional behavior or comments in email: 2<\/li>\n<\/ul>\n<p>The result of the investigation:<\/p>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the role of Code of Conduct\nconduct on conversations that don't go against the CoC.<\/li>\n<li>Education and coaching the individuals on the impact of making\nunprofessional comments which could be misunderstood leading\nto negative impressions about the community.<\/li>\n<\/ul>\n<p>The reports were about the offhand comments made while rejecting\nthe code which are not violations of the Code of Conduct<\/p>\n<p>Unacceptable behavior or comments on a private invitee only chat\nchannel: 1<\/p>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the role of Code of Conduct\nconduct on conversations that occur on a private chat channel.<\/li>\n<\/ul>\n<p>We would like to thank the Linux kernel community members who have\nsupported the adoption of the Code of Conduct and who continue to\nuphold the professional standards of our community. If you have\nquestions about this report, please write to &lt;<a class=\"reference external\" href=\"mailto:conduct&#64;kernel.org\">conduct&#64;kernel.org<\/a>&gt;.<\/p>\n<\/div>\n<div class=\"section\" id=\"september-2023\">\n<h3>September 2023<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/3351be6b-854e-479d-832c-83cb8829c010&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/3351be6b-854e-479d-832c-83cb8829c010&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of April 1, 2023 through September 30, 2023, the Code of\nConduct Committee received the following reports:<\/p>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 4<\/li>\n<\/ul>\n<p>The result of the investigation:<\/p>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the Code of Conduct conduct related\nto normal review and patch acceptance process: 3<\/li>\n<li>Clarification on the Code of Conduct conduct related to maintainer\nrights and responsibility to reject code: 1<\/li>\n<\/ul>\n<p>The reports were about the discussion during the patch review and\ndecisions made in rejecting code and these actions are not viewed as\nviolations of the Code of Conduct.<\/p>\n<p>Please see the excerpt from the Responsibilities section in the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct-interpretation.html\">Linux\nKernel Contributor Covenant Code of Conduct Interpretation<\/a> document:<\/p>\n<pre class=\"literal-block\">\nsetting expertise expectations, making decisions and rejecting unsuitable\ncontributions are not viewed as a violation of the Code of Conduct.\n<\/pre>\n<\/div>\n<div class=\"section\" id=\"march-2023\">\n<h3>March 2023<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/557ef895-ad2d-eff9-7cb8-70dbcf41adea&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/557ef895-ad2d-eff9-7cb8-70dbcf41adea&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of October 1, 2022 through March 31, 2023, the Code of\nConduct Committee received the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 6<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the Code of Conduct conduct related\nto normal review and patch acceptance process: 1<\/li>\n<li>Clarification on the Code of Conduct conduct related to maintainer\nrights and responsibility to reject code: 5<\/li>\n<\/ul>\n<\/blockquote>\n<p>The reports were about the decisions made in rejecting code and these\nactions are not viewed as violations of the Code of Conduct.<\/p>\n<p>Please see the excerpt from the Responsibilities section in the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/code-of-conduct-interpretation.html\">Linux\nKernel Contributor Covenant Code of Conduct Interpretation<\/a> document:<\/p>\n<pre class=\"literal-block\">\nsetting expertise expectations, making decisions and rejecting unsuitable\ncontributions are not viewed as a violation of the Code of Conduct.\n<\/pre>\n<\/div>\n<div class=\"section\" id=\"september-2022\">\n<h3>September 2022<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/57a492fb-928b-9e0a-5f0e-dc95ef599309&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/57a492fb-928b-9e0a-5f0e-dc95ef599309&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of April 1, 2022 through September 30, 2022, the Code of\nConduct Committee received the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 1<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Resolved with a public apology from the violator with a commitment\nfrom them to abide by the Code of Conduct in the future.<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<\/div>\n<div class=\"section\" id=\"march-2022\">\n<h2>March 2022<\/h2>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/4401af50-083d-0239-6b7f-3454c8d69fec&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/4401af50-083d-0239-6b7f-3454c8d69fec&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of October 1, 2021 through March 31, 2022, the Code of\nConduct Committee received the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 2<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the Code of Conduct conduct\nrelated to normal review process: 2<\/li>\n<\/ul>\n<\/blockquote>\n<div class=\"section\" id=\"september-2021\">\n<h3>September 2021<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/e81f0726-5f8f-f10f-d926-a9126941d38e&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/e81f0726-5f8f-f10f-d926-a9126941d38e&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of May 1, 2021 through September 30, 2021, the Code of\nConduct Committee received the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 1<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching clarifying the Code of Conduct conduct\nrelated to normal review process: 1<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"april-2021\">\n<h3>April 2021<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/448b06e4-41fc-26df-a862-c3ba2f70b6b3&#64;linuxfoundation.org\">https:\/\/lore.kernel.org\/r\/448b06e4-41fc-26df-a862-c3ba2f70b6b3&#64;linuxfoundation.org<\/a><\/p>\n<p>In the period of November 1, 2020 through April 30, 2021 the Code of\nConduct Committee received the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email (3rd party): 4<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching: 1<\/li>\n<li>Public response to call attention to the behavior and request\ncorrection with consequence of ban if behavior persists: 1<\/li>\n<li>Public response to attention to the behavior and request correction: 1<\/li>\n<li>Clarification on the Code of Conduct conduct related to maintainer\nrights and responsibility to reject code: 1<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"october-2020\">\n<h3>October 2020<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/lkml\/20201105083002.GA3429143&#64;kroah.com\/\">https:\/\/lore.kernel.org\/lkml\/20201105083002.GA3429143&#64;kroah.com\/<\/a><\/p>\n<p>In the period of January 1, 2020 through October 31, 2020 the Committee\nreceived the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Unacceptable behavior or comments in email: 1<\/li>\n<li>Unacceptable comments in github repo by non-community members: 1<\/li>\n<li>Unacceptable comments toward a company: 1<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching: 1<\/li>\n<li>Locking of github repo for any comments: 1<\/li>\n<li>Clarification that the Code of Conduct covers conduct related to individual developers only: 1<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"december-2019\">\n<h3>December 2019<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/lkml\/20200103105614.GC1047442&#64;kroah.com\/\">https:\/\/lore.kernel.org\/lkml\/20200103105614.GC1047442&#64;kroah.com\/<\/a><\/p>\n<p>In the period of December 1, 2019 through December 30, 2019 the Committee\nreceived the following report:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Insulting behavior in email: 1<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigation:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching: 1<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"august-to-november-2019\">\n<h3>August to November 2019<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/lkml\/20191218090054.GA5120&#64;kroah.com\/\">https:\/\/lore.kernel.org\/lkml\/20191218090054.GA5120&#64;kroah.com\/<\/a><\/p>\n<p>In the period of August 1, 2019 through November 31, 2019, the Committee\nreceived no reports.<\/p>\n<\/div>\n<div class=\"section\" id=\"september-2018-to-july-2019\">\n<h3>September 2018 to July 2019<\/h3>\n<p>Archival copy: <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/lkml\/20190810120700.GA7360&#64;kroah.com\/\">https:\/\/lore.kernel.org\/lkml\/20190810120700.GA7360&#64;kroah.com\/<\/a><\/p>\n<p>In the period of September 15, 2018 through July 31, 2019, the Committee\nreceived the following reports:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Inappropriate language in the kernel source: 1<\/li>\n<li>Insulting behavior in email: 3<\/li>\n<\/ul>\n<\/blockquote>\n<p>The result of the investigations:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li>Education and coaching: 4<\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<\/div>\n","category":{"@attributes":{"term":"About"}}},{"title":"Get notifications for your patches","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/get-notifications-for-your-patches.html","rel":"alternate"}},"published":"2018-12-13T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2018-12-13:\/get-notifications-for-your-patches.html","summary":"<p>We are trialing out a new feature that can send you a notification when\nthe patches you send to the LKML are applied to linux-next or to the\nmainline git trees. If you are interested in trying it out, here are the\ndetails:<\/p>\n<ul class=\"simple\">\n<li>The patches must be sent to the \u2026<\/li><\/ul>","content":"<p>We are trialing out a new feature that can send you a notification when\nthe patches you send to the LKML are applied to linux-next or to the\nmainline git trees. If you are interested in trying it out, here are the\ndetails:<\/p>\n<ul class=\"simple\">\n<li>The patches must be sent to the LKML (<a class=\"reference external\" href=\"mailto:linux-kernel&#64;vger.kernel.org\">linux-kernel&#64;vger.kernel.org<\/a>).<\/li>\n<li>One of the cc's must be <a class=\"reference external\" href=\"mailto:notify&#64;kernel.org\">notify&#64;kernel.org<\/a> (Bcc will not work).<\/li>\n<li>Alternatively, there should be a &quot;X-Patchwork-Bot: notify&quot; email header.<\/li>\n<li>The patches must not have been modified by the maintainer(s).<\/li>\n<li>All patches in the series must have been applied, not just some of them.<\/li>\n<\/ul>\n<p>The last two points are important, because if there are changes between\nthe content of the patch as it was first sent to the mailing list, and\nhow it looks like by the time it is applied to linux-next or mainline,\nthe bot will not be able to recognize it as the same patch. Similarly,\nfor series of multiple patches, the bot must be able to successfully\nmatch all patches in the series in order for the notification to go out.<\/p>\n<p>If you are using <tt class=\"docutils literal\"><span class=\"pre\">git-format-patch<\/span><\/tt>, it is best to add the special\nheader instead of using the Cc notification address, so as to avoid any\nunnecessary email traffic:<\/p>\n<pre class=\"literal-block\">\n--add-header=&quot;X-Patchwork-Bot: notify&quot;\n<\/pre>\n<p>You should receive one notification email per each patch series, so if\nyou send a series of 20 patches, you will get a single email in the form\nof a reply to the cover letter, or to the first patch in the series. The\nnotification will be sent directly to you, ignoring any other addresses\nin the Cc field.<\/p>\n<p>The bot uses our <a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/patchwork\">LKML patchwork instance<\/a> to perform matching and\ntracking, and the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/mricon\/korg-helpers.git\/tree\/git-patchwork-bot.py\">source code<\/a> for the bot is also available if you\nwould like to suggest improvements.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"List archives on lore.kernel.org","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/lore.html","rel":"alternate"}},"published":"2018-12-12T00:00:00+00:00","updated":"2025-08-06T04:14:42+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2018-12-12:\/lore.html","summary":"<p>You may access the archives of many Linux development mailing lists on\n<a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/\">lore.kernel.org<\/a>. Most of them include a full archive of messages going\nback several decades.<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/\">listing of currently hosted archives<\/a><\/li>\n<\/ul>\n<p>If you would like to suggest another kernel development mailing list to\nbe included in this list \u2026<\/p>","content":"<p>You may access the archives of many Linux development mailing lists on\n<a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/\">lore.kernel.org<\/a>. Most of them include a full archive of messages going\nback several decades.<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/\">listing of currently hosted archives<\/a><\/li>\n<\/ul>\n<p>If you would like to suggest another kernel development mailing list to\nbe included in this list, please follow the instructions on the\nfollowing wiki page:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/korg.wiki.kernel.org\/userdoc\/lore\">Adding list archives to lore.kernel.org<\/a><\/li>\n<\/ul>\n<div class=\"section\" id=\"archiving-software\">\n<h2>Archiving software<\/h2>\n<p>The software managing the archive is called <a class=\"reference external\" href=\"https:\/\/public-inbox.org\/design_notes.html\">Public Inbox<\/a> and offers\nthe following features:<\/p>\n<ul class=\"simple\">\n<li>Fast, searchable web archives<\/li>\n<li>Atom feeds per list or per individual thread<\/li>\n<li>Downloadable mbox archives to make replying easy<\/li>\n<li>Git-backed archival mechanism you can clone and pull<\/li>\n<li>Read-only nntp gateway<\/li>\n<\/ul>\n<p>We collected many list archives going as far back as 1998, and they are\nnow all available to anyone via a simple git clone. We would like to\nextend our thanks to everyone who helped in this effort by donating\ntheir personal archives.<\/p>\n<\/div>\n<div class=\"section\" id=\"obtaining-full-list-archives\">\n<h2>Obtaining full list archives<\/h2>\n<p>Git clone URLs are provided at the bottom of each page. Note, that due\nmailing list volume, list archives are sharded into multiple\nrepositories, each roughly 1GB in size. In addition to cloning from\nlore.kernel.org, you may also access these repositories on\n<a class=\"reference external\" href=\"https:\/\/erol.kernel.org\/\">erol.kernel.org<\/a>.<\/p>\n<div class=\"section\" id=\"mirroring\">\n<h3>Mirroring<\/h3>\n<p>You can continuously mirror the entire mailing list archive collection\nby using the <a class=\"reference external\" href=\"https:\/\/github.com\/mricon\/grokmirror\">grokmirror<\/a> tool. The following repos.conf file should get\nyou all you need:<\/p>\n<pre class=\"literal-block\">\n[lore.kernel.org]\nsite = https:\/\/lore.kernel.org\nmanifest = https:\/\/lore.kernel.org\/manifest.js.gz\ntoplevel = \/path\/to\/your\/local\/folder\nmymanifest = \/path\/to\/your\/local\/folder\/manifest.js.gz\npull_threads = 4\n<\/pre>\n<p>Please note, that you will require at least 20+ GB of local storage. The\nmirroring process only replicates the git repositories themselves -- if\nyou want to use public-inbox with them, you will need to run\n&quot;<tt class=\"docutils literal\"><span class=\"pre\">public-inbox-init<\/span><\/tt>&quot; and &quot;<tt class=\"docutils literal\"><span class=\"pre\">public-inbox-index<\/span><\/tt>&quot; to create the\ndatabase files required for public-inbox operation.<\/p>\n<\/div>\n<\/div>\n<div class=\"section\" id=\"linking-to-list-discussions-from-commits\">\n<h2>Linking to list discussions from commits<\/h2>\n<p>If you need to reference a mailing list discussion inside code comments\nor in a git commit message, please use the &quot;permalink&quot; URL provided by\npublic-inbox. It is available in the headers of each displayed message\nor thread discussion. Alternatively, you can use a generic message-id\nredirector in the form:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/lore.kernel.org\/r\/message&#64;id\">https:\/\/lore.kernel.org\/r\/message&#64;id<\/a><\/li>\n<\/ul>\n<p>That should display the message regardless in which mailing list archive\nit's stored.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Minor changes to kernel tarball releases","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/minor-changes-to-tarball-release-format.html","rel":"alternate"}},"published":"2018-07-27T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2018-07-27:\/minor-changes-to-tarball-release-format.html","summary":"<p>We'd like to announce several small changes to the way Linux tarballs\nare produced.<\/p>\n<div class=\"section\" id=\"mainline-release-tarball-signatures\">\n<h2>Mainline release tarball signatures<\/h2>\n<p>Starting with the 4.18 final release, all mainline tarball PGP\nsignatures will be made by Greg Kroah-Hartman instead of Linus Torvalds.\nThe main goal behind this change is to simplify the \u2026<\/p><\/div>","content":"<p>We'd like to announce several small changes to the way Linux tarballs\nare produced.<\/p>\n<div class=\"section\" id=\"mainline-release-tarball-signatures\">\n<h2>Mainline release tarball signatures<\/h2>\n<p>Starting with the 4.18 final release, all mainline tarball PGP\nsignatures will be made by Greg Kroah-Hartman instead of Linus Torvalds.\nThe main goal behind this change is to simplify the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/signature.html\">verification\nprocess<\/a> and make all kernel tarball releases available for download on\nkernel.org be signed by the same developer.<\/p>\n<p>Linus Torvalds will continue to PGP-sign all tags in the mainline\ngit repository. They can be verified using the <tt class=\"docutils literal\">git <span class=\"pre\">verify-tag<\/span><\/tt>\ncommand.<\/p>\n<\/div>\n<div class=\"section\" id=\"sunsetting-gz-tarball-generation\">\n<h2>Sunsetting .gz tarball generation<\/h2>\n<p>We stopped creating .bz2 copies of tarball releases 5 years ago, and the\ntime has come to stop producing .gz duplicate copies of all our content\nas well, as XZ tools and libraries are now available on all major\nplatforms. Starting September 1st, 2018, all tarball releases available\nvia <tt class=\"docutils literal\">\/pub<\/tt> download locations will only be available in XZ-compressed\nformat.<\/p>\n<p>If you absolutely must have .gz compressed tarballs, you may obtain them\nfrom git.kernel.org by following snapshot download links in the\nappropriate repository view.<\/p>\n<\/div>\n<div class=\"section\" id=\"no-future-pgp-signatures-on-patches-and-changelogs\">\n<h2>No future PGP signatures on patches and changelogs<\/h2>\n<p>For legacy purposes, we will continue to provide pre-generated\nchangelogs and patches (both to the previous mainline and incremental\npatches to previous stable). However, from now on they will be generated\nby automated processes and will no longer carry detached PGP signatures.\nIf you require cryptographically verified patches, please generate them\ndirectly from the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/stable\/linux.git\">stable git repository<\/a> after verifying the PGP\nsignatures on the tags using <tt class=\"docutils literal\">git <span class=\"pre\">verify-tag<\/span><\/tt>.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Best way to do linux clones for your CI","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/best-way-to-do-linux-clones-for-your-ci.html","rel":"alternate"}},"published":"2018-07-25T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2018-07-25:\/best-way-to-do-linux-clones-for-your-ci.html","summary":"<p>If you are in charge of CI infrastructure that needs to perform frequent\nfull clones of kernel trees from git.kernel.org, we strongly recommend\nthat you use the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/cloning-linux-from-a-bundle.html\">git bundles we provide<\/a> instead of performing a full\nclone directly from git repositories.<\/p>\n<p>It is better for you, because downloading \u2026<\/p>","content":"<p>If you are in charge of CI infrastructure that needs to perform frequent\nfull clones of kernel trees from git.kernel.org, we strongly recommend\nthat you use the <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/cloning-linux-from-a-bundle.html\">git bundles we provide<\/a> instead of performing a full\nclone directly from git repositories.<\/p>\n<p>It is better for you, because downloading the bundle from CDN is\nprobably going to be much faster for you than cloning from our frontends\ndue to the CDN being more local. You can even copy the bundle to a\nfileserver on your local infrastructure and save a lot of repeated\nexternal traffic.<\/p>\n<p>It is better for us, because if you first clone from the bundle, you\nonly need to fetch a handful of newer objects directly from\ngit.kernel.org frontends. This not only uses an order of magnitude less\nbandwidth, but also results in a much smaller memory footprint on our\nsystems -- git daemon needs a lot of RAM when serving full clones of\nlinux repositories.<\/p>\n<p>Here is a simple script that will help you automate the process of first\ndownloading the git bundle and then fetching the newer objects:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/mricon\/korg-helpers.git\/plain\/linux-bundle-clone\">linux-bundle-clone<\/a><\/li>\n<\/ul>\n<p>Thank you for helping us keep our systems fast and accessible to all.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Nitrokey digital tokens for kernel developers","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/nitrokey-digital-tokens-for-kernel-developers.html","rel":"alternate"}},"published":"2018-04-04T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2018-04-04:\/nitrokey-digital-tokens-for-kernel-developers.html","summary":"<p>The Linux Foundation IT team has been working to improve the code\nintegrity of git repositories hosted at kernel.org by promoting the use\nof PGP-signed git tags and commits. Doing so allows anyone to easily\nverify that git repositories have not been altered or tampered with no\nmatter from \u2026<\/p>","content":"<p>The Linux Foundation IT team has been working to improve the code\nintegrity of git repositories hosted at kernel.org by promoting the use\nof PGP-signed git tags and commits. Doing so allows anyone to easily\nverify that git repositories have not been altered or tampered with no\nmatter from which worldwide mirror they may have been cloned. If the\ndigital signature on your cloned repository matches the PGP key\nbelonging to Linus Torvalds or any other maintainer, then you can be\nassured that what you have on your computer is the exact replica of the\nkernel code without any omissions or additions.<\/p>\n<p>To help promote the use of PGP signatures in Linux kernel development,\nwe now offer a detailed guide within the kernel documentation tree:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/doc\/html\/latest\/process\/maintainer-pgp-guide.html\">Kernel Maintainer PGP Guide<\/a><\/li>\n<\/ul>\n<img alt=\"Nitrokey logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/nitrokey-logo.png\" style=\"width: 207px; height: 70px;\" \/>\n<p>Further, we are happy to announce a new special program sponsored by\n<a class=\"reference external\" href=\"https:\/\/linuxfoundation.org\/\">The Linux Foundation<\/a> in partnership with <a class=\"reference external\" href=\"https:\/\/www.nitrokey.com\/\">Nitrokey<\/a> -- the developer\nand manufacturer of smartcard-compatible digital tokens capable of\nstoring private keys and performing PGP operations on-chip. Under this\nprogram, any developer who is listed as a maintainer in the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\/tree\/MAINTAINERS\">MAINTAINERS<\/a>\nfile, or who has a kernel.org account can qualify for a free digital\ntoken to help improve the security of their PGP keys. The cost of the\ndevice, including any taxes, shipping and handling will be covered by\nThe Linux Foundation.<\/p>\n<p>To participate in this program, please access the special store front\non the Nitrokey website:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/kernel.nitrokey.com\/\">Nitrokey Start for Kernel Developers<\/a><\/li>\n<\/ul>\n<div class=\"section\" id=\"who-qualifies-for-this-program\">\n<h2>Who qualifies for this program?<\/h2>\n<p>To qualify for the program, you need to have an account at kernel.org or\nhave your email address listed in the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\/tree\/MAINTAINERS\">MAINTAINERS<\/a> file (following the\n&quot;<tt class=\"docutils literal\">M:<\/tt>&quot; heading). If you do not currently qualify but think you should,\nthe easiest course of action is to get yourself added to the MAINTAINERS\nfile or to <a class=\"reference external\" href=\"https:\/\/korg.wiki.kernel.org\/userdoc\/accounts\">apply for an account at kernel.org<\/a>.<\/p>\n<\/div>\n<div class=\"section\" id=\"which-devices-are-available-under-this-program\">\n<h2>Which devices are available under this program?<\/h2>\n<p>The program is limited to <a class=\"reference external\" href=\"https:\/\/shop.nitrokey.com\/shop\/product\/nitrokey-start-6\">Nitrokey Start<\/a> devices. There are several\nreasons why we picked this particular device among several available\noptions.<\/p>\n<p>First of all, many Linux kernel developers have a strong preference not\njust for open-source software, but for open hardware as well. Nitrokey\nis one of the few companies selling GnuPG-compatible smartcard devices\nthat provide both, since Nitrokey Start is based on Gnuk cryptographic\ntoken firmware developed by <a class=\"reference external\" href=\"https:\/\/www.fsij.org\/category\/gnuk.html\">Free Software Initiative of Japan<\/a>. It is\nalso one of the few commercially available devices that offer native\nsupport for ECC keys, which are both faster computationally than large\nRSA keys and generate smaller digital signatures. With our push to use\nmore code signing of git objects themselves, both the open nature of the\ndevice and its support for fast modern cryptography were key points in\nour evaluation.<\/p>\n<p>Additionally, Nitrokey devices (both Start and Pro models) are already\n<a class=\"reference external\" href=\"https:\/\/lwn.net\/Articles\/736231\/\">used by open-source developers<\/a> for cryptographic purposes and they\nare known to work well with Linux workstations.<\/p>\n<\/div>\n<div class=\"section\" id=\"what-is-the-benefit-of-digital-smartcard-tokens\">\n<h2>What is the benefit of digital smartcard tokens?<\/h2>\n<p>With usual GnuPG operations, the private keys are stored in the home\ndirectory where they can be stolen by malware or exposed via other\nmeans, such as poorly secured backups. Furthermore, each time a GnuPG\noperation is performed, the keys are loaded into system memory and can\nbe stolen from there using sufficiently advanced techniques (the likes\nof Meltdown and Spectre).<\/p>\n<p>A digital smartcard token like Nitrokey Start contains a cryptographic\nchip that is capable of storing private keys and performing crypto\noperations directly on the token itself. Because the key contents never\nleave the device, the operating system of the computer into which the\ntoken is plugged in is not able to retrieve the private keys themselves,\ntherefore significantly limiting the ways in which the keys can be\nleaked or stolen.<\/p>\n<\/div>\n<div class=\"section\" id=\"questions-or-problems\">\n<h2>Questions or problems?<\/h2>\n<p>If you qualify for the program, but encounter any difficulties\npurchasing the device, please contact Nitrokey at <a class=\"reference external\" href=\"mailto:shop&#64;nitrokey.com\">shop&#64;nitrokey.com<\/a>.<\/p>\n<p>For any questions about the program itself or with any other comments,\nplease reach out to <a class=\"reference external\" href=\"mailto:info&#64;linuxfoundation.org\">info&#64;linuxfoundation.org<\/a>.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Linux kernel releases PGP signatures","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/signature.html","rel":"alternate"}},"published":"2018-02-15T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2018-02-15:\/signature.html","summary":"<p>All kernel releases are cryptographically signed using OpenPGP-compliant\nsignatures. Everyone is strongly encouraged to verify the integrity of\ndownloaded kernel releases by verifying the corresponding signatures.<\/p>\n<div class=\"section\" id=\"basic-concepts\">\n<h2>Basic concepts<\/h2>\n<p>Every kernel release comes with a cryptographic signature from the\nperson making the release. This cryptographic signature allows anyone to\nverify whether \u2026<\/p><\/div>","content":"<p>All kernel releases are cryptographically signed using OpenPGP-compliant\nsignatures. Everyone is strongly encouraged to verify the integrity of\ndownloaded kernel releases by verifying the corresponding signatures.<\/p>\n<div class=\"section\" id=\"basic-concepts\">\n<h2>Basic concepts<\/h2>\n<p>Every kernel release comes with a cryptographic signature from the\nperson making the release. This cryptographic signature allows anyone to\nverify whether the files have been modified or otherwise tampered with\nafter the developer created and signed them. The signing and\nverification process uses public-key cryptography and it is next to\nimpossible to forge a PGP signature without first gaining access to the\ndeveloper's private key. If this does happen, the developers will revoke\nthe compromised key and will re-sign all their previously signed\nreleases with the new key.<\/p>\n<p>To learn more about the way PGP works, please consult <a class=\"reference external\" href=\"https:\/\/en.wikipedia.org\/wiki\/Pretty_Good_Privacy#How_PGP_encryption_works\">Wikipedia<\/a>.<\/p>\n<\/div>\n<div class=\"section\" id=\"kernel-org-web-of-trust\">\n<h2>Kernel.org web of trust<\/h2>\n<p>PGP keys used by members of kernel.org are cross-signed by other members\nof the Linux kernel development community (and, frequently, by many\nother people). If you wanted to verify the validity of any key belonging\nto a member of kernel.org, you could review the list of signatures on\ntheir public key and then make a decision whether you trust that key or\nnot. See the <a class=\"reference external\" href=\"https:\/\/en.wikipedia.org\/wiki\/Web_of_trust\">Wikipedia article<\/a> on the subject of the Web of Trust.<\/p>\n<\/div>\n<div class=\"section\" id=\"using-the-web-key-directory\">\n<h2>Using the Web Key Directory<\/h2>\n<p>If the task of maintaining your own web of trust is too daunting to you,\nyou can opt to shortcut this process by using the &quot;Trust on First Use&quot;\n(TOFU) approach and rely on the kernel.org Web Key Directory (WKD).<\/p>\n<p>To import keys belonging to many kernel developers, you can use the\nfollowing command:<\/p>\n<pre class=\"literal-block\">\n$ gpg2 --locate-keys [username]&#64;kernel.org\n<\/pre>\n<p>For example, to import keys belonging to Linus Torvalds and Greg\nKroah-Hartman, you would use:<\/p>\n<pre class=\"literal-block\">\n$ gpg2 --locate-keys torvalds&#64;kernel.org gregkh&#64;kernel.org\n<\/pre>\n<p>This command will verify the TLS certificate presented by kernel.org\nbefore importing these keys into your keyring.<\/p>\n<\/div>\n<div class=\"section\" id=\"using-gnupg-to-verify-kernel-signatures\">\n<h2>Using GnuPG to verify kernel signatures<\/h2>\n<p>All software released via kernel.org has detached PGP signatures you can\nuse to verify the integrity of your downloads.<\/p>\n<p>To illustrate the verification process, let's use Linux 4.6.6 release as\na walk-through example. First, use &quot;<tt class=\"docutils literal\">curl<\/tt>&quot; to download the release\nand the corresponding signature:<\/p>\n<pre class=\"literal-block\">\n$ curl -OL https:\/\/www.kernel.org\/pub\/linux\/kernel\/v4.x\/linux-4.6.6.tar.xz\n$ curl -OL https:\/\/www.kernel.org\/pub\/linux\/kernel\/v4.x\/linux-4.6.6.tar.sign\n<\/pre>\n<p>You will notice that the signature is made against the uncompressed\nversion of the archive. This is done so there is only one signature\nrequired for .gz and .xz compressed versions of the release. Start\nby uncompressing the archive, using <tt class=\"docutils literal\">unxz<\/tt> in our case:<\/p>\n<pre class=\"literal-block\">\n$ unxz linux-4.6.6.tar.xz\n<\/pre>\n<p>Now verify the .tar archive against the signature:<\/p>\n<pre class=\"literal-block\">\n$ gpg2 --verify linux-4.6.6.tar.sign\n<\/pre>\n<p>You can combine these steps into a one-liner:<\/p>\n<pre class=\"literal-block\">\n$ xz -cd linux-4.6.6.tar.xz | gpg2 --verify linux-4.6.6.tar.sign -\n<\/pre>\n<p>It's possible that you get a &quot;No public key error&quot;:<\/p>\n<pre class=\"literal-block\">\ngpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT using RSA key ID 38DBBDC86092693E\ngpg: Can't check signature: No public key\n<\/pre>\n<p>Please use the &quot;<tt class=\"docutils literal\">gpg2 <span class=\"pre\">--locate-keys<\/span><\/tt>&quot; command listed above to download\nthe key for Greg Kroah-Hartman and Linus Torvalds and then try again:<\/p>\n<pre class=\"literal-block\">\n$ gpg2 --locate-keys torvalds&#64;kernel.org gregkh&#64;kernel.org\n$ gpg2 --verify linux-4.6.6.tar.sign\ngpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT\ngpg:                using RSA key 38DBBDC86092693E\ngpg: Good signature from &quot;Greg Kroah-Hartman &lt;gregkh&#64;kernel.org&gt;&quot; [unknown]\ngpg: WARNING: This key is not certified with a trusted signature!\ngpg:          There is no indication that the signature belongs to the owner.\nPrimary key fingerprint: 647F 2865 4894 E3BD 4571  99BE 38DB BDC8 6092 693E\n<\/pre>\n<p>To make the &quot;<tt class=\"docutils literal\">WARNING<\/tt>&quot; message go away you can indicate that you\nchoose to trust that key using TOFU:<\/p>\n<pre class=\"literal-block\">\n$ gpg2 --tofu-policy good 38DBBDC86092693E\n$ gpg2 --trust-model tofu --verify linux-4.6.6.tar.sign\ngpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT\ngpg:                using RSA key 38DBBDC86092693E\ngpg: Good signature from &quot;Greg Kroah-Hartman &lt;gregkh&#64;kernel.org&gt;&quot; [full]\ngpg: gregkh&#64;kernel.org: Verified 1 signature in the past 53 seconds.  Encrypted\n     0 messages.\n<\/pre>\n<p>Note that you may have to pass &quot;<tt class=\"docutils literal\"><span class=\"pre\">--trust-model<\/span> tofu<\/tt>&quot; the first time\nyou run the verify command, but it should not be necessary after that.<\/p>\n<div class=\"section\" id=\"the-scripted-version\">\n<h3>The scripted version<\/h3>\n<p>If you need to perform this task in an automated environment or simply\nprefer a more convenient tool, you can use the following helper script\nto properly download and verify Linux kernel tarballs:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/mricon\/korg-helpers.git\/tree\/get-verified-tarball\">get-verified-tarball<\/a><\/li>\n<\/ul>\n<\/blockquote>\n<p>Please review the script before adopting it for your needs.<\/p>\n<\/div>\n<\/div>\n<div class=\"section\" id=\"important-fingerprints\">\n<h2>Important fingerprints<\/h2>\n<p>Here are key fingerprints for Linus Torvalds, Greg Kroah-Hartman, Sasha\nLevin, and Ben Hutchings, who are most likely to be releasing kernels:<\/p>\n<table border=\"1\" class=\"docutils\">\n<colgroup>\n<col width=\"25%\" \/>\n<col width=\"75%\" \/>\n<\/colgroup>\n<thead valign=\"bottom\">\n<tr><th class=\"head\">Developer<\/th>\n<th class=\"head\">Fingerprint<\/th>\n<\/tr>\n<\/thead>\n<tbody valign=\"top\">\n<tr><td>Linus Torvalds<\/td>\n<td><tt class=\"docutils literal\">ABAF 11C6 5A29 70B1 30AB&nbsp; E3C4 79BE 3E43 0041 1886<\/tt><\/td>\n<\/tr>\n<tr><td>Greg Kroah-Hartman<\/td>\n<td><tt class=\"docutils literal\">647F 2865 4894 E3BD 4571&nbsp; 99BE 38DB BDC8 6092 693E<\/tt><\/td>\n<\/tr>\n<tr><td>Sasha Levin<\/td>\n<td><tt class=\"docutils literal\">E27E 5D8A 3403 A2EF 6687&nbsp; 3BBC DEA6 6FF7 9777 2CDC<\/tt><\/td>\n<\/tr>\n<tr><td>Ben Hutchings<\/td>\n<td><tt class=\"docutils literal\">AC2B 29BD 34A6 AFDD B3F6&nbsp; 8F35 E7BF C8EC 9586 1109<\/tt><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Please verify the TLS certificate for this site in your browser before\ntrusting the above information.<\/p>\n<\/div>\n<div class=\"section\" id=\"if-you-get-bad-signature\">\n<h2>If you get &quot;BAD signature&quot;<\/h2>\n<p>If at any time you see &quot;BAD signature&quot; output from &quot;<tt class=\"docutils literal\">gpg2 <span class=\"pre\">--verify<\/span><\/tt>&quot;,\nplease first check the following first:<\/p>\n<ol class=\"arabic simple\">\n<li><strong>Make sure that you are verifying the signature against the .tar\nversion of the archive, not the compressed (.tar.xz) version.<\/strong><\/li>\n<li>Make sure the the downloaded file is correct and not truncated or\notherwise corrupted.<\/li>\n<\/ol>\n<p>If you repeatedly get the same &quot;BAD signature&quot; output, please email\n<a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>, so we can investigate the problem.<\/p>\n<\/div>\n<div class=\"section\" id=\"kernel-org-checksum-autosigner-and-sha256sums-asc\">\n<h2>Kernel.org checksum autosigner and sha256sums.asc<\/h2>\n<p>We have a dedicated off-the-network system that connects directly to our\ncentral attached storage and calculates checksums for all uploaded\nsoftware releases. The generated <tt class=\"docutils literal\">sha256sums.asc<\/tt> file is then signed\nwith a PGP key generated for this purpose and that doesn't exist outside\nof that system.<\/p>\n<p>These checksums are <strong>NOT<\/strong> intended to replace developer signatures. It\nis merely a way for someone to quickly verify whether contents on one of\nthe many kernel.org mirrors match the contents on the master mirror.\nWhile you may use them to quickly verify whether what you have\ndownloaded matches what we have on our central storage system, you\nshould continue to use developer signatures for best assurance.<\/p>\n<\/div>\n<div class=\"section\" id=\"kernel-releases-prior-to-september-2011\">\n<h2>Kernel releases prior to September, 2011<\/h2>\n<p>Prior to September, 2011 all kernel releases were signed automatically by\nthe same PGP key:<\/p>\n<pre class=\"literal-block\">\npub   1024D\/517D0F0E 2000-10-10 [revoked: 2011-12-11]\n      Key fingerprint = C75D C40A 11D7 AF88 9981  ED5B C86B A06A 517D 0F0E\nuid                  Linux Kernel Archives Verification Key &lt;ftpadmin&#64;kernel.org&gt;\n<\/pre>\n<p>Due to the kernel.org systems compromise, this key has been retired and\nrevoked. <strong>It will no longer be used to sign future releases and you\nshould NOT use this key to verify the integrity of any archives. It is\nalmost certain that this key has fallen into malicious hands.<\/strong><\/p>\n<p>All kernel releases that were previously signed with this key were\ncross-checked and signed with another key, created specifically\nfor this purpose:<\/p>\n<pre class=\"literal-block\">\npub   3072R\/C4790F9D 2013-08-08\n      Key fingerprint = BFA7 DD3E 0D42 1C9D B6AB  6527 0D3B 3537 C479 0F9D\nuid   Linux Kernel Archives Verification Key\n      (One-off resigning of old releases) &lt;ftpadmin&#64;kernel.org&gt;\n<\/pre>\n<p>The private key used for this purpose has been destroyed and cannot be\nused to sign any releases produced after 2011.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Signatures"}}},{"title":"RC tarballs and patches starting with 4.12-rc1","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/rc-tarballs-and-patches-starting-with-412-rc1.html","rel":"alternate"}},"published":"2017-05-16T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2017-05-16:\/rc-tarballs-and-patches-starting-with-412-rc1.html","summary":"<p>As you may be aware, starting with 4.12-rc1 Linus will <a class=\"reference external\" href=\"https:\/\/lwn.net\/Articles\/722660\/\">no longer provide<\/a>\nsigned tarballs and patches for pre-release (&quot;-rc&quot;) kernels. Reasons for\nthis are multiple, but largely this is because people who are most\ninterested in pre-release tags -- kernel developers -- do not rely on\npatches and tarballs to \u2026<\/p>","content":"<p>As you may be aware, starting with 4.12-rc1 Linus will <a class=\"reference external\" href=\"https:\/\/lwn.net\/Articles\/722660\/\">no longer provide<\/a>\nsigned tarballs and patches for pre-release (&quot;-rc&quot;) kernels. Reasons for\nthis are multiple, but largely this is because people who are most\ninterested in pre-release tags -- kernel developers -- do not rely on\npatches and tarballs to do their work.<\/p>\n<div class=\"section\" id=\"obtaining-tarballs-on-your-own\">\n<h2>Obtaining tarballs on your own<\/h2>\n<p>Here is how you can generate the tarball from a pre-release tag using\nthe &quot;<tt class=\"docutils literal\">git archive<\/tt>&quot; command (we'll use 4.12-rc1 in these examples):<\/p>\n<pre class=\"literal-block\">\ngit clone git:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\ncd linux\ngit verify-tag v4.12-rc1\ngit archive --format=tar.gz --prefix=linux-4.12-rc1\/ \\\n  -o linux-4.12-rc1.tar.gz v4.12-rc1\n<\/pre>\n<p>The upside of this method is that during the &quot;<tt class=\"docutils literal\">git <span class=\"pre\">verify-tag<\/span><\/tt>&quot; step\nyou will check the PGP signature on the tag to make sure that what you\ncloned is exactly the same tree as on Linus Torvalds's computer.<\/p>\n<p>The downside of this method is that you will need to download about 1\nGiB of data -- the entire git history of the Linux kernel -- just to get\nthe latest tag. Notably, when -rc2 is tagged, all you'll need to do is\nrun a quick &quot;<tt class=\"docutils literal\">git pull<\/tt>&quot; to get the latest objects and it will be\ndramatically less data to download, so cloning the whole tree may be\nworth it to you in the long run if you plan to do this again in the\nfuture.<\/p>\n<p>If you do not want to download the whole git repository and just want to\nget the latest tarball, you can download the version automatically\ngenerated by cgit at the following (or similar URL):<\/p>\n<pre class=\"literal-block\">\nwget https:\/\/git.kernel.org\/torvalds\/t\/linux-4.12-rc1.tar.gz\n<\/pre>\n<p>Please note that you will not be able to cryptographically verify the\nintegrity of this archive, but the download will be about 10 times less\nin size than the full git tree.<\/p>\n<\/div>\n<div class=\"section\" id=\"obtaining-patches-to-the-previous-mainline\">\n<h2>Obtaining patches to the previous mainline<\/h2>\n<p>If you would like to get just the patch to the previous mainline\nrelease, you can get it from cgit as well:<\/p>\n<pre class=\"literal-block\">\nwget -O patch-4.12-rc1 https:\/\/git.kernel.org\/torvalds\/p\/v4.12-rc1\/v4.11\n<\/pre>\n<p>Unfortunately, cgit does not currently offer an easy way to get\ngzip-compressed patches, but if you would like to reduce the amount of\ndata you download, you can use http-level gzip compression:<\/p>\n<pre class=\"literal-block\">\nwget -O patch-4.12-rc1.gz --header=&quot;accept-encoding: gzip&quot; \\\n  https:\/\/git.kernel.org\/torvalds\/p\/v4.12-rc1\/v4.11\n<\/pre>\n<p>The links to these patches are available on the front page of\n<a class=\"reference external\" href=\"https:\/\/www.kernel.org\/\">https:\/\/www.kernel.org\/<\/a>.<\/p>\n<\/div>\n<div class=\"section\" id=\"why-not-provide-these-at-their-old-locations\">\n<h2>Why not provide these at their old locations?<\/h2>\n<p>We intentionally did not provide these automatically generated tarballs\nand patches in locations previously used by Linus\n(<tt class=\"docutils literal\">\/pub\/linux\/kernel\/v4.x\/testing<\/tt>), even if this meant potentially\nbreaking automated scripts relying on contents published there. Anything\nplaced in the \/pub tree is signed and curated directly by developers\nand all patches and software archives published there invariably come\nwith a PGP signature provided directly by the developer of that software\n(or one of the developers).<\/p>\n<p>Patches and tarballs automatically generated by git.kernel.org are NOT\na replacement for this stringent process, but merely a convenience\nservice that comes with very different trust implications. By providing\nthese at different URLs we wanted all users of these services to make a\nconscious decision on whether they want to trust these automatically\ngenerated tarballs and patches, or whether they want to change their\nprocess to continue to use PGP-verifiable tags directly from the git\ntree.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"If you got \"BAD Signature\" this morning","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/if-you-got-bad-signature-this-morning.html","rel":"alternate"}},"published":"2017-05-14T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2017-05-14:\/if-you-got-bad-signature-this-morning.html","summary":"<p>The XZ tarballs for the following kernel releases did not initially pass\nsignature verification due to benign changes to the tarball structure\ndone by the pixz compression tool:<\/p>\n<ul class=\"simple\">\n<li>4.11.1<\/li>\n<li>4.10.16<\/li>\n<li>4.9.28<\/li>\n<li>4.4.68<\/li>\n<\/ul>\n<p>These changes would have resulted in GPG returning &quot;Bad Signature \u2026<\/p>","content":"<p>The XZ tarballs for the following kernel releases did not initially pass\nsignature verification due to benign changes to the tarball structure\ndone by the pixz compression tool:<\/p>\n<ul class=\"simple\">\n<li>4.11.1<\/li>\n<li>4.10.16<\/li>\n<li>4.9.28<\/li>\n<li>4.4.68<\/li>\n<\/ul>\n<p>These changes would have resulted in GPG returning &quot;Bad Signature&quot; if\nyou tried to verify their integrity. Once we identified the problem, we\ngenerated new XZ tarballs without tar header modifications and now they\nshould all pass PGP signature verification.<\/p>\n<p>We preserved the original .xz tarballs as -badsig files in the archives\nin case you wanted to verify that there was nothing malicious in them,\nmerely tar header changes. You can find them in the same v4.x directory:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.kernel.org\/pub\/linux\/kernel\/v4.x\/\">https:\/\/www.kernel.org\/pub\/linux\/kernel\/v4.x\/<\/a><\/li>\n<\/ul>\n<p>Our apologies for this problem and thanks to Brad Spengler and everyone\nelse who alerted us about this issue.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Fast new frontends with Packet","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/fast-new-frontends-with-packet.html","rel":"alternate"}},"published":"2017-03-11T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2017-03-11:\/fast-new-frontends-with-packet.html","summary":"<img alt=\"Packet logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/packet-logo.png\" style=\"width: 176px; height: 60px;\" \/>\n<p>We are extremely happy to announce that <a class=\"reference external\" href=\"https:\/\/www.packet.net\/\">Packet<\/a> has graciously donated\nthe new hardware systems providing read-only public access to the\nkernel.org git repositories and the public website (git.kernel.org and\nwww.kernel.org, respectively). We have avoided using cloud providers in\nthe past due to security implications \u2026<\/p>","content":"<img alt=\"Packet logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/packet-logo.png\" style=\"width: 176px; height: 60px;\" \/>\n<p>We are extremely happy to announce that <a class=\"reference external\" href=\"https:\/\/www.packet.net\/\">Packet<\/a> has graciously donated\nthe new hardware systems providing read-only public access to the\nkernel.org git repositories and the public website (git.kernel.org and\nwww.kernel.org, respectively). We have avoided using cloud providers in\nthe past due to security implications of sharing hypervisor memory with\nexternal parties, but Packet's hardware-based single-tenant approach\nsatisfies our security requirements while taking over the burden of\nsetting up and managing the physical hardware in multiple worldwide\ndatacenters.<\/p>\n<p>As of March 11, 2017, the four new public frontends are located in the\nfollowing geographical locations:<\/p>\n<ul class=\"simple\">\n<li>San Jose, California, USA<\/li>\n<li>Parsippany, New Jersey, USA<\/li>\n<li>Amsterdam, Netherlands<\/li>\n<li>Tokyo, Japan<\/li>\n<\/ul>\n<p>We have changed our DNS configuration to support GeoDNS, so your\nrequests should be routed to the frontend nearest to you.<\/p>\n<p>Each Packet-hosted system is <a class=\"reference external\" href=\"https:\/\/www.packet.net\/bare-metal\/servers\/type-2-virtualization\/\">significantly more powerful<\/a> than our\nprevious generation frontends and have triple the amount of available\nRAM, so they should be a lot more responsive even when a lot of people\nare cloning linux.git simultaneously.<\/p>\n<p>Our special thanks to the following organizations who have graciously\ndonated hosting for the previous incarnation of kernel.org frontends:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/www.isc.org\/\">Internet Systems Consortium<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/www.vexxhost.com\/\">Vexxhost<\/a><\/li>\n<li><a class=\"reference external\" href=\"https:\/\/www.tizen.org\/\">Tizen<\/a><\/li>\n<\/ul>\n<p>If you notice any problems with the new systems, please email\n<a class=\"reference external\" href=\"mailto:helpdesk&#64;kernel.org\">helpdesk&#64;kernel.org<\/a>.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Shutting down FTP services","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/shutting-down-ftp-services.html","rel":"alternate"}},"published":"2017-01-27T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2017-01-27:\/shutting-down-ftp-services.html","summary":"<p>Those of you who have been around for a while may remember a time when\nyou used to be able to mount kernel.org directly as a partition on your\nsystem using NFS (or even SMB\/CIFS). The Wayback Machine shows that this\nwas still advertised some time in <a class=\"reference external\" href=\"https:\/\/web.archive.org\/web\/19980130085039\/http:\/\/www.kernel.org\/\">January \u2026<\/a><\/p>","content":"<p>Those of you who have been around for a while may remember a time when\nyou used to be able to mount kernel.org directly as a partition on your\nsystem using NFS (or even SMB\/CIFS). The Wayback Machine shows that this\nwas still advertised some time in <a class=\"reference external\" href=\"https:\/\/web.archive.org\/web\/19980130085039\/http:\/\/www.kernel.org\/\">January 1998<\/a>, but was removed by\nthe time the <a class=\"reference external\" href=\"https:\/\/web.archive.org\/web\/19981212030306\/http:\/\/www.kernel.org\/\">December 1998<\/a> copy was made.<\/p>\n<p>Let's face it -- while kinda neat and convenient, offering a public\nNFS\/CIFS server was a Pretty Bad Idea, not only because both these\nprotocols are pretty terrible over high latency connections, but also\nbecause of important security implications.<\/p>\n<p>Well, 19 years later we're thinking it's time to terminate another\nservice that has important protocol and security implications -- our\nFTP servers. Our decision is driven by the following considerations:<\/p>\n<ul class=\"simple\">\n<li>The protocol is inefficient and requires adding awkward kludges to\nfirewalls and load-balancing daemons<\/li>\n<li>FTP servers have no support for caching or accelerators, which has\nsignificant performance impacts<\/li>\n<li>Most software implementations have stagnated and see infrequent updates<\/li>\n<\/ul>\n<p>All kernel.org FTP services will be shut down by the end of this year.\nIn hopes to minimise the potential disruption, we will be doing it in\ntwo stages:<\/p>\n<ol class=\"arabic simple\">\n<li><a class=\"reference external\" href=\"ftp:\/\/ftp.kernel.org\/\">ftp:\/\/ftp.kernel.org\/<\/a> service will be terminated on March 1, 2017<\/li>\n<li><a class=\"reference external\" href=\"ftp:\/\/mirrors.kernel.org\/\">ftp:\/\/mirrors.kernel.org\/<\/a> service will be terminated on December 1, 2017<\/li>\n<\/ol>\n<p>If you have any concerns, please feel free to contact\n<a class=\"reference external\" href=\"mailto:ftpadmin&#64;kernel.org\">ftpadmin&#64;kernel.org<\/a> (ah, the irony).<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Gandi.net TLS certificates","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/gandinet-tls-certificates.html","rel":"alternate"}},"published":"2016-10-11T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2016-10-11:\/gandinet-tls-certificates.html","summary":"<img alt=\"Gandi logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/gandi-logo.png\" style=\"width: 202px; height: 60px;\" \/>\n<p>If your browser alerted you that the site certificates have changed,\nthat would be because we replaced our StartCOM, Ltd certificates with\nthose offered by our DNS registrar, <a class=\"reference external\" href=\"https:\/\/gandi.net\/\">Gandi<\/a>. We are very thankful to\nGandi for this opportunity.<\/p>\n<p>A common question is why we aren't using the certificates offered by \u2026<\/p>","content":"<img alt=\"Gandi logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/gandi-logo.png\" style=\"width: 202px; height: 60px;\" \/>\n<p>If your browser alerted you that the site certificates have changed,\nthat would be because we replaced our StartCOM, Ltd certificates with\nthose offered by our DNS registrar, <a class=\"reference external\" href=\"https:\/\/gandi.net\/\">Gandi<\/a>. We are very thankful to\nGandi for this opportunity.<\/p>\n<p>A common question is why we aren't using the certificates offered by the\n<a class=\"reference external\" href=\"https:\/\/letsencrypt.org\/\">Let's Encrypt project<\/a>, and the answer is that there are several\ntechnical hurdles (on our end) that currently make it complicated. Once\nwe resolve them, we will most likely switch to using certificates issued\nby our fellow Linux Foundation project.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Cloning Linux from a bundle","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/cloning-linux-from-a-bundle.html","rel":"alternate"}},"published":"2016-03-02T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2016-03-02:\/cloning-linux-from-a-bundle.html","summary":"<p>If you find yourself on an unreliable Internet connection and need to\nperform a fresh clone of Linux.git, you may find it tricky to do so if\nyour connection resets before you are able to complete the clone. There\nis currently no way to resume a git clone using \u2026<\/p>","content":"<p>If you find yourself on an unreliable Internet connection and need to\nperform a fresh clone of Linux.git, you may find it tricky to do so if\nyour connection resets before you are able to complete the clone. There\nis currently no way to resume a git clone using git, but there is a neat\ntrick you can use instead of cloning directly -- using <a class=\"reference external\" href=\"https:\/\/git-scm.com\/docs\/git-bundle\">git bundle<\/a>\nfiles.<\/p>\n<p>Here is how you would do it.<\/p>\n<ol class=\"arabic\">\n<li><p class=\"first\">Start with &quot;<tt class=\"docutils literal\">wget <span class=\"pre\">-c<\/span><\/tt>&quot;, which tells wget to continue interrupted\ndownloads. If your connection resets, just rerun the same command while\nin the same directory, and it will pick up where it left off:<\/p>\n<pre class=\"literal-block\">\nwget -c https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\/clone.bundle\n<\/pre>\n<\/li>\n<li><p class=\"first\">Next, clone from the bundle:<\/p>\n<pre class=\"literal-block\">\ngit clone clone.bundle linux\n<\/pre>\n<\/li>\n<li><p class=\"first\">Now, point the origin to the live git repository and get the latest changes:<\/p>\n<pre class=\"literal-block\">\ncd linux\ngit remote remove origin\ngit remote add origin https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\ngit pull origin master\n<\/pre>\n<\/li>\n<\/ol>\n<p>Once this is done, you can delete the &quot;<tt class=\"docutils literal\">clone.bundle<\/tt>&quot; file, unless\nyou think you will need to perform a fresh clone again in the future.<\/p>\n<p>The &quot;<tt class=\"docutils literal\">clone.bundle<\/tt>&quot; files are generated weekly on Sunday, so they\nshould contain most objects you need, even during kernel merge windows\nwhen there are lots of changes committed daily.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Introducing Fastly CDN","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/introducing-fastly-cdn.html","rel":"alternate"}},"published":"2015-10-05T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2015-10-05:\/introducing-fastly-cdn.html","summary":"<img alt=\"Fastly logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/fastly-logo.png\" style=\"width: 156px; height: 60px;\" \/>\n<p>We are happy to announce that <a class=\"reference external\" href=\"https:\/\/fastly.com\/\">Fastly<\/a> has offered their worldwide CDN\nnetwork to provide fast download services for Linux kernel releases,\nwhich should improve download speeds for those of you located outside\nNorth America. We have modified the front page to offer CDN-powered\ndownload links, but all the existing \u2026<\/p>","content":"<img alt=\"Fastly logo\" class=\"align-left\" src=\"https:\/\/www.kernel.org\/news\/images\/fastly-logo.png\" style=\"width: 156px; height: 60px;\" \/>\n<p>We are happy to announce that <a class=\"reference external\" href=\"https:\/\/fastly.com\/\">Fastly<\/a> has offered their worldwide CDN\nnetwork to provide fast download services for Linux kernel releases,\nwhich should improve download speeds for those of you located outside\nNorth America. We have modified the front page to offer CDN-powered\ndownload links, but all the existing URLs should continue to work.<\/p>\n<p>If you would like to avoid using Fastly, you can simply change the URL\nto have &quot;www.kernel.org&quot; instead of &quot;cdn.kernel.org&quot;. As always, please\nuse <a class=\"reference external\" href=\"https:\/\/kernel.org\/signature.html\">PGP Signature Verification<\/a> for all downloaded files regardless of\nwhere you got them.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Hurr, Durr Im'a Sheep","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/hurr-durr-ima-sheep.html","rel":"alternate"}},"published":"2015-04-01T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2015-04-01:\/hurr-durr-ima-sheep.html","summary":"<p>Linus named the upcoming 4.0 release of the kernel &quot;Hurr Durr I'ma\nSheep&quot; (see his <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/cgit\/linux\/kernel\/git\/torvalds\/linux.git\/commit\/?id=c517d838eb7d07bbe9507871fab3931deccff539\">git commit<\/a>), so we are celebrating this April Fool's\nday with a minor prank. If you've been redirected to\n<a class=\"reference external\" href=\"https:\/\/imasheep.hurrdurr.org\/\">imasheep.hurrdurr.org<\/a>, do not panic. It's all part of the joke.<\/p>\n<p>We've also restored \u2026<\/p>","content":"<p>Linus named the upcoming 4.0 release of the kernel &quot;Hurr Durr I'ma\nSheep&quot; (see his <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/cgit\/linux\/kernel\/git\/torvalds\/linux.git\/commit\/?id=c517d838eb7d07bbe9507871fab3931deccff539\">git commit<\/a>), so we are celebrating this April Fool's\nday with a minor prank. If you've been redirected to\n<a class=\"reference external\" href=\"https:\/\/imasheep.hurrdurr.org\/\">imasheep.hurrdurr.org<\/a>, do not panic. It's all part of the joke.<\/p>\n<p>We've also restored all FTP and Rsync access to the\n<a class=\"reference external\" href=\"https:\/\/mirrors.kernel.org\/\">mirrors.kernel.org<\/a> servers, as we seem to have resolved our SSD\nand dm_cache problems. If you're still using FTP, however, please\nconsider switching to HTTP. FTP is a protocol designed for a different\nera -- these days everyone should be avoiding it for <a class=\"reference external\" href=\"http:\/\/mywiki.wooledge.org\/FtpMustDie\">multiple\nreasons<\/a>.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"FTP limited on mirrors.kernel.org","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/ftp-limited-on-mirrorskernelorg.html","rel":"alternate"}},"published":"2015-02-03T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2015-02-03:\/ftp-limited-on-mirrorskernelorg.html","summary":"<p>We've had to temporarily limit FTP access to mirrors.kernel.org due\nto high IO load.<\/p>\n<p>We have recently upgraded our hardware in order to increase capacity --\n16TB was no longer nearly sufficient enough to host all the distro\nmirrors and archives. We chose larger but slower disks and offset \u2026<\/p>","content":"<p>We've had to temporarily limit FTP access to mirrors.kernel.org due\nto high IO load.<\/p>\n<p>We have recently upgraded our hardware in order to increase capacity --\n16TB was no longer nearly sufficient enough to host all the distro\nmirrors and archives. We chose larger but slower disks and offset the\nloss of performance by heavily utilizing SSD IO caching using dm-cache.<\/p>\n<p>While it was performing very well, we have unfortunately run across an\nFS data corruption bug somewhere along this stack:<\/p>\n<pre class=\"literal-block\">\nmegaraid_sas + dm_cache + libvirt\/virtio + xfs\n<\/pre>\n<p>We've temporarily removed dm-cache from the picture and switched to\nVarnish on top of SSD for http object caching. Unfortunately, as Varnish\ndoes not support FTP, we had to restrict FTP protocol to a limited\nnumber of concurrent sessions in order to reduce disk IO. If you are\naffected by this, simply switch to HTTP protocol that does not have such\nrestrictions.<\/p>\n<p>This is a temporary measure until we identify the dm-cache problem that\nwas causing data corruption, at which point we will restore unrestricted\nFTP access.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Heartbleed statement","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/heartbleed-statement.html","rel":"alternate"}},"published":"2014-04-10T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2014-04-10:\/heartbleed-statement.html","summary":"<p>Since we rely on the OpenSSL library for serving most of our websites,\nwe, together with most of the rest of the open-source world, were\nvulnerable to the <a class=\"reference external\" href=\"http:\/\/heartbleed.com\/\">HeartBleed<\/a> vulnerability. We have switched to the\npatched version of OpenSSL within hours of it becoming available, plus\nhave performed the following \u2026<\/p>","content":"<p>Since we rely on the OpenSSL library for serving most of our websites,\nwe, together with most of the rest of the open-source world, were\nvulnerable to the <a class=\"reference external\" href=\"http:\/\/heartbleed.com\/\">HeartBleed<\/a> vulnerability. We have switched to the\npatched version of OpenSSL within hours of it becoming available, plus\nhave performed the following steps to mitigate any sensitive information\nleaked via malicious SSL heartbeat requests:<\/p>\n<ul class=\"simple\">\n<li>Replaced all SSL keys across all kernel.org sites.<\/li>\n<li>Expired all active sessions on Bugzilla, Patchwork, and Mediawiki\nsites, requiring everyone to re-login.<\/li>\n<li>Changed all passwords used for admin-level access to the above sites.<\/li>\n<\/ul>\n<p>As kernel.org developers do not rely on SSL to access git repositories,\nthere is no need to replace any SSH or PGP keys used for developer\nauthentication.<\/p>\n<p>If you have any questions or concerns, please email us at\n<a class=\"reference external\" href=\"mailto:webmaster&#64;kernel.org\">webmaster&#64;kernel.org<\/a> for more information.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Happy new year and good-bye bzip2","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/happy-new-year-and-good-bye-bzip2.html","rel":"alternate"}},"published":"2013-12-27T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2013-12-27:\/happy-new-year-and-good-bye-bzip2.html","summary":"<div class=\"section\" id=\"good-bye-bzip2\">\n<h2>Good-bye bzip2<\/h2>\n<p>We started listing xz-compressed versions of kernel archives in all our\nannouncements back in March 2013, and the time has come to complete the\nswitch. Effective immediately, we will no longer be providing\nbzip2-compressed versions for new releases of the Linux kernel and other\nsoftware. Any previously released \u2026<\/p><\/div>","content":"<div class=\"section\" id=\"good-bye-bzip2\">\n<h2>Good-bye bzip2<\/h2>\n<p>We started listing xz-compressed versions of kernel archives in all our\nannouncements back in March 2013, and the time has come to complete the\nswitch. Effective immediately, we will no longer be providing\nbzip2-compressed versions for new releases of the Linux kernel and other\nsoftware. Any previously released .tar.bz2 archives will continue to be\navailable without change, and we will also continue to provide\ngzip-compressed versions of all new releases for the foreseeable future.<\/p>\n<p>So, from now on, all releases will be offered as both .tar.gz and\n.tar.xz, but not as .tar.bz2. We apologize if this interferes with any\nautomated tools.<\/p>\n<\/div>\n<div class=\"section\" id=\"happy-new-year\">\n<h2>Happy new year!<\/h2>\n<p>Happy new year to all kernel.org users and visitors. The Linux\nFoundation and Linux Kernel Archives teams extend their warmest wishes\nto you all, and we hope that 2014 proves to be just as awesome (or\nawesomer) for the Linux kernel.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"New frontend and googlesource.com","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/new-frontend-and-googlesourcecom.html","rel":"alternate"}},"published":"2013-11-28T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":"Konstantin Ryabitsev"},"id":"tag:www.kernel.org,2013-11-28:\/new-frontend-and-googlesourcecom.html","summary":"<div class=\"section\" id=\"montreal-frontend\">\n<h2>Montreal frontend<\/h2>\n<p>We have added another official frontend for serving the kernel content,\ncourtesy of <a class=\"reference external\" href=\"https:\/\/vexxhost.com\">Vexxhost, Inc<\/a>. There is now a total of three frontends,\none in Palo Alto, California, one in Portland, Oregon, and one in\nMontreal, Quebec. This should allow for better geographic dispersion of\nofficial mirrors, as \u2026<\/p><\/div>","content":"<div class=\"section\" id=\"montreal-frontend\">\n<h2>Montreal frontend<\/h2>\n<p>We have added another official frontend for serving the kernel content,\ncourtesy of <a class=\"reference external\" href=\"https:\/\/vexxhost.com\">Vexxhost, Inc<\/a>. There is now a total of three frontends,\none in Palo Alto, California, one in Portland, Oregon, and one in\nMontreal, Quebec. This should allow for better geographic dispersion of\nofficial mirrors, as well as better fault tolerance.<\/p>\n<\/div>\n<div class=\"section\" id=\"kernel-googlesource-com\">\n<h2>Kernel.googlesource.com<\/h2>\n<p>We are happy to announce that kernel.googlesource.com is now relying on\ngrokmirror manifest data to efficiently mirror git.kernel.org, which\nmeans that if accessing git.kernel.org is too high latency for you due\nto your geographical location (EMEA, APAC), kernel.googlesource.com\nshould provide you with a fast local mirror that is at most 5 minutes\nbehind official sources.<\/p>\n<p>We extend our thanks to Google for making this available to all kernel\nhackers and enthusiasts worldwide.<\/p>\n<\/div>\n<div class=\"section\" id=\"tls-1-2-and-pfs\">\n<h2>TLS 1.2 and PFS<\/h2>\n<p>With the latest round of upgrades, we are now serving TLS 1.2 with PFS\nacross all kernel.org sites, offering higher protection against\neavesdropping.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Mirroring kernel.org repositories","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/mirroring-kernelorg-repositories.html","rel":"alternate"}},"published":"2013-06-03T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-06-03:\/mirroring-kernelorg-repositories.html","summary":"<p>If you would like to mirror all or a subset of kernel.org git\nrepositories, please use a tool we wrote for this purpose, called\ngrokmirror. Grokmirror is git-aware and will create a complete mirror of\nkernel.org repositories and keep them automatically updated with no\nfurther involvement on your \u2026<\/p>","content":"<p>If you would like to mirror all or a subset of kernel.org git\nrepositories, please use a tool we wrote for this purpose, called\ngrokmirror. Grokmirror is git-aware and will create a complete mirror of\nkernel.org repositories and keep them automatically updated with no\nfurther involvement on your part.<\/p>\n<p>Grokmirror works by keeping track of repositories being updated by\ndownloading and comparing the master manifest file. This file is only\ndownloaded if it's newer on the server, and only the repositories that\nhave changed will be updated via &quot;git remote update&quot;.<\/p>\n<p>You can read more about grokmirror by reading the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/cgit\/utils\/grokmirror\/grokmirror.git\/tree\/README.rst\">README<\/a> file.<\/p>\n<div class=\"section\" id=\"obtaining-grokmirror\">\n<h2>Obtaining grokmirror<\/h2>\n<p>If grokmirror is not yet packaged for your distribution, you can obtain\nit from a git repository:<\/p>\n<pre class=\"literal-block\">\ngit clone git:\/\/git.kernel.org\/pub\/scm\/utils\/grokmirror\/grokmirror.git\n<\/pre>\n<p>In additon to git, you will need to install the following python\ndependencies on your mirror server:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/pypi.python.org\/pypi\/GitPython\/\">GitPython<\/a><\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"setting-up-a-kernel-org-mirror\">\n<h2>Setting up a kernel.org mirror<\/h2>\n<p>It is recommended that you create a dedicated &quot;mirror&quot; user that will\nown all the content and run all the cron jobs. It is generally\ndiscouraged to run this as user &quot;root&quot;.<\/p>\n<p>The default repos.conf already comes pre-configured for kernel.org. We\nreproduce the minimal configuration here:<\/p>\n<pre class=\"literal-block\">\n[kernel.org]\nsite = git:\/\/git.kernel.org\nmanifest = http:\/\/git.kernel.org\/manifest.js.gz\ndefault_owner = Grokmirror User\n#\n# Where are we going to put the mirror on our disk?\ntoplevel = \/var\/lib\/git\/mirror\n#\n# Where do we store our own manifest? Usually in the toplevel.\nmymanifest = \/var\/lib\/git\/mirror\/manifest.js.gz\n#\n# Where do we put the logs?\nlog = \/var\/log\/mirror\/kernelorg.log\n#\n# Log level can be &quot;info&quot; or &quot;debug&quot;\nloglevel = info\n#\n# To prevent multiple grok-pull instances from running at the same\n# time, we first obtain an exclusive lock.\nlock = \/var\/lock\/mirror\/kernelorg.lock\n#\n# Use shell-globbing to list the repositories you would like to mirror.\n# If you want to mirror everything, just say &quot;*&quot;. Separate multiple entries\n# with newline plus tab. Examples:\n#\n# mirror everything:\n#include = *\n#\n# mirror just the main kernel sources:\n#include = \/pub\/scm\/linux\/kernel\/git\/torvalds\/linux.git\n#          \/pub\/scm\/linux\/kernel\/git\/stable\/linux-stable.git\n#          \/pub\/scm\/linux\/kernel\/git\/next\/linux-next.git\n#\n# mirror just git:\n#include = \/pub\/scm\/git\/*\ninclude = *\n#\n# This is processed after the include. If you want to exclude some specific\n# entries from an all-inclusive globbing above. E.g., to exclude all\n# linux-2.4 git sources:\n#exclude = *\/linux-2.4*\nexclude =\n<\/pre>\n<p>Install this configuration file anywhere that makes sense in your\nenvironment. You'll need to make sure that the following directories (or\nwhatever you changed them to) are writable by the &quot;mirror&quot; user:<\/p>\n<blockquote>\n<ul class=\"simple\">\n<li><tt class=\"docutils literal\">\/var\/lib\/git\/mirror<\/tt><\/li>\n<li><tt class=\"docutils literal\">\/var\/log\/mirror<\/tt><\/li>\n<li><tt class=\"docutils literal\">\/var\/lock\/mirror<\/tt><\/li>\n<\/ul>\n<\/blockquote>\n<\/div>\n<div class=\"section\" id=\"mirroring-kernel-org-git-repositories\">\n<h2>Mirroring kernel.org git repositories<\/h2>\n<p>Now all you need to do is to add a cronjob that will check the\nkernel.org mirror for updates. The following entry in\n<tt class=\"docutils literal\">\/etc\/cron.d\/grokmirror.cron<\/tt> will check the mirror every 5 minutes:<\/p>\n<pre class=\"literal-block\">\n# Run grok-pull every 5 minutes as &quot;mirror&quot; user\n*\/5 * * * * mirror \/usr\/bin\/grok-pull -p -c \/etc\/grokmirror\/repos.conf\n<\/pre>\n<p>(You will need to adjust the paths to the grok-pull command and to\nrepos.conf accordingly to reflect your environment.)<\/p>\n<p>The initial run will take many hours to complete, as it will need to\ndownload about 50 GB of data.<\/p>\n<\/div>\n<div class=\"section\" id=\"mirroring-a-subset-of-repositories\">\n<h2>Mirroring a subset of repositories<\/h2>\n<p>If you are only interested in carrying a subset of git repositories\ninstead of all of them, you are welcome to tweak the <tt class=\"docutils literal\">include<\/tt> and\n<tt class=\"docutils literal\">exclude<\/tt> parameters.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Fifty shades of Tux","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/fifty-shades-of-tux.html","rel":"alternate"}},"published":"2013-05-07T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-05-07:\/fifty-shades-of-tux.html","summary":"<p>Special thanks to Beno\u00eet Monin for donating a MIT-licensed CSS theme to\nthe kernel.org project to replace the one we hastily put together.\nThough the Pelican authors have since obtained a free-license\ncommitment from the copyright owners of the CSS files shipping with\nPelican, we wanted to have something \u2026<\/p>","content":"<p>Special thanks to Beno\u00eet Monin for donating a MIT-licensed CSS theme to\nthe kernel.org project to replace the one we hastily put together.\nThough the Pelican authors have since obtained a free-license\ncommitment from the copyright owners of the CSS files shipping with\nPelican, we wanted to have something that looked a bit less like the\ndefault theme anyway.<\/p>\n<p>If anyone else wants to participate, full sources of the kernel.org\nwebsite are available from the <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/cgit\/docs\/kernel\/website.git\">git repository<\/a>.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"XZ by default and JSON","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/xz-by-default-and-json.html","rel":"alternate"}},"published":"2013-03-11T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-03-11:\/xz-by-default-and-json.html","summary":"<p>We've implemented two oft-requested features today:<\/p>\n<ol class=\"arabic simple\">\n<li>The download links now default to .tar.xz versions of archives<\/li>\n<li>There is now a JSON file with the release information located in\n<a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.json\">https:\/\/www.kernel.org\/releases.json<\/a>. If you've been screen-scraping\nthe front page, please use this instead.<\/li>\n<\/ol>\n<p>If you have any \u2026<\/p>","content":"<p>We've implemented two oft-requested features today:<\/p>\n<ol class=\"arabic simple\">\n<li>The download links now default to .tar.xz versions of archives<\/li>\n<li>There is now a JSON file with the release information located in\n<a class=\"reference external\" href=\"https:\/\/www.kernel.org\/releases.json\">https:\/\/www.kernel.org\/releases.json<\/a>. If you've been screen-scraping\nthe front page, please use this instead.<\/li>\n<\/ol>\n<p>If you have any other feature suggestions, please send them to\n<a class=\"reference external\" href=\"mailto:webmaster&#64;kernel.org\">webmaster&#64;kernel.org<\/a>.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"\/pub tree resync-ing","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/pub-tree-resync-ing.html","rel":"alternate"}},"published":"2013-03-08T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-03-08:\/pub-tree-resync-ing.html","summary":"<p>Due to a failure in one of the rsync scripts during the maintenance\nwindow, the mirrors of \/pub hierarchy on www.kernel.org got erased. We\nare resyncing them now from the master storage, but in the meantime you\nwill probably get an occasional &quot;Forbidden&quot;. The entirety of the archive \u2026<\/p>","content":"<p>Due to a failure in one of the rsync scripts during the maintenance\nwindow, the mirrors of \/pub hierarchy on www.kernel.org got erased. We\nare resyncing them now from the master storage, but in the meantime you\nwill probably get an occasional &quot;Forbidden&quot;. The entirety of the archive\nshould be rsync'ed in a few hours.<\/p>\n<p>We apologize profusely for the problem and will fix the script to make\nsure this doesn't happen again.<\/p>\n<p>Contents of git.kernel.org are unaffected.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Cleanroom styles","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/cleanroom-styles.html","rel":"alternate"}},"published":"2013-03-03T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-03-03:\/cleanroom-styles.html","summary":"<p>You are probably wondering what happened to the site's look.\nUnfortunately, we've been alerted that the default theme shipped by\nPelican (which we largely adapted) has an unclear license. Until this is\ncleared up, we've put together a quick-and-dirty cleanroom CSS\nreimplementation that preserves the functional aspects of the site \u2026<\/p>","content":"<p>You are probably wondering what happened to the site's look.\nUnfortunately, we've been alerted that the default theme shipped by\nPelican (which we largely adapted) has an unclear license. Until this is\ncleared up, we've put together a quick-and-dirty cleanroom CSS\nreimplementation that preserves the functional aspects of the site, but\nsacrifices a lot of the bells and whistles.<\/p>\n<p>If you are a CSS designer and would like to donate your own cleanroom\nstyle, please let us know at <a class=\"reference external\" href=\"mailto:webmaster&#64;kernel.org\">webmaster&#64;kernel.org<\/a>.<\/p>\n<p>Our apologies, and we promise to keep a keener eye on licensing\ndetails of various templates distributed with open-source products.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Pelican","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/pelican.html","rel":"alternate"}},"published":"2013-03-01T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-03-01:\/pelican.html","summary":"<p>Welcome to the reworked kernel.org website. We have switched to using\n<a class=\"reference external\" href=\"http:\/\/docs.getpelican.com\/\">Pelican<\/a> in order to statically render our site content, which\nsimplifies mirroring and distribution. You can view the sources used to\nbuild this website in its own <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/?p=docs\/kernel\/website.git;a=summary\">git repository<\/a>.<\/p>\n<p>Additionally, we have switched from using gitweb-caching to using \u2026<\/p>","content":"<p>Welcome to the reworked kernel.org website. We have switched to using\n<a class=\"reference external\" href=\"http:\/\/docs.getpelican.com\/\">Pelican<\/a> in order to statically render our site content, which\nsimplifies mirroring and distribution. You can view the sources used to\nbuild this website in its own <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/?p=docs\/kernel\/website.git;a=summary\">git repository<\/a>.<\/p>\n<p>Additionally, we have switched from using gitweb-caching to using <a class=\"reference external\" href=\"https:\/\/git.zx2c4.com\/cgit\/\">cgit<\/a>\nfor <a class=\"reference external\" href=\"https:\/\/git.kernel.org\/cgit\/\">browsing git repositories<\/a>. There are rewrite rules in place to\nforward old gitweb URLs to the pages serviced by cgit, so there\nshouldn't be any broken links, hopefully. If you notice that something\nthat used to work with gitweb no longer works for you with cgit, please\ndrop us a note at <a class=\"reference external\" href=\"mailto:webmaster&#64;kernel.org\">webmaster&#64;kernel.org<\/a>.<\/p>\n","category":{"@attributes":{"term":"Site news"}}},{"title":"Legal disclaimers and copyright","link":{"@attributes":{"href":"https:\/\/www.kernel.org\/legal.html","rel":"alternate"}},"published":"2013-01-01T00:00:00+00:00","updated":"2024-08-06T19:40:29+00:00","author":{"name":{}},"id":"tag:www.kernel.org,2013-01-01:\/legal.html","summary":"<div class=\"section\" id=\"copyright-and-license\">\n<h2>Copyright and license<\/h2>\n<p>Except where otherwise stated, content on this site is\ncopyright (C) 1997-2014 by The Linux Kernel Organization, Inc.\nand is made available to you under the\n<a class=\"reference external\" href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/4.0\/\">Creative Commons Attribution ShareAlike 4.0 International License<\/a>.<\/p>\n<p>Distributed software is copyrighted by their respective contributors and\nare distributed under their \u2026<\/p><\/div>","content":"<div class=\"section\" id=\"copyright-and-license\">\n<h2>Copyright and license<\/h2>\n<p>Except where otherwise stated, content on this site is\ncopyright (C) 1997-2014 by The Linux Kernel Organization, Inc.\nand is made available to you under the\n<a class=\"reference external\" href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/4.0\/\">Creative Commons Attribution ShareAlike 4.0 International License<\/a>.<\/p>\n<p>Distributed software is copyrighted by their respective contributors and\nare distributed under their own individual licenses.<\/p>\n<\/div>\n<div class=\"section\" id=\"legal-disclaimer\">\n<h2>Legal Disclaimer<\/h2>\n<p>This site is provided as a public service by The Linux Kernel\nOrganization Inc., a California <a class=\"reference external\" href=\"https:\/\/www.kernel.org\/nonprofit.html\">501(c)3 nonprofit corporation<\/a>. Our\nservers are located in San Francisco, CA, USA; Palo Alto, CA, USA;\nCorvallis, OR, USA; Portland, OR, USA and Montr\u00e9al, Qu\u00e9bec, Canada. Use\nin violation of any applicable laws is strictly prohibited.<\/p>\n<p>Neither the Linux Kernel Organization nor any of its sponsors make any\nguarantees, explicit or implicit, about the contents of this site. Use\nat your own risk.<\/p>\n<\/div>\n<div class=\"section\" id=\"trademarks\">\n<h2>Trademarks<\/h2>\n<p>Linux is a Registered Trademark of Linus Torvalds. All trademarks are\nproperty of their respective owners.<\/p>\n<\/div>\n","category":{"@attributes":{"term":"About"}}}]}