linux-kernel - Re: [PATCH] boot install: Partially refactor the logic for detecting bootloader

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, 17 Mar 2022 12:36:46 +0000
From:   Boris Petkov <bp@...en8.de>
To:     Beru Shinsetsu <windowz414@...weeb.org>,
        Thomas Gleixner <tglx@...utronix.de>
CC:     Ingo Molnar <mingo@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        GNU/Weeb Mailing List <gwml@...weeb.org>,
        linux-kernel@...r.kernel.org,
        Alviro Iskandar Setiawan <alviro.iskandar@...weeb.org>
Subject: Re: [PATCH] boot install: Partially refactor the logic for detecting bootloader

On March 16, 2022 5:32:21 PM UTC, Beru Shinsetsu <windowz414@...weeb.org> wrote:
>While running `make install` after building the kernel and installing
>modules on several distros like EndeavourOS, there would be a pretty
>little output (To be exact, "Cannot find LILO") due to lack of LILO
>bootloader, which is really uncommon for a user to have it while
>GRUB is there. 

As a matter of fact I saw this yesterday on one of the test boxes here and was wondering why I am even seeing this. So before we do anything, it'd be prudent to know what has changed recently to cause this error message to happen. Because we would have to backport a fix to some kernels probably.

Thx.

-- 
Sent from a small device: formatting sux and brevity is inevitable.