Date: Fri, 22 Jan 1999 10:58:36 +1030 From: Greg Lehey <grog@lemis.com> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: "Matthew N. Dodd" <winter@jurai.net>, John Fieber <jfieber@indiana.edu>, Mikael Karpberg <karpen@ocean.campus.luth.se>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, abial@nask.pl, dfr@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys bus.h src/sys/kern subr_bus.c Message-ID: <19990122105836.Q417@freebie.lemis.com> In-Reply-To: <xzp67a09rxs.fsf@flood.ping.uio.no>; from Dag-Erling Smorgrav on Thu, Jan 21, 1999 at 11:33:51PM %2B0100 References: <Pine.BSF.4.02.9901201614590.8926-100000@sasami.jurai.net> <xzp67a09rxs.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 21 January 1999 at 23:33:51 +0100, Dag-Erling Smorgrav wrote: > "Matthew N. Dodd" <winter@jurai.net> writes: >> Actually, that sucks because `dmesg | grep ^da0` becomes useless. >> >> Why not come up with a dmesg bootup pretty printer that runs after the >> splashscreen? > > While we're at it, I'd *love* to have some way of logging the output > of /etc/rc*, since after a nasty crash fsck messages can easily > overflow the scrollback buffer, not to mention that it gets clobbered > by the splash screen or by a mode switch if you have e.g. VESA_132x60 > in allscreens_flags like me. I'm planning to do this. It involves starting a proto-syslogd and logging all the rc output to it. The daemon keeps the output in virtual memory until the startup has completed, when it gets a kick (signal), turns into a real syslogd, and logs all the output. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990122105836.Q417>