Ping?
On 01/03/2024, 15:43, "Simon Rowe" wrote:
Kernel parameters actually cover a range of purposes, including
userspace like systemd. They also need setting for a variety of
reasons:
* as distro defaults
* to provide configuration for a package
* for an admin to set desired
On 02/03/2024, 03:21, "Oskari Pirhonen" wrote:
> Would it be better to have the kernel command line args in GRUB config
> override the ones in
> any drop-ins? At least for me it would be surprising behavior if my distro
> set something in
> /usr/lib/kernel.d/ and changing that value in my GRUB
to any other kernel parameters
defined via GRUB_CMDLINE_LINUX etc. Files in /etc/kernel.d/ completely
replace those of the same name in /usr/lib/kernel.d/. This allows a
distro or installer to set parameters but then for an admin to
override them.
Signed-off-by: Simon Rowe
---
util/grub
On 08/02/2024, 18:46, "Daniel Kiper" wrote:
>
> Looks interesting. Though I think this could also be applied to other
> kernels/Xen/... Did you think how this could interact with the Boot
> Loader Specification (BLS) [1] too? It is not yet implemented in the
> GRUB but I hope we will get it in
I have a suggestion I’d like to have feedback on regarding the management of
Linux kernel parameters.
Today the parameters for a Linux menu entry have to be specified in the
GRUB_CMDLINE_LINUX entry of /etc/default/grub. These parameters cover a number
of purposes, not just the kernel (e.g.
