linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Burgess <matthew@linuxfromscratch.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 070 not create dvb device
Date: Wed, 26 Oct 2005 06:45:59 +0000	[thread overview]
Message-ID: <435F2627.8000602@linuxfromscratch.org> (raw)
In-Reply-To: <20051015141800.26330.qmail@web34812.mail.mud.yahoo.com>

Alexander E. Patrakov wrote:

> LFS udev/hotplug setup is horribly broken wrt running handlers for 
> firmware/module loading for at least three weeks since my report:
> 
> http://www.mail-archive.com/lfs-dev@linuxfromscratch.org/msg03236.html
> 
> I seriously recommend forgetting the distro that doesn't fix its current 
> known bugs with known fix but instead plans (without much understanding 
> of the underlying mechanisms) to remove the hotplug package.

Alexander, I'd prefer you refrain from berating the LFS project on a 
non-LFS list (obviously I'd rather you don't berate the project at all, 
but at least if you're going to do it, do it where the LFS community can 
be reasonably expected to see and comment on it).

Secondly, as with any open source project, it's a *voluntary* effort. 
I've already made some efforts to outline the general direction I want 
to see LFS head with regards to device and module handling.  The fact 
that I don't understand all (perhaps any?) of how this stuff works is 
completely excusable - the current documentation for hotplugless setup 
is non-existent as far as I can tell.  It relies on searching mailing 
list archives and such like, and doing so is fraught with the 
difficulties of stumbling across out of date or otherwise inaccurate 
information.

However, as you obviously have all the requisite knowledge about this, 
how about *you* document it, submit that as a patch to the udev project, 
then LFS (and other distros too) can act based on the information it 
provides?  If the documentation could provide examples of both an initrd 
and initrd-less configuration (if that is in fact possible, bugs 
notwithstanding), that'd be great.

Regards,

Matt.


-------------------------------------------------------
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-26  6:45 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 [this message]
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
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=435F2627.8000602@linuxfromscratch.org \
    --to=matthew@linuxfromscratch.org \
    --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).