Re: How does "alias ethX drivername" in modules.conf work?

[Riley Williams]

Hi Mark.

 > (apologies for splitting my reply into multiple pieces, but each
 > part covers different territory).

 >>  2. Multiple identical static interfaces.
 >>
 >>     At the moment, you are required to initialise the interfaces in
 >>     ascending order of their name in the modules.conf file.
 >>
 >>     I've dealt with this situation on several occasions, and never
 >>     found this to be a problem in any way.

 > Have you ever assembled a distribution that's going to be imaged
 > into several thousands to several tens of thousands of hardware
 > boxes, with evolving-into-the-future changes in hardware version
 > and changes in component suppliers?

I haven't personally, no, but RedHat, Caldera, SUSE, Debian and
Eridani all have, and (curiously enough) they all use the same basic
solution, although implemented in different ways. This is also the
solution implemented by the ifmap script I attached to my previous
email.

 > If Linux really wants to break into the appliance market, this
 > is going to be a bigger and bigger issue.

Agreed, but then, it appears to be an issue that has largely been
solved. The only part that may still need attention (I'm not up to
date on it, so can't say for sure) is the hotplug stuff.

Best wishes from Riley.