Subject: Re: A possible way of handling variant/common devices
To: None <email@example.com>
From: Mike Long <firstname.lastname@example.org>
Date: 03/28/1997 18:07:05
>Date: Fri, 28 Mar 1997 17:58:54 -0500
>From: Bill Sommerfeld <email@example.com>
>> I guess I'm missing the point. What would an _autoconfig_ parent for
>> Ethernet, or FDDI, or whatever, devices give us that we can't already
>> do with config's attribute mechanism, and the kernel config attributes
>> that exist for ether, fddi, arcnet, etc?
>It's purely a user-interface, user-convenience issue.
>If your first LAN interface is always at lan0, not at one of
>(this list was generated mechanically, and may leave out a few things..)
>then scripts and instructions for doing installation and configuration
>can be much simpler.
Well after Jason's addition of -l to ifconfig you can just use
lan0=`ifconfig -l |head`
(or something like that), which is a heck of a lot easier than mucking
with the kernel.
Mike Long <firstname.lastname@example.org> <URL:http://www.shore.net/~mikel>
VLSI Design Engineer finger email@example.com for PGP public key
Analog Devices, CPD Division CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA (eq (opinion 'ADI) (opinion 'mike)) -> nil