| 1 |
On 2020-08-06 19:20, Aaron Bauman wrote: |
| 2 |
> Wait, changes were made to genkernel to switch from mdev to (e)udev |
| 3 |
> which causes breakage, but it is *not* an issue with genkernel? |
| 4 |
|
| 5 |
Exactly. |
| 6 |
|
| 7 |
This failure can happen with genkernel version created 15 years ago, |
| 8 |
with new genkernel-4.1 which switched device manager or even with dracut |
| 9 |
-- the mistake is using non-permanent device names for things like root. |
| 10 |
|
| 11 |
I assume that most user don't do that. At least their default boot entry |
| 12 |
in /boot/extlinux/extlinux.cfg or via /etc/default/grub will have a |
| 13 |
permanent name -- but the problem are tools/scripts appending to that |
| 14 |
existing command-line. They will overwrite a good value... |
| 15 |
|
| 16 |
And it's even more a problem because even when you notice "Ah, something |
| 17 |
is appending root argument" you won't question that because the value |
| 18 |
you notice matches your expectation from POV of current running system. |
| 19 |
So you have to realize that this is a non-permanent value which could be |
| 20 |
different on next boot because you did X which caused and offset in |
| 21 |
numbering for example... |
| 22 |
|
| 23 |
|
| 24 |
> Aside from this, do we have any evidence or bugs validating that users |
| 25 |
> experience breakage with randomly named boot devices in kexec? |
| 26 |
> |
| 27 |
> It is great that you found an issue, but why try and be agnostic as to |
| 28 |
> which one caused the issue? It looks worse that we cannot simply say: |
| 29 |
> |
| 30 |
> "genkernel changed for the better and things *may* break now... please |
| 31 |
> read this!" |
| 32 |
> |
| 33 |
> Instead, we are pushing a news item to a lot of people simply because we |
| 34 |
> *assume* it may be an issue for others with no evidence. |
| 35 |
|
| 36 |
Well, the purpose of this is to educate and avoid problems for |
| 37 |
headless/server users. But if so many devs seem to care about pushing |
| 38 |
maybe unrelated information and believe that avoiding that has much more |
| 39 |
value than avoid a problem like an unbootable system for just a few |
| 40 |
people (and for headless/servers this is a major problem in case you |
| 41 |
cannot trigger remote reboot)... ¯\_(ツ)_/¯ |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
Regards, |
| 46 |
Thomas Deutschmann / Gentoo Linux Developer |
| 47 |
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives