From: Borislav Petkov <bp@alien8.de>
To: Beru Shinsetsu <windowz414@gnuweeb.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
GNU/Weeb Mailing List <gwml@gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Subject: Re: [PATCH] boot install: Partially refactor the logic for detecting bootloader
Date: Sat, 19 Mar 2022 22:20:12 +0100 [thread overview]
Message-ID: <YjZJDP21H+ngnQb4@zn.tnic> (raw)
In-Reply-To: <9fa42069edf92d0ca7d64e967e1b9c0030d9a6ec.camel@gnuweeb.org>
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.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-03-19 21:20 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 [this message]
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 \
--in-reply-to=YjZJDP21H+ngnQb4@zn.tnic \
--to=bp@alien8.de \
--cc=alviro.iskandar@gnuweeb.org \
--cc=dave.hansen@linux.intel.com \
--cc=gwml@gnuweeb.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=windowz414@gnuweeb.org \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.