Re: Multiple identical udev rules -- safe?
Am 31.01.2011 22:47, schrieb Martin Langhoff: Consider this file from nxt_python package: cat /etc/udev/rules.d/70-lego.rules BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660 Is it safe sane to include an identical udev rule file in the nbc package with different filename? To state the obvious -- it'd use the same group name and mode. Fallback plan is to prep a package just for this udev rule and depend on it, but it seems unnecesary overhead. m Yes, it would be safe. It's just code duplication. Why does it use group lego? Is there a daemon running? Or should the console user have access to it? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Multiple identical udev rules -- safe?
On Tue, 2011-02-01 at 11:04 +0100, Harald Hoyer wrote: Am 31.01.2011 22:47, schrieb Martin Langhoff: Consider this file from nxt_python package: cat /etc/udev/rules.d/70-lego.rules BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660 Is it safe sane to include an identical udev rule file in the nbc package with different filename? To state the obvious -- it'd use the same group name and mode. Fallback plan is to prep a package just for this udev rule and depend on it, but it seems unnecesary overhead. m Yes, it would be safe. It's just code duplication. Why does it use group lego? Is there a daemon running? Or should the console user have access to it? FWIW, I'd really like to see the console user have access to this by default. Then, uploading a file to the NXT brick would be plug and play. Jonathan signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Multiple identical udev rules -- safe?
On Tue, Feb 1, 2011 at 3:16 AM, Jonathan Dieter jdie...@lesbg.com wrote: FWIW, I'd really like to see the console user have access to this by default. Then, uploading a file to the NXT brick would be plug and play. Yeah. Trouble is - I know nothing about ConsoleKit policy. What's the trick to change this udev rule into something that works with CK? m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Multiple identical udev rules -- safe?
Consider this file from nxt_python package: cat /etc/udev/rules.d/70-lego.rules BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660 Is it safe sane to include an identical udev rule file in the nbc package with different filename? To state the obvious -- it'd use the same group name and mode. Fallback plan is to prep a package just for this udev rule and depend on it, but it seems unnecesary overhead. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel