On Fri, Oct 11, 2002, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Am Freitag, 11. Oktober 2002 22:56 schrieb Johannes Erdfelt:
> > On Fri, Oct 11, 2002, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> > > > However, the kernel only enforces the privileges. It doesn't set them.
> > >
> > > That is not true. Hotplugging changes it. By assigning new devices
> > > to existing device nodes, the kernel _does_ hand out permissions.
> >
> > It assigns the permissions that were configured by the user, either
> > implicitly the default, of explictly via devmode=.
> 
> For usbfs nodes. It doesn't work for /dev/usb/scannerX

I think the point is that we don't need /dev/usb/scannerX stuff anymore
if it's done completely via usbfs :)

> > Wait, let me go back to this. This cannot happen. A completely new
> > device node is created with the defaults assigned previously. This isn't
> > a traditional static /dev.
> 
> Entirely correct. You see, hotplug cannot do the job. It needs
> further support. For everything that doesn't use usbfs
> and reuses device nodes (everything but storage) we're in trouble.

Gotcha, I agree in that case. But that's another reason that static /dev
is broken by design.

> > Any other suggestions? devmode= is of limited usefulness.
> 
> No other. Sorry.

Of course we do. Kill the scanner kernel module.

JE



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to