diff for duplicates of <20091010044056.GA5350@mock.linuxdev.us.dell.com> diff --git a/a/1.txt b/N1/1.txt index c137c9e..b54cefb 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -27,7 +27,7 @@ mostly early 2.6 kernel days, the order in which network drivers loaded played a role in determining the name of the device. Drivers loaded first would get their devices named first. If I have two types of devices, say an e100-driven NIC and a tg3-driven NIC, I could -figure out that the names would be eth0á00 and eth1=tg3 by setting +figure out that the names would be eth0=e100 and eth1=tg3 by setting the load order in /etc/modules.conf (now modprobe.conf). If I wanted the other order, fine, just switch it around in modules.conf and reboot. OS installers, being the first running instance of Linux, @@ -60,7 +60,7 @@ breadth-first ordering became depth-first. (for each bus; for each device; if the device is a bridge, scan the busses behind it.). This caused NICs on bus 0 device 5, and bus 1 device 3, (eth0 and 1 respectively) to be enumerated differently due to the a bridge from -bus 0 to bus 1 at 0:4. My crude hack of pci¿sort, with some dmi +bus 0 to bus 1 at 0:4. My crude hack of pci=bfsort, with some dmi strings to match and auto-enable, at least reverted this back to the ordering the 2.4 kernel and Windows used. Now we have to keep adding systems to this DMI list (Dell has a number of systems on this list diff --git a/a/content_digest b/N1/content_digest index 90e400b..2495df3 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,7 +4,7 @@ "ref\020091009194401.036da080@nehalam\0" "From\0Matt Domsch <Matt_Domsch@dell.com>\0" "Subject\0Re: PATCH: Network Device Naming mechanism and policy\0" - "Date\0Sat, 10 Oct 2009 04:40:57 +0000\0" + "Date\0Fri, 9 Oct 2009 23:40:57 -0500\0" "To\0Stephen Hemminger <shemminger@vyatta.com>\0" "Cc\0netdev@vger.kernel.org" linux-hotplug@vger.kernel.org @@ -41,7 +41,7 @@ "loaded played a role in determining the name of the device. Drivers\n" "loaded first would get their devices named first. If I have two types\n" "of devices, say an e100-driven NIC and a tg3-driven NIC, I could\n" - "figure out that the names would be eth0\303\24100 and eth1=tg3 by setting\n" + "figure out that the names would be eth0=e100 and eth1=tg3 by setting\n" "the load order in /etc/modules.conf (now modprobe.conf). If I wanted\n" "the other order, fine, just switch it around in modules.conf and\n" "reboot. OS installers, being the first running instance of Linux,\n" @@ -74,7 +74,7 @@ "device; if the device is a bridge, scan the busses behind it.). This\n" "caused NICs on bus 0 device 5, and bus 1 device 3, (eth0 and 1\n" "respectively) to be enumerated differently due to the a bridge from\n" - "bus 0 to bus 1 at 0:4. My crude hack of pci\302\277sort, with some dmi\n" + "bus 0 to bus 1 at 0:4. My crude hack of pci=bfsort, with some dmi\n" "strings to match and auto-enable, at least reverted this back to the\n" "ordering the 2.4 kernel and Windows used. Now we have to keep adding\n" "systems to this DMI list (Dell has a number of systems on this list\n" @@ -188,4 +188,4 @@ "Technology Strategist, Dell Office of the CTO\n" linux.dell.com & www.dell.com/linux -1fdb7a51a92e771350a46818858dc316df0b1667a6e3af4d55093c0bda17724a +599784decb5d4780657e623ab1501a1ff443cc9044d27e037a422d9bdb59a75f
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.