all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36335@debbugs.gnu.org
Subject: bug#36335: Is /dev/kvm missing ACLs?
Date: Wed, 26 Jun 2019 23:32:37 -0700	[thread overview]
Message-ID: <87d0izlere.fsf@gmail.com> (raw)
In-Reply-To: <87v9wu4v3l.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 24 Jun 2019 21:54:54 +0200")

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

Hi Ludo,

Ludovic Courtès <ludo@gnu.org> writes:

> Guix System doesn’t use ACLs at all.
>
> However, the udev rule for kvm sets it up like this:
>
>   crw-rw---- 1 root kvm 10, 232 Jun 24 08:38 /dev/kvm
>
> and the build users are part of the ‘kvm’ group.  I personally arrange
> to have my user account in that group too.

It's good to know that the "kvm" group is the right way to grant
permissions.  However, if Guix System doesn't use ACLs, then why do some
of my device files have ACLs on them, such as the video device file?

--8<---------------cut here---------------start------------->8---
$ getfacl /dev/video0 
getfacl: Removing leading '/' from absolute path names
# file: dev/video0
# owner: root
# group: video
user::rw-
user:marusich:rw-
group::rw-
mask::rw-
other::---
--8<---------------cut here---------------end--------------->8---

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-06-27  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  4:20 bug#36335: Is /dev/kvm missing ACLs? Chris Marusich
2019-06-24 19:54 ` Ludovic Courtès
2019-06-27  6:32   ` Chris Marusich [this message]
2019-06-27 13:45     ` Ludovic Courtès
2019-07-01  8:41       ` Danny Milosavljevic
2019-07-10  6:23       ` Chris Marusich
2019-07-10 17:10         ` Ludovic Courtès
2019-07-11  7:18           ` Danny Milosavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0izlere.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=36335@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.