linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@hpl.hp.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev+ifrename integration
Date: Fri, 09 Mar 2007 17:11:22 +0000	[thread overview]
Message-ID: <20070309171122.GA27274@bougret.hpl.hp.com> (raw)
In-Reply-To: <20070307194435.GA22264@bougret.hpl.hp.com>

On Fri, Mar 09, 2007 at 11:57:49AM +0000, Scott James Remnant wrote:
> On Thu, 2007-03-08 at 10:15 -0800, Jean Tourrilhes wrote:
> > 
> > Yes, but your patch does not seem to be in the upstream
> > udev. Why is that ?
> > 
> It's been submitted upstream, but not accepted; Kay tends towards
> conservatism until things are proved to be needed.

	And my personal bias is modularity. All users should not have
to bear the cost of a selected few, but the selected few should be
able to do it.

> > And does you patch support all features of ifrename, or just a
> > select few ?
> > 
> Select few.
> 
> We explicitly do not want to support all of the features of ifrename,
> because it caused us nothing but headaches in the past.
> 
> All we want is for interface names to be consistent across reboots, and
> for there to be no race conditions between the interface being added and
> renamed; the patch we use is sufficient to do that.

	Actually, udev does a much better job at that than ifrename,
as ifrename does not autogenerate persistent rules.

> When we used to call-out ifrename from hotplug, we had incredible
> numbers of problems due to ifrename mis-features and race conditions
> inherent with not controlling the interface renaming ourselves.

	That was more a hotplug issue than a ifrename issue. And
actually, the other big culprit there was ifupdown and its stupid
locking strategy (thank god this is now fixed).

> Scott

	Jean

-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-03-09 17:11 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 [this message]
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
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=20070309171122.GA27274@bougret.hpl.hp.com \
    --to=jt@hpl.hp.com \
    --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).