On Fr, 15.07.22 10:03, Colin Walters (walters(a)verbum.org) wrote:
We recently did
https://github.com/coreos/fedora-coreos-config/pull/1840 for Fedora
CoreOS (more background:
https://github.com/coreos/fedora-coreos-tracker/issues/1244 ) and
I'd like to consider applying this to all Fedora editions.
There'd be no impact on desktop systems (commonly installed via
Anaconda and hence using `quiet`).
The benefit is for server systems where we *do* want some kernel
output at boot, but once we've successfully booted we don't want to
emit a message every time podman/docker creates a bridge device for
example.
Concretely today, I noticed that the RHEL 8.6 Cloud Guest image also
does not include `quiet` and so the kernel console log is full of
the same spam at runtime, and I think it makes sense to do this
change across all Fedora derivatives.
I am note entirely sure if this feature has merit or not, but I don't
want to comment on that. However, I'd like to suggest that if you do
this, please consider replacing this line:
<snip>
ExecStart=/bin/bash -euo pipefail -c 'mkdir -p /run/sysctl.d && chcon
--reference=/etc/sysctl.d /run/sysctl.d && echo "kernel.printk = 4" >
/run/sysctl.d/01-coreos-printk.conf'
</snip>
by something like this:
<snip>
ExecStart=/usr/bin/systemd-tmpfiles --create -
StandardInputText=f /run/sysctl.d/01-coreos-printk.conf - - - - kernel.printk 4
</snip>
Benefits: no shell, single process forked, no explicit selinux stuff,
or explicit mkdir, and other MACs will be honoured too if they exist.
Lennart
--
Lennart Poettering, Berlin