From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug docs?
Date: Thu, 22 Apr 2004 23:09:04 +0000 [thread overview]
Message-ID: <20040422230904.GA3649@kroah.com> (raw)
In-Reply-To: <40882306.40704@bulldog.unca.edu>
On Thu, Apr 22, 2004 at 03:54:46PM -0400, Erik Harrison wrote:
> I'm sure I'm just missing something, but I've perused the hotplug
> webpage, and googled till my eyes were sore, but I couldn't find it.
>
> Is there a comprehensive list of the hotplug events generated by the
> kernel?
Not really :(
> Specifically by 2.6?
Everything that contains a kobject in sysfs will generate a hotplug
event in the 2.6 kernel. That's a lot of different things these days.
> A quick comparison of the .agent files on my machine tells me that the
> list on the sourceforge page is probably not comprehensive. Any
> pointers?
If you do want to retify this lack of documentation, I would be glad to
add it to the hotplug web site or whereever.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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:[~2004-04-22 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 19:54 Hotplug docs? Erik Harrison
2004-04-22 23:09 ` Greg KH [this message]
2004-04-23 2:40 ` Erik Harrison
2004-05-06 19:00 ` Erik Harrison
2004-05-07 21:57 ` Greg KH
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=20040422230904.GA3649@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 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.