udev-076 and wait_for_sysfs removal

udev-076 and wait_for_sysfs removal

[Mika Penttilä]

RELEASE-NOTES informs to compensate removal of wait_for_sysfs with :
    ACTION="add", DEVPATH="/devices/*", ENV{PHYSDEVBUS}="?*", 
WAIT_FOR_SYSFS="bus"

Shouldn't class and block devices have this kind of treatment also?

Thanks,
Mika





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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

Re: udev-076 and wait_for_sysfs removal

[Kay Sievers]

On Fri, Nov 25, 2005 at 09:01:26PM +0200, Mika Penttilä wrote:
> RELEASE-NOTES informs to compensate removal of wait_for_sysfs with :
>    ACTION="add", DEVPATH="/devices/*", ENV{PHYSDEVBUS}="?*", 
> WAIT_FOR_SYSFS="bus"
> 
> Shouldn't class and block devices have this kind of treatment also?

If a class/ block device has a "device" link, which means it is backed
by a physical device with a "bus", udevd will delay the execution of the
class/block event until the event for the "device" has finished. So, this
should work just by resolving the dependencies, if there isn't something
going wrong in sysfs.

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
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

Re: udev-076 and wait_for_sysfs removal

[Mika Penttilä]

Kay Sievers wrote:

>On Fri, Nov 25, 2005 at 09:01:26PM +0200, Mika Penttilä wrote:
>  
>
>>RELEASE-NOTES informs to compensate removal of wait_for_sysfs with :
>>   ACTION="add", DEVPATH="/devices/*", ENV{PHYSDEVBUS}="?*", 
>>WAIT_FOR_SYSFS="bus"
>>
>>Shouldn't class and block devices have this kind of treatment also?
>>    
>>
>
>If a class/ block device has a "device" link, which means it is backed
>by a physical device with a "bus", udevd will delay the execution of the
>class/block event until the event for the "device" has finished. So, this
>should work just by resolving the dependencies, if there isn't something
>going wrong in sysfs.
>
>Kay
>
>  
>
Indeed, didn't remeber that we delay the physical device events we 
depend on.

Thanks,
Mika




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
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