<div dir="ltr">Hello Hans,<br><br>Thanks for starting this discussion.<br><br>Looking at this from a Fedora/Dracut POV, I think we should look at this as the start of implementing a configuration-only initramfs, (something Matthew Garret has been advocating for a while) rather than making this a vconsole.conf/plymouth specific solution.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 26, 2019 at 12:43 PM Hans de Goede <<a href="mailto:hdegoede@redhat.com">hdegoede@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
On 26-09-2019 11:53, Michael Chapman wrote:<br>
> On Thu, 26 Sep 2019, Hans de Goede wrote:<br>
>> Hi,<br>
>><br>
>> On 26-09-2019 11:10, Michael Chapman wrote:<br>
>>> On Thu, 26 Sep 2019, Hans de Goede wrote:<br>
>>> [...]<br>
>>>> I believe that the best alternative is to have localed append / update<br>
>>>> a rd.vconsole.keymap=foo argument to the kernel commandline, to override<br>
>>>> the vconsole.conf KEYMAP setting, but only in the initrd (so that later<br>
>>>> runtime changes when booted still work).<br>
>>>><br>
>>>> The way I see this working is that localed does a read-modify-write of<br>
>>>> all the BLS .conf files under /boot/loader/entries and updates their<br>
>>>> "options" line to have rd.vconsole.keymap=foo appended or updated if<br>
>>>> already present.Hi,<br>
>>><br>
>>> To be honest, I really do think having the initrd rebuilt completely is a<br>
>>> better approach... but I do not think localed should be directly<br>
>>> responsible for that.<br>
>><br>
>> As I already mentioned there are 2 issues with rebuilding the initrd:<br>
>><br>
>> 1) It might break booting the system and, assuming we rebuild the initrd<br>
>> for all installed kernels on a locale change, then their will not be<br>
>> an older one to fallback to as there normally is, which is BAD.<br>
>><br>
>> 2) We are moving (and in case of rpmostree based distros already shipping)<br>
>> to pre-generated (on the distros buildsys) initrds, which likely will<br>
>> also be signed.<br>
>><br>
>> How do you propose to solve these 2 issues?<br>
> <br>
> Hmm, these are good points. I do like the idea of using a<br>
> locally-generated overlay initrd though.<br>
<br>
Ok, looking at:<br>
<a href="https://github.com/fedora-silverblue/issue-tracker/issues/3" rel="noreferrer" target="_blank">https://github.com/fedora-silverblue/issue-tracker/issues/3</a><br>
<br>
It seems that this might be the preference of the silverblue<br>
developers too and Javier also seems to favor that, so I guess<br>
the first thing to do is to give that approach a try.<br>
<br>
I've added a comment to:<br>
<a href="https://github.com/fedora-silverblue/issue-tracker/issues/3" rel="noreferrer" target="_blank">https://github.com/fedora-silverblue/issue-tracker/issues/3</a><br>
asking the silverblue devs to confirm that the overlay initramfs<br>
is still their preferred approach, once that is confirmed I will<br>
give this a try by manually creating on overlay initramfs and then<br>
we will see from there.<br>
<br>
Regards,<br>
<br>
Hans<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>Alberto Ruiz<br></div>Engineering Manager - Desktop Hardware Enablement<br></div>Red Hat<br></div></div></div></div></div></div></div></div>