From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: bus id match
Date: Tue, 22 May 2012 13:09:10 +0000 [thread overview]
Message-ID: <4FBB8FF6.7000608@suse.de> (raw)
In-Reply-To: <op.wepn2cfimcnq8x@idontknow.suse.cz>
On 05/22/2012 03:07 PM, Michal Filka wrote:
> Hi,
>
> I've problem with following rule (simplified as much as possible):
>
> # replaced 70-persistent-net.rules
> SUBSYSTEM="net", KERNELS="0000:00:19.0", NAME="eth1"
>
> # udevadm test --action≠d /sys/class/net/eth0
> (snip)
> rename_netif: changing net interface name from 'eth0' to 'eth1'
> rename_netif: error changing net interface name eth0 to eth1: Device
> or resource busy
> (snip)
> UDEV_LOG=6
> DEVPATH=/devices/pci0000:00/0000:00:19.0/net/eth0
> INTERFACE=eth0
> IFINDEX=2
> ACTION≠d
> SUBSYSTEM=net
> ID_VENDOR_FROM_DATABASE=Intel Corporation
> ID_MODEL_FROM_DATABASEÇ566DC Gigabit Network Connection
> ID_BUS=pci
> ID_VENDOR_ID=0x8086
> ID_MODEL_ID=0x104b
> ID_MM_CANDIDATE=1
> SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth1
> TAGS=:systemd:
>
> So, the device is named correctly (eth1), but what about that
> rename_netif errors? Is that a problem?
>
You can't rename network interfaces in state 'UP'.
That only works for unconfigured interfaces.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-22 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 13:07 bus id match Michal Filka
2012-05-22 13:09 ` Hannes Reinecke [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=4FBB8FF6.7000608@suse.de \
--to=hare@suse.de \
--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).