Re: udev 070 not create dvb device

[Kay Sievers <kay.sievers@vrfy.org>]

On Thu, Oct 27, 2005 at 10:28:54AM +0600, Alexander E. Patrakov wrote:
> Kay Sievers wrote:
> 
> >You may try something stupid like this:
> >
> > while [ $(cat /proc/*/status 2> /dev/null | grep -c -E '^Name:.udevd?$') 
> > -gt 1 ]; do
> >     sleep 0.1
> > done
> > 
> >
> 1) This can be simplified to:
> 
> while pidof udevd | grep -q " " ; do
>      sleep 0.1
> done

No, that will not catch the "udev" processes. We need to catch both,
cause only the "rules-in-daemon" patch forks "udevd" processes.

> 2) Greg KH said to stick with (synchronous) udevstart for now, and I 
> agree with him here. But there's your comment at 
> http://bugs.debian.org/329226
> 
> >That's one of the problems with a synchronous udevstart. It should go
> >away for a lot of other reasons too and I refused all the "coldplug"
> >patches for udevstart for that reason.
> > 
> >
> That seems to be in disagreement with Greg's words. Is that viewpoint 
> obsolete?

No, thats fine. It depends on how you set-up your booting and it's a safe way
to do it for now.

> Or are there still plans to drop synchronous udevstart

Sure, I'm currently working on a sysfs triggered, kernel based hotplug:
  http://www.kernel.org/git/?p=linux/kernel/git/gregkh/patches.git;a=blob;hb=HEAD;f=driver/coldplug-emit-hotplug-events-from-sysfs.patch

> and make this "pidof" hack (or something equivalent) the official 
> recommended solution?

We'll see ...

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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