linux-kernel - Re: [PATCH v4] docs: admin-guide: Update bootloader and installation instructions

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] [day] [month] [year] [list]

Date: Wed, 14 Feb 2024 15:54:50 -0700
From: Jonathan Corbet <corbet@....net>
To: Hunter Chasens <hunter.chasens18@....edu>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Hunter Chasens
 <hunter.chasens18@....edu>
Subject: Re: [PATCH v4] docs: admin-guide: Update bootloader and
 installation instructions

Hunter Chasens <hunter.chasens18@....edu> writes:

> Updates the bootloader and installation instructions in
> admin-guide/README.rst to align with modern practices.
>
> Details of Changes:
>
>  - Added guidance on using EFISTUB for UEFI/EFI systems.
>  - Noted that LILO is no longer in active development and provides
>    alternatives.
>  - Kept LILO instructions but marked as Legacy LILO Instructions.
>    Suggest removal in future patch.
>
> Signed-off-by: Hunter Chasens <hunter.chasens18@....edu>
> ---
>  Documentation/admin-guide/README.rst | 69 ++++++++++++++++++----------
>  1 file changed, 45 insertions(+), 24 deletions(-)

So, I have applied this...but I got some warnings:

> .git/rebase-apply/patch:45: trailing whitespace.
>  - Booting a kernel directly from a storage device without the assistance 
> .git/rebase-apply/patch:46: trailing whitespace.
>    of a bootloader such as LILO or GRUB, is no longer supported in BIOS 
> .git/rebase-apply/patch:47: trailing whitespace.
>    (non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB 
> warning: 3 lines add whitespace errors.

This is something checkpatch should have warned you about.  I've fixed
it up this time, no need to resend.

Thanks,

jon