[ previous ] [ next ] [ threads ]
 
 From:  Kris Maglione <bsdaemon at comcast dot net>
 To:  m0n0wall-dev Mailing List <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Making interface assignments more resilient
 Date:  Sun, 6 Nov 2005 20:16:14 -0500
On Sun, Nov 06, 2005 at 08:07:47PM -0500, Chris Buechler wrote:
>there are other options, like parsing dmesg might produce more
>specific output under certain circumstances.
I considered that, and decided on pciconf -lv, rather than dmesg.

I agree that the device string can be confusing when it represents the 
chipset, rather than the device, but it's still useful. For instance, it's 
easy to look at 2 network cards and see one with a big chip that says 3com and 
another that says Realtek. Nevertheless, names like rl0, pcn2, etc. are 
meaningless to most people. It would be better to assign artificial names like 
Ethernet 1, WiFi 1, Firewire Ethernet 1, etc. than to use the real interface 
names, but I'd still advocate using the device strings.

-- 
Kris Maglione

Real programmers don't eat quiche.  In fact, real
programmers don't know how to spell quiche.  They eat
twinkies and szechuan food.