public inbox for [email protected]
 help / color / mirror / Atom feed
From: Beru Shinsetsu <[email protected]>
To: Borislav Petkov <[email protected]>
Cc: Thomas Gleixner <[email protected]>,
	Ingo Molnar <[email protected]>,
	 Dave Hansen <[email protected]>,
	[email protected], "H. Peter Anvin" <[email protected]>,
	 [email protected],
	GNU/Weeb Mailing List <[email protected]>,
	 Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH] boot install: Partially refactor the logic for detecting bootloader
Date: Sun, 20 Mar 2022 12:30:51 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Sat, 2022-03-19 at 22:20 +0100, Borislav Petkov wrote:
> On Thu, Mar 17, 2022 at 04:46:48PM +0300, Beru Shinsetsu wrote:
> > > Well, I saw this on SLE15-SP4 (brand new) yesterday while I haven't
> > > seen it on previous service packs. So this doesn't look like it has
> > > been there since 2007. I'll try to debug it when I get a chance.
> > 
> > Hmm alright. Good luck from now! Hope everything goes flawlessly.
> 
> Here it is:
> 
> From arch/x86/boot/install.sh:
> 
> ...
> # User may have a custom install script
> 
> if [ -x ~/bin/${INSTALLKERNEL} ]; then exec ~/bin/${INSTALLKERNEL} "$@"; fi
> if [ -x /sbin/${INSTALLKERNEL} ]; then exec /sbin/${INSTALLKERNEL} "$@"; fi
> ...
> 
> so distros *usually* should supply a custom, distro-specific
> installkernel script which does that. The distros which you are seeing
> it on simply don't have that script installed and I need to talk to
> distro people as to what the rule there is for supplying such a script
> now.
> 
> Because most distros should supply it though and those new distros
> dropping it looks like some new "strategy" or so.
> 
> We'll see.

I have seen that, and I had pretty much the same thoughts as well. Arch
isn't quite new either. And as I said, installing from AUR works pretty
fine (package is `linux-mainline`, it also compiles the kernel on
*your* PC locally, then installs it as a PacMan package). Just
compiling manually doesn't. I suppose that's one of the quirks of the
distro being installed manually by the user from the very first stage.
Not even counting Gentoo though, I haven't tried it out as I'm scared
it can explode my laptop as it *compiles the whole system locally*. But
let's see how it goes. Thank you so much by the way!
-- 
Beru Shinsetsu

      reply	other threads:[~2022-03-20  9:30 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
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 [this message]

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 \
    --in-reply-to=e0fb4826470cc052b59c8cba6319df160908af5d.camel@gnuweeb.org \
    [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