G'day,

In Fedora we use the `machine-id` in a few places in `/boot`. For example it is
part of the rescue kernel name and the BLS files. This is (from what I 
understand)
because we want to let our `/boot` (XBOOTLDR) partition be used by multiple
installations if required.

Please correct me if I misunderstand the reasoning on functionality or
purpose :)


Sadly having the machine-id used as the differentiator is difficult for those 
of us
who like to build images of operating systems. Since machine-ids are supposed 
to be
unique per machine we can't pre-fill them. We can build the system, including 
running
dracut, and reset the machine-id to something useful (such as `uninitialized`).

However that makes us end up with (for example) a rescue kernel with the wrong 
machine-id.
This leads to duplicate rescue kernels the next time dracut regenerates.

For many of our disk images produced in `koji` we turn off rescue kernel
generation because of this as it is a noticeable effect. However BLS files
are also stored in this way.


With the backstory out of the way. I've been looking into using 
`entry-token=os-id` instead
of `entry-token=machine-id`. In this case we would instead use `fedora` as the 
differentiator
for BLS and rescue kernels.

There's probably history on why Fedora uses `machine-id`, there's probably
things that preclude us from using `entry-token=os-id`. If you know any history
about or you know something that would break if we were to switch to using the
`os-id` please let me know.

I might consider turning this into a change proposal for a next version of
Fedora if there are no big downsides to changing this.

Simon
-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to