From: Fabian Steiner <fabian.steiner@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Permissions of usb hub and its children
Date: Wed, 06 Sep 2006 07:15:17 +0000 [thread overview]
Message-ID: <44FE7585.3060708@gmail.com> (raw)
In-Reply-To: <44FD48F6.6020900@gmail.com>
Greg KH wrote:
> On Tue, Sep 05, 2006 at 11:50:03PM +0200, Fabian Steiner wrote:
>> Greg KH wrote:
>>> On Tue, Sep 05, 2006 at 11:52:54AM +0200, Fabian Steiner wrote:
>>>> Hello!
>>>>
>>>> I am trying to change the permissions of my usb hub with the follwing
>>>> udev rule:
>>>>
>>>> SUBSYSTEM="usb", DEVPATH="/devices/pci0000:00/0000:00:02.1/usb1/1-3",
>>>> OWNER="fabi", MODE="600
>>> What are you trying to change here? The permissions of the usb hub in
>>> usbfs?
>> Yes, my intension was to assign proper permissions to the usb hub so
>> that all devices that are connected to that hub get the same permissions.
>
> Ah, multi-user type setup?
Exactly :-) As there is no solution for this so far, we tried to do it
on our own, but as you can see we are not that successful since there
are quite a lot of different aspects to think of.
Our current solution is based on a simple python script which is
executed whenever a user logins (by using the PostLogin mechanism of
GDM). It then reads the environment variables $DISPLAY and $USER which
are set by GDM properly and tries to find out whether a usb hub was
assigned to that particular display. This is done manually by using a
config file.
If someone is interested, I will publish the script.
>> I am not quite sure whether this rule will fulfill all of my
>> requirements but so far it looks good. I.e. I don't know for sure
>> whether ENV{PHYSDEVPATH} is set for all devices and whether it contains
>> a sysfs address. Perhaps you could give me a hint :-)
>
> Yes, that should work. But remember, "usb1" the next time you boot
> might not be the same root hub you thought it was last time. That all
> depends on PCI bus numbering (which can change, but rarely), and USB
> host controller driver loading order (which changes often due to the
> phase of the moon and such.)
>
> So be careful about that.
Oh, I wasn't aware of that so far. I will probably have to rethink the
whole thing, I suppose ... Of course, the system should work under all
circumstances and not when the moon wants it to ;-)
> good luck,
>
> greg k-h
>
Thank you,
Fabian STeiner
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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
prev parent reply other threads:[~2006-09-06 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 9:52 Permissions of usb hub and its children Fabian Steiner
2006-09-05 17:54 ` Greg KH
2006-09-05 21:50 ` Fabian Steiner
2006-09-06 0:35 ` Greg KH
2006-09-06 0:50 ` Kay Sievers
2006-09-06 7:15 ` Fabian Steiner [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=44FE7585.3060708@gmail.com \
--to=fabian.steiner@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.