From owner-freebsd-questions Wed Nov 17 13:57: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id B8D8D1520F for ; Wed, 17 Nov 1999 13:56:58 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id WAA22116; Wed, 17 Nov 1999 22:37:30 +0100 (CET) Message-Id: <199911172137.WAA22116@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Graeme Tait Cc: freebsd-questions@FreeBSD.ORG Subject: Re: How to discover SCSI ID's in a running system Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 17 Nov 1999 06:58:14 PST." <3832C286.17A2@echidna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Nov 1999 22:37:30 +0100 From: Gary Jennejohn Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graeme Tait writes: >As I said in my original post, the original boot information has long >since been displaced from the logs by other messages (in particular, a >flood of messages that resulted from a filesystem getting full). > [snip] Others have suggested /var/run/dmesg.boot, but I'm not certain that 2.2.7 had that. The boot messages should still be in /var/log/messages, or one of the backed up/compressed copies. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message