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: <87jzz7creg.fsf@meer.lwn.net>
Date:   Thu, 23 Mar 2023 11:24:23 -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:

> I currently can't really see the need for another book/top-level
> directory and to be honest it's by far my least favorite solution among
> the options on the table.

Well, it was just an idea that crossed my mind as I was thinking about
this stuff...it doesn't appear to have inspired a lot of enthusiasm.  So
never mind that for now, I guess...I reserve the right to come back to
it in the future once we're getting overwhelmed by these things :)

> I'm taken back and forth between the other two options (e.g. put the
> text in Documentation/admin-guide/ or
> Documentation/admin-guide/tutorials/). Maybe I prefer the latter a
> little bit more.

Let's just put it in admin-guide, I guess, though the fit feels a bit
awkward.  If we get more tutorials, we can make a separate section in
index.html, I don't think we need another subdirectory there at this
point.

Did you have further tweaks, or should I take v3?

Thanks,

jon