blscfg module $early_initrd and $default_kernelopts variables

blscfg module $early_initrd and $default_kernelopts variables

[Mike Beaton]

[-- Attachment #1: Type: text/plain, Size: 363 bytes --]

I was wondering if anybody could possibly help out and clarify, is there
any official documentation around the existence, and correct use, of the
blscfg $early_initrd and $default_kernelopts variables?

https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L764
https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L788

[-- Attachment #2: Type: text/html, Size: 602 bytes --]

Re: blscfg module $early_initrd and $default_kernelopts variables

[Javier Martinez Canillas]

Hello Mike,

On Wed, Aug 11, 2021 at 3:17 PM Mike Beaton <mjsbeaton@gmail.com> wrote:
>
> I was wondering if anybody could possibly help out and clarify, is there any official documentation around the existence, and correct use, of the blscfg $early_initrd and $default_kernelopts variables?
>

The blscfg module is not in upstream GRUB yet and it's only present in
the downstream package of some distros (e.g: Fedora Linux, Endless
OS). The mailing list is not a proper venue to discuss downstream
specific features and instead should be reported for your distribution
(i.e: Fedora's bugzilla).

> https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L764

This variable is not used anymore and is only there for backward
compatibility. Now in Fedora the kernel command line parameter is
stored in the BLS snippets instead.

> https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L788
>

The goal of this variable was to support the
GRUB_EARLY_INITRD_LINUX_CUSTOM option in /etc/default/grub, and so the
/etc/grub.d/10_linux script looks at this and sets the early_initrd
variable. So the use should be to set that option and then run
grub2-mkconfig as you would do on a non-BLS setup.

But I believe that instead the correct way should be for the BLS
snippet created to contain two devicetree options, and drop the
$early_initrd variable as well.

Best regards,
Javier

Re: blscfg module $early_initrd and $default_kernelopts variables

[Mike Beaton]

[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]

Dear Javier,

Many thanks for your very helpful answer.

With regards to whether $default_kernelopts is still used, it is definitely
still used in CentOS 8 - wider than that I cannot yet report.

I will attempt to look for a more appropriate forum for discussion!

Mike

---------- Forwarded message ----------
> From: Javier Martinez Canillas <javier@dowhile0.org>
> To: The development of GNU GRUB <grub-devel@gnu.org>, mjsbeaton@gmail.com
> Cc:
> Bcc:
> Date: Wed, 18 Aug 2021 09:03:15 +0200
> Subject: Re: blscfg module $early_initrd and $default_kernelopts variables
> Hello Mike,
>
> On Wed, Aug 11, 2021 at 3:17 PM Mike Beaton <mjsbeaton@gmail.com> wrote:
> >
> > I was wondering if anybody could possibly help out and clarify, is there
> any official documentation around the existence, and correct use, of the
> blscfg $early_initrd and $default_kernelopts variables?
> >
>
> The blscfg module is not in upstream GRUB yet and it's only present in
> the downstream package of some distros (e.g: Fedora Linux, Endless
> OS). The mailing list is not a proper venue to discuss downstream
> specific features and instead should be reported for your distribution
> (i.e: Fedora's bugzilla).
>
> >
> https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L764
>
> This variable is not used anymore and is only there for backward
> compatibility. Now in Fedora the kernel command line parameter is
> stored in the BLS snippets instead.
>
> >
> https://github.com/rhboot/grub2/blob/fedora-35/grub-core/commands/blscfg.c#L788
> >
>
> The goal of this variable was to support the
> GRUB_EARLY_INITRD_LINUX_CUSTOM option in /etc/default/grub, and so the
> /etc/grub.d/10_linux script looks at this and sets the early_initrd
> variable. So the use should be to set that option and then run
> grub2-mkconfig as you would do on a non-BLS setup.
>
> But I believe that instead the correct way should be for the BLS
> snippet created to contain two devicetree options, and drop the
> $early_initrd variable as well.
>
> Best regards,
> Javier
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

[-- Attachment #2: Type: text/html, Size: 3342 bytes --]