[syslinux] Using NIC-Specific Information to Choose a Config-File

[Gene Cumm]

On Fri, Nov 23, 2012 at 5:50 AM, Ady <ady-sf at hotmail.com> wrote:
>> The only concern I have at this time is about setting the standard in stone
>> for using VVVVDDDD.  There might be a better consideration for the label
>> namespace; maybe something like 'pcinicVVVVDDDD'.  Actually, typing all that
>> wouldn't be a picnic; very dreadful?
>>
>> - Shao Miller
>
> You are currently matching both Vendor and Device ID altogether, in a
> fix complete "8-characters" value.
>
> Maybe some partial matching selections would introduced more
> flexibility in comparison to using VVVVDDDD in stone.
>
> Some brainstorming...
>
>  LABEL install1
>      COM32 nictype.c32
>      APPEND --vendor --config
>
> would read VVVV only and point to a config file with name "VVVV____"
> (4 matching values, 4 underscore characters, (one period and file
> extension) ). The trailing underscore characters might be considered
> optional.

Using just the Vendor ID could be useful.

> And
>
>  LABEL install2
>      COM32 nictype.c32
>      APPEND --deviceid --config
>
> would read DDDD only and point to a config file with name "____DDDD".

This I'd say is likely to cause issues rather than benefits.  When
would someone ever have two or more independent vendors using the same
device ID that you want treated identically?

If we assume Ethernet and 802.11 devices are bootable, let's compare
Intel (8086) and Broadcom (14e4):
4220, 4222 are a place where the two match.  The disparity between
these two pair of cards is enough in my opinion to say that's a bad
idea.

-- 
-Gene