public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Doug Thompson <norsk5@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Wed, 16 Nov 2005 23:05:16 -0800	[thread overview]
Message-ID: <20051117070516.GB20760@kroah.com> (raw)
In-Reply-To: <20051116002638.762.qmail@web50106.mail.yahoo.com>

On Tue, Nov 15, 2005 at 04:26:38PM -0800, Doug Thompson wrote:
> Speaking of controls, edac has them  currently in
> /proc/sys/mc. I have proposed to have them in
> /sys/devices/system/edac/mc and friends. 
> 
> My question is:  Should I remove entirely my old
> /proc/sys/mc sysctl tree? Or still maintain the
> aliases there (which seems weird)? 

That would be wierd, just drop the sysctl stuff.

> If I do that, then /etc/sysctl.conf will no longer
> allow for setting things up there.

True.

> Is there going to be a similiar functionality as
> /etc/sysctl.conf for those items we place in sysfs, in
> the future?

If you want to write one, sure :)

But you can just probably use a udev rule to initialize your things
properly, that's what all of the distros are now using.

> PS. These questions on sysfs seem a perfect food
> stream for your 'HOWTO do kernel development'. Trying
> to do new entries in sysfs has been a painstaking
> adventure. After googling the web for info, it
> definitely has been a bit thin on information on sysfs
> at the level I am seeking.

sysfs and the driver model are woefully underdocumented.  Right now, I'd
recommend the Linux Device Drivers, third edition, free online if you
don't want to buy it, for anyone doing any driver core stuff.  It has a
whole chapter that is the most up-to-date and the best description I've
seen so far.

But even then, it is out of date, due to api changes, sorry.

thanks,

greg k-h

  reply	other threads:[~2005-11-17  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:14 [RFC] EDAC and the sysfs Doug Thompson
2005-11-14 22:31 ` Greg KH
2005-11-15  0:30   ` Dave Jones
2005-11-15 17:24     ` Greg KH
2005-11-15  0:47   ` Doug Thompson
2005-11-15  1:12     ` Doug Thompson
2005-11-15 17:25     ` Greg KH
2005-11-16  0:26       ` Doug Thompson
2005-11-17  7:05         ` Greg KH [this message]
2005-11-17 17:20           ` Doug Thompson
2005-11-17 17:18             ` Greg KH
2005-11-17 18:32               ` 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=20051117070516.GB20760@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.com \
    /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