kernel_org.atom.xml - sfeed_tests - sfeed tests and RSS and Atom files
 (HTM) git clone git://git.codemadness.org/sfeed_tests
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) README
 (DIR) LICENSE
       ---
       kernel_org.atom.xml (99877B)
       ---
            1 <?xml version="1.0" encoding="utf-8"?>
            2 <feed xmlns="http://www.w3.org/2005/Atom"><title>The Linux Kernel Archives</title><link href="https://www.kernel.org/" rel="alternate"></link><link href="https://www.kernel.org/feeds/all.atom.xml" rel="self"></link><id>https://www.kernel.org/</id><updated>2020-07-02T16:50:07+00:00</updated><entry><title>Active kernel releases</title><link href="https://www.kernel.org/releases.html" rel="alternate"></link><published>2020-07-02T16:50:07+00:00</published><updated>2020-07-02T16:50:07+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2020-07-02:releases.html</id><summary type="html">&lt;p&gt;There are several main categories into which kernel releases may fall:&lt;/p&gt;
            3 &lt;dl class="docutils"&gt;
            4 &lt;dt&gt;Prepatch&lt;/dt&gt;
            5 &lt;dd&gt;Prepatch or &amp;quot;RC&amp;quot; kernels are mainline kernel pre-releases that are
            6 mostly aimed at other kernel developers and Linux enthusiasts. They
            7 must be compiled from source and usually contain new features that
            8 must be tested before they can be put into a stable release.
            9 Prepatch kernels are maintained and released by Linus Torvalds.&lt;/dd&gt;
           10 &lt;dt&gt;Mainline&lt;/dt&gt;
           11 &lt;dd&gt;Mainline tree is maintained by Linus Torvalds. It's the tree where
           12 all new features are introduced and where all the exciting new
           13 development happens. New mainline kernels are released every 2-3
           14 months.&lt;/dd&gt;
           15 &lt;dt&gt;Stable&lt;/dt&gt;
           16 &lt;dd&gt;After each mainline kernel is released, it is considered &amp;quot;stable.&amp;quot;
           17 Any bug fixes for a stable kernel are backported from the mainline
           18 tree and applied by a designated stable kernel maintainer. There are
           19 usually only a few bugfix kernel releases until next mainline kernel
           20 becomes available -- unless it is designated a &amp;quot;longterm maintenance
           21 kernel.&amp;quot; Stable kernel updates are released on as-needed basis,
           22 usually once a week.&lt;/dd&gt;
           23 &lt;dt&gt;Longterm&lt;/dt&gt;
           24 &lt;dd&gt;There are usually several &amp;quot;longterm maintenance&amp;quot; kernel releases
           25 provided for the purposes of backporting bugfixes for older kernel
           26 trees. Only important bugfixes are applied to such kernels and they
           27 don't usually see very frequent releases, especially for older
           28 trees.&lt;/dd&gt;
           29 &lt;/dl&gt;
           30 &lt;table border="1" class="docutils"&gt;
           31 &lt;caption&gt;Longterm release kernels&lt;/caption&gt;
           32 &lt;colgroup&gt;
           33 &lt;col width="11%" /&gt;
           34 &lt;col width="46%" /&gt;
           35 &lt;col width="17%" /&gt;
           36 &lt;col width="26%" /&gt;
           37 &lt;/colgroup&gt;
           38 &lt;thead valign="bottom"&gt;
           39 &lt;tr&gt;&lt;th class="head"&gt;Version&lt;/th&gt;
           40 &lt;th class="head"&gt;Maintainer&lt;/th&gt;
           41 &lt;th class="head"&gt;Released&lt;/th&gt;
           42 &lt;th class="head"&gt;Projected EOL&lt;/th&gt;
           43 &lt;/tr&gt;
           44 &lt;/thead&gt;
           45 &lt;tbody valign="top"&gt;
           46 &lt;tr&gt;&lt;td&gt;5.4&lt;/td&gt;
           47 &lt;td&gt;Greg Kroah-Hartman &amp;amp; Sasha Levin&lt;/td&gt;
           48 &lt;td&gt;2019-11-24&lt;/td&gt;
           49 &lt;td&gt;Dec, 2025&lt;/td&gt;
           50 &lt;/tr&gt;
           51 &lt;tr&gt;&lt;td&gt;4.19&lt;/td&gt;
           52 &lt;td&gt;Greg Kroah-Hartman &amp;amp; Sasha Levin&lt;/td&gt;
           53 &lt;td&gt;2018-10-22&lt;/td&gt;
           54 &lt;td&gt;Dec, 2024&lt;/td&gt;
           55 &lt;/tr&gt;
           56 &lt;tr&gt;&lt;td&gt;4.14&lt;/td&gt;
           57 &lt;td&gt;Greg Kroah-Hartman &amp;amp; Sasha Levin&lt;/td&gt;
           58 &lt;td&gt;2017-11-12&lt;/td&gt;
           59 &lt;td&gt;Jan, 2024&lt;/td&gt;
           60 &lt;/tr&gt;
           61 &lt;tr&gt;&lt;td&gt;4.9&lt;/td&gt;
           62 &lt;td&gt;Greg Kroah-Hartman &amp;amp; Sasha Levin&lt;/td&gt;
           63 &lt;td&gt;2016-12-11&lt;/td&gt;
           64 &lt;td&gt;Jan, 2023&lt;/td&gt;
           65 &lt;/tr&gt;
           66 &lt;tr&gt;&lt;td&gt;4.4&lt;/td&gt;
           67 &lt;td&gt;Greg Kroah-Hartman &amp;amp; Sasha Levin&lt;/td&gt;
           68 &lt;td&gt;2016-01-10&lt;/td&gt;
           69 &lt;td&gt;Feb, 2022&lt;/td&gt;
           70 &lt;/tr&gt;
           71 &lt;/tbody&gt;
           72 &lt;/table&gt;
           73 &lt;div class="section" id="distribution-kernels"&gt;
           74 &lt;h2&gt;Distribution kernels&lt;/h2&gt;
           75 &lt;p&gt;Many Linux distributions provide their own &amp;quot;longterm maintenance&amp;quot;
           76 kernels that may or may not be based on those maintained by kernel
           77 developers. These kernel releases are not hosted at kernel.org and
           78 kernel developers can provide no support for them.&lt;/p&gt;
           79 &lt;p&gt;It is easy to tell if you are running a distribution kernel. Unless you
           80 downloaded, compiled and installed your own version of kernel from
           81 kernel.org, you are running a distribution kernel. To find out the
           82 version of your kernel, run &lt;cite&gt;uname -r&lt;/cite&gt;:&lt;/p&gt;
           83 &lt;pre class="literal-block"&gt;
           84 # uname -r
           85 5.6.19-300.fc32.x86_64
           86 &lt;/pre&gt;
           87 &lt;p&gt;If you see anything at all after the dash, you are running a distribution
           88 kernel. Please use the support channels offered by your distribution
           89 vendor to obtain kernel support.&lt;/p&gt;
           90 &lt;/div&gt;
           91 </summary></entry><entry><title>Git mirror available in Beijing</title><link href="https://www.kernel.org/beijing-git-mirror.html" rel="alternate"></link><published>2020-01-11T00:00:00+00:00</published><updated>2020-01-11T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2020-01-11:beijing-git-mirror.html</id><summary type="html">&lt;p&gt;If you are a developer located around Beijing, or if your connection to
           92 Beijing is faster and more reliable than to locations outside of China,
           93 then you may benefit from the new git.kernel.org mirror kindly provided
           94 by &lt;a class="reference external" href="https://www.codeaurora.org/"&gt;Code Aurora Forum&lt;/a&gt; at &lt;a class="reference external" href="https://kernel.source.codeaurora.cn/"&gt;https://kernel.source.codeaurora.cn/&lt;/a&gt;. This is
           95 a full mirror that is updated just as frequently as other git.kernel.org
           96 nodes (in fact, it is managed by the same team as the rest of kernel.org
           97 infrastructure, since CAF is part of Linux Foundation IT projects).&lt;/p&gt;
           98 &lt;p&gt;To start using the Beijing mirror, simply clone from that location or
           99 add a separate remote to your existing checkouts, e.g.:&lt;/p&gt;
          100 &lt;pre class="literal-block"&gt;
          101 git remote add beijing git://kernel.source.codeaurora.cn/pub/scm/.../linux.git
          102 git fetch beijing master
          103 &lt;/pre&gt;
          104 &lt;p&gt;You may also use &lt;a class="reference external" href="http://"&gt;http://&lt;/a&gt; and &lt;a class="reference external" href="https://"&gt;https://&lt;/a&gt; protocols if that makes it easier
          105 behind corporate firewalls.&lt;/p&gt;
          106 </summary></entry><entry><title>Code of Conduct</title><link href="https://www.kernel.org/code-of-conduct.html" rel="alternate"></link><published>2020-01-02T00:00:00+00:00</published><updated>2020-01-02T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2020-01-02:code-of-conduct.html</id><summary type="html">&lt;p&gt;The Linux kernel community operates a &lt;a class="reference external" href="https://www.kernel.org/doc/html/latest/process/code-of-conduct.html"&gt;Code of Conduct&lt;/a&gt; based on the
          107 &lt;a class="reference external" href="https://www.contributor-covenant.org/version/1/4/code-of-conduct.html"&gt;Contributor Covenant Code of Conduct&lt;/a&gt;.&lt;/p&gt;
          108 &lt;div class="section" id="code-of-conduct-committee"&gt;
          109 &lt;h2&gt;Code of Conduct Committee&lt;/h2&gt;
          110 &lt;p&gt;The Linux kernel Code of Conduct Committee is currently made up of the
          111 following people:&lt;/p&gt;
          112 &lt;blockquote&gt;
          113 &lt;ul class="simple"&gt;
          114 &lt;li&gt;Kristen Accardi &amp;lt;&lt;a class="reference external" href="mailto:kristen.c.accardi&amp;#64;intel.com"&gt;kristen.c.accardi&amp;#64;intel.com&lt;/a&gt;&amp;gt;&lt;/li&gt;
          115 &lt;li&gt;Mishi Choudhary &amp;lt;&lt;a class="reference external" href="mailto:mishi&amp;#64;linux.com"&gt;mishi&amp;#64;linux.com&lt;/a&gt;&amp;gt;&lt;/li&gt;
          116 &lt;li&gt;Shuah Khan &amp;lt;&lt;a class="reference external" href="mailto:skhan&amp;#64;linuxfoundation.org"&gt;skhan&amp;#64;linuxfoundation.org&lt;/a&gt;&amp;gt;&lt;/li&gt;
          117 &lt;li&gt;Greg Kroah-Hartman &amp;lt;&lt;a class="reference external" href="mailto:gregkh&amp;#64;linuxfoundation.org"&gt;gregkh&amp;#64;linuxfoundation.org&lt;/a&gt;&amp;gt;&lt;/li&gt;
          118 &lt;/ul&gt;
          119 &lt;/blockquote&gt;
          120 &lt;p&gt;Committee members can be reached all at once by writing to
          121 &amp;lt;&lt;a class="reference external" href="mailto:conduct&amp;#64;kernel.org"&gt;conduct&amp;#64;kernel.org&lt;/a&gt;&amp;gt;.&lt;/p&gt;
          122 &lt;/div&gt;
          123 &lt;div class="section" id="committee-reports"&gt;
          124 &lt;h2&gt;Committee Reports&lt;/h2&gt;
          125 &lt;p&gt;We would like to thank the Linux kernel community members who have supported
          126 the adoption of the Code of Conduct and who continue to uphold the professional
          127 standards of our community. If you have any questions about these reports,
          128 please write to &amp;lt;&lt;a class="reference external" href="mailto:conduct&amp;#64;kernel.org"&gt;conduct&amp;#64;kernel.org&lt;/a&gt;&amp;gt;.&lt;/p&gt;
          129 &lt;div class="section" id="december-2019"&gt;
          130 &lt;h3&gt;December 2019&lt;/h3&gt;
          131 &lt;p&gt;Archival copy: &lt;a class="reference external" href="https://lore.kernel.org/lkml/20200103105614.GC1047442&amp;#64;kroah.com/"&gt;https://lore.kernel.org/lkml/20200103105614.GC1047442&amp;#64;kroah.com/&lt;/a&gt;&lt;/p&gt;
          132 &lt;p&gt;In the period of December 1, 2019 through December 30, 2019 the Committee
          133 received the following report:&lt;/p&gt;
          134 &lt;blockquote&gt;
          135 &lt;ul class="simple"&gt;
          136 &lt;li&gt;Insulting behavior in email: 1&lt;/li&gt;
          137 &lt;/ul&gt;
          138 &lt;/blockquote&gt;
          139 &lt;p&gt;The result of the investigation:&lt;/p&gt;
          140 &lt;blockquote&gt;
          141 &lt;ul class="simple"&gt;
          142 &lt;li&gt;Education and coaching: 1&lt;/li&gt;
          143 &lt;/ul&gt;
          144 &lt;/blockquote&gt;
          145 &lt;/div&gt;
          146 &lt;div class="section" id="august-to-november-2019"&gt;
          147 &lt;h3&gt;August to November 2019&lt;/h3&gt;
          148 &lt;p&gt;Archival copy: &lt;a class="reference external" href="https://lore.kernel.org/lkml/20191218090054.GA5120&amp;#64;kroah.com/"&gt;https://lore.kernel.org/lkml/20191218090054.GA5120&amp;#64;kroah.com/&lt;/a&gt;&lt;/p&gt;
          149 &lt;p&gt;In the period of August 1, 2019 through November 31, 2019, the Committee
          150 received no reports.&lt;/p&gt;
          151 &lt;/div&gt;
          152 &lt;div class="section" id="september-2018-to-july-2019"&gt;
          153 &lt;h3&gt;September 2018 to July 2019&lt;/h3&gt;
          154 &lt;p&gt;Archival copy: &lt;a class="reference external" href="https://lore.kernel.org/lkml/20190810120700.GA7360&amp;#64;kroah.com/"&gt;https://lore.kernel.org/lkml/20190810120700.GA7360&amp;#64;kroah.com/&lt;/a&gt;&lt;/p&gt;
          155 &lt;p&gt;In the period of September 15, 2018 through July 31, 2019, the Committee
          156 received the following reports:&lt;/p&gt;
          157 &lt;blockquote&gt;
          158 &lt;ul class="simple"&gt;
          159 &lt;li&gt;Inappropriate language in the kernel source: 1&lt;/li&gt;
          160 &lt;li&gt;Insulting behavior in email: 3&lt;/li&gt;
          161 &lt;/ul&gt;
          162 &lt;/blockquote&gt;
          163 &lt;p&gt;The result of the investigations:&lt;/p&gt;
          164 &lt;blockquote&gt;
          165 &lt;ul class="simple"&gt;
          166 &lt;li&gt;Education and coaching: 4&lt;/li&gt;
          167 &lt;/ul&gt;
          168 &lt;/blockquote&gt;
          169 &lt;/div&gt;
          170 &lt;/div&gt;
          171 </summary></entry><entry><title>Frequently asked questions</title><link href="https://www.kernel.org/faq.html" rel="alternate"></link><published>2019-05-02T13:53:08+00:00</published><updated>2019-05-02T13:53:08+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2019-05-02:faq.html</id><summary type="html">&lt;p&gt;If you have questions, comments or concerns about the F.A.Q. please
          172 contact us at &lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt;.&lt;/p&gt;
          173 &lt;div class="section" id="is-linux-kernel-free-software"&gt;
          174 &lt;h2&gt;Is Linux Kernel Free Software?&lt;/h2&gt;
          175 &lt;p&gt;Linux kernel is released under GNU GPL version 2 and is therefore Free
          176 Software as defined by the &lt;a class="reference external" href="https://www.fsf.org/"&gt;Free Software Foundation&lt;/a&gt;. You may read the
          177 entire copy of the license in the &lt;a class="reference external" href="/pub/linux/kernel/COPYING"&gt;COPYING&lt;/a&gt; file distributed with each
          178 release of the Linux kernel.&lt;/p&gt;
          179 &lt;/div&gt;
          180 &lt;div class="section" id="what-does-stable-eol-and-longterm-mean"&gt;
          181 &lt;h2&gt;What does &amp;quot;stable/EOL&amp;quot; and &amp;quot;longterm&amp;quot; mean?&lt;/h2&gt;
          182 &lt;p&gt;As kernels move from the &amp;quot;mainline&amp;quot; into the &amp;quot;stable&amp;quot; category, two
          183 things can happen:&lt;/p&gt;
          184 &lt;ol class="arabic simple"&gt;
          185 &lt;li&gt;They can reach &amp;quot;End of Life&amp;quot; after a few bugfix revisions, which
          186 means that kernel maintainers will release no more bugfixes for this
          187 kernel version, or&lt;/li&gt;
          188 &lt;li&gt;They can be put into &amp;quot;longterm&amp;quot; maintenance, which means that
          189 maintainers will provide bugfixes for this kernel revision for a
          190 much longer period of time.&lt;/li&gt;
          191 &lt;/ol&gt;
          192 &lt;p&gt;If the kernel version you are using is marked &amp;quot;EOL,&amp;quot; you should consider
          193 upgrading to the next major version as there will be no more bugfixes
          194 provided for the kernel version you are using.&lt;/p&gt;
          195 &lt;p&gt;Please check the &lt;a class="reference external" href="https://www.kernel.org/releases.html"&gt;Releases&lt;/a&gt; page for more info.&lt;/p&gt;
          196 &lt;/div&gt;
          197 &lt;div class="section" id="why-is-an-lts-kernel-marked-as-stable-on-the-front-page"&gt;
          198 &lt;h2&gt;Why is an LTS kernel marked as &amp;quot;stable&amp;quot; on the front page?&lt;/h2&gt;
          199 &lt;p&gt;Long-term support (&amp;quot;LTS&amp;quot;) kernels announced on the &lt;a class="reference external" href="https://www.kernel.org/releases.html"&gt;Releases&lt;/a&gt; page will
          200 be marked as &amp;quot;stable&amp;quot; on the front page if there are no other current
          201 stable kernel releases. This is done to avoid breaking automated parsers
          202 monitoring kernel.org with an expectation that there will always be a
          203 kernel release marked as &amp;quot;stable.&amp;quot;&lt;/p&gt;
          204 &lt;/div&gt;
          205 &lt;div class="section" id="linus-has-tagged-a-new-release-but-it-s-not-listed-on-the-front-page"&gt;
          206 &lt;h2&gt;Linus has tagged a new release, but it's not listed on the front page!&lt;/h2&gt;
          207 &lt;p&gt;Linus Torvalds PGP-signs git repository tags for all new mainline kernel
          208 releases, however a separate set of PGP signatures needs to be generated
          209 by the stable release team in order to create downloadable tarballs. Due
          210 to timezone differences between Linus and the members of the stable
          211 team, there is usually a delay of several hours between when the new
          212 mainline release is tagged and when PGP-signed tarballs become
          213 available. The front page is updated once that process is completed.&lt;/p&gt;
          214 &lt;/div&gt;
          215 &lt;div class="section" id="is-there-an-rss-feed-for-the-latest-kernel-version"&gt;
          216 &lt;h2&gt;Is there an RSS feed for the latest kernel version?&lt;/h2&gt;
          217 &lt;p&gt;Yes, and you can find it at &lt;a class="reference external" href="https://www.kernel.org/feeds/kdist.xml"&gt;https://www.kernel.org/feeds/kdist.xml&lt;/a&gt;.&lt;/p&gt;
          218 &lt;p&gt;We also publish a .json file with the latest release information, which
          219 you can pull from here: &lt;a class="reference external" href="https://www.kernel.org/releases.json"&gt;https://www.kernel.org/releases.json&lt;/a&gt;.&lt;/p&gt;
          220 &lt;/div&gt;
          221 &lt;div class="section" id="why-are-there-files-that-are-dated-tomorrow"&gt;
          222 &lt;h2&gt;Why are there files that are dated tomorrow?&lt;/h2&gt;
          223 &lt;p&gt;All timestamps on kernel.org are in UTC (Coordinated Universal Time). If
          224 you live in the western hemisphere your local time lags behind UTC.
          225 Under Linux/Unix, type &lt;tt class="docutils literal"&gt;date &lt;span class="pre"&gt;-u&lt;/span&gt;&lt;/tt&gt; to get the current time in UTC.&lt;/p&gt;
          226 &lt;/div&gt;
          227 &lt;div class="section" id="can-i-get-an-account-on-kernel-org"&gt;
          228 &lt;h2&gt;Can I get an account on kernel.org?&lt;/h2&gt;
          229 &lt;p&gt;Kernel.org accounts are usually reserved for subsystem maintainers or
          230 high-profile developers. It is absolutely not necessary to have an
          231 account on kernel.org to contribute to the development of the Linux
          232 kernel, unless you submit pull requests directly to Linus.&lt;/p&gt;
          233 &lt;p&gt;If you are listed in the MAINTAINERS file or have reasons to believe you
          234 should have an account on kernel.org because of the amount of your
          235 contributions, please refer to the &lt;a class="reference external" href="https://korg.wiki.kernel.org/userdoc/accounts"&gt;accounts wiki page&lt;/a&gt; for the
          236 procedure to follow.&lt;/p&gt;
          237 &lt;/div&gt;
          238 &lt;div class="section" id="i-have-cool-project-x-can-you-guys-mirror-it-for-me"&gt;
          239 &lt;h2&gt;I have cool project X, can you guys mirror it for me?&lt;/h2&gt;
          240 &lt;p&gt;Probably not. Kernel.org deals with the Linux kernel, various
          241 distributions of the kernel and larger repositories of packages. We do
          242 not mirror individual projects, software, etc as we feel there are
          243 better places providing mirrors for those kinds of repositories. If you
          244 feel that kernel.org should mirror your project, please contact
          245 &lt;a class="reference external" href="mailto:ftpadmin&amp;#64;kernel.org"&gt;ftpadmin&amp;#64;kernel.org&lt;/a&gt; with the following information:&lt;/p&gt;
          246 &lt;ul class="simple"&gt;
          247 &lt;li&gt;name&lt;/li&gt;
          248 &lt;li&gt;project name&lt;/li&gt;
          249 &lt;li&gt;project website&lt;/li&gt;
          250 &lt;li&gt;detailed project description&lt;/li&gt;
          251 &lt;li&gt;reason for wanting us to mirror&lt;/li&gt;
          252 &lt;/ul&gt;
          253 &lt;p&gt;The Kernel.org admin team will then review your request and talk to you
          254 about it. As with any kind of account on kernel.org it's up to the
          255 discretion of the admin team.&lt;/p&gt;
          256 &lt;/div&gt;
          257 &lt;div class="section" id="how-does-kernel-org-provide-its-users-access-to-the-git-trees"&gt;
          258 &lt;h2&gt;How does kernel.org provide its users access to the git trees?&lt;/h2&gt;
          259 &lt;p&gt;We are using an access control system called &lt;a class="reference external" href="https://github.com/sitaramc/gitolite/wiki"&gt;gitolite&lt;/a&gt;, originally
          260 written and maintained by Sitaram Chamarty. We chose gitolite for a
          261 number of reasons:&lt;/p&gt;
          262 &lt;ul class="simple"&gt;
          263 &lt;li&gt;Limiting of ssh access to the system&lt;/li&gt;
          264 &lt;li&gt;Fine grained control over repository access&lt;/li&gt;
          265 &lt;li&gt;Well maintained and supported code base&lt;/li&gt;
          266 &lt;li&gt;Responsive development&lt;/li&gt;
          267 &lt;li&gt;Broad and diverse install base&lt;/li&gt;
          268 &lt;/ul&gt;
          269 &lt;p&gt;As well at the time of deployment the code had undergone an external
          270 code review.&lt;/p&gt;
          271 &lt;/div&gt;
          272 &lt;div class="section" id="how-do-i-create-an-rc-kernel-i-get-reversed-patch-detected"&gt;
          273 &lt;h2&gt;How do I create an -rc kernel? I get &amp;quot;Reversed patch detected!&amp;quot;&lt;/h2&gt;
          274 &lt;p&gt;-rc kernel patches are generated from the base stable release.&lt;/p&gt;
          275 &lt;p&gt;For example: to create the 2.6.14-rc5 kernel, you must:&lt;/p&gt;
          276 &lt;ul class="simple"&gt;
          277 &lt;li&gt;download 2.6.13 (not 2.6.13.4)&lt;/li&gt;
          278 &lt;li&gt;and then apply the 2.6.14-rc5 patch.&lt;/li&gt;
          279 &lt;/ul&gt;
          280 &lt;p&gt;Yes, you want 2.6.13, not 2.6.14. Remember, that's an -rc kernel, as in, 2.6.14 doesn't exist yet. :)&lt;/p&gt;
          281 &lt;/div&gt;
          282 &lt;div class="section" id="where-can-i-find-kernel-2-4-20-3-16"&gt;
          283 &lt;h2&gt;Where can I find kernel 2.4.20-3.16?&lt;/h2&gt;
          284 &lt;p&gt;Kernel version numbers of this form are distribution kernels, meaning
          285 they are modified kernels produced by distributions. Please contact the
          286 relevant distributor; or check out &lt;a class="reference external" href="https://mirrors.kernel.org/"&gt;https://mirrors.kernel.org/&lt;/a&gt;.&lt;/p&gt;
          287 &lt;p&gt;See the &lt;a class="reference external" href="https://www.kernel.org/releases.html"&gt;Releases&lt;/a&gt; page for more info on distribution kernels.&lt;/p&gt;
          288 &lt;/div&gt;
          289 &lt;div class="section" id="i-need-help-building-patching-fixing-linux-kernel-modules-drivers"&gt;
          290 &lt;h2&gt;I need help building/patching/fixing Linux kernel/modules/drivers!&lt;/h2&gt;
          291 &lt;p&gt;Please see the &lt;a class="reference external" href="http://kernelnewbies.org/"&gt;Kernel Newbies&lt;/a&gt; website.&lt;/p&gt;
          292 &lt;p&gt;There is also a wealth of knowledge on many topics involving Linux at
          293 The Linux Documentation Project (&lt;a class="reference external" href="http://www.tldp.org"&gt;http://www.tldp.org&lt;/a&gt;)&lt;/p&gt;
          294 &lt;p&gt;For finding or reporting bugs, look through the archives for the various
          295 Linux mailing lists, and if no specific list seems appropriate, try the
          296 browsing the Linux Kernel Mailing List.&lt;/p&gt;
          297 &lt;/div&gt;
          298 &lt;div class="section" id="what-happened-to-ftp-kernel-org"&gt;
          299 &lt;h2&gt;What happened to ftp.kernel.org?&lt;/h2&gt;
          300 &lt;p&gt;FTP service was terminated on March 1, 2017. All content that used to be
          301 available via ftp.kernel.org can be accessed by browsing
          302 &lt;a class="reference external" href="https://www.kernel.org/pub/"&gt;https://www.kernel.org/pub/&lt;/a&gt;. If you would like to use a command-line
          303 tool for accessing these files, you can do so with lftp:&lt;/p&gt;
          304 &lt;blockquote&gt;
          305 lftp &lt;a class="reference external" href="https://www.kernel.org/pub"&gt;https://www.kernel.org/pub&lt;/a&gt;&lt;/blockquote&gt;
          306 &lt;/div&gt;
          307 &lt;div class="section" id="when-will-the-next-kernel-be-released"&gt;
          308 &lt;h2&gt;When will the next kernel be released?&lt;/h2&gt;
          309 &lt;p&gt;The next kernel will be released when it is ready. There is no strict
          310 timeline for making releases, but if you really need an educated guess,
          311 visit the Linux kernel &lt;a class="reference external" href="http://phb-crystal-ball.org/"&gt;PHB Crystal Ball&lt;/a&gt; -- it tries to provide a
          312 ballpark guess based on previous kernel release schedule.&lt;/p&gt;
          313 &lt;/div&gt;
          314 &lt;div class="section" id="what-will-go-into-the-next-release"&gt;
          315 &lt;h2&gt;What will go into the next release?&lt;/h2&gt;
          316 &lt;p&gt;It is hard to predict with certainty, but you can either take a peek at
          317 &lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/"&gt;linux-next&lt;/a&gt; or read the &lt;a class="reference external" href="https://www.linux.com/news/2017/7/linux-weather-forecast"&gt;Linux Weather Forecast&lt;/a&gt;, where Jonathan
          318 Corbet provides a broad forecast of what will likely be included into
          319 the next mainline release.&lt;/p&gt;
          320 &lt;/div&gt;
          321 </summary></entry><entry><title>Get notifications for your patches</title><link href="https://www.kernel.org/get-notifications-for-your-patches.html" rel="alternate"></link><published>2018-12-13T00:00:00+00:00</published><updated>2018-12-13T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2018-12-13:get-notifications-for-your-patches.html</id><summary type="html">&lt;p&gt;We are trialing out a new feature that can send you a notification when
          322 the patches you send to the LKML are applied to linux-next or to the
          323 mainline git trees. If you are interested in trying it out, here are the
          324 details:&lt;/p&gt;
          325 &lt;ul class="simple"&gt;
          326 &lt;li&gt;The patches must be sent to the LKML (&lt;a class="reference external" href="mailto:linux-kernel&amp;#64;vger.kernel.org"&gt;linux-kernel&amp;#64;vger.kernel.org&lt;/a&gt;).&lt;/li&gt;
          327 &lt;li&gt;One of the cc's must be &lt;a class="reference external" href="mailto:notify&amp;#64;kernel.org"&gt;notify&amp;#64;kernel.org&lt;/a&gt; (Bcc will not work).&lt;/li&gt;
          328 &lt;li&gt;Alternatively, there should be a &amp;quot;X-Patchwork-Bot: notify&amp;quot; email header.&lt;/li&gt;
          329 &lt;li&gt;The patches must not have been modified by the maintainer(s).&lt;/li&gt;
          330 &lt;li&gt;All patches in the series must have been applied, not just some of them.&lt;/li&gt;
          331 &lt;/ul&gt;
          332 &lt;p&gt;The last two points are important, because if there are changes between
          333 the content of the patch as it was first sent to the mailing list, and
          334 how it looks like by the time it is applied to linux-next or mainline,
          335 the bot will not be able to recognize it as the same patch. Similarly,
          336 for series of multiple patches, the bot must be able to successfully
          337 match all patches in the series in order for the notification to go out.&lt;/p&gt;
          338 &lt;p&gt;If you are using &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;git-format-patch&lt;/span&gt;&lt;/tt&gt;, it is best to add the special
          339 header instead of using the Cc notification address, so as to avoid any
          340 unnecessary email traffic:&lt;/p&gt;
          341 &lt;pre class="literal-block"&gt;
          342 --add-header=&amp;quot;X-Patchwork-Bot: notify&amp;quot;
          343 &lt;/pre&gt;
          344 &lt;p&gt;You should receive one notification email per each patch series, so if
          345 you send a series of 20 patches, you will get a single email in the form
          346 of a reply to the cover letter, or to the first patch in the series. The
          347 notification will be sent directly to you, ignoring any other addresses
          348 in the Cc field.&lt;/p&gt;
          349 &lt;p&gt;The bot uses our &lt;a class="reference external" href="https://lore.kernel.org/patchwork"&gt;LKML patchwork instance&lt;/a&gt; to perform matching and
          350 tracking, and the &lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/git-patchwork-bot.py"&gt;source code&lt;/a&gt; for the bot is also available if you
          351 would like to suggest improvements.&lt;/p&gt;
          352 </summary></entry><entry><title>List archives on lore.kernel.org</title><link href="https://www.kernel.org/lore.html" rel="alternate"></link><published>2018-12-12T00:00:00+00:00</published><updated>2018-12-12T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2018-12-12:lore.html</id><summary type="html">&lt;p&gt;You may access the archives of many Linux development mailing lists on
          353 &lt;a class="reference external" href="https://lore.kernel.org/lists.html"&gt;lore.kernel.org&lt;/a&gt;. Most of them include a full archive of messages going
          354 back several decades.&lt;/p&gt;
          355 &lt;ul class="simple"&gt;
          356 &lt;li&gt;&lt;a class="reference external" href="https://lore.kernel.org/lists.html"&gt;listing of currently hosted archives&lt;/a&gt;&lt;/li&gt;
          357 &lt;/ul&gt;
          358 &lt;p&gt;If you would like to suggest another kernel development mailing list to
          359 be included in this list, please follow the instructions on the
          360 following wiki page:&lt;/p&gt;
          361 &lt;ul class="simple"&gt;
          362 &lt;li&gt;&lt;a class="reference external" href="https://korg.wiki.kernel.org/userdoc/lore"&gt;Adding list archives to lore.kernel.org&lt;/a&gt;&lt;/li&gt;
          363 &lt;/ul&gt;
          364 &lt;div class="section" id="archiving-software"&gt;
          365 &lt;h2&gt;Archiving software&lt;/h2&gt;
          366 &lt;p&gt;The software managing the archive is called &lt;a class="reference external" href="https://public-inbox.org/design_notes.html"&gt;Public Inbox&lt;/a&gt; and offers
          367 the following features:&lt;/p&gt;
          368 &lt;ul class="simple"&gt;
          369 &lt;li&gt;Fast, searchable web archives&lt;/li&gt;
          370 &lt;li&gt;Atom feeds per list or per individual thread&lt;/li&gt;
          371 &lt;li&gt;Downloadable mbox archives to make replying easy&lt;/li&gt;
          372 &lt;li&gt;Git-backed archival mechanism you can clone and pull&lt;/li&gt;
          373 &lt;li&gt;Read-only nntp gateway&lt;/li&gt;
          374 &lt;/ul&gt;
          375 &lt;p&gt;We collected many list archives going as far back as 1998, and they are
          376 now all available to anyone via a simple git clone. We would like to
          377 extend our thanks to everyone who helped in this effort by donating
          378 their personal archives.&lt;/p&gt;
          379 &lt;/div&gt;
          380 &lt;div class="section" id="obtaining-full-list-archives"&gt;
          381 &lt;h2&gt;Obtaining full list archives&lt;/h2&gt;
          382 &lt;p&gt;Git clone URLs are provided at the bottom of each page. Note, that due
          383 mailing list volume, list archives are sharded into multiple
          384 repositories, each roughly 1GB in size. In addition to cloning from
          385 lore.kernel.org, you may also access these repositories on
          386 &lt;a class="reference external" href="https://erol.kernel.org/"&gt;erol.kernel.org&lt;/a&gt;.&lt;/p&gt;
          387 &lt;div class="section" id="mirroring"&gt;
          388 &lt;h3&gt;Mirroring&lt;/h3&gt;
          389 &lt;p&gt;You can continuously mirror the entire mailing list archive collection
          390 by using the &lt;a class="reference external" href="https://github.com/mricon/grokmirror"&gt;grokmirror&lt;/a&gt; tool. The following repos.conf file should get
          391 you all you need:&lt;/p&gt;
          392 &lt;pre class="literal-block"&gt;
          393 [lore.kernel.org]
          394 site = https://lore.kernel.org
          395 manifest = https://lore.kernel.org/manifest.js.gz
          396 toplevel = /path/to/your/local/folder
          397 mymanifest = /path/to/your/local/folder/manifest.js.gz
          398 pull_threads = 4
          399 &lt;/pre&gt;
          400 &lt;p&gt;Please note, that you will require at least 20+ GB of local storage. The
          401 mirroring process only replicates the git repositories themselves -- if
          402 you want to use public-inbox with them, you will need to run
          403 &amp;quot;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;public-inbox-init&lt;/span&gt;&lt;/tt&gt;&amp;quot; and &amp;quot;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;public-inbox-index&lt;/span&gt;&lt;/tt&gt;&amp;quot; to create the
          404 database files required for public-inbox operation.&lt;/p&gt;
          405 &lt;/div&gt;
          406 &lt;/div&gt;
          407 &lt;div class="section" id="linking-to-list-discussions-from-commits"&gt;
          408 &lt;h2&gt;Linking to list discussions from commits&lt;/h2&gt;
          409 &lt;p&gt;If you need to reference a mailing list discussion inside code comments
          410 or in a git commit message, please use the &amp;quot;permalink&amp;quot; URL provided by
          411 public-inbox. It is available in the headers of each displayed message
          412 or thread discussion. Alternatively, you can use a generic message-id
          413 redirector in the form:&lt;/p&gt;
          414 &lt;ul class="simple"&gt;
          415 &lt;li&gt;&lt;a class="reference external" href="https://lore.kernel.org/r/message&amp;#64;id"&gt;https://lore.kernel.org/r/message&amp;#64;id&lt;/a&gt;&lt;/li&gt;
          416 &lt;/ul&gt;
          417 &lt;p&gt;That should display the message regardless in which mailing list archive
          418 it's stored.&lt;/p&gt;
          419 &lt;/div&gt;
          420 </summary></entry><entry><title>Minor changes to kernel tarball releases</title><link href="https://www.kernel.org/minor-changes-to-tarball-release-format.html" rel="alternate"></link><published>2018-07-27T00:00:00+00:00</published><updated>2018-07-27T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2018-07-27:minor-changes-to-tarball-release-format.html</id><summary type="html">&lt;p&gt;We'd like to announce several small changes to the way Linux tarballs
          421 are produced.&lt;/p&gt;
          422 &lt;div class="section" id="mainline-release-tarball-signatures"&gt;
          423 &lt;h2&gt;Mainline release tarball signatures&lt;/h2&gt;
          424 &lt;p&gt;Starting with the 4.18 final release, all mainline tarball PGP
          425 signatures will be made by Greg Kroah-Hartman instead of Linus Torvalds.
          426 The main goal behind this change is to simplify the &lt;a class="reference external" href="https://www.kernel.org/signature.html"&gt;verification
          427 process&lt;/a&gt; and make all kernel tarball releases available for download on
          428 kernel.org be signed by the same developer.&lt;/p&gt;
          429 &lt;p&gt;Linus Torvalds will continue to PGP-sign all tags in the mainline
          430 git repository. They can be verified using the &lt;tt class="docutils literal"&gt;git &lt;span class="pre"&gt;verify-tag&lt;/span&gt;&lt;/tt&gt;
          431 command.&lt;/p&gt;
          432 &lt;/div&gt;
          433 &lt;div class="section" id="sunsetting-gz-tarball-generation"&gt;
          434 &lt;h2&gt;Sunsetting .gz tarball generation&lt;/h2&gt;
          435 &lt;p&gt;We stopped creating .bz2 copies of tarball releases 5 years ago, and the
          436 time has come to stop producing .gz duplicate copies of all our content
          437 as well, as XZ tools and libraries are now available on all major
          438 platforms. Starting September 1st, 2018, all tarball releases available
          439 via &lt;tt class="docutils literal"&gt;/pub&lt;/tt&gt; download locations will only be available in XZ-compressed
          440 format.&lt;/p&gt;
          441 &lt;p&gt;If you absolutely must have .gz compressed tarballs, you may obtain them
          442 from git.kernel.org by following snapshot download links in the
          443 appropriate repository view.&lt;/p&gt;
          444 &lt;/div&gt;
          445 &lt;div class="section" id="no-future-pgp-signatures-on-patches-and-changelogs"&gt;
          446 &lt;h2&gt;No future PGP signatures on patches and changelogs&lt;/h2&gt;
          447 &lt;p&gt;For legacy purposes, we will continue to provide pre-generated
          448 changelogs and patches (both to the previous mainline and incremental
          449 patches to previous stable). However, from now on they will be generated
          450 by automated processes and will no longer carry detached PGP signatures.
          451 If you require cryptographically verified patches, please generate them
          452 directly from the &lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"&gt;stable git repository&lt;/a&gt; after verifying the PGP
          453 signatures on the tags using &lt;tt class="docutils literal"&gt;git &lt;span class="pre"&gt;verify-tag&lt;/span&gt;&lt;/tt&gt;.&lt;/p&gt;
          454 &lt;/div&gt;
          455 </summary></entry><entry><title>Best way to do linux clones for your CI</title><link href="https://www.kernel.org/best-way-to-do-linux-clones-for-your-ci.html" rel="alternate"></link><published>2018-07-25T00:00:00+00:00</published><updated>2018-07-25T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2018-07-25:best-way-to-do-linux-clones-for-your-ci.html</id><summary type="html">&lt;p&gt;If you are in charge of CI infrastructure that needs to perform frequent
          456 full clones of kernel trees from git.kernel.org, we strongly recommend
          457 that you use the &lt;a class="reference external" href="https://www.kernel.org/cloning-linux-from-a-bundle.html"&gt;git bundles we provide&lt;/a&gt; instead of performing a full
          458 clone directly from git repositories.&lt;/p&gt;
          459 &lt;p&gt;It is better for you, because downloading the bundle from CDN is
          460 probably going to be much faster for you than cloning from our frontends
          461 due to the CDN being more local. You can even copy the bundle to a
          462 fileserver on your local infrastructure and save a lot of repeated
          463 external traffic.&lt;/p&gt;
          464 &lt;p&gt;It is better for us, because if you first clone from the bundle, you
          465 only need to fetch a handful of newer objects directly from
          466 git.kernel.org frontends. This not only uses an order of magnitude less
          467 bandwidth, but also results in a much smaller memory footprint on our
          468 systems -- git daemon needs a lot of RAM when serving full clones of
          469 linux repositories.&lt;/p&gt;
          470 &lt;p&gt;Here is a simple script that will help you automate the process of first
          471 downloading the git bundle and then fetching the newer objects:&lt;/p&gt;
          472 &lt;ul class="simple"&gt;
          473 &lt;li&gt;&lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/plain/linux-bundle-clone"&gt;linux-bundle-clone&lt;/a&gt;&lt;/li&gt;
          474 &lt;/ul&gt;
          475 &lt;p&gt;Thank you for helping us keep our systems fast and accessible to all.&lt;/p&gt;
          476 </summary></entry><entry><title>Nitrokey digital tokens for kernel developers</title><link href="https://www.kernel.org/nitrokey-digital-tokens-for-kernel-developers.html" rel="alternate"></link><published>2018-04-04T00:00:00+00:00</published><updated>2018-04-04T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2018-04-04:nitrokey-digital-tokens-for-kernel-developers.html</id><summary type="html">&lt;p&gt;The Linux Foundation IT team has been working to improve the code
          477 integrity of git repositories hosted at kernel.org by promoting the use
          478 of PGP-signed git tags and commits. Doing so allows anyone to easily
          479 verify that git repositories have not been altered or tampered with no
          480 matter from which worldwide mirror they may have been cloned. If the
          481 digital signature on your cloned repository matches the PGP key
          482 belonging to Linus Torvalds or any other maintainer, then you can be
          483 assured that what you have on your computer is the exact replica of the
          484 kernel code without any omissions or additions.&lt;/p&gt;
          485 &lt;p&gt;To help promote the use of PGP signatures in Linux kernel development,
          486 we now offer a detailed guide within the kernel documentation tree:&lt;/p&gt;
          487 &lt;ul class="simple"&gt;
          488 &lt;li&gt;&lt;a class="reference external" href="https://www.kernel.org/doc/html/latest/process/maintainer-pgp-guide.html"&gt;Kernel Maintainer PGP Guide&lt;/a&gt;&lt;/li&gt;
          489 &lt;/ul&gt;
          490 &lt;img alt="Nitrokey logo" class="align-left" src="https://www.kernel.org/static/news/images/nitrokey-logo.png" style="width: 207px; height: 70px;" /&gt;
          491 &lt;p&gt;Further, we are happy to announce a new special program sponsored by
          492 &lt;a class="reference external" href="https://linuxfoundation.org/"&gt;The Linux Foundation&lt;/a&gt; in partnership with &lt;a class="reference external" href="https://www.nitrokey.com/"&gt;Nitrokey&lt;/a&gt; -- the developer
          493 and manufacturer of smartcard-compatible digital tokens capable of
          494 storing private keys and performing PGP operations on-chip. Under this
          495 program, any developer who is listed as a maintainer in the &lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS"&gt;MAINTAINERS&lt;/a&gt;
          496 file, or who has a kernel.org account can qualify for a free digital
          497 token to help improve the security of their PGP keys. The cost of the
          498 device, including any taxes, shipping and handling will be covered by
          499 The Linux Foundation.&lt;/p&gt;
          500 &lt;p&gt;To participate in this program, please access the special store front
          501 on the Nitrokey website:&lt;/p&gt;
          502 &lt;ul class="simple"&gt;
          503 &lt;li&gt;&lt;a class="reference external" href="https://kernel.nitrokey.com/"&gt;Nitrokey Start for Kernel Developers&lt;/a&gt;&lt;/li&gt;
          504 &lt;/ul&gt;
          505 &lt;div class="section" id="who-qualifies-for-this-program"&gt;
          506 &lt;h2&gt;Who qualifies for this program?&lt;/h2&gt;
          507 &lt;p&gt;To qualify for the program, you need to have an account at kernel.org or
          508 have your email address listed in the &lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS"&gt;MAINTAINERS&lt;/a&gt; file (following the
          509 &amp;quot;&lt;tt class="docutils literal"&gt;M:&lt;/tt&gt;&amp;quot; heading). If you do not currently qualify but think you should,
          510 the easiest course of action is to get yourself added to the MAINTAINERS
          511 file or to &lt;a class="reference external" href="https://korg.wiki.kernel.org/userdoc/accounts"&gt;apply for an account at kernel.org&lt;/a&gt;.&lt;/p&gt;
          512 &lt;/div&gt;
          513 &lt;div class="section" id="which-devices-are-available-under-this-program"&gt;
          514 &lt;h2&gt;Which devices are available under this program?&lt;/h2&gt;
          515 &lt;p&gt;The program is limited to &lt;a class="reference external" href="https://shop.nitrokey.com/shop/product/nitrokey-start-6"&gt;Nitrokey Start&lt;/a&gt; devices. There are several
          516 reasons why we picked this particular device among several available
          517 options.&lt;/p&gt;
          518 &lt;p&gt;First of all, many Linux kernel developers have a strong preference not
          519 just for open-source software, but for open hardware as well. Nitrokey
          520 is one of the few companies selling GnuPG-compatible smartcard devices
          521 that provide both, since Nitrokey Start is based on Gnuk cryptographic
          522 token firmware developed by &lt;a class="reference external" href="https://www.fsij.org/category/gnuk.html"&gt;Free Software Initiative of Japan&lt;/a&gt;. It is
          523 also one of the few commercially available devices that offer native
          524 support for ECC keys, which are both faster computationally than large
          525 RSA keys and generate smaller digital signatures. With our push to use
          526 more code signing of git objects themselves, both the open nature of the
          527 device and its support for fast modern cryptography were key points in
          528 our evaluation.&lt;/p&gt;
          529 &lt;p&gt;Additionally, Nitrokey devices (both Start and Pro models) are already
          530 &lt;a class="reference external" href="https://lwn.net/Articles/736231/"&gt;used by open-source developers&lt;/a&gt; for cryptographic purposes and they
          531 are known to work well with Linux workstations.&lt;/p&gt;
          532 &lt;/div&gt;
          533 &lt;div class="section" id="what-is-the-benefit-of-digital-smartcard-tokens"&gt;
          534 &lt;h2&gt;What is the benefit of digital smartcard tokens?&lt;/h2&gt;
          535 &lt;p&gt;With usual GnuPG operations, the private keys are stored in the home
          536 directory where they can be stolen by malware or exposed via other
          537 means, such as poorly secured backups. Furthermore, each time a GnuPG
          538 operation is performed, the keys are loaded into system memory and can
          539 be stolen from there using sufficiently advanced techniques (the likes
          540 of Meltdown and Spectre).&lt;/p&gt;
          541 &lt;p&gt;A digital smartcard token like Nitrokey Start contains a cryptographic
          542 chip that is capable of storing private keys and performing crypto
          543 operations directly on the token itself. Because the key contents never
          544 leave the device, the operating system of the computer into which the
          545 token is plugged in is not able to retrieve the private keys themselves,
          546 therefore significantly limiting the ways in which the keys can be
          547 leaked or stolen.&lt;/p&gt;
          548 &lt;/div&gt;
          549 &lt;div class="section" id="questions-or-problems"&gt;
          550 &lt;h2&gt;Questions or problems?&lt;/h2&gt;
          551 &lt;p&gt;If you qualify for the program, but encounter any difficulties
          552 purchasing the device, please contact Nitrokey at &lt;a class="reference external" href="mailto:shop&amp;#64;nitrokey.com"&gt;shop&amp;#64;nitrokey.com&lt;/a&gt;.&lt;/p&gt;
          553 &lt;p&gt;For any questions about the program itself or with any other comments,
          554 please reach out to &lt;a class="reference external" href="mailto:info&amp;#64;linuxfoundation.org"&gt;info&amp;#64;linuxfoundation.org&lt;/a&gt;.&lt;/p&gt;
          555 &lt;/div&gt;
          556 </summary></entry><entry><title>Linux kernel releases PGP signatures</title><link href="https://www.kernel.org/signature.html" rel="alternate"></link><published>2018-02-15T00:00:00+00:00</published><updated>2018-02-15T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2018-02-15:signature.html</id><summary type="html">&lt;p&gt;All kernel releases are cryptographically signed using OpenPGP-compliant
          557 signatures. Everyone is strongly encouraged to verify the integrity of
          558 downloaded kernel releases by verifying the corresponding signatures.&lt;/p&gt;
          559 &lt;div class="section" id="basic-concepts"&gt;
          560 &lt;h2&gt;Basic concepts&lt;/h2&gt;
          561 &lt;p&gt;Every kernel release comes with a cryptographic signature from the
          562 person making the release. This cryptographic signature allows anyone to
          563 verify whether the files have been modified or otherwise tampered with
          564 after the developer created and signed them. The signing and
          565 verification process uses public-key cryptography and it is next to
          566 impossible to forge a PGP signature without first gaining access to the
          567 developer's private key. If this does happen, the developers will revoke
          568 the compromised key and will re-sign all their previously signed
          569 releases with the new key.&lt;/p&gt;
          570 &lt;p&gt;To learn more about the way PGP works, please consult &lt;a class="reference external" href="https://en.wikipedia.org/wiki/Pretty_Good_Privacy#How_PGP_encryption_works"&gt;Wikipedia&lt;/a&gt;.&lt;/p&gt;
          571 &lt;/div&gt;
          572 &lt;div class="section" id="kernel-org-web-of-trust"&gt;
          573 &lt;h2&gt;Kernel.org web of trust&lt;/h2&gt;
          574 &lt;p&gt;PGP keys used by members of kernel.org are cross-signed by other members
          575 of the Linux kernel development community (and, frequently, by many
          576 other people). If you wanted to verify the validity of any key belonging
          577 to a member of kernel.org, you could review the list of signatures on
          578 their public key and then make a decision whether you trust that key or
          579 not. See the &lt;a class="reference external" href="https://en.wikipedia.org/wiki/Web_of_trust"&gt;Wikipedia article&lt;/a&gt; on the subject of the Web of Trust.&lt;/p&gt;
          580 &lt;/div&gt;
          581 &lt;div class="section" id="using-the-web-key-directory"&gt;
          582 &lt;h2&gt;Using the Web Key Directory&lt;/h2&gt;
          583 &lt;p&gt;If the task of maintaining your own web of trust is too daunting to you,
          584 you can opt to shortcut this process by using the &amp;quot;Trust on First Use&amp;quot;
          585 (TOFU) approach and rely on the kernel.org Web Key Directory (WKD).&lt;/p&gt;
          586 &lt;p&gt;To import keys belonging to many kernel developers, you can use the
          587 following command:&lt;/p&gt;
          588 &lt;pre class="literal-block"&gt;
          589 $ gpg2 --locate-keys [username]&amp;#64;kernel.org
          590 &lt;/pre&gt;
          591 &lt;p&gt;For example, to import keys belonging to Linus Torvalds and Greg
          592 Kroah-Hartman, you would use:&lt;/p&gt;
          593 &lt;pre class="literal-block"&gt;
          594 $ gpg2 --locate-keys torvalds&amp;#64;kernel.org gregkh&amp;#64;kernel.org
          595 &lt;/pre&gt;
          596 &lt;p&gt;This command will verify the TLS certificate presented by kernel.org
          597 before importing these keys into your keyring.&lt;/p&gt;
          598 &lt;/div&gt;
          599 &lt;div class="section" id="using-gnupg-to-verify-kernel-signatures"&gt;
          600 &lt;h2&gt;Using GnuPG to verify kernel signatures&lt;/h2&gt;
          601 &lt;p&gt;All software released via kernel.org has detached PGP signatures you can
          602 use to verify the integrity of your downloads.&lt;/p&gt;
          603 &lt;p&gt;To illustrate the verification process, let's use Linux 4.6.6 release as
          604 a walk-through example. First, use &amp;quot;&lt;tt class="docutils literal"&gt;curl&lt;/tt&gt;&amp;quot; to download the release
          605 and the corresponding signature:&lt;/p&gt;
          606 &lt;pre class="literal-block"&gt;
          607 $ curl -OL https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.6.6.tar.xz
          608 $ curl -OL https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.6.6.tar.sign
          609 &lt;/pre&gt;
          610 &lt;p&gt;You will notice that the signature is made against the uncompressed
          611 version of the archive. This is done so there is only one signature
          612 required for .gz and .xz compressed versions of the release. Start
          613 by uncompressing the archive, using &lt;tt class="docutils literal"&gt;unxz&lt;/tt&gt; in our case:&lt;/p&gt;
          614 &lt;pre class="literal-block"&gt;
          615 $ unxz linux-4.6.6.tar.xz
          616 &lt;/pre&gt;
          617 &lt;p&gt;Now verify the .tar archive against the signature:&lt;/p&gt;
          618 &lt;pre class="literal-block"&gt;
          619 $ gpg2 --verify linux-4.6.6.tar.sign
          620 &lt;/pre&gt;
          621 &lt;p&gt;You can combine these steps into a one-liner:&lt;/p&gt;
          622 &lt;pre class="literal-block"&gt;
          623 $ xz -cd linux-4.6.6.tar.xz | gpg2 --verify linux-4.6.6.tar.sign -
          624 &lt;/pre&gt;
          625 &lt;p&gt;It's possible that you get a &amp;quot;No public key error&amp;quot;:&lt;/p&gt;
          626 &lt;pre class="literal-block"&gt;
          627 gpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT using RSA key ID 38DBBDC86092693E
          628 gpg: Can't check signature: No public key
          629 &lt;/pre&gt;
          630 &lt;p&gt;Please use the &amp;quot;&lt;tt class="docutils literal"&gt;gpg2 &lt;span class="pre"&gt;--locate-keys&lt;/span&gt;&lt;/tt&gt;&amp;quot; command listed above to download
          631 the key for Greg Kroah-Hartman and Linus Torvalds and then try again:&lt;/p&gt;
          632 &lt;pre class="literal-block"&gt;
          633 $ gpg2 --locate-keys torvalds&amp;#64;kernel.org gregkh&amp;#64;kernel.org
          634 $ gpg2 --verify linux-4.6.6.tar.sign
          635 gpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT
          636 gpg:                using RSA key 38DBBDC86092693E
          637 gpg: Good signature from &amp;quot;Greg Kroah-Hartman &amp;lt;gregkh&amp;#64;kernel.org&amp;gt;&amp;quot; [unknown]
          638 gpg: WARNING: This key is not certified with a trusted signature!
          639 gpg:          There is no indication that the signature belongs to the owner.
          640 Primary key fingerprint: 647F 2865 4894 E3BD 4571  99BE 38DB BDC8 6092 693E
          641 &lt;/pre&gt;
          642 &lt;p&gt;To make the &amp;quot;&lt;tt class="docutils literal"&gt;WARNING&lt;/tt&gt;&amp;quot; message go away you can indicate that you
          643 choose to trust that key using TOFU:&lt;/p&gt;
          644 &lt;pre class="literal-block"&gt;
          645 $ gpg2 --tofu-policy good 38DBBDC86092693E
          646 $ gpg2 --trust-model tofu --verify linux-4.6.6.tar.sign
          647 gpg: Signature made Wed 10 Aug 2016 06:55:15 AM EDT
          648 gpg:                using RSA key 38DBBDC86092693E
          649 gpg: Good signature from &amp;quot;Greg Kroah-Hartman &amp;lt;gregkh&amp;#64;kernel.org&amp;gt;&amp;quot; [full]
          650 gpg: gregkh&amp;#64;kernel.org: Verified 1 signature in the past 53 seconds.  Encrypted
          651      0 messages.
          652 &lt;/pre&gt;
          653 &lt;p&gt;Note that you may have to pass &amp;quot;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;--trust-model&lt;/span&gt; tofu&lt;/tt&gt;&amp;quot; the first time
          654 you run the verify command, but it should not be necessary after that.&lt;/p&gt;
          655 &lt;div class="section" id="the-scripted-version"&gt;
          656 &lt;h3&gt;The scripted version&lt;/h3&gt;
          657 &lt;p&gt;If you need to perform this task in an automated environment or simply
          658 prefer a more convenient tool, you can use the following helper script
          659 to properly download and verify Linux kernel tarballs:&lt;/p&gt;
          660 &lt;blockquote&gt;
          661 &lt;ul class="simple"&gt;
          662 &lt;li&gt;&lt;a class="reference external" href="https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/get-verified-tarball"&gt;get-verified-tarball&lt;/a&gt;&lt;/li&gt;
          663 &lt;/ul&gt;
          664 &lt;/blockquote&gt;
          665 &lt;p&gt;Please review the script before adopting it for your needs.&lt;/p&gt;
          666 &lt;/div&gt;
          667 &lt;/div&gt;
          668 &lt;div class="section" id="important-fingerprints"&gt;
          669 &lt;h2&gt;Important fingerprints&lt;/h2&gt;
          670 &lt;p&gt;Here are key fingerprints for Linus Torvalds, Greg Kroah-Hartman, Sasha
          671 Levin, and Ben Hutchings, who are most likely to be releasing kernels:&lt;/p&gt;
          672 &lt;table border="1" class="docutils"&gt;
          673 &lt;colgroup&gt;
          674 &lt;col width="25%" /&gt;
          675 &lt;col width="75%" /&gt;
          676 &lt;/colgroup&gt;
          677 &lt;thead valign="bottom"&gt;
          678 &lt;tr&gt;&lt;th class="head"&gt;Developer&lt;/th&gt;
          679 &lt;th class="head"&gt;Fingerprint&lt;/th&gt;
          680 &lt;/tr&gt;
          681 &lt;/thead&gt;
          682 &lt;tbody valign="top"&gt;
          683 &lt;tr&gt;&lt;td&gt;Linus Torvalds&lt;/td&gt;
          684 &lt;td&gt;&lt;tt class="docutils literal"&gt;ABAF 11C6 5A29 70B1 30AB&amp;nbsp; E3C4 79BE 3E43 0041 1886&lt;/tt&gt;&lt;/td&gt;
          685 &lt;/tr&gt;
          686 &lt;tr&gt;&lt;td&gt;Greg Kroah-Hartman&lt;/td&gt;
          687 &lt;td&gt;&lt;tt class="docutils literal"&gt;647F 2865 4894 E3BD 4571&amp;nbsp; 99BE 38DB BDC8 6092 693E&lt;/tt&gt;&lt;/td&gt;
          688 &lt;/tr&gt;
          689 &lt;tr&gt;&lt;td&gt;Sasha Levin&lt;/td&gt;
          690 &lt;td&gt;&lt;tt class="docutils literal"&gt;E27E 5D8A 3403 A2EF 6687&amp;nbsp; 3BBC DEA6 6FF7 9777 2CDC&lt;/tt&gt;&lt;/td&gt;
          691 &lt;/tr&gt;
          692 &lt;tr&gt;&lt;td&gt;Ben Hutchings&lt;/td&gt;
          693 &lt;td&gt;&lt;tt class="docutils literal"&gt;AC2B 29BD 34A6 AFDD B3F6&amp;nbsp; 8F35 E7BF C8EC 9586 1109&lt;/tt&gt;&lt;/td&gt;
          694 &lt;/tr&gt;
          695 &lt;/tbody&gt;
          696 &lt;/table&gt;
          697 &lt;p&gt;Please verify the TLS certificate for this site in your browser before
          698 trusting the above information.&lt;/p&gt;
          699 &lt;/div&gt;
          700 &lt;div class="section" id="if-you-get-bad-signature"&gt;
          701 &lt;h2&gt;If you get &amp;quot;BAD signature&amp;quot;&lt;/h2&gt;
          702 &lt;p&gt;If at any time you see &amp;quot;BAD signature&amp;quot; output from &amp;quot;&lt;tt class="docutils literal"&gt;gpg2 &lt;span class="pre"&gt;--verify&lt;/span&gt;&lt;/tt&gt;&amp;quot;,
          703 please first check the following first:&lt;/p&gt;
          704 &lt;ol class="arabic simple"&gt;
          705 &lt;li&gt;&lt;strong&gt;Make sure that you are verifying the signature against the .tar
          706 version of the archive, not the compressed (.tar.xz) version.&lt;/strong&gt;&lt;/li&gt;
          707 &lt;li&gt;Make sure the the downloaded file is correct and not truncated or
          708 otherwise corrupted.&lt;/li&gt;
          709 &lt;/ol&gt;
          710 &lt;p&gt;If you repeatedly get the same &amp;quot;BAD signature&amp;quot; output, please email
          711 &lt;a class="reference external" href="mailto:helpdesk&amp;#64;kernel.org"&gt;helpdesk&amp;#64;kernel.org&lt;/a&gt;, so we can investigate the problem.&lt;/p&gt;
          712 &lt;/div&gt;
          713 &lt;div class="section" id="kernel-org-checksum-autosigner-and-sha256sums-asc"&gt;
          714 &lt;h2&gt;Kernel.org checksum autosigner and sha256sums.asc&lt;/h2&gt;
          715 &lt;p&gt;We have a dedicated off-the-network system that connects directly to our
          716 central attached storage and calculates checksums for all uploaded
          717 software releases. The generated &lt;tt class="docutils literal"&gt;sha256sums.asc&lt;/tt&gt; file is then signed
          718 with a PGP key generated for this purpose and that doesn't exist outside
          719 of that system.&lt;/p&gt;
          720 &lt;p&gt;These checksums are &lt;strong&gt;NOT&lt;/strong&gt; intended to replace developer signatures. It
          721 is merely a way for someone to quickly verify whether contents on one of
          722 the many kernel.org mirrors match the contents on the master mirror.
          723 While you may use them to quickly verify whether what you have
          724 downloaded matches what we have on our central storage system, you
          725 should continue to use developer signatures for best assurance.&lt;/p&gt;
          726 &lt;/div&gt;
          727 &lt;div class="section" id="kernel-releases-prior-to-september-2011"&gt;
          728 &lt;h2&gt;Kernel releases prior to September, 2011&lt;/h2&gt;
          729 &lt;p&gt;Prior to September, 2011 all kernel releases were signed automatically by
          730 the same PGP key:&lt;/p&gt;
          731 &lt;pre class="literal-block"&gt;
          732 pub   1024D/517D0F0E 2000-10-10 [revoked: 2011-12-11]
          733       Key fingerprint = C75D C40A 11D7 AF88 9981  ED5B C86B A06A 517D 0F0E
          734 uid                  Linux Kernel Archives Verification Key &amp;lt;ftpadmin&amp;#64;kernel.org&amp;gt;
          735 &lt;/pre&gt;
          736 &lt;p&gt;Due to the kernel.org systems compromise, this key has been retired and
          737 revoked. &lt;strong&gt;It will no longer be used to sign future releases and you
          738 should NOT use this key to verify the integrity of any archives. It is
          739 almost certain that this key has fallen into malicious hands.&lt;/strong&gt;&lt;/p&gt;
          740 &lt;p&gt;All kernel releases that were previously signed with this key were
          741 cross-checked and signed with another key, created specifically
          742 for this purpose:&lt;/p&gt;
          743 &lt;pre class="literal-block"&gt;
          744 pub   3072R/C4790F9D 2013-08-08
          745       Key fingerprint = BFA7 DD3E 0D42 1C9D B6AB  6527 0D3B 3537 C479 0F9D
          746 uid   Linux Kernel Archives Verification Key
          747       (One-off resigning of old releases) &amp;lt;ftpadmin&amp;#64;kernel.org&amp;gt;
          748 &lt;/pre&gt;
          749 &lt;p&gt;The private key used for this purpose has been destroyed and cannot be
          750 used to sign any releases produced after 2011.&lt;/p&gt;
          751 &lt;/div&gt;
          752 </summary></entry><entry><title>RC tarballs and patches starting with 4.12-rc1</title><link href="https://www.kernel.org/rc-tarballs-and-patches-starting-with-412-rc1.html" rel="alternate"></link><published>2017-05-16T00:00:00+00:00</published><updated>2017-05-16T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-05-16:rc-tarballs-and-patches-starting-with-412-rc1.html</id><summary type="html">&lt;p&gt;As you may be aware, starting with 4.12-rc1 Linus will &lt;a class="reference external" href="https://lwn.net/Articles/722660/"&gt;no longer provide&lt;/a&gt;
          753 signed tarballs and patches for pre-release (&amp;quot;-rc&amp;quot;) kernels. Reasons for
          754 this are multiple, but largely this is because people who are most
          755 interested in pre-release tags -- kernel developers -- do not rely on
          756 patches and tarballs to do their work.&lt;/p&gt;
          757 &lt;div class="section" id="obtaining-tarballs-on-your-own"&gt;
          758 &lt;h2&gt;Obtaining tarballs on your own&lt;/h2&gt;
          759 &lt;p&gt;Here is how you can generate the tarball from a pre-release tag using
          760 the &amp;quot;&lt;tt class="docutils literal"&gt;git archive&lt;/tt&gt;&amp;quot; command (we'll use 4.12-rc1 in these examples):&lt;/p&gt;
          761 &lt;pre class="literal-block"&gt;
          762 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
          763 cd linux
          764 git verify-tag v4.12-rc1
          765 git archive --format=tar.gz --prefix=linux-4.12-rc1/ \
          766   -o linux-4.12-rc1.tar.gz v4.12-rc1
          767 &lt;/pre&gt;
          768 &lt;p&gt;The upside of this method is that during the &amp;quot;&lt;tt class="docutils literal"&gt;git &lt;span class="pre"&gt;verify-tag&lt;/span&gt;&lt;/tt&gt;&amp;quot; step
          769 you will check the PGP signature on the tag to make sure that what you
          770 cloned is exactly the same tree as on Linus Torvalds's computer.&lt;/p&gt;
          771 &lt;p&gt;The downside of this method is that you will need to download about 1
          772 GiB of data -- the entire git history of the Linux kernel -- just to get
          773 the latest tag. Notably, when -rc2 is tagged, all you'll need to do is
          774 run a quick &amp;quot;&lt;tt class="docutils literal"&gt;git pull&lt;/tt&gt;&amp;quot; to get the latest objects and it will be
          775 dramatically less data to download, so cloning the whole tree may be
          776 worth it to you in the long run if you plan to do this again in the
          777 future.&lt;/p&gt;
          778 &lt;p&gt;If you do not want to download the whole git repository and just want to
          779 get the latest tarball, you can download the version automatically
          780 generated by cgit at the following (or similar URL):&lt;/p&gt;
          781 &lt;pre class="literal-block"&gt;
          782 wget https://git.kernel.org/torvalds/t/linux-4.12-rc1.tar.gz
          783 &lt;/pre&gt;
          784 &lt;p&gt;Please note that you will not be able to cryptographically verify the
          785 integrity of this archive, but the download will be about 10 times less
          786 in size than the full git tree.&lt;/p&gt;
          787 &lt;/div&gt;
          788 &lt;div class="section" id="obtaining-patches-to-the-previous-mainline"&gt;
          789 &lt;h2&gt;Obtaining patches to the previous mainline&lt;/h2&gt;
          790 &lt;p&gt;If you would like to get just the patch to the previous mainline
          791 release, you can get it from cgit as well:&lt;/p&gt;
          792 &lt;pre class="literal-block"&gt;
          793 wget -O patch-4.12-rc1 https://git.kernel.org/torvalds/p/v4.12-rc1/v4.11
          794 &lt;/pre&gt;
          795 &lt;p&gt;Unfortunately, cgit does not currently offer an easy way to get
          796 gzip-compressed patches, but if you would like to reduce the amount of
          797 data you download, you can use http-level gzip compression:&lt;/p&gt;
          798 &lt;pre class="literal-block"&gt;
          799 wget -O patch-4.12-rc1.gz --header=&amp;quot;accept-encoding: gzip&amp;quot; \
          800   https://git.kernel.org/torvalds/p/v4.12-rc1/v4.11
          801 &lt;/pre&gt;
          802 &lt;p&gt;The links to these patches are available on the front page of
          803 &lt;a class="reference external" href="https://www.kernel.org/"&gt;https://www.kernel.org/&lt;/a&gt;.&lt;/p&gt;
          804 &lt;/div&gt;
          805 &lt;div class="section" id="why-not-provide-these-at-their-old-locations"&gt;
          806 &lt;h2&gt;Why not provide these at their old locations?&lt;/h2&gt;
          807 &lt;p&gt;We intentionally did not provide these automatically generated tarballs
          808 and patches in locations previously used by Linus
          809 (&lt;tt class="docutils literal"&gt;/pub/linux/kernel/v4.x/testing&lt;/tt&gt;), even if this meant potentially
          810 breaking automated scripts relying on contents published there. Anything
          811 placed in the /pub tree is signed and curated directly by developers
          812 and all patches and software archives published there invariably come
          813 with a PGP signature provided directly by the developer of that software
          814 (or one of the developers).&lt;/p&gt;
          815 &lt;p&gt;Patches and tarballs automatically generated by git.kernel.org are NOT
          816 a replacement for this stringent process, but merely a convenience
          817 service that comes with very different trust implications. By providing
          818 these at different URLs we wanted all users of these services to make a
          819 conscious decision on whether they want to trust these automatically
          820 generated tarballs and patches, or whether they want to change their
          821 process to continue to use PGP-verifiable tags directly from the git
          822 tree.&lt;/p&gt;
          823 &lt;/div&gt;
          824 </summary></entry><entry><title>If you got "BAD Signature" this morning</title><link href="https://www.kernel.org/if-you-got-bad-signature-this-morning.html" rel="alternate"></link><published>2017-05-14T00:00:00+00:00</published><updated>2017-05-14T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-05-14:if-you-got-bad-signature-this-morning.html</id><summary type="html">&lt;p&gt;The XZ tarballs for the following kernel releases did not initially pass
          825 signature verification due to benign changes to the tarball structure
          826 done by the pixz compression tool:&lt;/p&gt;
          827 &lt;ul class="simple"&gt;
          828 &lt;li&gt;4.11.1&lt;/li&gt;
          829 &lt;li&gt;4.10.16&lt;/li&gt;
          830 &lt;li&gt;4.9.28&lt;/li&gt;
          831 &lt;li&gt;4.4.68&lt;/li&gt;
          832 &lt;/ul&gt;
          833 &lt;p&gt;These changes would have resulted in GPG returning &amp;quot;Bad Signature&amp;quot; if
          834 you tried to verify their integrity. Once we identified the problem, we
          835 generated new XZ tarballs without tar header modifications and now they
          836 should all pass PGP signature verification.&lt;/p&gt;
          837 &lt;p&gt;We preserved the original .xz tarballs as -badsig files in the archives
          838 in case you wanted to verify that there was nothing malicious in them,
          839 merely tar header changes. You can find them in the same v4.x directory:&lt;/p&gt;
          840 &lt;ul class="simple"&gt;
          841 &lt;li&gt;&lt;a class="reference external" href="https://www.kernel.org/pub/linux/kernel/v4.x/"&gt;https://www.kernel.org/pub/linux/kernel/v4.x/&lt;/a&gt;&lt;/li&gt;
          842 &lt;/ul&gt;
          843 &lt;p&gt;Our apologies for this problem and thanks to Brad Spengler and everyone
          844 else who alerted us about this issue.&lt;/p&gt;
          845 </summary></entry><entry><title>The Linux Kernel Organization</title><link href="https://www.kernel.org/nonprofit.html" rel="alternate"></link><published>2017-04-13T06:05:03+00:00</published><updated>2017-04-13T06:05:03+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-04-13:nonprofit.html</id><summary type="html">&lt;p&gt;The Linux Kernel Organization is a California Public Benefit Corporation
          846 established in 2002 to distribute the Linux kernel and other Open Source
          847 software to the public without charge. We are recognized by the IRS as a
          848 501(c)3 private operating foundation.&lt;/p&gt;
          849 &lt;ul class="simple"&gt;
          850 &lt;li&gt;&lt;a class="reference external" href="https://www.kernel.org/static/corporate/irs-nonprofit-ok-redacted.pdf"&gt;IRS determination letter&lt;/a&gt;&lt;/li&gt;
          851 &lt;li&gt;&lt;a class="reference external" href="https://www.kernel.org/static/corporate/state-nonprofit-ok-redacted.pdf"&gt;California determination letter&lt;/a&gt;&lt;/li&gt;
          852 &lt;/ul&gt;
          853 &lt;p&gt;The Linux Kernel Organization is managed by &lt;a class="reference external" href="http://linuxfoundation.org/"&gt;The Linux Foundation&lt;/a&gt;, which
          854 provides full technical, financial and staffing support for running and
          855 maintaining the kernel.org infrastructure.&lt;/p&gt;
          856 &lt;div class="section" id="legal-information"&gt;
          857 &lt;h2&gt;Legal information&lt;/h2&gt;
          858 &lt;p&gt;Due to U.S. Exports Regulations, all cryptographic software on this site
          859 is subject to the following legal notice:&lt;/p&gt;
          860 &lt;blockquote&gt;
          861 &lt;strong&gt;This site includes publicly available encryption source code which,
          862 together with object code resulting from the compiling of publicly
          863 available source code, may be exported from the United States under
          864 License Exception &amp;quot;TSU&amp;quot; pursuant to 15 C.F.R. Section 740.13(e).&lt;/strong&gt;&lt;/blockquote&gt;
          865 &lt;p&gt;This legal notice applies to cryptographic software only. Please see the
          866 &lt;a class="reference external" href="https://www.bis.doc.gov/"&gt;Bureau of Industry and Security&lt;/a&gt; for more information about current U.S.
          867 regulations.&lt;/p&gt;
          868 &lt;p&gt;Our servers are located in Corvallis, Oregon, USA; Palo Alto and San
          869 Francisco, California, USA; Portland, Oregon, USA; and Montréal, Québec,
          870 Canada.&lt;/p&gt;
          871 &lt;p&gt;Use in violation of any applicable laws is prohibited.&lt;/p&gt;
          872 &lt;p&gt;Linux is a Registered Trademark of Linus Torvalds. All trademarks are
          873 property of their respective owners.&lt;/p&gt;
          874 &lt;/div&gt;
          875 </summary></entry><entry><title>About Linux Kernel</title><link href="https://www.kernel.org/linux.html" rel="alternate"></link><published>2017-04-13T06:05:03+00:00</published><updated>2017-04-13T06:05:03+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-04-13:linux.html</id><summary type="html">&lt;div class="section" id="what-is-linux"&gt;
          876 &lt;h2&gt;What is Linux?&lt;/h2&gt;
          877 &lt;p&gt;Linux is a clone of the operating system Unix, written from scratch by
          878 Linus Torvalds with assistance from a loosely-knit team of hackers
          879 across the Net. It aims towards POSIX and &lt;a class="reference external" href="http://www.unix.org/"&gt;Single UNIX Specification&lt;/a&gt;
          880 compliance.&lt;/p&gt;
          881 &lt;p&gt;It has all the features you would expect in a modern fully-fledged Unix,
          882 including true multitasking, virtual memory, shared libraries, demand
          883 loading, shared copy-on-write executables, proper memory management, and
          884 multistack networking including IPv4 and IPv6.&lt;/p&gt;
          885 &lt;p&gt;Although originally developed first for 32-bit x86-based PCs (386 or
          886 higher), today Linux also runs on a multitude of other processor
          887 architectures, in both 32- and 64-bit variants.&lt;/p&gt;
          888 &lt;/div&gt;
          889 &lt;div class="section" id="new-to-linux"&gt;
          890 &lt;h2&gt;New to Linux?&lt;/h2&gt;
          891 &lt;p&gt;If you're new to Linux, you don't want to download the kernel, which is
          892 just a component in a working Linux system. Instead, you want what is
          893 called a distribution of Linux, which is a complete Linux system. There
          894 are numerous distributions available for download on the Internet as
          895 well as for purchase from various vendors; some are general-purpose, and
          896 some are optimized for specific uses. We currently have mirrors of
          897 several distributions available at &lt;a class="reference external" href="https://mirrors.kernel.org/"&gt;https://mirrors.kernel.org/&lt;/a&gt;.&lt;/p&gt;
          898 &lt;p&gt;Note, however, that most distributions are very large (several
          899 gigabytes), so unless you have a fast Internet link you may want to save
          900 yourself some hassle and purchase a CD-ROM with a distribution; such
          901 CD-ROMs are available from a number of vendors.&lt;/p&gt;
          902 &lt;/div&gt;
          903 &lt;div class="section" id="mailing-lists"&gt;
          904 &lt;h2&gt;Mailing lists&lt;/h2&gt;
          905 &lt;p&gt;The Linux kernel is discussed on the linux-kernel mailing list at
          906 &lt;a class="reference external" href="http://vger.kernel.org/"&gt;vger.kernel.org&lt;/a&gt;. Please read the &lt;a class="reference external" href="http://www.tux.org/lkml/"&gt;FAQ&lt;/a&gt; before subscribing.&lt;/p&gt;
          907 &lt;p&gt;Although there is no official archive site, unofficial archives of the list can be found at:&lt;/p&gt;
          908 &lt;ul class="simple"&gt;
          909 &lt;li&gt;&lt;a class="reference external" href="https://lkml.org/"&gt;https://lkml.org/&lt;/a&gt;&lt;/li&gt;
          910 &lt;li&gt;&lt;a class="reference external" href="https://marc.info/?l=linux-kernel"&gt;https://marc.info/?l=linux-kernel&lt;/a&gt;&lt;/li&gt;
          911 &lt;/ul&gt;
          912 &lt;/div&gt;
          913 </summary></entry><entry><title>Contacts</title><link href="https://www.kernel.org/contact.html" rel="alternate"></link><published>2017-04-13T06:05:03+00:00</published><updated>2017-04-13T06:05:03+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-04-13:contact.html</id><summary type="html">&lt;p&gt;Email is the only reliable way of contacting Kernel.org administrators.&lt;/p&gt;
          914 &lt;div class="section" id="general-contacts"&gt;
          915 &lt;h2&gt;General contacts&lt;/h2&gt;
          916 &lt;dl class="docutils"&gt;
          917 &lt;dt&gt;&lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt;:&lt;/dt&gt;
          918 &lt;dd&gt;General requests and comments about kernel.org infrastructure.&lt;/dd&gt;
          919 &lt;dt&gt;&lt;a class="reference external" href="mailto:ftpadmin&amp;#64;kernel.org"&gt;ftpadmin&amp;#64;kernel.org&lt;/a&gt;:&lt;/dt&gt;
          920 &lt;dd&gt;Questions or comments about kernel.org mirrors.&lt;/dd&gt;
          921 &lt;dt&gt;&lt;a class="reference external" href="mailto:keys&amp;#64;kernel.org"&gt;keys&amp;#64;kernel.org&lt;/a&gt;:&lt;/dt&gt;
          922 &lt;dd&gt;Account requests (see &lt;a class="reference external" href="https://www.kernel.org/faq.html"&gt;FAQ&lt;/a&gt;)&lt;/dd&gt;
          923 &lt;/dl&gt;
          924 &lt;p&gt;&lt;strong&gt;Please do not send general Linux questions or bug reports to these
          925 addresses. We do not have the resources to reply to them.&lt;/strong&gt;&lt;/p&gt;
          926 &lt;p&gt;Please try the following sites for general Linux help:&lt;/p&gt;
          927 &lt;ul class="simple"&gt;
          928 &lt;li&gt;&lt;a class="reference external" href="https://superuser.com/"&gt;https://superuser.com/&lt;/a&gt; - for computer enthusiasts and power users&lt;/li&gt;
          929 &lt;li&gt;&lt;a class="reference external" href="https://serverfault.com/"&gt;https://serverfault.com/&lt;/a&gt; - for systems administrators&lt;/li&gt;
          930 &lt;li&gt;&lt;a class="reference external" href="https://askubuntu.com/"&gt;https://askubuntu.com/&lt;/a&gt; - for users of Ubuntu Linux&lt;/li&gt;
          931 &lt;/ul&gt;
          932 &lt;p&gt;Linux Foundation also offers training opportunities if you are
          933 interested in learning more about Linux, want to become a more
          934 proficient Linux systems administrator, or want to know more about how
          935 Linux can help your company succeed.&lt;/p&gt;
          936 &lt;ul class="simple"&gt;
          937 &lt;li&gt;&lt;a class="reference external" href="https://training.linuxfoundation.org/"&gt;https://training.linuxfoundation.org/&lt;/a&gt;&lt;/li&gt;
          938 &lt;/ul&gt;
          939 &lt;/div&gt;
          940 &lt;div class="section" id="mailing-address"&gt;
          941 &lt;h2&gt;Mailing address&lt;/h2&gt;
          942 &lt;p&gt;Please send any mail correspondence to the Linux Foundation:&lt;/p&gt;
          943 &lt;blockquote&gt;
          944 &lt;div class="line-block"&gt;
          945 &lt;div class="line"&gt;The Linux Foundation&lt;/div&gt;
          946 &lt;div class="line"&gt;1 Letterman Drive&lt;/div&gt;
          947 &lt;div class="line"&gt;Building D, Suite D4700&lt;/div&gt;
          948 &lt;div class="line"&gt;San Francisco, CA 94129&lt;/div&gt;
          949 &lt;div class="line"&gt;Phone/Fax: +1 415 723 9709&lt;/div&gt;
          950 &lt;/div&gt;
          951 &lt;/blockquote&gt;
          952 &lt;/div&gt;
          953 </summary></entry><entry><title>Fast new frontends with Packet</title><link href="https://www.kernel.org/fast-new-frontends-with-packet.html" rel="alternate"></link><published>2017-03-11T00:00:00+00:00</published><updated>2017-03-11T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-03-11:fast-new-frontends-with-packet.html</id><summary type="html">&lt;img alt="Packet logo" class="align-left" src="https://www.kernel.org/static/news/images/packet-logo.png" style="width: 176px; height: 60px;" /&gt;
          954 &lt;p&gt;We are extremely happy to announce that &lt;a class="reference external" href="https://www.packet.net/"&gt;Packet&lt;/a&gt; has graciously donated
          955 the new hardware systems providing read-only public access to the
          956 kernel.org git repositories and the public website (git.kernel.org and
          957 www.kernel.org, respectively). We have avoided using cloud providers in
          958 the past due to security implications of sharing hypervisor memory with
          959 external parties, but Packet's hardware-based single-tenant approach
          960 satisfies our security requirements while taking over the burden of
          961 setting up and managing the physical hardware in multiple worldwide
          962 datacenters.&lt;/p&gt;
          963 &lt;p&gt;As of March 11, 2017, the four new public frontends are located in the
          964 following geographical locations:&lt;/p&gt;
          965 &lt;ul class="simple"&gt;
          966 &lt;li&gt;San Jose, California, USA&lt;/li&gt;
          967 &lt;li&gt;Parsippany, New Jersey, USA&lt;/li&gt;
          968 &lt;li&gt;Amsterdam, Netherlands&lt;/li&gt;
          969 &lt;li&gt;Tokyo, Japan&lt;/li&gt;
          970 &lt;/ul&gt;
          971 &lt;p&gt;We have changed our DNS configuration to support GeoDNS, so your
          972 requests should be routed to the frontend nearest to you.&lt;/p&gt;
          973 &lt;p&gt;Each Packet-hosted system is &lt;a class="reference external" href="https://www.packet.net/bare-metal/servers/type-2-virtualization/"&gt;significantly more powerful&lt;/a&gt; than our
          974 previous generation frontends and have triple the amount of available
          975 RAM, so they should be a lot more responsive even when a lot of people
          976 are cloning linux.git simultaneously.&lt;/p&gt;
          977 &lt;p&gt;Our special thanks to the following organizations who have graciously
          978 donated hosting for the previous incarnation of kernel.org frontends:&lt;/p&gt;
          979 &lt;ul class="simple"&gt;
          980 &lt;li&gt;&lt;a class="reference external" href="https://www.isc.org/"&gt;Internet Systems Consortium&lt;/a&gt;&lt;/li&gt;
          981 &lt;li&gt;&lt;a class="reference external" href="https://www.vexxhost.com/"&gt;Vexxhost&lt;/a&gt;&lt;/li&gt;
          982 &lt;li&gt;&lt;a class="reference external" href="https://www.tizen.org/"&gt;Tizen&lt;/a&gt;&lt;/li&gt;
          983 &lt;/ul&gt;
          984 &lt;p&gt;If you notice any problems with the new systems, please email
          985 &lt;a class="reference external" href="mailto:helpdesk&amp;#64;kernel.org"&gt;helpdesk&amp;#64;kernel.org&lt;/a&gt;.&lt;/p&gt;
          986 </summary></entry><entry><title>Shutting down FTP services</title><link href="https://www.kernel.org/shutting-down-ftp-services.html" rel="alternate"></link><published>2017-01-27T00:00:00+00:00</published><updated>2017-01-27T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2017-01-27:shutting-down-ftp-services.html</id><summary type="html">&lt;p&gt;Those of you who have been around for a while may remember a time when
          987 you used to be able to mount kernel.org directly as a partition on your
          988 system using NFS (or even SMB/CIFS). The Wayback Machine shows that this
          989 was still advertised some time in &lt;a class="reference external" href="https://web.archive.org/web/19980130085039/http://www.kernel.org/"&gt;January 1998&lt;/a&gt;, but was removed by
          990 the time the &lt;a class="reference external" href="https://web.archive.org/web/19981212030306/http://www.kernel.org/"&gt;December 1998&lt;/a&gt; copy was made.&lt;/p&gt;
          991 &lt;p&gt;Let's face it -- while kinda neat and convenient, offering a public
          992 NFS/CIFS server was a Pretty Bad Idea, not only because both these
          993 protocols are pretty terrible over high latency connections, but also
          994 because of important security implications.&lt;/p&gt;
          995 &lt;p&gt;Well, 19 years later we're thinking it's time to terminate another
          996 service that has important protocol and security implications -- our
          997 FTP servers. Our decision is driven by the following considerations:&lt;/p&gt;
          998 &lt;ul class="simple"&gt;
          999 &lt;li&gt;The protocol is inefficient and requires adding awkward kludges to
         1000 firewalls and load-balancing daemons&lt;/li&gt;
         1001 &lt;li&gt;FTP servers have no support for caching or accelerators, which has
         1002 significant performance impacts&lt;/li&gt;
         1003 &lt;li&gt;Most software implementations have stagnated and see infrequent updates&lt;/li&gt;
         1004 &lt;/ul&gt;
         1005 &lt;p&gt;All kernel.org FTP services will be shut down by the end of this year.
         1006 In hopes to minimise the potential disruption, we will be doing it in
         1007 two stages:&lt;/p&gt;
         1008 &lt;ol class="arabic simple"&gt;
         1009 &lt;li&gt;&lt;a class="reference external" href="ftp://ftp.kernel.org/"&gt;ftp://ftp.kernel.org/&lt;/a&gt; service will be terminated on March 1, 2017&lt;/li&gt;
         1010 &lt;li&gt;&lt;a class="reference external" href="ftp://mirrors.kernel.org/"&gt;ftp://mirrors.kernel.org/&lt;/a&gt; service will be terminated on December 1, 2017&lt;/li&gt;
         1011 &lt;/ol&gt;
         1012 &lt;p&gt;If you have any concerns, please feel free to contact
         1013 &lt;a class="reference external" href="mailto:ftpadmin&amp;#64;kernel.org"&gt;ftpadmin&amp;#64;kernel.org&lt;/a&gt; (ah, the irony).&lt;/p&gt;
         1014 </summary></entry><entry><title>Gandi.net TLS certificates</title><link href="https://www.kernel.org/gandinet-tls-certificates.html" rel="alternate"></link><published>2016-10-11T00:00:00+00:00</published><updated>2016-10-11T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2016-10-11:gandinet-tls-certificates.html</id><summary type="html">&lt;img alt="Gandi logo" class="align-left" src="https://www.kernel.org/static/news/images/gandi-logo.png" style="width: 202px; height: 60px;" /&gt;
         1015 &lt;p&gt;If your browser alerted you that the site certificates have changed,
         1016 that would be because we replaced our StartCOM, Ltd certificates with
         1017 those offered by our DNS registrar, &lt;a class="reference external" href="https://gandi.net/"&gt;Gandi&lt;/a&gt;. We are very thankful to
         1018 Gandi for this opportunity.&lt;/p&gt;
         1019 &lt;p&gt;A common question is why we aren't using the certificates offered by the
         1020 &lt;a class="reference external" href="https://letsencrypt.org/"&gt;Let's Encrypt project&lt;/a&gt;, and the answer is that there are several
         1021 technical hurdles (on our end) that currently make it complicated. Once
         1022 we resolve them, we will most likely switch to using certificates issued
         1023 by our fellow Linux Foundation project.&lt;/p&gt;
         1024 </summary></entry><entry><title>Cloning Linux from a bundle</title><link href="https://www.kernel.org/cloning-linux-from-a-bundle.html" rel="alternate"></link><published>2016-03-02T00:00:00+00:00</published><updated>2016-03-02T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2016-03-02:cloning-linux-from-a-bundle.html</id><summary type="html">&lt;p&gt;If you find yourself on an unreliable Internet connection and need to
         1025 perform a fresh clone of Linux.git, you may find it tricky to do so if
         1026 your connection resets before you are able to complete the clone. There
         1027 is currently no way to resume a git clone using git, but there is a neat
         1028 trick you can use instead of cloning directly -- using &lt;a class="reference external" href="https://git-scm.com/docs/git-bundle"&gt;git bundle&lt;/a&gt;
         1029 files.&lt;/p&gt;
         1030 &lt;p&gt;Here is how you would do it.&lt;/p&gt;
         1031 &lt;ol class="arabic"&gt;
         1032 &lt;li&gt;&lt;p class="first"&gt;Start with &amp;quot;&lt;tt class="docutils literal"&gt;wget &lt;span class="pre"&gt;-c&lt;/span&gt;&lt;/tt&gt;&amp;quot;, which tells wget to continue interrupted
         1033 downloads. If your connection resets, just rerun the same command while
         1034 in the same directory, and it will pick up where it left off:&lt;/p&gt;
         1035 &lt;pre class="literal-block"&gt;
         1036 wget -c https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/clone.bundle
         1037 &lt;/pre&gt;
         1038 &lt;/li&gt;
         1039 &lt;li&gt;&lt;p class="first"&gt;Once the download is completed, verify that the bundle has downloaded
         1040 correctly:&lt;/p&gt;
         1041 &lt;pre class="literal-block"&gt;
         1042 git bundle verify clone.bundle
         1043 ...
         1044 clone.bundle is okay
         1045 &lt;/pre&gt;
         1046 &lt;/li&gt;
         1047 &lt;li&gt;&lt;p class="first"&gt;Next, clone from the bundle:&lt;/p&gt;
         1048 &lt;pre class="literal-block"&gt;
         1049 git clone clone.bundle linux
         1050 &lt;/pre&gt;
         1051 &lt;/li&gt;
         1052 &lt;li&gt;&lt;p class="first"&gt;Now, point the origin to the live git repository and get the latest changes:&lt;/p&gt;
         1053 &lt;pre class="literal-block"&gt;
         1054 cd linux
         1055 git remote remove origin
         1056 git remote add origin https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
         1057 git pull origin master
         1058 &lt;/pre&gt;
         1059 &lt;/li&gt;
         1060 &lt;/ol&gt;
         1061 &lt;p&gt;Once this is done, you can delete the &amp;quot;&lt;tt class="docutils literal"&gt;clone.bundle&lt;/tt&gt;&amp;quot; file, unless
         1062 you think you will need to perform a fresh clone again in the future.&lt;/p&gt;
         1063 &lt;p&gt;The &amp;quot;&lt;tt class="docutils literal"&gt;clone.bundle&lt;/tt&gt;&amp;quot; files are generated weekly on Sunday, so they
         1064 should contain most objects you need, even during kernel merge windows
         1065 when there are lots of changes committed daily.&lt;/p&gt;
         1066 </summary></entry><entry><title>Introducing Fastly CDN</title><link href="https://www.kernel.org/introducing-fastly-cdn.html" rel="alternate"></link><published>2015-10-05T00:00:00+00:00</published><updated>2015-10-05T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2015-10-05:introducing-fastly-cdn.html</id><summary type="html">&lt;img alt="Fastly logo" class="align-left" src="https://www.kernel.org/static/news/images/fastly-logo.png" style="width: 156px; height: 60px;" /&gt;
         1067 &lt;p&gt;We are happy to announce that &lt;a class="reference external" href="https://fastly.com/"&gt;Fastly&lt;/a&gt; has offered their worldwide CDN
         1068 network to provide fast download services for Linux kernel releases,
         1069 which should improve download speeds for those of you located outside
         1070 North America. We have modified the front page to offer CDN-powered
         1071 download links, but all the existing URLs should continue to work.&lt;/p&gt;
         1072 &lt;p&gt;If you would like to avoid using Fastly, you can simply change the URL
         1073 to have &amp;quot;www.kernel.org&amp;quot; instead of &amp;quot;cdn.kernel.org&amp;quot;. As always, please
         1074 use &lt;a class="reference external" href="https://kernel.org/signature.html"&gt;PGP Signature Verification&lt;/a&gt; for all downloaded files regardless of
         1075 where you got them.&lt;/p&gt;
         1076 </summary></entry><entry><title>Hurr, Durr Im'a Sheep</title><link href="https://www.kernel.org/hurr-durr-ima-sheep.html" rel="alternate"></link><published>2015-04-01T00:00:00+00:00</published><updated>2015-04-01T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2015-04-01:hurr-durr-ima-sheep.html</id><summary type="html">&lt;p&gt;Linus named the upcoming 4.0 release of the kernel &amp;quot;Hurr Durr I'ma
         1077 Sheep&amp;quot; (see his &lt;a class="reference external" href="https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c517d838eb7d07bbe9507871fab3931deccff539"&gt;git commit&lt;/a&gt;), so we are celebrating this April Fool's
         1078 day with a minor prank. If you've been redirected to
         1079 &lt;a class="reference external" href="https://imasheep.hurrdurr.org/"&gt;imasheep.hurrdurr.org&lt;/a&gt;, do not panic. It's all part of the joke.&lt;/p&gt;
         1080 &lt;p&gt;We've also restored all FTP and Rsync access to the
         1081 &lt;a class="reference external" href="https://mirrors.kernel.org/"&gt;mirrors.kernel.org&lt;/a&gt; servers, as we seem to have resolved our SSD
         1082 and dm_cache problems. If you're still using FTP, however, please
         1083 consider switching to HTTP. FTP is a protocol designed for a different
         1084 era -- these days everyone should be avoiding it for &lt;a class="reference external" href="http://mywiki.wooledge.org/FtpMustDie"&gt;multiple
         1085 reasons&lt;/a&gt;.&lt;/p&gt;
         1086 </summary></entry><entry><title>FTP limited on mirrors.kernel.org</title><link href="https://www.kernel.org/ftp-limited-on-mirrorskernelorg.html" rel="alternate"></link><published>2015-02-03T00:00:00+00:00</published><updated>2015-02-03T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2015-02-03:ftp-limited-on-mirrorskernelorg.html</id><summary type="html">&lt;p&gt;We've had to temporarily limit FTP access to mirrors.kernel.org due
         1087 to high IO load.&lt;/p&gt;
         1088 &lt;p&gt;We have recently upgraded our hardware in order to increase capacity --
         1089 16TB was no longer nearly sufficient enough to host all the distro
         1090 mirrors and archives. We chose larger but slower disks and offset the
         1091 loss of performance by heavily utilizing SSD IO caching using dm-cache.&lt;/p&gt;
         1092 &lt;p&gt;While it was performing very well, we have unfortunately run across an
         1093 FS data corruption bug somewhere along this stack:&lt;/p&gt;
         1094 &lt;pre class="literal-block"&gt;
         1095 megaraid_sas + dm_cache + libvirt/virtio + xfs
         1096 &lt;/pre&gt;
         1097 &lt;p&gt;We've temporarily removed dm-cache from the picture and switched to
         1098 Varnish on top of SSD for http object caching. Unfortunately, as Varnish
         1099 does not support FTP, we had to restrict FTP protocol to a limited
         1100 number of concurrent sessions in order to reduce disk IO. If you are
         1101 affected by this, simply switch to HTTP protocol that does not have such
         1102 restrictions.&lt;/p&gt;
         1103 &lt;p&gt;This is a temporary measure until we identify the dm-cache problem that
         1104 was causing data corruption, at which point we will restore unrestricted
         1105 FTP access.&lt;/p&gt;
         1106 </summary></entry><entry><title>Heartbleed statement</title><link href="https://www.kernel.org/heartbleed-statement.html" rel="alternate"></link><published>2014-04-10T00:00:00+00:00</published><updated>2014-04-10T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2014-04-10:heartbleed-statement.html</id><summary type="html">&lt;p&gt;Since we rely on the OpenSSL library for serving most of our websites,
         1107 we, together with most of the rest of the open-source world, were
         1108 vulnerable to the &lt;a class="reference external" href="http://heartbleed.com/"&gt;HeartBleed&lt;/a&gt; vulnerability. We have switched to the
         1109 patched version of OpenSSL within hours of it becoming available, plus
         1110 have performed the following steps to mitigate any sensitive information
         1111 leaked via malicious SSL heartbeat requests:&lt;/p&gt;
         1112 &lt;ul class="simple"&gt;
         1113 &lt;li&gt;Replaced all SSL keys across all kernel.org sites.&lt;/li&gt;
         1114 &lt;li&gt;Expired all active sessions on Bugzilla, Patchwork, and Mediawiki
         1115 sites, requiring everyone to re-login.&lt;/li&gt;
         1116 &lt;li&gt;Changed all passwords used for admin-level access to the above sites.&lt;/li&gt;
         1117 &lt;/ul&gt;
         1118 &lt;p&gt;As kernel.org developers do not rely on SSL to access git repositories,
         1119 there is no need to replace any SSH or PGP keys used for developer
         1120 authentication.&lt;/p&gt;
         1121 &lt;p&gt;If you have any questions or concerns, please email us at
         1122 &lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt; for more information.&lt;/p&gt;
         1123 </summary></entry><entry><title>Happy new year and good-bye bzip2</title><link href="https://www.kernel.org/happy-new-year-and-good-bye-bzip2.html" rel="alternate"></link><published>2013-12-27T00:00:00+00:00</published><updated>2013-12-27T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2013-12-27:happy-new-year-and-good-bye-bzip2.html</id><summary type="html">&lt;div class="section" id="good-bye-bzip2"&gt;
         1124 &lt;h2&gt;Good-bye bzip2&lt;/h2&gt;
         1125 &lt;p&gt;We started listing xz-compressed versions of kernel archives in all our
         1126 announcements back in March 2013, and the time has come to complete the
         1127 switch. Effective immediately, we will no longer be providing
         1128 bzip2-compressed versions for new releases of the Linux kernel and other
         1129 software. Any previously released .tar.bz2 archives will continue to be
         1130 available without change, and we will also continue to provide
         1131 gzip-compressed versions of all new releases for the foreseeable future.&lt;/p&gt;
         1132 &lt;p&gt;So, from now on, all releases will be offered as both .tar.gz and
         1133 .tar.xz, but not as .tar.bz2. We apologize if this interferes with any
         1134 automated tools.&lt;/p&gt;
         1135 &lt;/div&gt;
         1136 &lt;div class="section" id="happy-new-year"&gt;
         1137 &lt;h2&gt;Happy new year!&lt;/h2&gt;
         1138 &lt;p&gt;Happy new year to all kernel.org users and visitors. The Linux
         1139 Foundation and Linux Kernel Archives teams extend their warmest wishes
         1140 to you all, and we hope that 2014 proves to be just as awesome (or
         1141 awesomer) for the Linux kernel.&lt;/p&gt;
         1142 &lt;/div&gt;
         1143 </summary></entry><entry><title>New frontend and googlesource.com</title><link href="https://www.kernel.org/new-frontend-and-googlesourcecom.html" rel="alternate"></link><published>2013-11-28T00:00:00+00:00</published><updated>2013-11-28T00:00:00+00:00</updated><author><name>Konstantin Ryabitsev</name></author><id>tag:https://www.kernel.org,2013-11-28:new-frontend-and-googlesourcecom.html</id><summary type="html">&lt;div class="section" id="montreal-frontend"&gt;
         1144 &lt;h2&gt;Montreal frontend&lt;/h2&gt;
         1145 &lt;p&gt;We have added another official frontend for serving the kernel content,
         1146 courtesy of &lt;a class="reference external" href="https://vexxhost.com"&gt;Vexxhost, Inc&lt;/a&gt;. There is now a total of three frontends,
         1147 one in Palo Alto, California, one in Portland, Oregon, and one in
         1148 Montreal, Quebec. This should allow for better geographic dispersion of
         1149 official mirrors, as well as better fault tolerance.&lt;/p&gt;
         1150 &lt;/div&gt;
         1151 &lt;div class="section" id="kernel-googlesource-com"&gt;
         1152 &lt;h2&gt;Kernel.googlesource.com&lt;/h2&gt;
         1153 &lt;p&gt;We are happy to announce that kernel.googlesource.com is now relying on
         1154 grokmirror manifest data to efficiently mirror git.kernel.org, which
         1155 means that if accessing git.kernel.org is too high latency for you due
         1156 to your geographical location (EMEA, APAC), kernel.googlesource.com
         1157 should provide you with a fast local mirror that is at most 5 minutes
         1158 behind official sources.&lt;/p&gt;
         1159 &lt;p&gt;We extend our thanks to Google for making this available to all kernel
         1160 hackers and enthusiasts worldwide.&lt;/p&gt;
         1161 &lt;/div&gt;
         1162 &lt;div class="section" id="tls-1-2-and-pfs"&gt;
         1163 &lt;h2&gt;TLS 1.2 and PFS&lt;/h2&gt;
         1164 &lt;p&gt;With the latest round of upgrades, we are now serving TLS 1.2 with PFS
         1165 across all kernel.org sites, offering higher protection against
         1166 eavesdropping.&lt;/p&gt;
         1167 &lt;/div&gt;
         1168 </summary></entry><entry><title>Mirroring kernel.org repositories</title><link href="https://www.kernel.org/mirroring-kernelorg-repositories.html" rel="alternate"></link><published>2013-06-03T00:00:00+00:00</published><updated>2013-06-03T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-06-03:mirroring-kernelorg-repositories.html</id><summary type="html">&lt;p&gt;If you would like to mirror all or a subset of kernel.org git
         1169 repositories, please use a tool we wrote for this purpose, called
         1170 grokmirror. Grokmirror is git-aware and will create a complete mirror of
         1171 kernel.org repositories and keep them automatically updated with no
         1172 further involvement on your part.&lt;/p&gt;
         1173 &lt;p&gt;Grokmirror works by keeping track of repositories being updated by
         1174 downloading and comparing the master manifest file. This file is only
         1175 downloaded if it's newer on the server, and only the repositories that
         1176 have changed will be updated via &amp;quot;git remote update&amp;quot;.&lt;/p&gt;
         1177 &lt;p&gt;You can read more about grokmirror by reading the &lt;a class="reference external" href="https://git.kernel.org/cgit/utils/grokmirror/grokmirror.git/tree/README.rst"&gt;README&lt;/a&gt; file.&lt;/p&gt;
         1178 &lt;div class="section" id="obtaining-grokmirror"&gt;
         1179 &lt;h2&gt;Obtaining grokmirror&lt;/h2&gt;
         1180 &lt;p&gt;If grokmirror is not yet packaged for your distribution, you can obtain
         1181 it from a git repository:&lt;/p&gt;
         1182 &lt;pre class="literal-block"&gt;
         1183 git clone git://git.kernel.org/pub/scm/utils/grokmirror/grokmirror.git
         1184 &lt;/pre&gt;
         1185 &lt;p&gt;In additon to git, you will need to install the following python
         1186 dependencies on your mirror server:&lt;/p&gt;
         1187 &lt;blockquote&gt;
         1188 &lt;ul class="simple"&gt;
         1189 &lt;li&gt;&lt;a class="reference external" href="https://pypi.python.org/pypi/GitPython/"&gt;GitPython&lt;/a&gt;&lt;/li&gt;
         1190 &lt;/ul&gt;
         1191 &lt;/blockquote&gt;
         1192 &lt;/div&gt;
         1193 &lt;div class="section" id="setting-up-a-kernel-org-mirror"&gt;
         1194 &lt;h2&gt;Setting up a kernel.org mirror&lt;/h2&gt;
         1195 &lt;p&gt;It is recommended that you create a dedicated &amp;quot;mirror&amp;quot; user that will
         1196 own all the content and run all the cron jobs. It is generally
         1197 discouraged to run this as user &amp;quot;root&amp;quot;.&lt;/p&gt;
         1198 &lt;p&gt;The default repos.conf already comes pre-configured for kernel.org. We
         1199 reproduce the minimal configuration here:&lt;/p&gt;
         1200 &lt;pre class="literal-block"&gt;
         1201 [kernel.org]
         1202 site = git://git.kernel.org
         1203 manifest = http://git.kernel.org/manifest.js.gz
         1204 default_owner = Grokmirror User
         1205 #
         1206 # Where are we going to put the mirror on our disk?
         1207 toplevel = /var/lib/git/mirror
         1208 #
         1209 # Where do we store our own manifest? Usually in the toplevel.
         1210 mymanifest = /var/lib/git/mirror/manifest.js.gz
         1211 #
         1212 # Where do we put the logs?
         1213 log = /var/log/mirror/kernelorg.log
         1214 #
         1215 # Log level can be &amp;quot;info&amp;quot; or &amp;quot;debug&amp;quot;
         1216 loglevel = info
         1217 #
         1218 # To prevent multiple grok-pull instances from running at the same
         1219 # time, we first obtain an exclusive lock.
         1220 lock = /var/lock/mirror/kernelorg.lock
         1221 #
         1222 # Use shell-globbing to list the repositories you would like to mirror.
         1223 # If you want to mirror everything, just say &amp;quot;*&amp;quot;. Separate multiple entries
         1224 # with newline plus tab. Examples:
         1225 #
         1226 # mirror everything:
         1227 #include = *
         1228 #
         1229 # mirror just the main kernel sources:
         1230 #include = /pub/scm/linux/kernel/git/torvalds/linux.git
         1231 #          /pub/scm/linux/kernel/git/stable/linux-stable.git
         1232 #          /pub/scm/linux/kernel/git/next/linux-next.git
         1233 #
         1234 # mirror just git:
         1235 #include = /pub/scm/git/*
         1236 include = *
         1237 #
         1238 # This is processed after the include. If you want to exclude some specific
         1239 # entries from an all-inclusive globbing above. E.g., to exclude all
         1240 # linux-2.4 git sources:
         1241 #exclude = */linux-2.4*
         1242 exclude =
         1243 &lt;/pre&gt;
         1244 &lt;p&gt;Install this configuration file anywhere that makes sense in your
         1245 environment. You'll need to make sure that the following directories (or
         1246 whatever you changed them to) are writable by the &amp;quot;mirror&amp;quot; user:&lt;/p&gt;
         1247 &lt;blockquote&gt;
         1248 &lt;ul class="simple"&gt;
         1249 &lt;li&gt;&lt;tt class="docutils literal"&gt;/var/lib/git/mirror&lt;/tt&gt;&lt;/li&gt;
         1250 &lt;li&gt;&lt;tt class="docutils literal"&gt;/var/log/mirror&lt;/tt&gt;&lt;/li&gt;
         1251 &lt;li&gt;&lt;tt class="docutils literal"&gt;/var/lock/mirror&lt;/tt&gt;&lt;/li&gt;
         1252 &lt;/ul&gt;
         1253 &lt;/blockquote&gt;
         1254 &lt;/div&gt;
         1255 &lt;div class="section" id="mirroring-kernel-org-git-repositories"&gt;
         1256 &lt;h2&gt;Mirroring kernel.org git repositories&lt;/h2&gt;
         1257 &lt;p&gt;Now all you need to do is to add a cronjob that will check the
         1258 kernel.org mirror for updates. The following entry in
         1259 &lt;tt class="docutils literal"&gt;/etc/cron.d/grokmirror.cron&lt;/tt&gt; will check the mirror every 5 minutes:&lt;/p&gt;
         1260 &lt;pre class="literal-block"&gt;
         1261 # Run grok-pull every 5 minutes as &amp;quot;mirror&amp;quot; user
         1262 */5 * * * * mirror /usr/bin/grok-pull -p -c /etc/grokmirror/repos.conf
         1263 &lt;/pre&gt;
         1264 &lt;p&gt;(You will need to adjust the paths to the grok-pull command and to
         1265 repos.conf accordingly to reflect your environment.)&lt;/p&gt;
         1266 &lt;p&gt;The initial run will take many hours to complete, as it will need to
         1267 download about 50 GB of data.&lt;/p&gt;
         1268 &lt;/div&gt;
         1269 &lt;div class="section" id="mirroring-a-subset-of-repositories"&gt;
         1270 &lt;h2&gt;Mirroring a subset of repositories&lt;/h2&gt;
         1271 &lt;p&gt;If you are only interested in carrying a subset of git repositories
         1272 instead of all of them, you are welcome to tweak the &lt;tt class="docutils literal"&gt;include&lt;/tt&gt; and
         1273 &lt;tt class="docutils literal"&gt;exclude&lt;/tt&gt; parameters.&lt;/p&gt;
         1274 &lt;/div&gt;
         1275 </summary></entry><entry><title>Fifty shades of Tux</title><link href="https://www.kernel.org/fifty-shades-of-tux.html" rel="alternate"></link><published>2013-05-07T00:00:00+00:00</published><updated>2013-05-07T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-05-07:fifty-shades-of-tux.html</id><summary type="html">&lt;p&gt;Special thanks to Benoît Monin for donating a MIT-licensed CSS theme to
         1276 the kernel.org project to replace the one we hastily put together.
         1277 Though the Pelican authors have since obtained a free-license
         1278 commitment from the copyright owners of the CSS files shipping with
         1279 Pelican, we wanted to have something that looked a bit less like the
         1280 default theme anyway.&lt;/p&gt;
         1281 &lt;p&gt;If anyone else wants to participate, full sources of the kernel.org
         1282 website are available from the &lt;a class="reference external" href="https://git.kernel.org/cgit/docs/kernel/website.git"&gt;git repository&lt;/a&gt;.&lt;/p&gt;
         1283 </summary></entry><entry><title>XZ by default and JSON</title><link href="https://www.kernel.org/xz-by-default-and-json.html" rel="alternate"></link><published>2013-03-11T00:00:00+00:00</published><updated>2013-03-11T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-03-11:xz-by-default-and-json.html</id><summary type="html">&lt;p&gt;We've implemented two oft-requested features today:&lt;/p&gt;
         1284 &lt;ol class="arabic simple"&gt;
         1285 &lt;li&gt;The download links now default to .tar.xz versions of archives&lt;/li&gt;
         1286 &lt;li&gt;There is now a JSON file with the release information located in
         1287 &lt;a class="reference external" href="https://www.kernel.org/releases.json"&gt;https://www.kernel.org/releases.json&lt;/a&gt;. If you've been screen-scraping
         1288 the front page, please use this instead.&lt;/li&gt;
         1289 &lt;/ol&gt;
         1290 &lt;p&gt;If you have any other feature suggestions, please send them to
         1291 &lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt;.&lt;/p&gt;
         1292 </summary></entry><entry><title>/pub tree resync-ing</title><link href="https://www.kernel.org/pub-tree-resync-ing.html" rel="alternate"></link><published>2013-03-08T00:00:00+00:00</published><updated>2013-03-08T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-03-08:pub-tree-resync-ing.html</id><summary type="html">&lt;p&gt;Due to a failure in one of the rsync scripts during the maintenance
         1293 window, the mirrors of /pub hierarchy on www.kernel.org got erased. We
         1294 are resyncing them now from the master storage, but in the meantime you
         1295 will probably get an occasional &amp;quot;Forbidden&amp;quot;. The entirety of the archive
         1296 should be rsync'ed in a few hours.&lt;/p&gt;
         1297 &lt;p&gt;We apologize profusely for the problem and will fix the script to make
         1298 sure this doesn't happen again.&lt;/p&gt;
         1299 &lt;p&gt;Contents of git.kernel.org are unaffected.&lt;/p&gt;
         1300 </summary></entry><entry><title>Cleanroom styles</title><link href="https://www.kernel.org/cleanroom-styles.html" rel="alternate"></link><published>2013-03-03T00:00:00+00:00</published><updated>2013-03-03T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-03-03:cleanroom-styles.html</id><summary type="html">&lt;p&gt;You are probably wondering what happened to the site's look.
         1301 Unfortunately, we've been alerted that the default theme shipped by
         1302 Pelican (which we largely adapted) has an unclear license. Until this is
         1303 cleared up, we've put together a quick-and-dirty cleanroom CSS
         1304 reimplementation that preserves the functional aspects of the site, but
         1305 sacrifices a lot of the bells and whistles.&lt;/p&gt;
         1306 &lt;p&gt;If you are a CSS designer and would like to donate your own cleanroom
         1307 style, please let us know at &lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt;.&lt;/p&gt;
         1308 &lt;p&gt;Our apologies, and we promise to keep a keener eye on licensing
         1309 details of various templates distributed with open-source products.&lt;/p&gt;
         1310 </summary></entry><entry><title>Pelican</title><link href="https://www.kernel.org/pelican.html" rel="alternate"></link><published>2013-03-01T00:00:00+00:00</published><updated>2013-03-01T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-03-01:pelican.html</id><summary type="html">&lt;p&gt;Welcome to the reworked kernel.org website. We have switched to using
         1311 &lt;a class="reference external" href="http://docs.getpelican.com/"&gt;Pelican&lt;/a&gt; in order to statically render our site content, which
         1312 simplifies mirroring and distribution. You can view the sources used to
         1313 build this website in its own &lt;a class="reference external" href="https://git.kernel.org/?p=docs/kernel/website.git;a=summary"&gt;git repository&lt;/a&gt;.&lt;/p&gt;
         1314 &lt;p&gt;Additionally, we have switched from using gitweb-caching to using &lt;a class="reference external" href="https://git.zx2c4.com/cgit/"&gt;cgit&lt;/a&gt;
         1315 for &lt;a class="reference external" href="https://git.kernel.org/cgit/"&gt;browsing git repositories&lt;/a&gt;. There are rewrite rules in place to
         1316 forward old gitweb URLs to the pages serviced by cgit, so there
         1317 shouldn't be any broken links, hopefully. If you notice that something
         1318 that used to work with gitweb no longer works for you with cgit, please
         1319 drop us a note at &lt;a class="reference external" href="mailto:webmaster&amp;#64;kernel.org"&gt;webmaster&amp;#64;kernel.org&lt;/a&gt;.&lt;/p&gt;
         1320 </summary></entry><entry><title>Legal disclaimers and copyright</title><link href="https://www.kernel.org/legal.html" rel="alternate"></link><published>2013-01-01T00:00:00+00:00</published><updated>2013-01-01T00:00:00+00:00</updated><author><name></name></author><id>tag:https://www.kernel.org,2013-01-01:legal.html</id><summary type="html">&lt;div class="section" id="copyright-and-license"&gt;
         1321 &lt;h2&gt;Copyright and license&lt;/h2&gt;
         1322 &lt;p&gt;Except where otherwise stated, content on this site is
         1323 copyright (C) 1997-2014 by The Linux Kernel Organization, Inc.
         1324 and is made available to you under the
         1325 &lt;a class="reference external" href="https://creativecommons.org/licenses/by-sa/4.0/"&gt;Creative Commons Attribution ShareAlike 4.0 International License&lt;/a&gt;.&lt;/p&gt;
         1326 &lt;p&gt;Distributed software is copyrighted by their respective contributors and
         1327 are distributed under their own individual licenses.&lt;/p&gt;
         1328 &lt;/div&gt;
         1329 &lt;div class="section" id="legal-disclaimer"&gt;
         1330 &lt;h2&gt;Legal Disclaimer&lt;/h2&gt;
         1331 &lt;p&gt;This site is provided as a public service by The Linux Kernel
         1332 Organization Inc., a California &lt;a class="reference external" href="https://www.kernel.org/nonprofit.html"&gt;501(c)3 nonprofit corporation&lt;/a&gt;. Our
         1333 servers are located in San Francisco, CA, USA; Palo Alto, CA, USA;
         1334 Corvallis, OR, USA; Portland, OR, USA and Montréal, Québec, Canada. Use
         1335 in violation of any applicable laws is strictly prohibited.&lt;/p&gt;
         1336 &lt;p&gt;Neither the Linux Kernel Organization nor any of its sponsors make any
         1337 guarantees, explicit or implicit, about the contents of this site. Use
         1338 at your own risk.&lt;/p&gt;
         1339 &lt;/div&gt;
         1340 &lt;div class="section" id="trademarks"&gt;
         1341 &lt;h2&gt;Trademarks&lt;/h2&gt;
         1342 &lt;p&gt;Linux is a Registered Trademark of Linus Torvalds. All trademarks are
         1343 property of their respective owners.&lt;/p&gt;
         1344 &lt;/div&gt;
         1345