From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: swapping interface names (again)
Date: Sun, 25 Jun 2006 03:07:58 +0000 [thread overview]
Message-ID: <449DFE0E.5090208@ums.usu.ru> (raw)
In-Reply-To: <449C9C3D.30601@bham.ac.uk>
juuso.alasuutari@tamperelainen.org wrote:
> I accidentally only sent my message to Marco. Here it is for the list also:
>
> Quoting Marco d'Itri <md@Linux.IT>:
>
>> On Jun 24, MS Colclough <m.s.colclough@bham.ac.uk> wrote:
>>
>>> imply that the whole process can be done by some udev rules that run
>>> at boot time? If so, how please?
>> Look at the Debian package for a simple script which generates rules on
>> demand.
>
> It's of course easy to write a script that creates something like
> z99-network.rules. But what should it contain?
>
> If I have eth0 and eth1, and want to swap their names, I first need to rename
> them to e.g. tempeth0 and tempeth1, and then to eth1 and eth0. But what kind of
> rule would recognise when all temporary names are created and apply the final
> ones?
Don't look at the Debian package. It is very likely to contain this problem,
because for my single-card setup, Debian udev 0.093-1 writes:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# PCI device 10ec:8139 (8139too)
SUBSYSTEM="net", DRIVER="?*", SYSFS{address}="00:e0:4c:7c:4a:d3", NAME="eth0"
Of course this will break if I a new card in such a way (read: PCI slot) so that
without this rule it becomes eth0. Then this rule will attempt to rename my old
card to eth0, and boom... there is already eth0.
And I don't know any solution that allows eth%d as a final name.
--
Alexander E. Patrakov
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
next prev parent reply other threads:[~2006-06-25 3:07 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 [this message]
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=449DFE0E.5090208@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).