From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev+ifrename integration
Date: Fri, 16 Mar 2007 00:14:22 +0000 [thread overview]
Message-ID: <1174004062.21936.3.camel@lov.localdomain> (raw)
In-Reply-To: <20070307194435.GA22264@bougret.hpl.hp.com>
On Thu, 2007-03-15 at 16:27 -0700, Jean Tourrilhes wrote:
> On Mon, Mar 12, 2007 at 05:51:04PM +0100, Kay Sievers wrote:
> > On Mon, 2007-03-12 at 09:07 -0700, Jean Tourrilhes wrote:
> >
> > > 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.
>
> Thanks for the help, I'm still learning about udev. It all
> make sense now.
> I've tested udev with your patch (see below) and the following
> udev rule and confirm that it works properly.
Nice!
> ---------------------------------
> SUBSYSTEM="net", ACTION="add", IMPORT="/sbin/ifrename -u -i %k", NAME:="%k"
> ---------------------------------
Current udev git should also prevent any later naming rule to match,
with NAME="" now.
> If the interface is specified in /etc/iftab, the renaming is
> done and further rules ignored. If the interface is not in /etc/iftab,
> or if /etc/iftab does not exist, no renaming is done and further rule
> do apply. And it works properly at boot time. This allow smooth
> integration.
> I've released a new version of ifrename that fixes some
> devpath bugs.
Sounds good.
> Also, with the additional fix in the attached patch, you can
> use udevtest like this :
>
> ---------------------------------
> ENV{UDEV_LOG}="6", SUBSYSTEM="net", ACTION="add", IMPORT="/sbin/ifrename -D -V -u -i %k", NAME:="%k"
> ---------------------------------
I've applied the udevtest part, the other part I already committed
yesterday.
Thanks,
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
next prev parent reply other threads:[~2007-03-16 0:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 19:44 [PATCH] udev+ifrename integration Jean Tourrilhes
2007-03-07 20:35 ` Kay Sievers
2007-03-07 21:11 ` Jean Tourrilhes
2007-03-08 11:24 ` Scott James Remnant
2007-03-08 18:15 ` Jean Tourrilhes
2007-03-09 11:57 ` Scott James Remnant
2007-03-09 13:59 ` Kay Sievers
2007-03-09 17:11 ` Jean Tourrilhes
2007-03-09 17:17 ` Jean Tourrilhes
2007-03-10 1:50 ` Jean Tourrilhes
2007-03-10 13:28 ` Kay Sievers
2007-03-12 16:07 ` Jean Tourrilhes
2007-03-12 16:51 ` Kay Sievers
2007-03-15 23:27 ` Jean Tourrilhes
2007-03-16 0:14 ` Kay Sievers [this message]
2007-03-16 0:24 ` Jean Tourrilhes
2007-04-30 10:02 ` Kay Sievers
2007-04-30 17:00 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1174004062.21936.3.camel@lov.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).