All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: $local and user change
Date: Wed, 03 Mar 2004 20:14:03 +0000	[thread overview]
Message-ID: <20040303201401.GA28511@kroah.com> (raw)
In-Reply-To: <200403031337.04427.dev@gioelebarabucci.com>

On Wed, Mar 03, 2004 at 09:08:46PM +0100, Gioele Barabucci wrote:
> On Wednesday 03 March 2004 19:37, Greg KH wrote:
> > > [usbkey]
> > > How should one solve this problem?
> >
> > Not use the $local rule for such a device?  :)
> >
> > Seriously, it sounds like you should just give the device write access
> > to a specific group of users, which is much easier to do.
> The same problem remains even with groups (if I want the usbkey only by the 
> owner).
> I don't see how chgrp'ing the device can be useful...

You are saying that you want a range of users to be able to use the
device, right?  Either put them all in the same group, or run some
script at login/logout time, or have them unplug and replug the device.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-03-03 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 12:37 $local and user change Gioele Barabucci
2004-03-03 18:37 ` Greg KH
2004-03-03 20:08 ` Gioele Barabucci
2004-03-03 20:14 ` Greg KH [this message]
2004-03-04  5:28 ` Robert Love

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=20040303201401.GA28511@kroah.com \
    --to=greg@kroah.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.