On Wed, Oct 3, 2012 at 5:05 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Wed, Oct 03, 2012 at 08:52:31AM -0600, Daniel Drake wrote: >> On Tue, Oct 2, 2012 at 5:36 PM, Dmitry Torokhov >> <dmitry.torokhov@xxxxxxxxx> wrote: >> > Why can't you change event device ownership to the local user? Then you >> > can read and act upon events. >> >> That would work, I guess. >> >> However, it sounds like your suggesting that we add some custom rules >> in OLPC's own builds and leave it at that. I'm not sure what >> user/group we could use for a generic rule matching this hardware. > > That shouldn't be a custom rule, other distros bind the keyboard / mouse > to the local user in order to handle the multi-seat situation properly. > That should all be done already in the console-kit logic (or whatever > handles it now.) > > Have you looked into that? The usual model is not uid/gid, it's ACLs dynamically applied for logged-in users with active sessions: http://www.freedesktop.org/software/systemd/man/systemd-logind.service.html http://cgit.freedesktop.org/systemd/systemd/tree/src/login/70-uaccess.rules Kay -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
