linux-kernel - Re: [PATCH] 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:   Fri, 27 Oct 2023 03:16:15 -0400
From:   Hunter Chasens <hunter.chasens18@....edu>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     corbet@....net, linux-kernel@...r.kernel.org,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: admin-guide: Update bootloader and installation instructions

Thank you for the catch. v2, has just been sent.

On Fri, Oct 27, 2023 at 12:41 AM Randy Dunlap <rdunlap@...radead.org> wrote:
>
>
>
> On 10/26/23 21:10, Hunter Chasens wrote:
> > 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 | 71 ++++++++++++++++++----------
> >  1 file changed, 46 insertions(+), 25 deletions(-)
> >
> > diff --git a/Documentation/admin-guide/README.rst b/Documentation/admin-guide/README.rst
> > index 9a969c0157f1..fba66f909f98 100644
> > --- a/Documentation/admin-guide/README.rst
> > +++ b/Documentation/admin-guide/README.rst
> > @@ -252,7 +252,7 @@ Configuring the kernel
> >      - The "kernel hacking" configuration details usually result in a
> >        bigger or slower kernel (or both), and can even make the kernel
> >        less stable by configuring some routines to actively try to
> > -      break bad code to find kernel problems (kmalloc()).  Thus you
>
> I don't see a problem with the above notation.
>
> > +      break bad code to find kernel problems (kmalloc()().  Thus you
>
> This way has unmatched parens.
>
> >        should probably answer 'n' to the questions for "development",
> >        "experimental", or "debugging" features.
> >
>
>
> --
> ~Randy