From: Russell Coker <russell@coker.com.au>
To: Murray McAllister <mmcallis@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: user guide draft: "Examples: Booleans for NFS"
Date: Thu, 30 Oct 2008 15:25:16 +1100 [thread overview]
Message-ID: <200810301525.19737.russell@coker.com.au> (raw)
In-Reply-To: <4908F1AA.9060006@redhat.com>
On Thursday 30 October 2008 10:28, Murray McAllister <mmcallis@redhat.com>
wrote:
> These Booleans exist in SELinux policy as shipped with Fedora 10. They
> may not exist in policy shipped with other versions of Fedora or other
> operating systems.
>
> I'll keep these things in mind when the guide is forked for Red Hat
> Enterprise Linux.
Given that M4 knowledge is required for anyone who does anything serious with
SE Linux, maybe you should write your documentation in M4.
Some years ago I wrote my CV in M4 and had it produce about 10 different
versions (I also had a Makefile). Then it a recruiting agent wanted a
version of my CV that emphasised my C coding experience I could just send the
relevant file.
The same technique could be used for any other document. It would be good if
you could type "make" and produce documents for several versions of Fedora
and a couple of versions of RHEL at the same time.
--
russell@coker.com.au
http://etbe.coker.com.au/ My Blog
http://www.coker.com.au/sponsorship.html Sponsoring Free Software development
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-10-30 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 3:14 user guide draft: "Examples: Booleans for NFS" Murray McAllister
2008-10-29 12:29 ` Daniel J Walsh
2008-10-29 23:28 ` Murray McAllister
2008-10-30 4:25 ` Russell Coker [this message]
2008-10-30 5:38 ` Murray McAllister
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=200810301525.19737.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=mmcallis@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.