All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 070 not create dvb device
Date: Thu, 27 Oct 2005 15:51:45 +0000	[thread overview]
Message-ID: <4360F791.9090605@ums.usu.ru> (raw)
In-Reply-To: <20051015141800.26330.qmail@web34812.mail.mud.yahoo.com>

Marco d'Itri wrote:

>On Oct 27, "Alexander E. Patrakov" <patrakov@ums.usu.ru> wrote:
>  
>
>>Anyway, I think that the following will work safely enough if one 
>>ignores the input subsystem:
>>    
>>
>For a fully working recipe, look at the debian package.
>  
>
Done, thanks.

>It currently uses a patched udevsynthesize, but it will be trivial to
>switch later to the kernel-based coldplugging method.
>  
>
I see that you essentially use the same shell script that Kay pasted: 
the script waits for the time when there remains only one instance of 
udevd and no "udev". Note taken, it only remains to compare that with 
Greg's words.

Is there any rationale for choosing a 8-seconds value for the default 
timeout?

As for input, I see that you just unconditionally modprobe the most 
frequently used "undetectable" modules (evdev and mousedev).

>>Benefit for BLFS: those RUN rules will be applied with /usr certainly 
>>mounted, thus there's no longer any need to wait for /usr in the alsa 
>>RUN helper.
>>    
>>
>Not worth the trouble IMO, it's easier to wait for /usr.
>  
>
Here one of the editors specifically requested that comments about what 
is going on are added to the loop (because the whole concept of waiting 
for /usr is new and non-obvious), you can see them at 
http://www.linuxfromscratch.org/blfs/view/svn/multimedia/alsa-utils.html

And as you see, that page is still incorrect now (i.e. waiting for /usr 
is hard to get right). Of course when the "sleep at the top" and 
"/usr/bin/expr" bugs are fixed, this will be a good template for other 
BLFS packages, should they need a RUN+=... rule.

So I think I should let people decide (maybe vote) in (B)LFS for themselves.

-- 
Alexander E. Patrakov


-------------------------------------------------------
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

  parent reply	other threads:[~2005-10-27 15:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 14:18 udev 070 not create dvb device lukkinosat
2005-10-18  5:45 ` Greg KH
2005-10-19 11:19 ` lukkinosat
2005-10-19 13:18 ` Alexander E. Patrakov
2005-10-22  6:58 ` lukkinosat
2005-10-22 13:28 ` Alexander E. Patrakov
2005-10-23  7:01 ` lukkinosat
2005-10-23 20:34 ` Kay Sievers
2005-10-24  6:31 ` lukkinosat
2005-10-24 17:51 ` Kay Sievers
2005-10-26  2:44 ` Alexander E. Patrakov
2005-10-26  6:45 ` Matthew Burgess
2005-10-26  7:46 ` Alexander E. Patrakov
2005-10-26 11:35 ` lukkinosat
2005-10-26 12:32 ` Alexander E. Patrakov
2005-10-26 15:07 ` Greg KH
2005-10-26 15:52 ` Greg KH
2005-10-26 18:25 ` Kay Sievers
2005-10-27  2:53 ` Olivier Blin
2005-10-27  4:28 ` Alexander E. Patrakov
2005-10-27 13:48 ` Kay Sievers
2005-10-27 14:48 ` Alexander E. Patrakov
2005-10-27 15:21 ` Marco d'Itri
2005-10-27 15:50 ` Alexander E. Patrakov
2005-10-27 15:51 ` Alexander E. Patrakov [this message]
2005-10-27 16:24 ` Marco d'Itri
2005-10-28  1:43 ` 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=4360F791.9090605@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --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.