[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New Package: Lejos NXJ



On Wed, 2010-07-21 at 09:38 +0800, Paul Wise wrote:
> On Wed, Jul 21, 2010 at 2:14 AM, Chris Baines <cbaines8@gmail.com> wrote:
> 
> > Secondly, I have little understanding of the usb permissions on Debian.
> > I have done some basic tests and the device can't be accessed without
> > root permissions on a standard installation of Debian. The project
> > readme says:
> >        To use udev rules, set up a file such
> >        as /etc/udev/rules.d/70-lego.rules and populate it with the
> >        following lines:
> >        # Lego NXT
> >        BUS=="usb", SYSFS{idVendor}=="03eb", GROUP="lego", MODE="0660"
> >        BUS=="usb", SYSFS{idVendor}=="0694", GROUP="lego", MODE="0660"
> >
> >        This relies on the username you are using being in the lego
> >        group. You can modify the file to your requirements. The two
> >        vendors are LEGO and Atmel (for the samba driver used in
> >        firmware update mode). You may need to reload the rules or
> >        restart udev. On some Linux systems, the command to reload the
> >        rules is udevadm control --reload-rules.
> >
> > However I don't believe this is the best solution, the device just needs
> > to be accessible by the normal user, does a specific group need to be
> > added just for this purpose?
> 
> Probably you or upstream need to look at PolicyKit (and possibly
> ConsoleKit). It was created in an effort to get rid of the need for
> all these groups.
> 
> -- 
> bye,
> pabs
> 
> http://wiki.debian.org/PaulWise
>

Thanks for the info, I was thinking some more about this, could I just
add a udev rule to make it work just like say a usb mouse, you plug it
in and it works. The action of installing the package would be the bit
requiring root permissions. However once this is done the device should
if possible work for all normal users. i don't think policy kit is quite
the right method (but I am not upstream, this is just my intuition).

Thanks,

Chris





Reply to: