On 02.11.2011 21:41, Volker Kuhlmann wrote:
On Wed 26 Oct 2011 21:34:52 NZDT +1300, Stefan Seyfried wrote:
Example: stuff in the (badly named) CrossToolchain:avr repo: IIRC it installs totally unacceptable (for general use) udev rules that allow all users in the "users" group access to all (usb?) serial ports.
Instead of raving over badly packaged software that enhances the usability of your distribution considerably (and openSUSE is still rather short on a lot of things that matter to professionals in their respective fields) you could provide more information to help remedy the situation.
You are barking up the wrong tree. I am working on the CT:avr stuff. However, it is pretty hard (if not impossible) to package such stuff (which needs e.g. raw serial port access) in a way that's both acceptable for inclusion in openSUSE (=> no raw serial access for users) and actually useful for anyone. So such software has to stay in its special repositories where people can and will find it, but they will also know that it is "special".
In http://en.opensuse.org/openSUSE:Packaging_guidelines e.g. the eclipse plugin heading is empty. Handling of udev rules and cross compilers isn't even mentioned.
I'm not sure if there is a section for "do not allow every user to send expensive SMS via", but I honestly don't think is necessary as it is common sense.
I have been trying to re-compile avr-gcc and it's been a bit of a process. Can you point me to something please that explains what configure options to use so that it goes under /usr instead of /opt without interfering with the system's gcc on openSUSE?
It is perfectly fine in /opt, avr-gcc is not one of the packages which would be unacceptable IMHO. Additionally, everybody installs cross-compilers into /opt/cross, so I happily ignore the FHS in this case. Standards are cool, but you have to know when to ignore them, especially if they are created by some round table and do not reflect reality ;-) It's more the arduino, uisp, avrdude and friends. They need access to serial ports. Period. Often through very generic interfaces (FTDI usb-serial adapters). No way you would want to grant this to every user on a system.
=> unacceptable for general usage (think of a worm sending expensive SMS via your mobile phone / 3G card)
The rules I see there identify various USB programmers by their IDs and set them mode 666 (I look forward to your project description of how to send SMS with AVR MCU programmers...). Parallel port anything however seems to be set to 666 too, so not so good.
Basically all usb-serial are set to 0666. Not good.
Can you please point me to openSUSE's guidelines on how to create udev rules in packages for things like MCU programmers?
=> makes the AVR stuff "just work" for developers (which is important to them)
I expect many users of the avr packages are not developers in your sense of the word, but people who need to get their electronics equipment working without spending time on operating systems that is subtracted from time available for their projects. openSUSE could do more to support those users.
They will not run the tools on their dialup server but on a development machine. So they are developers. I cannot see why plain end users might want to reprogram their electronics equipment :) If you want to improve that, work upstream with the tool development projects and implement consolekit or whatever is the tool-of-the-day handling for these devices. I honestly don't have the time to do that. And upstream projects are often not really interested in the additional dependencies and complexity and tell you "just do chmod 666 on the device, here is the udev rule" :-) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org