linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: general hotplug/udev questions
Date: Fri, 19 Aug 2005 16:23:51 +0000	[thread overview]
Message-ID: <20050819162351.GA17462@kroah.com> (raw)
In-Reply-To: <1124394814.4483.46.camel@rich>

On Fri, Aug 19, 2005 at 03:09:59PM +0600, Alexander E. Patrakov wrote:
> Kay Sievers wrote:
> 
> >SUSE's current "event replay from initramfs" works nice so far and is
> >a generic way to solve the boot sequencing problems. One other option
> >may be to crawl /sys and submit the events to udevd instead of getting
> >it from initramfs. That would also work with every kernel, not only
> >with a special prepared initramfs. We will need to test if this
> >option works "good enough" - for now it only sounds like a nice
> >alternative.
> > 
> >
> Do I understand correctly that the "crawl through sysfs" approach means 
> bus-specific conversion between sysfs contents (e.g the fact that 
> /sys/bus/usb/devices/1-1/idProduct contains "4002" here) and environment 
> variables (in this case, PRODUCT=...)?

Yes, but it's a world easier now that we have added the 'modalias' sysfs
files so we don't have to reconstruct anything.  All we care about at
coldplug time is loading the modules and creating existing device nodes.

The hotplug events can usually be safely ignored.

Although some people don't feel the same way, so they "plug" the hotplug
events and then replay them, which is probably the more correct thing to
do.

> I.e., is it just a reimplementation of old /etc/hotplug/*.rc scripts
> in C?

no.

thanks,

greg k-h


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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-08-19 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 19:53 general hotplug/udev questions rich turner
2005-08-18 20:14 ` Greg KH
2005-08-18 20:49 ` Kay Sievers
2005-08-19  9:09 ` Alexander E. Patrakov
2005-08-19 11:10 ` Marco d'Itri
2005-08-19 16:23 ` Greg KH [this message]
2005-08-19 16:33 ` Alexander E. Patrakov
2005-08-19 16:35 ` Kay Sievers
2005-08-19 16:38 ` Marco d'Itri
2005-08-19 16:47 ` Greg KH
2005-08-19 16:56 ` Kay Sievers
2005-08-19 17:11 ` Greg KH
2005-08-19 17:18 ` Kay Sievers
2005-08-21  7:16 ` Alexander E. Patrakov
2005-08-24 19: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=20050819162351.GA17462@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).