From: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: /dev/kvm permissions
Date: Sun, 17 Jun 2007 19:44:34 +0100 [thread overview]
Message-ID: <46758112.4030604@ev-en.org> (raw)
Hello,
What do peoples do/think about the permissions for /dev/kvm?
I'm the maintainer for the Debian package and currently the package uses
a group to control access, for no good reason really. I've seen that
kqemu in Debian simply uses 0666 permissions and consider doing the same
for kvm. I wanted to know what others do in other distributions and what
others think the permissions should be.
Thanks,
Baruch
p.s. Please cc me as I'm not subscribed to kvm-devel. Thanks.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next reply other threads:[~2007-06-17 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 18:44 Baruch Even [this message]
[not found] ` <46758112.4030604-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
2007-06-17 18:52 ` /dev/kvm permissions Avi Kivity
[not found] ` <4675830B.3020404-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-17 19:17 ` Baruch Even
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=46758112.4030604@ev-en.org \
--to=baruch-6p1dz+xqpllytjvyw6ydsg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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