Bruce Dubbs wrote: > As I understand this discussion, we are talking about the situation > when a system has more than one network card.
Yep, otherwise it'll always be eth0. (...Well, usually. Madwifi cards will be ath0, wireless devices may be wifi0 or wlan0 or various other strings depending on driver, PPP devices are ppp0 (of course they're virtual anyway so it doesn't much matter), etc. But you get the idea.) > I was once told that the card closest to the power supply would come > up first because it is in the lowest numbered pci slot. I am not sure, but I do not believe this is the case anymore. (Or if it is, it's not supposed to be relied on.) ISTR reading something about the PCI device discovery order changing several kernels ago. > Getting it perfect on the very first boot would only be necessary if > you were doing a remote build where you have multiple network cards > and that is a pretty advanced topic, well beyond the target audience > of the book. This is true. On the other hand, if it's not too complex to get it perfect, it may be worth it; see my response to Alex on just having the user generate a persistent rule for each NIC before reboot (like we do today).
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
