Am 11.04.2013 13:46, schrieb Colin Guthrie: > 'Twas brillig, and Harald Hoyer at 11/04/13 12:27 did gyre and gimble: >> Only >> $ rpm -qf /lib/udev/rename_device >> initscripts-9.45-2.fc19.x86_64 >> >> kicks in and renames interfaces according to the ifcfg-* files, if HWADDR is >> set, and if there are no conflicts. > > It's the "if there are no conflicts" bit that's hard to address tho' > right? I mean, this is what the persistent rules stuff was meant to fix > (but didn't due to the afore mentioned races etc.). If I have two NICs > (quite common) and the kernel happens to initialise them the "wrong" way > round, this logic breaks down does it not? (please correct me if I'm wrong). > > Should we then consider trying to push a new default name scheme into > the kernel side such that they come up as "eth-ng0" etc. by default > allowing any userspace stuff to rename them to "eth1" or whatever > without so much likelihood of such conflicts. > > That shouldn't affect the udev persistent name scheme, and should allow > people who want to keep the traditional ethX names to carry on with out > *that* much risk of the rename failing.
THAT SOUNDS GREAT!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
