On 11/24/18 1:34 PM, Oleg Cherkasov wrote:
On 24.11.2018 18:44, sean darcy wrote:
> I'm trying to disable the spectre mitigations. I've set up
> /etc/default/grub:
>
> cat grub
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> GRUB_DEFAULT=saved
> GRUB_DISABLE_SUBMENU=true
> GRUB_TERMINAL_OUTPUT="console"
> #GRUB_CMDLINE_LINUX="resume=UUID=d695f875-5220-49ab-8b0d-4f58649cd8ad
> nomodeset rhgb quiet"
> GRUB_CMDLINE_LINUX="resume=UUID=d695f875-5220-49ab-8b0d-4f58649cd8ad
> nomodeset pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable
> no_stf_barrier"
> GRUB_DISABLE_RECOVERY="true"
>
> but the command line is not used when I update the kernel. I tried
> again with dnf reinstall kernel*.
Shall you update grub configuration instead?
grub2-mkconfig --output=/boot/grub2/grub.cfg
_______________________________________________
Yes, I could do that. But I'd like this to happen on each update.
Doesn't/shouldn't kernel update run grub2-mkconfig ?
And which kernel* is supposed to run it ? Or is the user expected to
roll his own ?