Date: Thu, 8 Sep 2022 13:21:26 -0400 From: grarpamp <grarpamp@gmail.com> To: hackers@freebsd.org Subject: Re: [summary] Re: Reasonable/sane limits for kern.msgbufsize? Message-ID: <CAD2Ti2-aT5LKYHnpNrJ3_xbn%2BjJyFPALKGUU7JPwJaWhvYpbOQ@mail.gmail.com> In-Reply-To: <YxnMCxJszmkobhoH@albert.catwhisker.org> References: <YxFCDGCRmoXpDJn/@albert.catwhisker.org> <YxnMCxJszmkobhoH@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> sane limits for kern.msgbufsize > ... > /var/run/dmesg.boot gets the full boot log, even for a verbose A sane default might exist where users can stuff their boxes and kernels full of hardware (drives, GPU's, USB's, CPU cores, LINT, etc) and have the entire verbose boot through login still available in the buffer. Default at times past may not have even supported verbose LINT w/no hw.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2-aT5LKYHnpNrJ3_xbn%2BjJyFPALKGUU7JPwJaWhvYpbOQ>