On Mon, Apr 08, 2013 at 02:07:21PM -0400, Scott Talbert wrote: > On Mon, 8 Apr 2013, Phil Dibowitz wrote: > > >>>> Well, it sounds like xdm doesn't have ConsoleKit support, so that is > >>>> probably the problem: > >>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615020 > >>>> > >>>> So, maybe for your case, the recommended approach would be to use the > >>>> "old" udev rules? > >>> > >>> The old one didn't work for me either. This may be a reason for me to > >>> move to > >>> lightdm or something. But we should have SOMETHING that works for this > >>> case. > >>> > >>> I think the reason the old udev rules don't work is because they use SYSFS > >>> instead of ATTR. I'll test that today. That would give use 3 generations > >>> of > >>> udev to support: > >>> > >>> * really old (requires SYSFS) > >>> * old (requires ATTR, but no ConsoleKit) > >>> * new (supports ConsoleKit). > >>> > >>> Which means I would say we'd just drop really old. > >> > >> And just to check, when you tested the "old" rules, you had your user as a > >> member of group 'dialout'? > > > > Yeah, but also: > > > > [phil@rider ~]$ ls -l /dev/bus/usb/001/029 > > crw-rw-r-T 1 root root 189, 28 Apr 8 09:20 /dev/bus/usb/001/029 > > > > And also: > > > > Apr 8 09:19:28 rider udevd[21864]: unknown key 'SYSFS{idVendor}' in > > /lib/udev/rules.d/60-libconcord.rules:38 > > Apr 8 09:19:28 rider udevd[21864]: invalid rule > > '/lib/udev/rules.d/60-libconcord.rules:38' > > > > If I change the udev rules to be ATTR then: > > > > [phil@rider ~]$ ls -l /dev/bus/usb/001/030 > > crw-rw-r-T 1 root dialout 189, 29 Apr 8 09:21 /dev/bus/usb/001/030 > > > > And then it works. > > > > Changing that file to: > > > > SUBSYSTEM=="usb", ATTR{idVendor}=="046d", > > ATTR{idProduct}=="c1[1-4][0-9a-f]", > > MODE="0660", GROUP="dialout" > > > > Also works wonderfully. > > > > So after a night to think this over, I'm actually going to purpose this: > > > > * Change current udev to use the glob syntax instead of the list. > > * Add a new generic-udev rule which uses MODE/GROUP instead of > > REMOTE_CONTROL > > * Leave old-dev as-is > > Makes sense - I think, if I understand correctly. So we'd now have 4 udev > options: > > * Old "policykit" rule with ATTR and SYMLINK (w/ list) > * Old no-policykit rule with SYSFS and GROUP (w/ list) > * New no-policykit rule with ATTR and ID_REMOTE_CONTROL (w/ glob syntax) > * New no-policykit rule with ATTR and GROUP (w/ glob syntax?)
No, just three: * udev: console-kit, ATTR, ID_REMOTE_CONTROL, glob syntax * generic_udev: console-kit, ATTR, MODE/GROUP, glob syntax (same as udev, except doesn't require console-kit, for people using modern udev, but non-compliant window managers) * old_udev: SYSFS, MODE/GROUP, full list (for people running older systems that don't support globs and ATTR) And we'll keep the super deprecated "policykit" and "consolekit" stuff which manually setup policykit and consolekit kit on old systems, but I don't think anyone uses. Diff coming. -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
