On 10/29/12 at 08:09pm, Tom Gundersen wrote:
> On Mon, Oct 29, 2012 at 3:24 PM, Curtis Shimamoto
> wrote:
> > One more thing I forgot to ask. Do I need to include the ACTION and
> > ENV{MAJOR} stuff in my personal rule (71-my-uaccess.rule)? Namely:
> >
> > ACTION=="remove", GOTO="uaccess_end"
>
> So far, I have not heard any mention of this being a bad idea, or a
> security concern.
I much prefer the output of ls but the acl man page says that the acls
update the filesystem permissions and vice versa, so I would expect that
if the getfacl command shows rw for the users you have in the vi
On Mon, Oct 29, 2012 at 3:24 PM, Curtis Shimamoto
wrote:
> One more thing I forgot to ask. Do I need to include the ACTION and
> ENV{MAJOR} stuff in my personal rule (71-my-uaccess.rule)? Namely:
>
> ACTION=="remove", GOTO="uaccess_end"
> ENV{MAJOR}=="", GOTO="uaccess_end"
> ...
> LABEL="uaccess
On 10/29/12 at 12:46pm, Rodrigo Rivas wrote:
> On Mon, Oct 29, 2012 at 5:47 AM, Curtis Shimamoto <
> sugar.and.scru...@gmail.com> wrote:
>
> > I did run into one problem though. I sometimes use mplayer from the
> > console. To do this, I have set mplayer up to use fbdev2. Previously
> > (when i
On 10/29/12 at 12:46pm, Rodrigo Rivas wrote:
> On Mon, Oct 29, 2012 at 5:47 AM, Curtis Shimamoto <
> sugar.and.scru...@gmail.com> wrote:
>
> > I did run into one problem though. I sometimes use mplayer from the
> > console. To do this, I have set mplayer up to use fbdev2. Previously
> > (when i
On Mon, Oct 29, 2012 at 12:49 PM, F.Gr. wrote:
> Excerpt from Giorgio Lando's message
> of 2012-10-28T12:29+0100:
>
>> > "Note: Adding your user to groups (optical, audio, scanner, ...)
>> > is not necessary with systemd. It might even break the wanted
>> > functionality if you do so."
>>
>> While
Excerpt from Giorgio Lando's message
of 2012-10-28T12:29+0100:
> > "Note: Adding your user to groups (optical, audio, scanner, ...)
> > is not necessary with systemd. It might even break the wanted
> > functionality if you do so."
>
> While I ignore the technical reasons, my scanner does not work
>
> Not really. Logind does not at all manage non-local users, so if you
> want to give them access to your hardware you have to use another
> mechanism (such as groups).
>
I'm trying to setup an Arch instalation with remote logins using LDAP and
systemd and didn't have audio at all. So it because
On Mon, Oct 29, 2012 at 5:47 AM, Curtis Shimamoto <
sugar.and.scru...@gmail.com> wrote:
> I did run into one problem though. I sometimes use mplayer from the
> console. To do this, I have set mplayer up to use fbdev2. Previously
> (when in all those groups), I was able to do this with no proble
On 10/29/12 at 12:00am, Tom Gundersen wrote:
> On Sun, Oct 28, 2012 at 7:09 PM, Fons Adriaensen wrote:
> > You (Tom) pointed out a way to disable logind modifying device
> > ACLs recently. It could be a good thing to have that in the
> > online docs for those users (like me) for whom this sort of
On 29/10/12 01:17, Zeke Sulastin wrote:
On Sun, Oct 28, 2012 at 4:26 AM, Dave Morgan
wrote:
What are the the technical reasons for group membership breaking
functionality when using systemd?
With a typical desktop use case, systemd-logind's session management
handles the ability to do things
On Sun, Oct 28, 2012 at 7:09 PM, Fons Adriaensen wrote:
> You (Tom) pointed out a way to disable logind modifying device
> ACLs recently. It could be a good thing to have that in the
> online docs for those users (like me) for whom this sort of
> thing is unwanted.
The rule that tags device nodes
On Sun, Oct 28, 2012 at 06:08:46PM +0100, Tom Gundersen wrote:
> This means that both the user granted permissons by ACL, and the user
> granted permission by being in the right group will have access to the
> device. In other words, if your user had access without logind/CK s/he
> will still have
On Sun, Oct 28, 2012 at 12:29 PM, Giorgio Lando wrote:
>> "Note: Adding your user to groups (optical, audio, scanner, ...) is not
>> necessary with systemd. It might even break the wanted functionality if
>> you do so."
>
> While I ignore the technical reasons, my scanner does not work if I am not
On Sun, Oct 28, 2012 at 11:30 AM, Daniel Micay wrote:
> On Sun, Oct 28, 2012 at 4:26 AM, Dave Morgan
> wrote:
>>
>> Hi,
>>
>> The systemd wiki article says:
>>
>> "Note: Adding your user to groups (optical, audio, scanner, ...) is not
>> necessary with systemd. It might even break the wanted func
Nice explanation Zeke. Just one comment:
On Sun, Oct 28, 2012 at 3:17 PM, Zeke Sulastin wrote:
> Adding a user to a group can cause this process to be subverted -
> logind can't manage who is in what group.
This means that both the user granted permissons by ACL, and the user
granted permission
On Sun, Oct 28, 2012 at 4:26 AM, Dave Morgan
wrote:
> What are the the technical reasons for group membership breaking
> functionality when using systemd?
With a typical desktop use case, systemd-logind's session management
handles the ability to do things like use audio/video via ACLs:
$ ls -l
Hi,
The systemd wiki article says:
"Note: Adding your user to groups (optical, audio, scanner, ...) is not
necessary with systemd. It might even break the wanted functionality if
you do so."
What are the the technical reasons for group membership breaking
functionality when using systemd?
--
Da
18 matches
Mail list logo
