From owner-freebsd-questions Fri Oct 24 12:30:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13644 for questions-outgoing; Fri, 24 Oct 1997 12:30:50 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13636 for ; Fri, 24 Oct 1997 12:30:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA26629; Fri, 24 Oct 1997 12:28:09 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026623; Fri Oct 24 19:28:00 1997 Date: Fri, 24 Oct 1997 12:26:25 -0700 (PDT) From: Julian Elischer To: David K Phinney cc: FreeBSD-Questions@FreeBSD.ORG Subject: Re: Listing devices in 2.2.x In-Reply-To: <199710241856.LAA08193@lithium.dowco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk on some systems there is /var/log/dmesg.today if you had devfs you could look at that.. (or you could just reboot? but I guess there must be a reason this is not true.) you could always recompile /sbin/dset to print out ALL the values, and not just the ones it touches. On Fri, 24 Oct 1997, David K Phinney wrote: > > That file has unfortunately been rotated enough times that the boot > messages have been purged. > > Is there any other way? Is there no tool to extract the info from the > kernel? > > Please send answers to my email address, and thanks again! > > > --dave > David K. Phinney > Systems Administrator (604) 933-2821 > dowco.com internet dave@dowco.com > > > look in /var/log/messages > > > > > > On Fri, 24 Oct 1997, David K Phinney wrote: > > > > > Hello, > > > > > > How does one go about listing configured devices in FreeBSD 2.2, it > > > seems 2.1's `lsdev' command is no longer supported. (It hasn't been > > > updated by CVSup in a while, and when I run it I get an error about > > > hw.devconf.number not existing.) I can't use `dmesg' to see what it > > > said at boot-up, because those messages have long since been pushed > > > out of the buffer. >