From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem recreating 70-persistent-net.rules with udev 0.125-7
Date: Wed, 11 Mar 2009 10:21:09 +0000 [thread overview]
Message-ID: <1236766869.6339.102.camel@quest> (raw)
In-Reply-To: <639c60080903100948y1bab13a1x8909348fcdcbc186@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On Tue, 2009-03-10 at 18:33 +0100, Marco d'Itri wrote:
> On Mar 10, Nilshar <nilshar@gmail.com> wrote:
>
> > And after more tries, I noticed this only appear on a vmware system.
> Indeed, these rules are not automatically created on vmware systems
> since this is generally undesirable.
> If you need rules to rename network interfaces, write your owns.
>
Do you have a patch for that? :)
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-11 10:21 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 ` 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 [this message]
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=1236766869.6339.102.camel@quest \
--to=scott@canonical.com \
--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).