From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 070 not create dvb device
Date: Wed, 26 Oct 2005 15:52:48 +0000 [thread overview]
Message-ID: <20051026155247.GA3088@kroah.com> (raw)
In-Reply-To: <20051015141800.26330.qmail@web34812.mail.mud.yahoo.com>
On Wed, Oct 26, 2005 at 01:46:40PM +0600, Alexander E. Patrakov wrote:
> 5) (BUG) make sure that /dev/hda1 is created before a bootscript attempts to
> check the filesystem. There is some file in sysfs (forgot its name and this
> mail writing from 2.4 so can't check) that holds the sequence number of the
> last hotplug event. Maybe this file should be polled and the boot process
> should continue only if there were no changes in 5 seconds.
Heh, that will not work. What about the drivers that wait 5 seconds in
their probe functions before doing device discovery? Seriously, we have
them...
Only thing waiting 5 seconds would tell you is that nothing has changed
in 5 seconds, not that you are finished doing anything.
Why not just do what every other distro does and do the udevstart-like
stuff before checking any filesystems...
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-10-26 15:52 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 [this message]
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
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=20051026155247.GA3088@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).