From: Boris Petkov <[email protected]>
To: Beru Shinsetsu <[email protected]>,
Thomas Gleixner <[email protected]>
Cc: Ingo Molnar <[email protected]>,
Dave Hansen <[email protected]>,
"H. Peter Anvin" <[email protected]>,
[email protected], GNU/Weeb Mailing List <[email protected]>,
[email protected],
Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH] boot install: Partially refactor the logic for detecting bootloader
Date: Thu, 17 Mar 2022 12:36:46 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On March 16, 2022 5:32:21 PM UTC, Beru Shinsetsu <[email protected]> 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.
next prev parent reply other threads:[~2022-03-17 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 17:32 [PATCH] boot install: Partially refactor the logic for detecting bootloader Beru Shinsetsu
2022-03-17 12:36 ` Boris Petkov [this message]
2022-03-17 13:16 ` Beru Shinsetsu
2022-03-17 13:42 ` Boris Petkov
2022-03-17 13:46 ` Beru Shinsetsu
2022-03-19 21:20 ` Borislav Petkov
2022-03-20 9:30 ` Beru Shinsetsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox