All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yan Seiner <yan@seiner.com>
To: linux-hotplug@vger.kernel.org
Subject: multi-user, udev, consolkit, oh my
Date: Sun, 16 Nov 2008 15:31:54 +0000	[thread overview]
Message-ID: <49203CEA.2030201@seiner.com> (raw)

I'm working on multi-user setups.

I'd like to be assign some resources - like a USB hub - to a seat and 
have hotplug for that hub work only for that seat.

Currently, what happens is that a user plugs in a camera, and hal 
reports the event.  All of the concurrent gnome-volume-manager instances 
then try to grab that resource, and what results is a mess.

consolekit has been suggested as a way to resolve this, but I can't 
figure out how to use it.

googling around, I've found suggestions for using udev to limit access 
to usb devices by creating a group that only has access to the usb 
subsystem.

If I want to group some resources and only have those resources on 
behalf of a specific user, and not any other, is there a way to do 
that?  Can I set up groups for hotplugging usb devices and set it up so 
that the event is only reported to specific group members?

Thanks.,

--Yan

             reply	other threads:[~2008-11-16 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 15:31 Yan Seiner [this message]
2008-11-16 16:32 ` multi-user, udev, consolkit, oh my Kay Sievers
2008-11-16 16:47 ` Yan Seiner

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=49203CEA.2030201@seiner.com \
    --to=yan@seiner.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.