From owner-freebsd-hackers Tue Aug 4 11:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05459 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 11:59:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05444 for ; Tue, 4 Aug 1998 11:58:56 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id LAA09291 for freebsd-hackers@freebsd.org; Tue, 4 Aug 1998 11:55:36 -0700 (PDT) (envelope-from dhw) Date: Tue, 4 Aug 1998 11:55:36 -0700 (PDT) From: David Wolfskill Message-Id: <199808041855.LAA09291@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Parsing /var/run/dmesg.boot In-Reply-To: <199807271842.LAA25740@pau-amma.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 27 Jul 1998 11:25:51 -0700 >From: Mike Smith >Something like /var/run/dmesg.boot, perhaps? [As a means of determining what the machine "saw" at boot time. dhw] OK; I've been poking & prowling around a bit, mostly with /var/run/dmesg.boot. Is it intended that the format & structure of this output be constrained in any way? The reason I'm asking is that I think it *might* be nice to be able to post-process the output to try to "better" (in some sense) analyze & depict the machine's configuration. However, if it's strictly for human consumption, this could well be a wasted effort... and each of us, I expect, has quite enough to do without such things. :-} [I've got a start toward a Perl script cobbled up that reads /var/run/dmesg.boot (or an alternative file, if you like), scans it to find the (last) boot messages, & then... well, at the moment, it just spits them out to STDOUT. Why use the script? Well, sometimes the boot messages aren't first in the file. Anyway, I tried it on a -current system, and found that -current doesn't have the empty line just before the /^FreeBSD 2/ line that 2.x does.... the goal, as alluded to above, is to generate some sort of representation of the machine's configuration as of the most recent boot in order to make replication of the machine (for disaster recovery) more nearly feasible -- assuming, of course, that the representation is available, as are current backups.] Thanks, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message