linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: MS Colclough <m.s.colclough@bham.ac.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: swapping interface names (again)
Date: Sun, 25 Jun 2006 14:39:52 +0000	[thread overview]
Message-ID: <449EA038.5010009@bham.ac.uk> (raw)
In-Reply-To: <449C9C3D.30601@bham.ac.uk>

I also found the Ubuntu patch (70-ifrename.patch).  Taking just the part
that deals with the rename_net_if() function, I found it to be exactly
what I want.  A pair of rules like
... SYSFS{address}="00:16:17:5a:e5:7e", NAME="eth0"
... SYSFS{address}="00:40:95:46:f4:16", NAME="eth1"
enforce the necessary stability, swapping the kernel names on occasions
when that proves necessary.

I would certainly like to see this merged with udev.  It's certainly
better than me telling users "you can have any names you like, except
those you are used to".

Thanks,   Mark

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-06-25 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  1:58 swapping interface names (again) MS Colclough
2006-06-24  7:59 ` Marco d'Itri
2006-06-24 20:02 ` juuso.alasuutari
2006-06-25  3:07 ` Alexander E. Patrakov
2006-06-25  8:35 ` Marco d'Itri
2006-06-25 12:18 ` juuso.alasuutari
2006-06-25 12:21 ` Marco d'Itri
2006-06-25 14:39 ` MS Colclough [this message]
2006-06-26  7:46 ` Scott James Remnant

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=449EA038.5010009@bham.ac.uk \
    --to=m.s.colclough@bham.ac.uk \
    --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).