On Sun, 2012-03-11 at 14:36 +0100, Jogchum Reitsma wrote:
> Op 11-03-12 03:12, Adam Williamson schreef:
> > On Sat, 2012-03-10 at 20:36 -0500, Scott Talbert wrote:
> >> On Sat, 10 Mar 2012, Jogchum Reitsma wrote:
> >>
> >>> Op 10-03-12 20:23, Scott Talbert schreef:
> >>> grep dialout /etc/group
> >>>
> >>> grep dialout /etc/group
> >>> dialout:x:16:jogchum
> >>>
> >>> So, apparently the group exists. Which comes to no suprise with me, since
> >>> I
> >>> added myself to this group trough Yast, the sysadmin tool from OpenSuse.
> >>>
> >>> But why these udev rules are not obliged (they *are* seen, as I
> >>> demonstrated
> >>> in the messages log some posts before in this tread)? Can it be that the
> >>> new
> >>> systemd in OpenSuse 12.1 kicks in here? Should I post questions on the
> >>> opensuse forums (but, cross posting is not netiquette, I know)?
> >> One thing you could try is to change the "SYSFS" in the relevant udev rule
> >> to "ATTR" to see if that might fix it.
> >>
> >> But yes, you should at the very least file a bug with OpenSUSE as this
> >> sounds like a problem with their packaging of concordance.
> > Scott - I mailed a fairly large patch to this list back in January,
> > together with extensive explanation / justification, which should
> > considerably improve the behaviour of libconcord in re udev on modern
> > distros. I didn't hear any kind of reply, though. I was hoping it would
> > be merged upstream.
> >
> > I suspect the SYSFS/ATTR thing may well be to blame here, yes. Recent
> > udev builds have now stopped just warning about the SYSFS syntax (which
> > has been deprecated for about five years, IIRC) and now flat out refuse
> > it.
> >
> > My patch fixes that, and also takes advantage of udev's ACL support to
> > allow access to the remote for locally logged-in users (only) with no
> > abuse of the 'dialout' group.
> >
> > The post I made was:
> >
> > http://sourceforge.net/mailarchive/forum.php?thread_name=1326769277.1782.23.camel%40adam&forum_name=concordance-devel
> >
> > The patch is still being carried in Fedora's libconcord:
> >
> > http://pkgs.fedoraproject.org/gitweb/?p=libconcord.git;a=blob;f=libconcord-0.23-modern_udev.patch;h=5efd8f4a41db0f7977bcefda3cd7c5456ffc0110;hb=HEAD
> >
> > so users of Fedora get seamless access to Harmony remotes, it 'just
> > works' so long as libconcord and congruity are installed.
> >
> > Jogchum, you may find this patch useful on openSUSE 12.1. I suspect it
> > probably has a new enough udev to use the 'new-generation udev' stuff in
> > my patch.
> Adam,
>
> Thanks. As you can see from my last reply to Scott, updating the rules
> file has made it possible to get access to the remote as a normal user,
> so this problem was solved that way.
>
> I suppose this patch is a rules-file itself, so I can take it, remove
> line numbering and save it as 70-acl.rules in /etc/udev/rules.d ? Done
> so already, so I hope my assumption is correct...
Um...no, not really. When libconcord is built it 'generates' the udev
rules file, depending on whether you tell it to use generic udev
support, hal/consolekit support or hal/policykit support. The basic rule
template that's used gets changed based on which you ask for, and a
simple script builds a udev rules file with several dozen lines, each
based on the template selected, one for each Harmony USB ID libconcord
knows of.
My patch is to libconcord's udev rules generation script; it renames the
existing 'generic udev' template to be 'old udev' support and replaces
it with a new 'generic udev' template which uses modern syntax and also
uses udev's ACL support to make the node accessible to all
locally-logged in users, no special group membership required. It also
patches the docs to explain this.
So no, you can't just rename any file in the patch and save it as a udev
rule, that's not going to work. But you could edit your existing
libconcord rules file and adjust it to match my
UDEV_NEW_NO_POLICY_TEMPLATE, which is:
ATTR{idVendor}=="%s", ATTR{idProduct}=="%s", ENV{ID_REMOTE_CONTROL}="1"
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
