Re: [PATCH] udev+ifrename integration

[Kay Sievers <kay.sievers@vrfy.org>]

On Mon, 2007-03-12 at 09:07 -0700, Jean Tourrilhes wrote:
> On Sat, Mar 10, 2007 at 02:28:13PM +0100, Kay Sievers wrote:
> > 
> > Oh, I think we should just match on a DEVPATH variable to import. Any
> > external tool, not limited to the INTERFACE variable, that causes the
> > kernel to change the devpath, would just need to pass the new value for
> > udev to update all internal values like %k %n %p.
> 
> 	I'm sorry, but I don't get it.
> 	First, I don't see how the other internal variables are
> updated.

sysfs_device_set_values(udev->dev, value, NULL, NULL);
will do this with the value of DEVPATH passed by the tool.

The tool called by IMPORT= will return:
  DEVPATH=/...
and whatever it "thinks" is useful here, like the new INTERFACE name.
If udev finds DEVPATH, it will update %p %k %n. All other variables just
set or replace the current event environment.

> Maybe a sample of rules would help me.

SUBSYSTEM="net", ACTION="add", IMPORT="/sbin/ifrename --export -i %k"

> 	Second, I don't see how this would prevent subsequent naming
> rules to apply.

We can make NAME="" work, to prevent other NAME rules from matching. For
now NAME="%k" may already work.

Kay


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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