All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Rynö" <Jouni.Ryno@fmi.fi>
To: linux-hotplug@vger.kernel.org
Subject: udev and sysfs node permissions
Date: Mon, 20 Mar 2006 11:27:47 +0000	[thread overview]
Message-ID: <1142854067.6832.6.camel@adic> (raw)

I'm trying to use the sysfs attributes instead IOCTL, as it's easier to
run shell or tcl scripts than writing C-code ...

Around 2005-05-28 there was discussion about sysfs node permissions to
be changeable, and yes, it can be done now.

But what is the proper way to change them trough udev now. A separate
script to be called upon device node coming up? Any development in the
idea, that sysfs nodes would take the same permissions as the
corresponding device nodes?

regards
	Jouni

-- 

  Jouni Rynö                            mailto://Jouni.Ryno@fmi.fi/
                                        http://www.geo.fmi.fi/~ryno/
  Finnish Meteorological Institute      http://www.fmi.fi/
  Space Research                        http://www.geo.fmi.fi/
  P.O.BOX 503                           Tel      (+358)-9-19294656
  FIN-00101 Helsinki                    FAX      (+358)-9-19294603
  Finland                               priv-GSM (+358)-50-5302903
  
  "It's just zeros and ones, it cannot be hard"




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
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

                 reply	other threads:[~2006-03-20 11:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1142854067.6832.6.camel@adic \
    --to=jouni.ryno@fmi.fi \
    --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.