Am 26.11.24 um 19:42 schrieb Stoiko Ivanov:
> we got a few reports of kernel-output drawing over the TUI-installer.
> (e.g. when ZFS loads for the pool-cleanup, also mkfs.xfs sometimes
> triggers a message being printed).
> 
> As the information gets logged in the kernel ringbuffer (`dmesg`)
> anyways, there's little gain on having it displayed on the console in
> addition.
> 
> following https://www.kernel.org/doc/Documentation/sysctl/kernel.txt
> and
> https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/getting-started-with-kernel-logging_managing-monitoring-and-updating-the-kernel
> simply set the sysctl to log only messages of level warn and above to
> the console.
> 
> Tested in a VM, where I manually ran the command before starting the
> TUI installer (and selecting XFS as filesystem there). without it the
> messages got displayed, with the command they did not.
> 
> Signed-off-by: Stoiko Ivanov <s.iva...@proxmox.com>
> ---
> as it's a cosmetic issue I would not pull it in late in the release cycle.
> Sending it nonetheless now, in order not to forget it.
> 
>  unconfigured.sh | 3 +++
>  1 file changed, 3 insertions(+)
> 
>

applied, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to