All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: how to rename network interface?
Date: Tue, 11 May 2004 10:41:59 +0000	[thread overview]
Message-ID: <20040511104159.GA12034@vrfy.org> (raw)
In-Reply-To: <c7lt0l$dr7$1@sea.gmane.org>

On Mon, May 10, 2004 at 08:41:39AM -0400, mikep wrote:
> and syslog shows that the rules are applied:
> 
> udev[7620]: configured rule in '/etc/udev/rules.d//10-udev.rules' at 
> line 3 applied, 'eth0' becomes 'eth1'
> 
> udev[7621]: configured rule in '/etc/udev/rules.d//10-udev.rules' at 
> line 2 applied, 'eth1' becomes 'eth0'
> 
> However, the end result is that device 0x8139 is still configured as 
> eth0 as ifconfig shows:

Are you sure the the interface is not in use, while udev tries to rename
it. Maybe your network script is faster than udev?

Kay


> >>ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:01:0A:10:A7:3B
>           inet addr:192.168.0.5  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
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:[~2004-05-11 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09 18:24 how to rename network interface? mikep
2004-05-10  2:05 ` Kay Sievers
2004-05-10 11:30 ` mikep
2004-05-10 12:41 ` mikep
2004-05-11 10:41 ` Kay Sievers [this message]

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=20040511104159.GA12034@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.