On Tue, Jul 19, 2022, at 12:24 PM, Lennart Poettering wrote: > On Fr, 15.07.22 10:03, Colin Walters (walt...@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,
Definitely interested in your opinion, because...a bikeshed here is where to put this unit if it's not systemd. For CoreOS, we have this nice "overlay" git repository for stuff like this that isn't an RPM, it has a lot of our miscellaneous systemd units and config files and such; so we can just do a pull request, have that pull request go through CI and merge and then it gets baked into the image and ship...no "manual package builds". The closest analogue in the yum world (i.e. only understands RPMs) is probably the generic-release type packages. So in theory it could go there. But this all said...it perhaps is worth considering the alternative, which is just this one-liner diff to the kernel config (AFAIK): diff --git a/kernel-x86_64-fedora.config b/kernel-x86_64-fedora.config index 517763fc9..b4b5708a3 100644 --- a/kernel-x86_64-fedora.config +++ b/kernel-x86_64-fedora.config @@ -981,7 +981,7 @@ CONFIG_COMPAT_32BIT_TIME=y # CONFIG_COMPILE_TEST is not set CONFIG_CONFIGFS_FS=y CONFIG_CONNECTOR=y -CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7 +CONFIG_CONSOLE_LOGLEVEL_DEFAULT=4 CONFIG_CONSOLE_LOGLEVEL_QUIET=3 CONFIG_CONTEXT_SWITCH_TRACER=y # CONFIG_CONTEXT_TRACKING_FORCE is not set The implications to that are obviously much larger, which is why I hesitated to propose it. While the stream of debug-level spew for servers has caused serious problems, it feels odd to me to switch servers to be entirely quiet by default. I am *certain* there are people who are doing CI/testing systems and are gathering the kernel console today and expect non-quiet output by default. But, this is also a much simpler change to understand, and anyone who wants it can start specifying e.g. `debug` on the kernel command line. I'm certainly curious about the opinions of the kernel maintainers in particular here. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
