my .1 cents on you questions On Fri, 27 Jan 2012, Nicolas Bourdaud wrote: > The udev rules were broken, so I needed to update them, especially, the > permission of "all" is updated by another udev rule that I have not yet > identified but anyways, I am not sure it was a good practice to grant > access to any user.
yeap -- doesn't sound ideal ;-) > Instead I set the group to plugdev, so that any user > of plugdev (normal desktop user are usually) can access and this is not > altered by any other rule. My question is now: do you think it make > sense? If so does the plugdev group make sense as well? If you don't > know, I can ask on mentor mailing list to have the opinion of the community. 'plugdev' group makes total sense to me -- even more than allocating a new group solely for kinect -- but sure thing do not hesitate to seek further advice on -mentors or even -dev mailing list. > ... > (the one that entered in testing today). Now I have 3 solutions but none > are good: > - solution 1: installing libfreenect0.1 package installs a modprobe rule > >...< > - solution 2: write a patch to libfreenect which detaches the kernel > >...< > - solution 3: Status quo. We don't do anything, just inform users in the > >...< Arne's suggestion is right to the point imho. Lazy guy like me would have just reverted to 3. in one form or another ;-) suggesting admin to decide via debconf (with 'high' priority for the question) sounds the best but would require a bit more work, especially since i18n will be on your back quite soon -- get ready to incorporate their patches ;-) Cheers, -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
