From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Conflicting udev rules shipped for KVM
Date: Sat, 14 Sep 2019 13:53:37 +0200 [thread overview]
Message-ID: <20190914115337.xPksC_o5cU8BFJC55eCB8oVsUucs4UfgkRszoGQxGnQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14440@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/14440#issuecomment-531473672
Comment:
Indeed, I tried on my second Void installation and it had /dev/kvm set to 0666 after a system boot. It was probably libvirt on my first installation that touched the device that touched the device and thus lead to udev setting the correct permissions.
I experimented a bit with it and if I comment out the udev default rule, the permissions get applied correctly. If I remove both rules, the default is root:root and 0600. Not really finding an explanation why the second rule seems to be ignored on boot I thought it might be because the first one is more specific and the rules don't match exactly. I'm still not sure if that is the cause but either removing `OPTIONS+="static_node=kvm"` from the first rule oder adding it to the second rule leads to both rules being executed during udev startup and it works as expected.
While we could just patch the udev default rules, I think it would be better to change the base-files rule so the default one gets properly overridden.
next prev parent reply other threads:[~2019-09-14 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 20:30 [ISSUE] " voidlinux-github
2019-09-14 8:12 ` voidlinux-github
2019-09-14 9:50 ` voidlinux-github
2019-09-14 11:53 ` voidlinux-github [this message]
2019-09-14 13:55 ` voidlinux-github
2019-09-16 14:20 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190914115337.xPksC_o5cU8BFJC55eCB8oVsUucs4UfgkRszoGQxGnQ@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).