http://bugs.linuxfromscratch.org/show_bug.cgi?id=1672
------- Additional Comments From [EMAIL PROTECTED] 2005-12-19 07:41 -------
To clarify and summarize:
1) Unconfigured system with hotplug removed and udev upgraded, and with 8139too
and e100 network cards, both drivers as modules:
sometimes e100 gets eth0 and 8139too gets eth1, sometimes the other way round.
That's because the module loading order is unpredictable. Attempts to rename
cards to some stable names using rules like:
SUBSYSTEM=="net", SYSFS{address}=="00:11:22:33:44:55", NAME="homenet"
sometimes work (i.e. the new "homenet" name gets applied to this card) and
sometimes fail (i.e. the original "eth0" or "eth1" name sticks).
2) Same system with this rule:
ACTION=="add", SUBSYSTEM=="net", WAIT_FOR_SYSFS="address"
The 8139too sometimes gets eth0 and sometimes eth1. The same holds for e100.
But, a stable name can now be _reliably_ assigned by rules like:
SUBSYSTEM=="net", SYSFS{address}=="00:11:22:33:44:55", NAME="homenet"
SUBSYSTEM=="net", SYSFS{address}=="00:ff:ee:dd:cc:bb", NAME="internet"
3) Same system with all three rules.
One card always gets the "homenet" name, and the other card is "internet". One
can assign IPs by creating
/etc/sysconfig/network-devices/ifconfig.{home,inter}net (instead of
ifconfig.eth{0,1}) as the book says.
The module loading order is still unpredictable, but it doesn't matter now.
Proposed changes to the book: upgrade udev and the kernel, remove hotplug,
explain how to blacklist unwanted modules in /etc/modprobe.conf, explain how to
(and why) rename network interfaces. In the far future, handle network hotplug
events so that a Zaurus gets assigned an IP just after it is connected to a USB
port.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
