Date: Sun, 02 Feb 2025 20:14:03 +0000 From: "Steven Harms (High-Security Mail)" <sgharms@stevengharms.com> To: Tomek CEDRO <tomek@cedro.info> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Adjustments to userland for a quieter startup (RC system) Message-ID: <44Sc-RwC_I83PwTD-UykFfG8EFcHnBwZscSteeNEqJ_sdnmc-wrhdj-kWf2XxYDln0qB70HW3AD9qqBLEkBNeohWxlugR68PuDNYVR85PBE=@stevengharms.com> In-Reply-To: <CAFYkXjnKHjwEbsZ2r7n-HvdWZjvBBdNBBp5enLLdRy63D1Z02g@mail.gmail.com> References: <JDv17dtjl93rFR9A8XB9qHlawC2oW7JmmXWsnMKq2r51p61si48CAAOzIBi6pY_nTMdJ7zCvSL6M-Hics-CrqLhDJjZP2SG0v1zEHqH8Ug4=@stevengharms.com> <CAFYkXjmN7ma1GDuFP5p3KdHJtoO9Yri-iNLtuOL6mDKx91CBhA@mail.gmail.com> <CAFYkXjnEW8G03VKw4B77-aMQFnPLH7RZQApxWqCZpts5rpQWiA@mail.gmail.com> <S0scwcCr6CV-mqjXoa25r0XOQqm86TCcIXyl9iZ0mV-BrIKOlkfuHKxqjpbH8cuinimu4-9QRren6m9GGEZ5j_euqb9Vz0Wry1kXCalH30Y=@stevengharms.com> <CAFYkXjnKHjwEbsZ2r7n-HvdWZjvBBdNBBp5enLLdRy63D1Z02g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, February 2nd, 2025 at 2:38 PM, Tomek CEDRO <tomek@cedro.info> wr= ote: > One "black box" scenario that came to my mind we did not mention is > some embedded system that we really do not want to show anything OS > related just the final login prompt.. or was that the initial idea? That wasn't one of my main drivers, but once you settle that position at one extreme (silence) versus say a class on learning kernel design (maximal verbosity using FreeBSD as platform), it suggests that an RC mechanism that supports the full range of verbosity is useful. > Log levels is just an idea for generic commonly practiced solution > that may be applied to rc/init, you replace echo / printf with > log(lvl, fmsg, ..), but its quite a big task and not sure if really > critical right now / worth the time..? Is it critical? Probably not. Supporting more video hardware and wifi cards= is critical. But is it more than just mere chrome polishing? I think so. It's the first chance to show the market what the FreeBSD way looks like; it's a chance to show that it's not _entirely_ spartan. There's some consideration to tas= te and design. While Apple represents an extreme case, how the box feels when = it's opened is a legitimate concern. How the laptop looks at boot, I think, is a similar concern. > > Sadly boot_mute=3D"YES" was insufficient as well. It only seems to mute= /kernel/-level diagnostics. Afterward, my screen was still full of RC-orig= inating content. And yes, suppose we /could/ do an overlay until the login = prompt -- I think that should be supported. It's what I expected boot_mute= =3DYES to do by default, frankly. >=20 >=20 > Looks like the boot logo screen component needs an update, so it > covers the rc scripts too, and maybe show some animated spinner > indicating working stuff in the background, and this should fix the > problem right? Most systems work that way already, and pressing Tab or > Esc jumps to the log messages easily when necessary / possible / > allowed. I support this implementation. boot_mute=3DYES hides all diagnostic data up to the prompt being ready (surely one could hook getty's code for an ioctl?). I also think that ESC as a means for getting to the full diagnostics as in status quo is a great place to debug uh-oh moments. It's beyond my capability to size this story, *but* I can't imagine it being a weeks-long effort. Steven
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44Sc-RwC_I83PwTD-UykFfG8EFcHnBwZscSteeNEqJ_sdnmc-wrhdj-kWf2XxYDln0qB70HW3AD9qqBLEkBNeohWxlugR68PuDNYVR85PBE=>