From owner-freebsd-hackers Mon Jul 27 11:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07621 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:27:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07578 for ; Mon, 27 Jul 1998 11:27:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00633; Mon, 27 Jul 1998 11:25:51 -0700 (PDT) Message-Id: <199807271825.LAA00633@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-reply-to: Your message of "Mon, 27 Jul 1998 10:45:50 PDT." <199807271745.KAA25470@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 11:25:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. Something like /var/run/dmesg.boot, perhaps? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message