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: swapping interface names (again)
Date: Sat, 24 Jun 2006 01:58:21 +0000	[thread overview]
Message-ID: <449C9C3D.30601@bham.ac.uk> (raw)

Sorry to labour this point.  I understand that swapping eth0 and eth1
(should that prove necessary because of the initial ordering) can be
done by an application like ifrename, by making use of a temporary name
and invoking dev_change_name() in the kernel.  But does the recent
answer:
On 2006-06-15 06:29, Kay Sievers wrote:
...
 > You probably try to rename the interface to an already existing
 > name. If you want to swap names, you have to give one interface
 > a temporary name first.

imply that the whole process can be done by some udev rules that run
at boot time?  If so, how please?

Personally, I am happier with meaningful names, which I know how to
substitute using udev, but we have some users (and scripts!) who
would be happier with the old names, nailed to particular interfaces.

Thanks,
Mark
Zenwalk udev warrior

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

             reply	other threads:[~2006-06-24  1:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  1:58 MS Colclough [this message]
2006-06-24  7:59 ` swapping interface names (again) 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
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=449C9C3D.30601@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).