linux-kernel - Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87a60frxk0.fsf@meer.lwn.net>
Date:   Tue, 14 Mar 2023 12:35:11 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Thorsten Leemhuis <linux@...mhuis.info>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

Thorsten Leemhuis <linux@...mhuis.info> writes:

> 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.

So I think the time has come to apply this.  I did have one final
thought, though...  In the v2 discussion, you said:

> Be warned, if it works I might do the same for "reporting issues". ;)
> But let's first see how this goes (and if we get any feedback to be able
> to tell if this experiment worked).

This caused me to wonder if we shouldn't create a new book called
"tutorials" for this kind of stuff, with an explicit proviso that a more
web-oriented approach is OK in that section?  Tutorial documentation
*is* quite different from reference material, but we've really made no
effort to treat the two differently so far.

Thoughts?

Thanks,

jon