faq16: clarify ownership management

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

faq16: clarify ownership management

Klemens Nanni-2
"system" is ambigious, see `owner id` in vm.conf(5).

OK?

Index: faq16.html
===================================================================
RCS file: /cvs/www/faq/faq16.html,v
retrieving revision 1.2
diff -u -p -r1.2 faq16.html
--- faq16.html 25 Oct 2018 15:43:31 -0000 1.2
+++ faq16.html 30 Oct 2018 09:59:28 -0000
@@ -62,7 +62,7 @@ The following features are available:
 <ul>
   <li>serial console access to the virtual machines
   <li><a href="https://man.openbsd.org/tap">tap(4)</a> interfaces
-  <li>per-system user/group ownership
+  <li>per-VM user/group ownership
   <li>privilege separation
   <li>raw, qcow2 and qcow2-derived images
   <li>dumping and restoring of guest system memory

Reply | Threaded
Open this post in threaded view
|

Re: faq16: clarify ownership management

Solene Rapenne
Klemens Nanni <[hidden email]> wrote:

> "system" is ambigious, see `owner id` in vm.conf(5).
>
> OK?
>
> Index: faq16.html
> ===================================================================
> RCS file: /cvs/www/faq/faq16.html,v
> retrieving revision 1.2
> diff -u -p -r1.2 faq16.html
> --- faq16.html 25 Oct 2018 15:43:31 -0000 1.2
> +++ faq16.html 30 Oct 2018 09:59:28 -0000
> @@ -62,7 +62,7 @@ The following features are available:
>  <ul>
>    <li>serial console access to the virtual machines
>    <li><a href="https://man.openbsd.org/tap">tap(4)</a> interfaces
> -  <li>per-system user/group ownership
> +  <li>per-VM user/group ownership
>    <li>privilege separation
>    <li>raw, qcow2 and qcow2-derived images
>    <li>dumping and restoring of guest system memory

seems fine to me. The original idea was to say it uses system user/group for VM
ownership, but in fact the current wording doesn't make sense.

ok solene@