From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v1] docs: describe how to quickly build Linux
Date: Wed, 1 Feb 2023 14:22:07 +0100 [thread overview]
Message-ID: <3d568611-8119-37c7-7d84-61cb97532446@leemhuis.info> (raw)
In-Reply-To: <Y9pep+GBBaTiN/sN@kroah.com>
On 01.02.23 13:44, Greg KH wrote:
> On Wed, Feb 01, 2023 at 01:42:29PM +0100, Greg KH wrote:
>> On Wed, Feb 01, 2023 at 12:52:30PM +0100, Thorsten Leemhuis wrote:
>>> Add a text explaining how to quickly build a kernel, as that's something
>>> users will often have to do when they want to report an issue or test
>>> proposed fixes. This is a huge and frightening task for quite a few
>>> users these days, as many rely on pre-compiled kernels and have never
>>> built their own. They find help on quite a few websites explaining the
>>> process in various ways, but those howtos often omit important details
>>> or make things too hard for the 'quickly build just for testing' case
>>> that 'localmodconfig' is really useful for. Hence give users something
>>> at hand to guide them, as that makes it easier for them to help with
>>> testing, debugging, and fixing the kernel.
>>
>> First off, this is great, thanks for doing this.
Thx, feels good to hear.
Bisection is next on my todo list once this matured...
>> One minor comment, to prevent people from "overloading" the
>> git.kernel.org systems:
>>
>>> +.. _sources_sbs:
>>> +
>>> + * Retrieve the sources of the Linux version you intend to build; then change
>>> + into the directory holding them, as all further commands in this guide are
>>> + meant to be executed from there.
>>> +
>>> + If you plan to only build one particular kernel version, download its source
>>> + archive from https://kernel.org; afterwards extract its content to '~/linux/'
>>> + and change into the directory created during extraction.
>>> +
>>> + In most other situations your best choice is to fetch the sources using git::
>>> +
>>> + git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git \
>>> + ~/linux/sources
>>> + cd ~/linux/sources/
>>
>> Ideally you should never do a "full clone from scratch" like this, as it
>> takes up loads of server resources. The "best" way to do this is to
>> download the kernel git bundle, and then pull and resolve the remaining
>> bits. It's explained, with a script to do the work for you, here:
>>
>> https://kernel.org/best-way-to-do-linux-clones-for-your-ci.html
>
> Oops, here's the full steps involved:
> https://www.kernel.org/cloning-linux-from-a-bundle.html
> the first link above has a script that does it all for you, but you
> probably just want to copy the steps at this last link instead.
Great idea, thx for bringing this up -- now that you mention it, I
remember those pages and the script again... :-/
Sadly my "after cloning Linus tree, add the stable tree as remote and
fetch everything" approach would will still create a lot of load. I
could use the script with the stable git repo, as that includes
mainline; but I noticed it sometimes is not fully up2date. At least I
once noticed it was quite a few hours (or maybe even a day?) behind. Is
that normal? I assume you should know.
Anyway: maybe "a little bit behind" isn't something that's much of a
problem for this document.
Ciao, Thorsten
next prev parent reply other threads:[~2023-02-01 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 11:52 [PATCH v1] docs: describe how to quickly build Linux Thorsten Leemhuis
2023-02-01 12:42 ` Greg KH
2023-02-01 12:44 ` Greg KH
2023-02-01 13:22 ` Thorsten Leemhuis [this message]
2023-02-01 14:02 ` Greg KH
2023-02-02 11:15 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-02 14:27 ` Greg KH
2023-02-02 14:57 ` Thorsten Leemhuis
2023-02-02 15:08 ` Konstantin Ryabitsev
2023-02-02 15:36 ` Thorsten Leemhuis
2023-02-03 9:44 ` Jani Nikula
2023-02-03 9:52 ` Thorsten Leemhuis
2023-02-10 11:38 ` Thorsten Leemhuis
2023-02-10 13:55 ` Konstantin Ryabitsev
2023-02-25 9:17 ` Pavel Machek
2023-02-25 9:29 ` Thorsten Leemhuis
2023-02-25 13:34 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d568611-8119-37c7-7d84-61cb97532446@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).