Re: [Xen-devel] [PATCH 8/8] xl.pod.1: improve documentation of FLASK commands

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Tue, 13 Dec 2011, Daniel De Graaf wrote:
> +=head2 FLASK
> +
> +=over 4
> +
> +=item B<getenforce>
> +
> +Determine if the FLASK security module is loaded and enforcing its policy.
> +
> +=item B<setenforce> I<1|0|Enforcing|Permissive>
> +
> +Enable or disable enforcing of the FLASK access controls. The default is
> +permissive and can be changed using the flask_enforcing option on the
> +hypervisor's command line.
> +
> +=item B<loadpolicy> I<policy-file>
> +
> +Load FLASK policy from the given policy file. The initial policy is provided 
> to
> +the hypervisor as a multiboot module; this command allows runtime updates to 
> the
> +policy. Loading new security policy will reset runtime changes to device 
> labels.

Thanks for the patch!
Since we are trying to improve the documentation for Xl, would you be up
for writing a couple of more lines explaining why people might want to
use XSM?
In case there are some parameters to be used in the VM config
file, could you please write a simple text file, like
docs/misc/xl-network-configuration.markdown, describing which ones they
are?
Finally it would be great if you could submit, as a separate patch, an
example policy file that we can keep under tools/examples/ or docs/misc
for everybody to use.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel