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: Problem recreating 70-persistent-net.rules with udev 0.125-7 on
Date: Tue, 10 Mar 2009 17:34:59 +0000	[thread overview]
Message-ID: <ac3eb2510903101034l54d1abecm5ac9c38dee0b67ec@mail.gmail.com> (raw)
In-Reply-To: <639c60080903100948y1bab13a1x8909348fcdcbc186@mail.gmail.com>

On Tue, Mar 10, 2009 at 17:48, Nilshar <nilshar@gmail.com> wrote:
> My problem is on a debian 5.0 (Lenny) with udev version 0.125-7.
> on previous versions of debian, I often deleted the file
> /etc/udev/rules.d/z25-persistent-net.rules, and this file was
> recreated after a reboot.
> I tried to do same thing with Lenny.
> First, I saw that name of this file changed to
> /etc/udev/rules.d/70-persistent-net.rules, si I deleted that file, but
> after a reboot, it was not created.
> After several hours searching the internet, I found nothing solving
> this problem.
> And after more tries, I noticed this only appear on a vmware system.
> Recreating the file /etc/udev/rules.d/70-persistent-net.rules on a
> "normal" Dell server is working just fine.

It might be, that the vmware interface does not trigger the creation
of a persistent rule. Network interfaces need to be created by a
"driver", be backed by a "bus".

Look a the devpath of the device and it will tell you the parent devices:
  /sys/class/net/eth0 -> ../../devices/pci0000:00/[...]/net/eth0
which means, that it's backed by a PCI device, and therefore a rule
will be created. Maybe the vmware interface is a virtual one.

Kay

  parent reply	other threads:[~2009-03-10 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 16:48 Problem recreating 70-persistent-net.rules with udev 0.125-7 on Nilshar
2009-03-10 17:33 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 Marco d'Itri
2009-03-10 17:34 ` Kay Sievers [this message]
2009-03-10 17:48 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 on Nilshar
2009-03-10 17:55 ` Nilshar
2009-03-10 17:59 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 Marco d'Itri
2009-03-10 18:05 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 on Nilshar
2009-03-10 18:06 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 Marco d'Itri
2009-03-11 10:21 ` Scott James Remnant
2009-03-12 10:35 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 on Nilshar
2009-03-12 12:31 ` Sujit Karataparambil
2009-03-17 10:13 ` Nilshar

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=ac3eb2510903101034l54d1abecm5ac9c38dee0b67ec@mail.gmail.com \
    --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.