Optionally silence devmatch, routing rc scripts operations #1582
Conversation
The rc scripts afford various levels of support for quiet mode. For example, route(8) has `-q` and `wpa_supplicant(8)` has `-s`. The rc file for `/etc/rc.d/devmatch` uses the standard shell `echo` command. For those who like a quieter bootup (less-technical users, those whose infrastructure environments are reliable/stable), this can be confusing or frustrating. With this change, users may squelch the echo behavior. devmatch_autoloading_msgs="NO" # Do not log "Autoloading" to console from devmatch rc. Signed-off-by: Steven G. Harms <[email protected]>
route(8) supports a quiet mode that was inaccessible. This changes surfaces a means for adding an arbitrary number of flags (similar to dhclient RC and others). For those who like a quieter bootup (less-technical users, those whose infrastructure environments are reliable/stable), the previous output could be confusing or frustrating. Signed-off-by: Steven G. Harms <[email protected]>
If we're not interested in checking messages thru rc_quiet and we're not interested in start messages thru rc_startmsgs=NO.. then why not send errors to the bit-bucket for a cleaner startup? Signed-off-by: Steven G. Harms <[email protected]>
|
Thank you for your interest regarding this topic. |
|
Tecrübesizim bu tür konularda , cihazımda sürekli olarak değiştirildiğini hissettiğim birseyler var. Değiştirilmiş birşeyi nasıl bulabilirim |
There was a problem hiding this comment.
Thanks @sgharms :-)
- There is already
rc_infothat may be used?freebsd-src/libexec/rc/rc.conf
Line 29 in 50c962d
- There is already
rc_startmsgthat may be used?freebsd-src/libexec/rc/rc.conf
Line 30 in 50c962d
- If really necessary
_msgscan be replaced with_verbosesuffix?freebsd-src/libexec/rc/rc.conf
Line 568 in 50c962d
- Adding
routing_flagsseems okay as-qmay be set that way :-) - I guess the idea is to silence the terminal? How many flags need to be put to silent instead just one? Why not just put a boot logo image if you really do not want to see the boot messages? It may provide expected user experience and will not impact diagnostic information that are usually useful :-)
|
To close the loop here (in parallel to the mailing list): I think the optimal solution is for boot_mute=YES to extend the overlay until the point that the login menu is ready (probably after doing a screen reset so that the login prompt is the only thing on screen). Presently boot_mute seems to stop the overlay after the kernel gets a hold of the VTs (explains the phenomenon I'm seeing here). Extending that overlay's duration would fix things IMHO. |
|
Thank you @sgharms for a good discussion !! :-) |
I am interested in helping the Laptop working group (a focus of 2025) and was
trying to help smooth any rough edges that might spook a newer installer/user.
One of the items overwhelming is the chattiness of startup. While boot_mute=YES
catches a stage's worth of messages, the rc startup scripts can be daunting
or...well, there's just a lot of them. The forums and other development
efforts document this. It's a recurrent forum question and helloSystem has
done some...extraordinary work to hide them
Looking at the scripts, there didn't seem to be a unified way to lower their
verbosity. Additionally, what's emitting could be the binary where a
more-silent flag is not used e.g. routing OR the rc script devmatch.
Lacking a single "master control" to silence things, I just want after the
chattiest things that irritated, uh, me. ;)