Date: Tue, 22 Jan 2002 16:14:06 -0500 From: Brian Reichert <reichert@numachi.com> To: Roger 'Rocky' Vetterberg <listsub@rambo.simx.org> Cc: Brian Reichert <reichert@numachi.com>, Brooks Davis <brooks@one-eyed-alien.net>, hackers@FreeBSD.ORG Subject: Re: cpu info in userland Message-ID: <20020122161406.L2872@numachi.com> In-Reply-To: <3C4DD39B.2050906@rambo.simx.org>; from listsub@rambo.simx.org on Tue, Jan 22, 2002 at 10:03:23PM %2B0100 References: <20020122113351.A25927@Odin.AC.HMC.Edu> <20020122155202.J2872@numachi.com> <3C4DD39B.2050906@rambo.simx.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 22, 2002 at 10:03:23PM +0100, Roger 'Rocky' Vetterberg wrote: > Brian Reichert wrote: > > > On Tue, Jan 22, 2002 at 11:33:51AM -0800, Brooks Davis wrote: > > > > What I've taken to doing it preserving dmesg upon boot into a known > > file, and referencing _that_ via whatever mechanism I want. Easy > > to scan. > > > Isnt dmesg always preserved in /var/run/dmesg.boot? I guess it is. A point of confusion on my part is that sometime it seems that system message buffer is preserved accross reboots, if that makes any sense. I've seen situations where 'dmesg' (and by extension dmesg.boot) will contain multiple passes of device probes, etc. I could easily be imagining this, as I can't think of a mechanism to allow for it, nor a reason to do it... > -- > R -- Brian 'you Bastard' Reichert <reichert@numachi.com> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020122161406.L2872>