From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem recreating 70-persistent-net.rules with udev 0.125-7
Date: Tue, 10 Mar 2009 17:59:32 +0000 [thread overview]
Message-ID: <20090310175932.GA27693@bongo.bofh.it> (raw)
In-Reply-To: <639c60080903100948y1bab13a1x8909348fcdcbc186@mail.gmail.com>
On Mar 10, Nilshar <nilshar@gmail.com> wrote:
> For example, if I need to restore a sytem into a vmware, this file
> needs to be changed. on a normal box, udev will add the new interfaces
Every time you change the hardware for a system, even if it is virtual
hardware, you need to delete the file.
> as eth2 etc.. so I'll have to delete the file so it will be recreated
> with eth0. How can I do that on a vmware ?
udev will do it if needed, but it's not mandatory to have one (e.g. if
all or your interfaces are handled by the same driver then their names
will usually never change).
BTW, we are talking about paravirtualized network interfaces. If vmware
is emulating a real interface then there is some other issues.
--
ciao,
Marco
next prev parent reply other threads:[~2009-03-10 17:59 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 ` Problem recreating 70-persistent-net.rules with udev 0.125-7 on Kay Sievers
2009-03-10 17:48 ` Nilshar
2009-03-10 17:55 ` Nilshar
2009-03-10 17:59 ` Marco d'Itri [this message]
2009-03-10 18:05 ` 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=20090310175932.GA27693@bongo.bofh.it \
--to=md@linux.it \
--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.