Greetings, As per previous thread, I am still interested in a quieter fbsd experience: ideally no kernel / rc output on startup and no console messages on default TTY after login.
As I was trying to see if I could extend boot_mute, I came across another approach: - set the default console to not-zero (e.g. 4) - But then the default login prompt was also ttyv4. So I.... - Added a kernel option whereby to specify which VT the starting one (instead of following to e.g. 4). - (supporting code to make all that work) - Pair with the status quo boot_mute, you get a remarkably quiet boot up. Logo, black screen (as your getty session waits), prompt. Mea Culpa: I'm waaaaayyy out of my depth on the kernel hacking piece (just enough C to be dangerous). Consider these sketches. https://github.com/freebsd/freebsd-src/pull/1600 The suggestion separates "Which VT gets the console" and "Which VT is the starting VT." These two roles are conflated and my sketch unwinds that. Hereby one gets: - a nice quiet boot up - a default login screen whose vi session isn't interrupted (by default) with noise from your wificard (if you're on laptop fbsd) -- frightening/annoying to some - a dedicated live sink for console messages (versus a log file or versus your vi session) closer to a real serial console or OSX's console.app Is this a better approach vs extending boot_mute's run? Or if this is wrong-headed I'll go back to previous paths of inquiry. Steven --- Public Key: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE Messages from this account are considered the best-secured and most reliable. Send information regarding health, wealth, or requiring higher standards of security to this address. Sent with [Proton Mail](https://proton.me/mail/home) secure email.
