On Sun, Aug 25, 2019 at 01:12:12AM +0100, Ken Moffat via blfs-dev wrote:
> On Sat, Aug 24, 2019 at 05:57:10PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 8/24/19 4:38 PM, Ken Moffat via blfs-dev wrote:
> >
> > polkit.addAdminRule(function(action, subject) {
> > return ["unix-group:wheel"];
>
On Mon, Aug 26, 2019 at 05:41:15PM +0200, Armin K. via blfs-dev wrote:
>
> You seem to be missing one important piece of software in this
> discussion, and that's the one and only device manager, the (E)Udev.
> (E)Udev is responsible for "tagging" a device that can be accessed
> through a seat tha
Armin K. via blfs-dev wrote:
On 25. 8. 2019. 19:38, Bruce Dubbs via blfs-dev wrote:
On 8/25/19 12:18 PM, Pierre Labastie via blfs-dev wrote:
[snip]
/dev/input/xxx. Actually, I don't think polkit is involved for
accessing
those: it is the whole purpose of dbus to provide access to hardware
de
On 8/26/19 10:41 AM, Armin K. via blfs-dev wrote:
On 25. 8. 2019. 19:38, Bruce Dubbs via blfs-dev wrote:
On 8/25/19 12:18 PM, Pierre Labastie via blfs-dev wrote:
[snip]
/dev/input/xxx. Actually, I don't think polkit is involved for accessing
those: it is the whole purpose of dbus to provide a
On 25. 8. 2019. 19:38, Bruce Dubbs via blfs-dev wrote:
On 8/25/19 12:18 PM, Pierre Labastie via blfs-dev wrote:
[snip]
/dev/input/xxx. Actually, I don't think polkit is involved for accessing
those: it is the whole purpose of dbus to provide access to hardware
devices
for normal users.
That'
On Sun, Aug 25, 2019 at 08:27:03PM +0100, Ken Moffat via blfs-dev wrote:
>
> First, can I mention that I overthought my attitude to adding my
> user to the wheel group ? This is a developer's workstation (for
> some value of workstation) with a single human user. Being in the
> wheel group doesn
On Sun, Aug 25, 2019 at 06:10:37PM +, DJ Lucas via blfs-dev wrote:
>
> >
> Yes, the input devices get associated with the seat. I'm in the same boat.
> It has and does work perfectly for a regular user with only primary group
> membership. I am unable to figure out why the polkit mechanism is
On Sun, Aug 25, 2019 at 07:18:33PM +0200, Pierre Labastie via blfs-dev wrote:
> On 25/08/2019 18:26, Ken Moffat via blfs-dev wrote:
> >
> > On the pre-9.0 system on my haswell I'll explore membership of the
> > wheel group.
Failed to startx, I think I've broken something there. But that was
supp
On Sun, Aug 25, 2019 at 06:39:03PM +0100, hazel debian via blfs-dev wrote:
> My understanding of polkit is that it isn't concerned with hardware access
> at all but with access to certain actions within programs. Polkit-aware
> programs list their available actions and these are rationed out to
>
On 8/25/2019 7:41 AM, Pierre Labastie via blfs-dev wrote:
On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote:
On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
Not sure how any of this fits with Pierre's earlier observation
about multiple users on the same machine, and frankly that part is
On 8/25/19 12:18 PM, Pierre Labastie via blfs-dev wrote:
[snip]
/dev/input/xxx. Actually, I don't think polkit is involved for accessing
those: it is the whole purpose of dbus to provide access to hardware devices
for normal users.
That's my biggest problem wit dbus. According the the websit
On Sun, Aug 25, 2019 at 6:21 PM Pierre Labastie via blfs-dev <
blfs-dev@lists.linuxfromscratch.org> wrote:
> On 25/08/2019 18:26, Ken Moffat via blfs-dev wrote:
> > On Sun, Aug 25, 2019 at 02:41:17PM +0200, Pierre Labastie via blfs-dev
> wrote:
> >> On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote
On 8/25/2019 11:26 AM, Ken Moffat via blfs-dev wrote:
My _current_ understanding is that with the whole elogind stack,
polkit provides the authorization for /dev/input/ but only for admin
users, and an admin user appears to mean anybody in the wheel group.
To expand on Pierre's answer a bit, u
On 25/08/2019 18:26, Ken Moffat via blfs-dev wrote:
> On Sun, Aug 25, 2019 at 02:41:17PM +0200, Pierre Labastie via blfs-dev wrote:
>> On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote:
>>>
>>>
>>> On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
Not sure how any of this fits with Pierre's
On Sun, Aug 25, 2019 at 02:41:17PM +0200, Pierre Labastie via blfs-dev wrote:
> On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote:
> >
> >
> > On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
> >> Not sure how any of this fits with Pierre's earlier observation
> >> about multiple users on the
On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote:
>
>
> On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
>> Not sure how any of this fits with Pierre's earlier observation
>> about multiple users on the same machine, and frankly that part is
>> not my problem. Now I really WILL step away fro
On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
Not sure how any of this fits with Pierre's earlier observation
about multiple users on the same machine, and frankly that part is
not my problem. Now I really WILL step away from the machine.
Goodnight, thanks for the assistance.
Goodnight
On Sat, Aug 24, 2019 at 09:00:36PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 8/24/19 8:14 PM, Ken Moffat via blfs-dev wrote:
>
> It's installed right at the end of my log after installing the header files.
>
> -- Bruce
Yeah, I managed to boot a system from a couple of weeks ago, which
had elo
On Sun, Aug 25, 2019 at 01:33:12AM +, DJ Lucas via blfs-dev wrote:
>
>
> On 8/24/2019 8:14 PM, Ken Moffat via blfs-dev wrote:
> > On Sun, Aug 25, 2019 at 12:42:12AM +, DJ Lucas via blfs-dev wrote:
> > > > At this point, I'm clearly out of my depth, and I will not be
> > > > updating furth
On Sun, Aug 25, 2019 at 02:46:19AM +0100, Ken Moffat via blfs-dev wrote:
> On Sat, Aug 24, 2019 at 08:05:41PM -0500, Bruce Dubbs via blfs-dev wrote:
> >
> > As best I can tell, our configurations are the same. I do have both the
> > elogind and mountcgroupfs bootscripts running at startup. The o
On 8/24/19 8:14 PM, Ken Moffat via blfs-dev wrote:
On Sun, Aug 25, 2019 at 12:42:12AM +, DJ Lucas via blfs-dev wrote:
At this point, I'm clearly out of my depth, and I will not be
updating further systems (nor reviewing if the kernel config for
elogind is adequate, nor if the mountcgroupfs
On 8/24/2019 8:14 PM, Ken Moffat via blfs-dev wrote:
On Sun, Aug 25, 2019 at 12:42:12AM +, DJ Lucas via blfs-dev wrote:
At this point, I'm clearly out of my depth, and I will not be
updating further systems (nor reviewing if the kernel config for
elogind is adequate, nor if the mountcgroup
On 8/24/2019 8:14 PM, Ken Moffat via blfs-dev wrote:
On Sun, Aug 25, 2019 at 12:42:12AM +, DJ Lucas via blfs-dev wrote:
At this point, I'm clearly out of my depth, and I will not be
updating further systems (nor reviewing if the kernel config for
elogind is adequate, nor if the mountcgroup
On Sat, Aug 24, 2019 at 08:05:41PM -0500, Bruce Dubbs via blfs-dev wrote:
>
> As best I can tell, our configurations are the same. I do have both the
> elogind and mountcgroupfs bootscripts running at startup. The only thing
> left that I can tell is that we may have used different build procedu
On 8/24/19 7:12 PM, Ken Moffat via blfs-dev wrote:
On Sat, Aug 24, 2019 at 05:57:10PM -0500, Bruce Dubbs via blfs-dev wrote:
On 8/24/19 4:38 PM, Ken Moffat via blfs-dev wrote:
Assuming that the reply to my earlier post (should I be in the input
group?) is 'no', can somebody please spare some ti
On Sun, Aug 25, 2019 at 12:42:12AM +, DJ Lucas via blfs-dev wrote:
>
> > At this point, I'm clearly out of my depth, and I will not be
> > updating further systems (nor reviewing if the kernel config for
> > elogind is adequate, nor if the mountcgroupfs and elogind
> > bootscripts are really n
On 8/24/2019 4:38 PM, Ken Moffat via blfs-dev wrote:
Assuming that the reply to my earlier post (should I be in the input
group?) is 'no', can somebody please spare some time to explain how
authorisation via polkit (which I think is the intended route to
gaining access to /dev/input/event*) is
On Sat, Aug 24, 2019 at 05:57:10PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 8/24/19 4:38 PM, Ken Moffat via blfs-dev wrote:
> > Assuming that the reply to my earlier post (should I be in the input
> > group?) is 'no', can somebody please spare some time to explain how
> > authorisation via polki
On 8/24/19 4:38 PM, Ken Moffat via blfs-dev wrote:
Assuming that the reply to my earlier post (should I be in the input
group?) is 'no', can somebody please spare some time to explain how
authorisation via polkit (which I think is the intended route to
gaining access to /dev/input/event*) is supp
Assuming that the reply to my earlier post (should I be in the input
group?) is 'no', can somebody please spare some time to explain how
authorisation via polkit (which I think is the intended route to
gaining access to /dev/input/event*) is supposed to work ?
I've built polkit with the patch for
30 matches
Mail list logo
