mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
Ian Campbell
8e84e3f524
Having both the Xen tree and the tools tree recurse into the foreign headers directory causes headaches in parallel builds and when building 32-bit tools + 64 bit Xen in the same tree. Therefore we cause mk-symlinks to symlink in the foreign headers build bits and generate a local version of the headers and checker tool. Only libxc needs to do this since the other tools were actually picking up the libxc version of the headers anyway so the mk-symlinks calls can be removed from these components. Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
## # readme.txt <description to the sHype/Xen access control architecture> # # Author: # Reiner Sailer 08/30/2006 <sailer@watson.ibm.com> # # # This file is a toc for information regarding # the access control policy and tools in Xen. ## 1. Xen User Guide describes how to configure, install, and deploy the sHype Access Control Module in Xen. See chapter "sHype/Xen Access Control". 2. 'xm' man page describes the commands related to Xen management, including the commands to manage security policies and labels. Read the access control subcommand section of the xm manual first. 3. policy.txt describes examples for access control policies in Xen. First read the policy description in the Xen User Guide. 4. policytools.txt describes the available tools for creating and managing security policies in Xen.