Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 17 Mar 2022 12:36:46 +0000
From:   Boris Petkov <bp@alien8.de>
To:     Beru Shinsetsu <windowz414@gnuweeb.org>,
        Thomas Gleixner <tglx@linutronix.de>
CC:     Ingo Molnar <mingo@redhat.com>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        "H. Peter Anvin" <hpa@zytor.com>, x86@kernel.org,
        GNU/Weeb Mailing List <gwml@gnuweeb.org>,
        linux-kernel@vger.kernel.org,
        Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Subject: =?US-ASCII?Q?Re=3A_=5BPATCH=5D_boot_install=3A_Partially_ref?= =?US-ASCII?Q?actor_the_logic_for_detecting_bootloader?=
User-Agent: K-9 Mail for Android
In-Reply-To: <20220316173221.5937-1-windowz414@gnuweeb.org>
References: <20220316173221.5937-1-windowz414@gnuweeb.org>
Message-ID: <2E28CA0C-34F2-4985-86CC-B1823AF8D747@alien8.de>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On March 16, 2022 5:32:21 PM UTC, Beru Shinsetsu <windowz414@gnuweeb=2Eorg>=
 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=2E=20

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=2E So before we do anything, it'd =
be prudent to know what has changed recently to cause this error message to=
 happen=2E Because we would have to backport a fix to some kernels probably=
=2E

Thx=2E

--=20
Sent from a small device: formatting sux and brevity is inevitable=2E