FWIW I recently added logic to our local.rc.subr to redirect output to a console.log if desired (some platforms boot quicker with less output going to console). It does nothing for output from kernel modules loaded by rc, but greatly reduces output and has the major benefit that we can examine the "console" output after the fact. Which is much more useful than sending the output to /dev/null.
The above is much easier done in our env as we have an initial rootfs which is an iso image, and run a preboot script which does things like mounting the real rootfs after fsck etc before running the real init(8). That preboot can thus take care of rotating and initializing console.log or disabiling it under various circumstances, and we set rc_config_xtra in local.rc.subr so we can tell when it is being read for first the so we can redirect output again for rc. Doing something like that via rc alone would be "tricky". Warner Losh <i...@bsdimp.com> wrote: > If you rarely want silence to the login prompt, we likely need to find > a way to redirect the console output to a second screen or > something. I thought we had a null console, but that appears to be > only in the boot loader. The rc output goes to the first console in > the list of all the consoles since that's what /dev/console is > connected to. One much wanted, often started but not finished project > is to actually make /dev/console connected to all the consoles > together.
