On Mon, Nov 4, 2024 at 4:20 PM Jaroslav Škarvada <jskarvad@xxxxxxxxxx> wrote: > > On Mon, Nov 4, 2024 at 3:02 PM Ian Pilcher <arequipeno@xxxxxxxxx> wrote: > > > > On 11/4/24 7:42 AM, Fabio Valentini wrote: > > > Oof ... the fact that tuned mangles bootloader parameters wasn't > > > mentioned at all in the Change Proposal to enable it by default. To me > > > that would have been a no-go. (I already voted -1 for this change for > > > other reasons, but these bootloader shenanigans definitely don't make > > > me regret that decision ...) > > > > Should there be a packaging guideline about this? > > > > Hi, > > kernel command line parameters can be changed by the bootloader plugin > which is not used in the profiles that were used in the tuned-ppd > replacement. So that's probably why it wasn't explicitly mentioned. > Patching of bootloader entries is done to clearly mark what can be > changed by TuneD, i.e. by the $tuned_* variables. If the bootloader > plugin is not used, these variables are empty. It's interesting that > this problem wasn't reported during the F41 test days I wonder if it would be possible to just ... not set bootloader parameters at all if the bootloader plugin isn't used? The current implementation seems like a very brittle solution to me (as witnessed by the systemd-boot breakage). Fabio -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
