public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Doug Thompson <norsk5@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Thu, 17 Nov 2005 19:32:36 +0100	[thread overview]
Message-ID: <20051117183236.GA24650@vrfy.org> (raw)
In-Reply-To: <20051117171856.GB27534@kroah.com>

On Thu, Nov 17, 2005 at 09:18:56AM -0800, Greg KH wrote:
> On Thu, Nov 17, 2005 at 09:20:53AM -0800, Doug Thompson wrote:
> > > But you can just probably use a udev rule to
> > > initialize your things
> > > properly, that's what all of the distros are now
> > > using.
> > 
> > Ok. That's another area for me to research. edac does
> > not have any /dev/ entries, just the files and
> > controls previous mentioned. 
> > 
> > So, from your comment then, udev has some mechanism to
> > set controls in sysfs?
> 
> udev gets called whenever you add a kobject to the system.  You can then
> do whatever you want in udev when this happens.  As an example, on one
> distro, when a bluetooth device is created by the kernel, a bluetooth
> startup script is run by udev.

We do things like this:
  ACTION=="add", SUBSYSTEM="scsi", SYSFS{type}=="1", RUN+="/bin/sh -c 'echo 900 > /sys/$DEVPATH/timeout'"

There are only very few users now, that set values in sysfs. If that is
a common need to change values with udev rules we may integrate that into
udev itself, instead of calling a shell, but that works fine so far.

Kay

      reply	other threads:[~2005-11-17 18:32 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
2005-11-17 17:20           ` Doug Thompson
2005-11-17 17:18             ` Greg KH
2005-11-17 18:32               ` 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=20051117183236.GA24650@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=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