linux-kernel - Re: [v5.1] Documentation: bootconfig: Update boot configuration documentation

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]

Date:   Fri, 6 Mar 2020 19:40:28 +0100
From:   Markus Elfring <Markus.Elfring@....de>
To:     Masami Hiramatsu <mhiramat@...nel.org>, linux-doc@...r.kernel.org
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Jonathan Corbet <corbet@....net>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [v5.1] Documentation: bootconfig: Update boot configuration
 documentation

>>>> …
>>>>> +++ b/Documentation/admin-guide/bootconfig.rst
>>>> …
>>>>> +If you think that kernel/init options become too long to write in boot-loader
>>>>> +configuration file or you want to comment on each option, the boot
>>>>> +configuration may be suitable. …
>>>>
>>>> Would you like to specify any settings in the boot configuration file
>>>> because the provided storage capacity would be too limited by the kernel command line?
>>>
>>> Yes.
>>
>> How will affected places be improved after such an agreement?
>
> Would you please make a patch of new sentence?

Not directly.

* If I would need to provide another wording alternative as a concrete patch,
  I would have to wait until previously accepted changes would become available
  in a Linux development repository.

* So I would find it easier to agree on wording variants during our current
  development discussion from which you would present results as a subsequent patch.

Regards,
Markus