linux-kernel - Re: [PATCH v2] docs: admin-guide: Clarify sentences

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:   Thu, 9 Apr 2020 11:13:11 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Cristian Souza <cristianmsbr@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        corbet@....net
Subject: Re: [PATCH v2] docs: admin-guide: Clarify sentences

On Wed, Apr 08, 2020 at 11:46:53AM -0300, Cristian Souza wrote:
> @@ -1,34 +1,30 @@
> -Explaining the dreaded "No working init found." boot hang message
> -=================================================================
> +Explaining the "No working init found." boot hang message
> +=========================================================
> 
> -OK, so you have got this pretty unintuitive message (currently located
> -in init/main.c) and are wondering what went wrong.
> -Some high-level reasons for failure (listed roughly in order of execution)
> -to load the init binary are:
> +Message location: ``init/main.c``

I don't think this should be the first paragraph ;-)

Maybe just skip it altogether?  The sysadmin doesn't care where the
message is located.

> +5) **Binary cannot be loaded**: Make sure the binary's architecture matches your hardware.

Line exceeds 80 characters (other occurrences of this)

>    e.g. by providing additional error messages at affected places.
> 
>  Andreas Mohr <andi at lisas period de>
> +Cristian Souza <cristianmsbr at gmail period com>

We tend to use :Author: at the top of the file instead of signatories at the
bottom.