http://bugzilla.suse.com/show_bug.cgi?id=1140623 http://bugzilla.suse.com/show_bug.cgi?id=1140623#c2 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com, | |teuniz@gmail.com Flags| |needinfo?(teuniz@gmail.com) --- Comment #2 from Franck Bui --- Not really, udev doesn't deal with such specific devices. Which package/driver were/are you using to access those devices ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1140623 http://bugzilla.suse.com/show_bug.cgi?id=1140623#c4 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #4 from Franck Bui --- That's not a package. As the specific permissions you're asking for are unlikely set by the driver, you probably installed a package which contained the udev rule file for these devices if the permissions were set as you expected (gid=usbtmc) with Leap 42.2. Anyway if this package doesn't exist (and then I'm wondering how the perms were set with Leap 42.2) feel free to create one that will ship the udev rule file and create "usbtmc" group. Again that's not udev job to deal with such specific devices. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1140623 http://bugzilla.suse.com/show_bug.cgi?id=1140623#c6 --- Comment #6 from Teuniz XXX --- I don't want to create a package in order to resolve the problem. I was under the impression that the groupid of /dev/usbtmc* should be set to "usbtmc" by default without having any package installed. I guess you guys are the experts so if you believe that that shouldn't be the case, then, please close this bug report. I'm just thinking what happens if two different packages assign different groupid's to the same device files... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1140623 http://bugzilla.suse.com/show_bug.cgi?id=1140623#c8 --- Comment #8 from Teuniz XXX --- Could it be an idea to look how it's done with virtual comports? The device files /dev/ttyUSB* are created when you plugin an USB to serial port converter. Uid will be root and guid will be "dialout". Is this because there's a package installed which uses the serial port and has created the udev rule? Or is the guid already set to "dialout" as default by the system? I guess it's the latter. If so, it sounds natural to apply the same to /dev/usbtmc* device files. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1140623 http://bugzilla.suse.com/show_bug.cgi?id=1140623#c10 --- Comment #10 from Teuniz XXX --- The group "usbtmc" was created by me. After performing a fresh install of openSuse, there's no such group. When connecting certain devices e.g. a Rigol DS1000Z series oscilloscope, the system automatically creates the device file /dev/usbtmc0 with both uid and gid set to root. That's it. Now, to make the comparison with tty devices, we all know that serial ports these days are used for a lot more than traditional terminals. There are a gazillion devices out there that uses the serial port to communicate, many times by using their own specific commands. The same is true with USBTMC protocol. It's used by test and measuring equipment and the basic communication protocol (USBTMC) is the same for all them. On top of that, they can have their on own implementation (specific commands, etc.) exactly like the serial port where the low level interface is the same but the protocol on top of that usually is device dependent. It's just a bit inconvenient for T&M equipment users that they need to create manually this udev rule while the T&M equipment that uses the serial port for communication already have this rule. Then again, if you let the package decide which gid to use for the device file, it opens the door for situations where different packages using the same protocol, rename the gid after installing and possibly create problems for the package installed before. Keep in mind that USBTMC is a generic protocol, not related to just one manufacturer. -- You are receiving this mail because: You are on the CC list for the bug.