From: Paul Wagland <paul@kungfoocoder.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux SCSI mailing list <linux-scsi@vger.kernel.org>
Subject: Re: megaraid /proc under kernel 2.6.2
Date: Mon, 16 Feb 2004 09:33:57 +0100 [thread overview]
Message-ID: <1076920436.2022.13.camel@morsel.kungfoocoder.org> (raw)
In-Reply-To: <40302342.10806@pobox.com>
On Mon, 2004-02-16 at 02:56, Jeff Garzik wrote:
> Paul Wagland wrote:
> >
> > However, the /proc/megaraid directory is no longer populated, and I am
> > not quite sure why.
>
>
> Maybe I can address the issue another way :)
>
> We are moving away from procfs... so may I suggest taking this
> opportunity to consider what procfs outputs, and a better way to provide
> that to userspace. Perhaps this information is already duplicated in
> sysfs...
I think you miss the point... I was looking at _decreasing_ the amount
of work I had to do! :-)
Anyway, this sysfs stuff is something for me to look at, but at the
moment there are no attributes being exported via sysfs, I am currently
reading up on the lwn.net articles about it... I will try to submit a
patch to add some of this stuff later this week.
However, for at least edification purposes, I would still like to know
why the proc directory is not working. It appears to me that a static
global variable is not being read somehow?!? I sent a second e-mail
through about that though.
Thanks for the input,
Paul
next prev parent reply other threads:[~2004-02-16 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 22:41 megaraid /proc under kernel 2.6.2 Paul Wagland
2004-02-16 0:18 ` Paul Wagland
2004-02-16 23:04 ` *solved* " Paul Wagland
2004-02-17 16:57 ` Matthew Wilcox
2004-02-17 17:36 ` Paul Wagland
2004-02-16 1:56 ` Jeff Garzik
2004-02-16 8:33 ` Paul Wagland [this message]
2004-02-16 9:59 ` Christoph Hellwig
2004-02-16 21:03 ` Paul Wagland
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=1076920436.2022.13.camel@morsel.kungfoocoder.org \
--to=paul@kungfoocoder.org \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@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