From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Conflicting udev rules shipped for KVM
Date: Sat, 14 Sep 2019 15:55:32 +0200 [thread overview]
Message-ID: <20190914135532.E9fq2c82xSA14GDZjfn0JGxvzboT0b6o1ZGOIVhS2EA@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: 517 bytes --]
New comment by thomas-t-w on void-packages repository
https://github.com/void-linux/void-packages/issues/14440#issuecomment-531481665
Comment:
I agree. I will create a pull request for that adding those options to our base files. I did some research and kvm is created as a static node in eudev because the module isn't loaded on some platforms until first use. Best not to patch the rules file in eudev because that could change from time to time in eudev and because we probably want to keep it as a static node.
next prev parent reply other threads:[~2019-09-14 13:55 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
2019-09-14 13:55 ` voidlinux-github [this message]
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=20190914135532.E9fq2c82xSA14GDZjfn0JGxvzboT0b6o1ZGOIVhS2EA@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).