On Sat, Jul 30, 2005 at 08:27:51PM -0400, Jon Smirl wrote:
> On 7/30/05, Kay Sievers <[EMAIL PROTECTED]> wrote:
> > On Sat, Jul 30, 2005 at 07:58:09PM -0400, Jon Smirl wrote:
> > > On 7/30/05, Kay Sievers <[EMAIL PROTECTED]> wrote:
> > > > On Wed, Jul 27, 2005 at 02:49:30PM -0700, Greg KH wrote:
> > > > > On Wed, Jul 27, 2005 at 09:36:13PM +0200, Kay Sievers wrote:
> > > > > > This patch introduces a /sys/class/usb_device/ class
> > > > > > where every connected usb-device will show up:
> > > > > >
> > > > > >   tree /sys/class/usb_device/
> > > > > >   /sys/class/usb_device/
> > > > > >   |-- usb1.1
> > > > > >   |   |-- dev
> > > > > >   |   `-- device -> ../../../devices/pci0000:00/0000:00:1d.0/usb1
> > > > > >   |-- usb2.1
> > > > > >   |   |-- dev
> > > > > >   |   `-- device -> ../../../devices/pci0000:00/0000:00:1d.1/usb2
> > > > > >   ...
> > >
> > > Can I use this patch to generate stable USB mouse/keyboard names based
> > > on port numbers? Like always map 2-2.3:1.0 to mouse0, 4-1:1.0 to
> > > mouse1, etc..
> > 
> > Yes, sure you can do that. If we go this way, you can use the whole
> > udev hell to match against anything the kernel or the device itself provides
> > to create stable names, you can even use a script/program in udev to make
> > a subdirectory in /dev for every "console-group" and put all the nodes for
> > this group in. :)
> > 
> > A lot of USB device have serial numbers, that may be the easiest match
> > you can do.
> 
> I can't find any serial numbers in any of the mice/keyboards that I own.

Yes, unfortunately most mice don't have it.

> Are you going to fully implement console groups? It is something we
> need for multiuser Xserver and console.

I just heard about this idea from your mail yesterday. It sounds
like a reasonable requirement.

> Where will the description of the group contents be stored? The
> contents of the group need to be assigned to the user at login.

We need to figure that out, nothing is decided by now.

I just started with the usbfs replacement, cause udev will play a central
role in a possible pam_console/resmgr replacement. I will start working
on it as soon as we get the usb device access solved, cause we will need
ACL and symlink support.

> We would also like to be able to assign USB hubs to the group. The
> ownership of the hub would transfer at login. From then on anything
> plugged into the hub would belong to the user that owns the hub. I
> guess these added devices should go into limbo when the user logs out
> too.

Sounds like sane policy.

Btw:
I ask your question back: Any idea where to move this discussion to?
usb-devel is obviously not the right place. :)

Kay


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to