From owner-freebsd-current Thu Nov 12 16:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20745 for freebsd-current-outgoing; Thu, 12 Nov 1998 16:31:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20734 for ; Thu, 12 Nov 1998 16:31:32 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA21865; Fri, 13 Nov 1998 11:00:56 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811121942.LAA28198@pau-amma.whistle.com> Date: Fri, 13 Nov 1998 11:00:56 +1030 (CST) From: "Daniel O'Connor" To: David Wolfskill Subject: Re: StarOffice-5.0... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Nov-98 David Wolfskill wrote: > Well, one example of something I would like to be able to do is to have > an automatic procedure (say, a script) that I could run on a box and get > enough information that I could squirrel away (off-site, for example) so > that, given the list and enough money, I could specify what parts to buy > so the machine could be re-created (and so that once the off-site > backups were restored, I'd have a fairly good approximation to the > original machine). How about... ssh user@machine 'mail -s "dmesg from machine" my@email.com Even better: I'd like for a person who is not necessarily a FreeBSD > wizard be able to read the list, specify the parts, and assemble them > into a working whole. Well, dmesg isn't that hard to read... > That may well be useful for many purposes. It's not at all obvious that > it's useful for what I'm trying to do. So far, looking at > /var/run/dmesg.boot comes closest that I've been able to find, but > there's very little there about the video card(s?), for example. And what irq's it uses are going to be any better? IMHO the only way you could do that would be to read the X output.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message