Date: Wed, 23 Jan 2002 12:04:07 +1000 From: Greg Black <gjb@gbch.net> To: "Crist J . Clark" <cjc@FreeBSD.ORG> Cc: Brian Reichert <reichert@numachi.com>, "Roger 'Rocky' Vetterberg" <listsub@rambo.simx.org>, Brooks Davis <brooks@one-eyed-alien.net>, hackers@FreeBSD.ORG Subject: Re: cpu info in userland Message-ID: <nospam-1011751447.75737@bambi.gbch.net> In-Reply-To: <20020122175631.A83184@blossom.cjclark.org> of Tue, 22 Jan 2002 17:56:31 PST References: <20020122113351.A25927@Odin.AC.HMC.Edu> <20020122155202.J2872@numachi.com> <3C4DD39B.2050906@rambo.simx.org> <20020122161406.L2872@numachi.com> <nospam-1011750084.73718@bambi.gbch.net> <20020122175631.A83184@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Crist J . Clark" wrote: | On Wed, Jan 23, 2002 at 11:41:24AM +1000, Greg Black wrote: | > Brian Reichert wrote: | > | > | 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... | > | > You're not imagining it -- certainly 4.4-RELEASE does this. | | If you drop to single-user and go back to multi-user, dmesg.boot gets | written again in rc(8). I have patched rc(8) to only write dmesg.boot | at boot. I should look again at committing that. I have never dropped to single-user. But my 4.4-RELEASE laptop has the records of several full reboots in /var/run/dmesg.boot, which I really wish it wouldn't ... 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?nospam-1011751447.75737>