Date: Sun, 04 May 2025 07:48:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 286556] boot_mute is improperly specified in loader.conf(5); man page doesn't mention Message-ID: <bug-286556-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286556 Bug ID: 286556 Summary: boot_mute is improperly specified in loader.conf(5); man page doesn't mention Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: sgharms@stevengharms.com Per: stand/defaults/loader.conf #boot_mute="" # -m: Mute the console This is inaccurate. The documentation reflects the original intention of this option. Per Warner Losh[1]: > Originally, it was done by Whistle in 1993 for muting the console on their > WhistleJet internet systems since it printed things Whistle generally didn't > want disclosed. So far, things are consistent. However, boot_mute does not live up to this commitment. Rather it: 1. Displays a beastie orb image covering up the hardware testing sequence kernel initialization 2. After moving to init(8), the overlay is removed and rc initialization is printed to screen in violation of expectation of the option Continued Losh: > ...the vt(4) authors weren't aware of this when vt was merged, and none of the > reviewer caught it... In conclusion, the incomplete guidance is inaccurate. That the de facto functionality *also* fails, is another concern that will be opened in a different bug. [1]: https://lists.freebsd.org/archives/freebsd-current/2025-March/007230.html -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-286556-227>