On Wed, Nov 26, 2003 at 01:37:48PM -0800, Soren Jacobsen wrote:
> If you don't mind, I'd like to make a couple comments about this. The
> first is that the system message buffer often gets overwritten during
> the uptime of a system. For instance, I've got a few lines of:
> 
> nfs server 192.168.0.7:/usr/pkgsrc: not responding
> nfs server 192.168.0.7:/usr/pkgsrc: is alive again
> 
> in my buffer. If I got a lot more of those messages, the hardware probe
> info that you expect to find would be pushed off. So instead of "dmesg |
> grep" you ought to just grep /var/run/dmesg.boot.
> 
> The second thing is that ifconfig presents the information in a much
> nicer way. Something like "ifconfig <interface> | awk '/address:/ {print
> $2}' would work nicely.

And I would add that, for this specific problem, the driver fails to read the
MAC address properly (or think it has), so neither the dmesg nor ifconfig
will show any MAC address.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--