All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and sysfs permissions
Date: Fri, 20 May 2005 21:53:33 +0000	[thread overview]
Message-ID: <9e47339105052014531d19ffe3@mail.gmail.com> (raw)
In-Reply-To: <9e47339105051915025188e535@mail.gmail.com>

On 5/20/05, Greg KH <greg@kroah.com> wrote:
> On Fri, May 20, 2005 at 05:40:05PM -0400, Jon Smirl wrote:
> > On 5/20/05, Greg KH <greg@kroah.com> wrote:
> > > > That would make things simpler for driver writers if more devices are
> > > > going to follow this model.
> > >
> > > I think you are going to be pretty unique here, as no one else has come
> > > up with a situation yet that requires this.
> >
> > If the mantra about sysfs attributes being superior to IOCTLs is true,
> > then anyone who converts to sysfs attributes is going to run into this
> > problem.  In the IOCTL model permission obviously follows the owner of
> > the /dev device. There is no parallel for this in the sysfs model.
> 
> True.  Hm, let me look into the sysfs code to see if we can just save
> the changed attributes, so that they do not get lost.  That would be the
> simplest solution, right?

That will work. Right now it is random for me from half an hour to
four hours before they get lost.

> 
> thanks,
> 
> greg k-h
> 


-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id\x16344&opÌk
_______________________________________________
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

  parent reply	other threads:[~2005-05-20 21:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 22:02 udev and sysfs permissions Jon Smirl
2005-05-19 22:10 ` Kay Sievers
2005-05-20  4:33 ` Greg KH
2005-05-20 14:06 ` Jon Smirl
2005-05-20 18:33 ` Greg KH
2005-05-20 21:11 ` Jon Smirl
2005-05-20 21:26 ` Jon Smirl
2005-05-20 21:27 ` Greg KH
2005-05-20 21:40 ` Jon Smirl
2005-05-20 21:40 ` Greg KH
2005-05-20 21:41 ` Jon Smirl
2005-05-20 21:53 ` Jon Smirl [this message]
2005-05-20 21:54 ` Greg KH
2005-05-20 21:56 ` Greg KH
2005-05-20 22:07 ` Kay Sievers
2005-05-20 22:09 ` Greg KH
2005-05-26 23:09 ` Greg KH
2005-05-27 12:44 ` Maneesh Soni
2005-05-27 16:39 ` Jon Smirl
2005-05-27 21:51 ` Greg KH
2005-05-28  5:06 ` maneesh
2005-05-28  5:08 ` maneesh

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=9e47339105052014531d19ffe3@mail.gmail.com \
    --to=jonsmirl@gmail.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.