From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: any whitepaper for the linux hotplug interface progress
Date: Fri, 02 Dec 2005 16:45:09 +0000 [thread overview]
Message-ID: <20051202164509.GA5072@vrfy.org> (raw)
In-Reply-To: <87ab37ab0512012201k39a0c151g7f96fb733fa7004@mail.gmail.com>
On Fri, Dec 02, 2005 at 02:01:04PM +0800, kylin wrote:
> hello everyone:
> it have been some time since my last visit the maillist
> i feel myself out of the date of the linux hotplug usermode and
> communication technology
> ,is there any info about how are the linux hotplug ,including udev going on ?
> waiting for ur kind reply :) thank u
There are just the packages from the distros who are working on it. It's
pretty straighforward what we do now compared to what we did in the
past.
A few things are in the udev README file, but there is no general
documentaion about how "hotplug" works today. I'm expected to write
something for the "SUSE Administration Guide" during the next two weeks,
which will give an overview about it. It will be available on the web,
but I just started writing things down. :)
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-12-02 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 6:01 any whitepaper for the linux hotplug interface progress kylin
2005-12-02 16:45 ` Kay Sievers [this message]
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=20051202164509.GA5072@vrfy.org \
--to=kay.sievers@vrfy.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).