Date: Fri, 4 Aug 2006 10:17:16 -0300 (ADT) From: User Freebsd <freebsd@hub.org> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: Olivier Nicole <on@cs.ait.ac.th>, freebsd-questions@freebsd.org Subject: Re: Stand up and be counted - BSDStats Project Message-ID: <20060804101513.R25268@ganymede.hub.org> In-Reply-To: <44D3262B.2000400@infracaninophile.co.uk> References: <20060803180553.B6529@ganymede.hub.org> <200608040314.k743EBK6050609@banyan.cs.ait.ac.th> <44D3262B.2000400@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Aug 2006, Matthew Seaman wrote: > This is cool and all, but why are the concentration solely on PCI > devices? pciconf output doesn't tell you directly what CPUs are in the > system or even how many there are. It doesn't tell you exactly what > sort of memory or disk drives the system uses -- all of which would be > important information that might just persuade hardware manufacturers to > provide more FreeBSD support. Surely a condensed version of > /var/run/dmesg.boot is more to the point. /var/run/dmesg.boot can't be relied on, unfortunately ... I've had *many* times where a reboot leaves that blank, or with "non-dmesg like" output ... if you can provide a non-dmesg method of adding this information that is consistent (ie. pciconf), then sure, we can add this sort of information ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060804101513.R25268>