From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and Mylex Dac960
Date: Fri, 13 Feb 2004 21:05:07 +0000 [thread overview]
Message-ID: <20040213210507.GF14048@kroah.com> (raw)
In-Reply-To: <4022CB7D.4010505@snscrew.net>
On Thu, Feb 12, 2004 at 03:02:56AM +0100, claude wrote:
> Yes i will do, but is there any docs about sysfs and how it works ? I've
> only found sysfs.txt in linux-2.6.2/Documentation, and it was too light
> explanation for my poor knowledge. Any pointer ?
What do you want to know about sysfs?
How to write code to use it? If so, lwn.net has has a few good articles
about it, and there is a OLS and linux.conf.au paper about it.
If you just want to know what in the world these different directories
are, and how they relate to each other, from a user point of view,
that's not so well documentated, yet :(
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
next prev parent reply other threads:[~2004-02-13 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 23:02 Udev and Mylex Dac960 claude
2004-02-06 0:07 ` Greg KH
2004-02-06 14:40 ` claude
2004-02-07 19:04 ` claude
2004-02-11 23:49 ` Greg KH
2004-02-12 1:41 ` Greg KH
2004-02-12 2:02 ` claude
2004-02-13 21:05 ` Greg KH [this message]
2004-02-16 5:46 ` claude
2004-02-16 5:52 ` Greg KH
2004-02-16 7:35 ` claude
2004-02-16 18:22 ` Greg KH
2004-02-16 20:10 ` claude
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=20040213210507.GF14048@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.