From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: net interface renaming issue (+fix?)
Date: Thu, 13 Apr 2006 08:39:53 +0000 [thread overview]
Message-ID: <20060413083953.GD4046@wonderland.linux.it> (raw)
In-Reply-To: <20060409192140.73644723@eusebe>
On Apr 09, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> > So i wonder, maybe such a rule should be added to the standard early
> > ones? It should maybe use more checks though, to be sure there is
> > actually a driver to wait. Something like ENV{PHYSDEVPATH}="?*"
> > and/or ENV{PHYSDEVDRIVER}="?*".
> >
>
> You probably get reply that they are obsolete and should not be used in new
> rules :)
So, is this an acceptable workaround until the kernel is fixed or not?
I implemented interfaces persistence for the Debian package, but users
will get mad if the rules are randomly ignored (which apparently is
already happening).
Also, is there a kernel patch yet?
--
ciao,
Marco
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-04-13 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 17:21 net interface renaming issue (+fix?) Thomas de Grenier de Latour
2006-04-09 17:56 ` Sergey Vlasov
2006-04-09 17:56 ` Sergey Vlasov
2006-04-09 18:00 ` Andrey Borzenkov
2006-04-09 19:28 ` Thomas de Grenier de Latour
2006-04-13 8:39 ` Marco d'Itri [this message]
2006-04-13 9:06 ` Thomas de Grenier de Latour
2006-04-13 10:29 ` Kay Sievers
2006-04-13 10:36 ` Marco d'Itri
2006-04-13 11:10 ` Kay Sievers
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=20060413083953.GD4046@wonderland.linux.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.