From 2b10a6ce32ad9556794557de815f4bc4a34541cc Mon Sep 17 00:00:00 2001 From: Chris PeBenito Date: Thu, 13 Apr 2006 18:13:26 +0000 Subject: [PATCH] fix formatting, fix xml in example. --- www/html/getting-started.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/www/html/getting-started.html b/www/html/getting-started.html index d00e82ce..f3490f18 100644 --- a/www/html/getting-started.html +++ b/www/html/getting-started.html @@ -120,7 +120,9 @@ documentation. Create myapp.if and add the following: ## Execute a domain transition to run myapp. ## </summary> ## <param name="domain"> +## <summary> ## Domain allowed to transition. +## </summary> ## </param> interface(`myapp_domtrans',` gen_requires(` @@ -139,7 +141,9 @@ interface(`myapp_domtrans',` ## Read myapp log files. ## </summary> ## <param name="domain"> +## <summary> ## Domain allowed to read the log files. +## </summary> ## </param> interface(`myapp_read_log',` gen_requires(` @@ -165,15 +169,14 @@ the class and the permissions used by the interface must also be listed.

Compiling Modules

-Two methods of building modules are supported, -headers and complete source. +

+Two methods of building modules are supported, headers and complete source. Current systems, such as Fedora Core 5, which support loadable policy modules should compile modules using headers. Using the complete source for building modules is only needed if loadable modules are not supported on the system or if when doing other modifications to the base policy. Genereally this is only suggested for experts.

-

Building Using Policy Headers

When building a loadable policy module, the three module source files need not