Hello.
I need to know how can I add a kernel parameter to the kernel commandline on a Fedora silverblue system.
I am trying to install silverblue on a laptop but I need to add few kernel parameters before it gets updated to latest 4.19 kernel or things will break.
Also I am trying to regenerate grub config using the command sudo ostree admin instutil grub2-generate but it gives a “no boot device found” error.
Is there any way to add a kernel parameter like adding it on /etc/default/grub on normal system?
grub2-mkconfig actually creates a wrong config on UEFI systems. It uses linux16 and initrd16 instead of linux and initrd command respectively.
Edit by @dustymabe:Please don’t use grubby as it does not integrate with ostree and your added kernel arguments may get lost. See Colin’s response below.
Try running:
sudo grubby --default-kernel
On my system this gives an output of the following (warning: it could be different on yours):
It means that the %post section of an RPM is run when the ostree compose is being done (i.e on the compose server) rather than on the client side (i.e. your host).
This is different than traditional RPM/yum/dnf where all the RPM %post stuff is done on your host when you are doing an install.
Not exactly. The package layering operation is something that is done client side; you don’t talk to the (remote) compose server to generate a new compose for you.
But the client can create a new ostree commit that includes the base compose (already on your host) and the new layered packages. In this case, the %post would technically run on the client (i.e. your host), however it is sandboxed from your running deployment. Just like when you do an upgrade, the new files are checked out into a new deployment (aka new ostree commit) and does not disrupt your running system.