Re: Fwd: udev suggestion (persistent-net)

[md@Linux.IT (Marco d'Itri)]

On Nov 13, Matthias Schwarzott <zzam@gentoo.org> wrote:

> The first idea is to store in net-persistent.rules always one
> interface *less* than what is actually found. This works really
This would still not solve the case of the image of a server with
two interfaces which is moved to a different server.

> Instead of storing the full MAC immediately store only a not-so-unique
> information like e.g. the used kernel module first: Only if further
> interfaces using the same kernel module appear, store the MAC of that
> *further* interfaces. Again, this works reliable at the next boot (the
> first "unknown" interface is supposed to be the one which had appeared
> first at the last boot and gets the corresponding name).
No, because the enumeration order of drivers is not guaranteed to be
stable.

> Combining both ideas, most setups will require no persistent-net.rules,
> and people using typical setups like e.g. if there is only one ethernet
A typical server has two network interfaces.

> I would be really glad if udev would be heading into such a direction.
I would not. This would add a lot of complexity and hard to understand
conditions about when rules are created for little gain.

-- 
ciao,
Marco

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel