From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 13 Apr 2006 10:29:05 +0000 Subject: Re: net interface renaming issue (+fix?) Message-Id: <20060413102905.GA25983@vrfy.org> List-Id: References: <20060409192140.73644723@eusebe> In-Reply-To: <20060409192140.73644723@eusebe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Apr 13, 2006 at 10:39:53AM +0200, Marco d'Itri wrote: > On Apr 09, Andrey Borzenkov 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? Sure, it will not go away soon, and for temporary fixes, if that helps working around something that is on the way to be fixed, it's fine. But right, the longer term goal is that the notion of "physical devices" and "virtual devices" should not be exported that way by the kernel and therefore the use of these values, or the "device" link, or the symlinks, or a hardcoded sequence of sysfs parent devices must be avoided for other things than temporary workarounds. Thanks, Kay ------------------------------------------------------- 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&kid0944&bid$1720&dat1642 _______________________________________________ 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