mirror-tutorial updated on cvs
by Hugo Cisneiros
Hau,
As in bugzilla #178790, I asked stickster for updating the
mirror-tutorial, so I did it today. It is on cvs, so any feedback will
be really appreciated, since my english grammar isn't so good :)
Changes made:
/cvs/docs/mirror-tutorial/en/mirror-tutorial-en.xml
--
[]'s
Eitch
http://www.devin.com.br/eitch/
"Talk is cheap. Show me the code." - Linus Torvalds
18 years, 2 months
press release format, for translation too
by Karsten Wade
We want to be able to translate Fedora press releases using our existing
systems, and we need to figure out a format that works best. We
need .po files for the translation, the question is, what to write in
and how to get them.
Here are the choices we cooked up on IRC today[1]:
1. Formatted ASCII text.
We'd have to write a custom text2po and po2text, with strict
formatting rules on the TXT side.
2. DocBook XML
Proven, but the stylesheets do not make a pretty press release. If
an XSL fanatic would make a nice stylesheet for us ...
3. OO.o SXW -> XML -> .po -> XML -> SXW
No one has experimented with this yet, but it could work
conceivably. If it doesn't work, we could manually unpack the SXW
and work on the XML directly. I reckon that would work.
4. Wiki -> .po
Theoretically possible, but no idea if it's been done.
What do you think about all this?
- Karsten
[1] Full log of the chat, provides all the technical details known:
http://www.redhat.com/archives/fedora-docs-list/2006-February/msg00026.html
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Content Services Fedora Documentation Project
http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
18 years, 2 months
Self-Introduction: Cody DeHaan
by Cody R. DeHaan
- Cody DeHaan
- Wisconsin, USA
- Student
- As a recent cold-turkey convert after years of meddling with Linux,
I would like to aid in the creation of documentation in things that
could really help people make that step from looking at Linux/Fedora,
to truly using it. I have been using RedHat since version 6, and
followed the migration to Fedora Core. I have many ideas for
documentation that I could contribute. I would be more than willing to
help in the process of editing documents, and I am willing to attempt
just about anything.
- I have done computer support for quite some time now. I have fairly
advanced computer skills, administering a Domain environment, and I
have experience in NT/XP/2003, Linux and OS X. I have experience in
web design, along with simplifying documentation/instructions to make
it easy to read and follow for even a novice user. Overall, I really
appreciate the documentation that helped me fully make the switch to
Fedora that I have used up until now, and I would like to help give
something back in any way possible. Thanks for your time and I look
forward to working with all of you!
[cdehaan@notebook ~]$ gpg --fingerprint cody.dehaan(a)gmail.com
pub 1024D/CA7E1376 2006-02-05 [expires: 2007-01-02]
Key fingerprint = 6E51 4866 FD7C 6E23 03E2 CDC1 896D 934D CA7E 1376
uid Cody DeHaan <Cody.DeHaan(a)gmail.com>
sub 1024g/F3FA3738 2006-02-05 [expires: 2007-01-02]
18 years, 2 months
Re: docs-common/bin fdpsh,1.6,1.7
by Tommy Reynolds
Uttered "Paul W. Frields" (pfrields) <fedora-docs-commits(a)redhat.com>, spake thus:
> Pushd/popd stuff was ugly, it's true; this should be more portable.
> -FDPDIR=${FDPBINDIR}/../.. export FDPDIR
> +FDPDIR=`cd ${FDPBINDIR}/../.. ; /bin/pwd` export FDPDIR
OK, OK, if you insist on avoiding relative paths, I won't quibble
about this construct ;-) At least it fits on one line.
Cheers
18 years, 2 months
Re: selinux-faq selinux-faq-en.xml,1.25,1.26
by Karsten Wade
BTW, there is a freeze date of 10 Feb. Midnight UTC for getting guides,
such as this one, translated. Plan to get all of your FC5 changes in by
that date. We'll tag a freeze at that point, and you can continue
writing at that point. We'll arrange translation freezes for new
content later, such as the final FC5 content freeze for guides on 03
Mar.
On Fri, 2006-02-03 at 17:41 -0500, Chad Sellers wrote:
> Author: csellers
>
> Update of /cvs/docs/selinux-faq
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2745
>
> Modified Files:
> selinux-faq-en.xml
> Log Message:
> First cut at an CF5 FAQ. Still missing several necessary new items, but
> old items should be consistent with FC5 now.
>
>
>
> Index: selinux-faq-en.xml
> ===================================================================
> RCS file: /cvs/docs/selinux-faq/selinux-faq-en.xml,v
> retrieving revision 1.25
> retrieving revision 1.26
> diff -u -r1.25 -r1.26
> --- selinux-faq-en.xml 29 Jun 2005 14:51:04 -0000 1.25
> +++ selinux-faq-en.xml 3 Feb 2006 22:40:55 -0000 1.26
> @@ -6,11 +6,11 @@
> <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
> %FEDORA-ENTITIES-EN;
>
> -<!ENTITY BOOKID "selinux-faq-1.3-8 (2005-01-20-T16:20-0800)"> <!-- version of manual and date -->
> +<!ENTITY DOCID "selinux-faq-1.5-1 (2005-12-30-T12:21-0500)"> <!-- version of manual and date -->
>
> <!-- ************** local entities *********** -->
> <!ENTITY APACHE "Apache HTTP">
> -<!ENTITY LOCALVER "3"> <!-- Set value to your choice, when guide version is out -->
> +<!ENTITY LOCALVER "5"> <!-- Set value to your choice, when guide version is out -->
> <!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
> <!ENTITY BUG-URL
> "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%...!
> t;20of%20FAQ%20%28found%20on%0D%0Ahttp%3A%2F%2Ffedora.redhat.com%2Fdocs%2Fselinux-faq-fc3%2Fln-legalnotice.html%29%2C%0D%0Afor%20example%3A%0D%0A%0D%0A%20%20selinux-faq-1.3-8%20%282005-01-20-T16%3A20-0800%29%0D%0A%0D%0A%0D%0A%0D%0A%0D%0A%0D%0A%0D%0A%0D%0A&keywords=&dependson=&blocked=118757%20%20&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">
> @@ -28,6 +28,10 @@
> <surname>Wade</surname>
> <firstname>Karsten</firstname>
> </author>
> + <author>
> + <surname>Sellers</surname>
> + <firstname>Chad</firstname>
> + </author>
> </authorgroup>
> &LEGALNOTICE;
> </articleinfo>
> @@ -43,8 +47,9 @@
> <note>
> <title>This FAQ is specific to &FC; &LOCALVER;</title>
> <para>
> - If you are looking for the FAQ for &FC; 2, refer to <ulink
> - url="http://fedora.redhat.com/docs/selinux-faq-fc2/" />.
> + If you are looking for the FAQ for &FC; 2 or &FC; 3, refer to <ulink
> + url="http://fedora.redhat.com/docs/selinux-faq-fc2/" /> or <ulink
> + url="http://fedora.redhat.com/docs/selinux-faq-fc3/" />, respectively.
> </para>
> </note>
> <para>
> @@ -80,13 +85,29 @@
> </listitem>
> <listitem>
> <para>
> - Writing SE Linux policy HOWTO — <ulink
> + Writing traditional SE Linux policy HOWTO — <ulink
> url="https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266"
> />
> </para>
> </listitem>
> <listitem>
> <para>
> + Reference Policy (the new policy found in &FC; 5) — <ulink
> + url="http://serefpolicy.sourceforge.net/"
> + />
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> + SELinux policy development training courses — <ulink
> + url="http://tresys.com/services/training.shtml"
> + /> and <ulink
> + url="https://www.redhat.com/training/security/courses/rhs429.html"
> + />
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> Getting Started with SE Linux HOWTO: the new SE Linux (Debian) —
> <ulink
> url="https://sourceforge.net/docman/display_doc.php?docid=20372&group_id=21266" />
> @@ -94,6 +115,13 @@
> </listitem>
> <listitem>
> <para>
> + List of SELinux object classes and permissions —
> + <ulink
> + url="http://tresys.com/selinux/obj_perms_help.shtml" />
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> On IRC — irc.freenode.net, #fedora-selinux
> </para>
> </listitem>
> @@ -110,7 +138,7 @@
> <title>Making changes/additions to the &FED; &SEL; FAQ</title>
> <para>
> This FAQ is available at <ulink
> - url="http://fedora.redhat.com/docs/selinux-faq-fc3/">http://fedora.redhat.com/docs/selinux-faq-fc3/</ulink>.
> + url="http://fedora.redhat.com/docs/selinux-faq-fc5/">http://fedora.redhat.com/docs/selinux-faq-fc5/</ulink>.
> </para>
> <para>
> For changes or additions to the &FED; &SEL; FAQ, use this <ulink
> @@ -224,29 +252,49 @@
> delivered in a package, with an associated source package. Current
> shipping policy packages are:
> </para>
> + <itemizedlist>
> + <listitem>
> + <para><filename>selinux-policy-<replaceable><version></replaceable>.noarch.rpm</filename>
> + </para>
> + </listitem>
> + </itemizedlist>
> + <para>
> + This package is common to all types of policy and contains config
> + files/man pages.
> + </para>
> + <itemizedlist>
> + <listitem>
> + <para><filename>selinux-policy-devel-<replaceable><version></replaceable>.noarch.rpm</filename>
> + </para>
> + </listitem>
> + </itemizedlist>
> + <para>
> + This is the development environment. This replaces the -sources
> + package from the past. This package contains the interface files
> + used in reference policy along with a Makefile and a small tool
> + used to generate a policy template file. The interface files
> + reside in /usr/share/selinux/refpolicy/headers directory.
> + </para>
> <itemizedlist>
> <listitem>
> - <para><filename>selinux-policy-strict-<replaceable><version-arch></replaceable>.rpm</filename>
> - and
> - <filename>selinux-policy-strict-sources-<replaceable><version-arch></replaceable>.rpm</filename>
> + <para><filename>selinux-policy-strict-<replaceable><version></replaceable>.noarch.rpm</filename>
> </para>
> </listitem>
> <listitem>
> <para>
> - <filename>selinux-policy-targeted-<replaceable><version-arch></replaceable>.rpm</filename>
> - and
> - <filename>selinux-policy-targeted-sources-<replaceable><version-arch></replaceable>.rpm</filename>
> + <filename>selinux-policy-targeted-<replaceable><version></replaceable>.noarch.rpm</filename>
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> + <filename>selinux-policy-mls-<replaceable><version></replaceable>.noarch.rpm</filename>
> </para>
> </listitem>
> </itemizedlist>
> <para>
> - Policy source resides in
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy</filename>,
> - when it is installed, and the binary policy file is in
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy</filename>.
> - Policy source is not required for ultra-minimal installations. The
> - policy for the types and domains is configured separately from
> - security context for the subjects and objects.
> + Binary policy files are in /etc/selinux/policyname. The policy for the
> + types and domains is configured separately from security context for the
> + subjects and objects.
> </para>
> </answer>
> </qandaentry>
> @@ -374,6 +422,47 @@
> <qandaentry>
> <question>
> <para>
> + What is the mls policy? Who is it for?
> + </para>
> + </question>
> + <answer>
> + <para>
> + The mls policy is similar to the strict policy, but adds an additional
> + field to security contexts for separating levels. These levels can be
> + used to separate data in an environment that calls for strict
> + hierarchical separation. The most common example of this is a military
> + setting where data is classified at a certain level. This policy is
> + geared toward these sorts of users, and is probably not useful to
> + you unless you fall into this category.
> + </para>
> + </answer>
> + </qandaentry>
> + <qandaentry id="faq-entry-whatis-refpolicy" xreflabel="Reference Policy">
> + <question>
> + <para>
> + What is the Reference Policy?
> + </para>
> + </question>
> + <answer>
> + <para>
> + The Reference Policy
> + is a new project designed to rewrite the entire SELinux policy in a
> + way that is easier to use and understand. To do this, it uses
> + the concepts of modularity, abstraction, and well-defined interfaces.
> + See <ulink
> + url="http://serefpolicy.sourceforge.net/">it's project page</ulink>
> + for more information on it.
> + </para>
> + <para>
> + Fedora policies at version 1.x are based on the traditional example
> + policy. Policies version 2.x (as used in &FC; &LOCALVER;) are based
> + on the Reference Policy.
> + </para>
> + </answer>
> + </qandaentry>
> + <qandaentry>
> + <question>
> + <para>
> What are file contexts?
> </para>
> </question>
> @@ -423,8 +512,8 @@
> <para>
> There is no difference between a domain and a type, although
> domain is sometimes used to refer to the type of a process. The
> - use of domain in this way stems from traditional TE models, where
> - domains and types are separate.
> + use of domain in this way stems from Domain and Type Enforcement (DTE)
> + models, where domains and types are separate.
> </para>
> </answer>
> </qandaentry>
> @@ -796,7 +885,7 @@
> kernel command line to turn system-call auditing off.
> </para>
> <para>
> - System-call auditing is off by default. When on, it provides
> + System-call auditing is on by default. When on, it provides
> information about the system-call that was executing when SELinux
> generated a <computeroutput>denied</computeroutput> message. This
> may be helpful when debugging policy.
> @@ -812,8 +901,8 @@
> </question>
> <answer>
> <para>
> - This is not supported at this time. In the future, a utility will
> - be provided to tune auditing.
> + To do this, run <command>auditctl -e 0</command>. Note that this
> + will not affect auditing of SELinux AVC denials.
> </para>
> </answer>
> </qandaentry>
> @@ -1000,9 +1089,9 @@
> You can create your new user with the standard
> <command>useradd</command> command. First you must become root;
> under the strict policy you will need to change role to
> - <computeroutput>sysadm_r</computeroutput>. This context switch
> - has been incorporated into the <command>su</command> command and
> - occurs automatically. For the targeted policy, you will not need
> + <computeroutput>sysadm_r</computeroutput> using
> + <computeroutput>newrole -r sysadm_r</computeroutput>
> + For the targeted policy, you will not need
> to switch roles, staying in
> <computeroutput>unconfined_t</computeroutput>:
> </para>
> @@ -1024,7 +1113,7 @@
> </para>
> </answer>
> </qandaentry>
> - <qandaentry>
> +<!-- <qandaentry>
> <question>
> <para>
> All of the other &SEL; documentation states that the
> @@ -1052,7 +1141,7 @@
> change.
> </para>
> </answer>
> - </qandaentry>
> + </qandaentry> -->
> <qandaentry>
> <question>
> <para>
> @@ -1104,12 +1193,14 @@
> </para>
> </answer>
> </qandaentry>
> + <!-- Need to modify this to work with new policy sources, or find
> + a better method than modifying all source
> <qandaentry>
> <question>
> <para>
> I get a specific permission denial only when &SEL; is in enforcing
> mode, but I don't see any audit messages in
> - <filename>/var/log/messages</filename>. How can I identify the
> + <filename>/var/log/audit/audit.log</filename>. How can I identify the
> cause of these silent denials?
> </para>
> </question>
> @@ -1155,7 +1246,7 @@
> <command>cd /etc/selinux/targeted/src/policy
> make clean
> make load</command>
> -</screen>
> +</screen> -->
> <!-- commented out just in case it needs to be rewritten and included:
> <para>
> Another reason for getting silent denials is on an
> @@ -1180,9 +1271,9 @@
>
> audit(1083674459.837:0): security_compute_sid: invalid context root:sysadm_r:system_chkpwd_t for scontext=root:sysadm_r:newrole_t tcontext=system_u:object_r:chkpwd_exec_t tclass=process
>
> --->
> </answer>
> </qandaentry>
> +-->
> <qandaentry>
> <question>
> <para>
> @@ -1246,18 +1337,7 @@
> changes in the updated policy.
> </para>
> <para>
> - If you have installed the policy source packages, e.g.
> - <filename>selinux-policy-strict</filename>, you can execute these
> - commands to relabel the file system.
> - </para>
> -<screen>
> -<command>cd /etc/selinux/targeted/src/policy
> -make
> -make relabel
> -reboot</command>
> -</screen>
> - <para>
> - If you aren't using policy sources, another approach is to use the
> + To relabel, use the
> <command>fixfiles</command> command or take advantage of the
> <filename>/.autorelabel</filename> mechanism:
> </para>
> @@ -1288,6 +1368,8 @@
> </para>
> </answer>
> </qandaentry>
> + <!-- Source package doesn't exist any more
> + Is there something similar now?
> <qandaentry>
> <question>
> <para>
> @@ -1296,11 +1378,13 @@
> </para>
> </question>
> <answer>
> + -->
> <!--
> thanks to "Gene C." <czar czarc net> for authoring the
> original answer in
> http://www.redhat.com/archives/fedora-test-list/2004-April/msg00755.html
> -->
> + <!--
> <para>
> A policy package such as
> <filename>selinux-policy-targeted</filename> is a requirement for
> @@ -1338,6 +1422,7 @@
> file as well as the <filename>file_contexts</filename> file, then
> loads them as the currently effective policy.
> </para>
> + -->
>
> <!-- not sure if currently still an issue, or how to rephrase
> <caution>
> @@ -1351,32 +1436,28 @@
> </para>
> </caution>
> -->
> + <!--
> </answer>
> </qandaentry>
> + -->
> <qandaentry>
> <!--
> http://www.redhat.com/archives/fedora-selinux-list/2004-May/msg00061.html
> -->
> <question>
> <para>
> - Why do the files
> + Why do binary policies (e.g.
> <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy/policy.<<replaceable>version</replaceable>></filename>
> - and
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy/policy.<<replaceable>version</replaceable>></filename>
> - have different (sizes, md5sums, dates)?
> + distributed with Fedora and those I compile myself have different sizes
> + and md5sums?
> </para>
> </question>
> <answer>
> <para>
> When you install a policy package, pre-compiled binary policy
> files are put directly into <filename>/etc/selinux</filename>.
> - When a policy source package is installed or updated, binary
> - policy files are built in
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy</filename>,
> - then moved to
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy/</filename>.
> The different build environments will make target files that have
> - different sizes, md5sums, and dates.
> + different sizes, md5sums.
> </para>
> </answer>
> </qandaentry>
> @@ -1409,39 +1490,94 @@
> </question>
> <answer>
> <para>
> - Your help is definitely appreciated. You can start by joining the
> - &SEL; mailing list, <ulink
> - url="mailto:fedora-selinux-list@redhat.com">fedora-selinux-list(a)redhat.com</ulink>;
> - you can subscribe and read the archives at <ulink
> - url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">http://www.redhat.com/mailman/listinfo/fedora-selinux-list</ulink>.
> - The UnOfficial FAQ has some generic policy writing HOWTO
> - information (<ulink
> - url="http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21266#...">http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21266#...</ulink>).
> - Another new resource is the Writing SE Linux policy HOWTO (<ulink
> - url="https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266">https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266</ulink>).
> + Your help is definitely appreciated.
> + <itemizedlist>
> + <listitem>
> + <para>
> + You can start by joining the
> + &FED; &SEL; mailing list, <ulink
> + url="mailto:fedora-selinux-list@redhat.com">fedora-selinux-list(a)redhat.com</ulink>;
> + you can subscribe and read the archives at <ulink
> + url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">http://www.redhat.com/mailman/listinfo/fedora-selinux-list</ulink>.
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> + The UnOfficial FAQ has some generic policy writing HOWTO
> + information (<ulink
> + url="http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21266#...">http://sourceforge.net/docman/display_doc.php?docid=14882&group_id=21266#...</ulink>).
> + </para>
> + </listitem>
> + <listitem>
> + <para>
> + Another new resource is the Writing SE Linux policy HOWTO (<ulink
> + url="https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266">https://sourceforge.net/docman/display_doc.php?docid=21959&group_id=21266</ulink>).
> + </para>
> + </listitem>
> + </itemizedlist>
> + Also, since the &FC; &LOCALVER; policy is based on the <xref linkend="faq-entry-whatis-refpolicy"/>,
> + you should look at the documentation on its project page.
> </para>
> <para>
> Your best bet is to look at the policy files in
> - <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy/</filename>
> - and try experiments. Watch the <computeroutput>avc
> - denied</computeroutput> messages in
> - <filename>/var/log/messages</filename> for clues.
> - </para>
> - <para>
> - A useful tool for the policy writer is
> - <command>/usr/bin/audit2allow</command>, which translates
> - <computeroutput>avc</computeroutput> messages from
> - <filename>/var/log/messages</filename> into rules that can be used
> - by &SEL;. These rules will likely need to be cleaned up.
> - </para>
> - <para>
> - The command <command>audit2allow</command> can receive input via
> - three methods. Default is from standard input
> - (<firstterm>STDIN</firstterm>). Using the <option>-i</option>
> - option reads input from <filename>/var/log/messages</filename>,
> - and the <option>-d</option> option reads input from
> - <command>dmesg</command> output.
> + <filename>/usr/share/doc/selinux-policy-<replaceable>>version<</replaceable></filename>
> + which shows examples of policy.
> </para>
> + <para>
> + If you want to write a new policy domain, you should install the
> + selinux-policy-devel package. This will place reference policy
> + interface files into the
> + <filename>/usr/share/selinux/refpolicy directory</filename>.
> + </para>
> + <para>
> + There is also a tool there to help you get started. You can use
> + the tool <command>policygentool</command> to generate your own
> + <filename>te</filename>, <filename>fc</filename>
> + and <filename>if</filename> file.
> + This tool takes two parameters: the Name of the policy module
> + (mydaemon) and the full path to the executable
> + (<filename>/usr/sbin/mydaemon</filename>). This will create three
> + files <filename>mydaemon.te</filename>,
> + <filename>mydaemon.fc</filename> and
> + <filename>mydaemon.if</filename>.
> + After you generate the policy files,
> + use the supplied Makefile,
> + <filename>/usr/share/selinux/refpolicy/Makefile</filename>,
> + build a policy package (<filename>mydaemon.pp</filename>). Now
> + you can load the policy
> + module, using <command>semodule</command>, and relabel the
> + executable using
> + <filename>restorecon</filename>. Since you have very limited
> + policy for your
> + executeable, SELinux will prevent it from doing much. So you need
> + to turn on permissive mode and then use the init script to start
> + your daemon. Now you can start collect avc messages. You can use
> + <command>audit2allow</command> to translate the avc messages to
> + allow rules and begin
> + updating you <filename>mydaemon.te</filename> file. You should
> + search for interface
> + macros in the <filename>/etc/selinux/refpolicy/include</filename>
> + directory and use
> + these instead of using the allow rules directly, whenever
> + possible. If you want more examples of polcy, you could always
> + install the selinux-policy src rpm, which contains all of the
> + policy te files for the reference policy.
> + </para>
> +<screen>
> +<command># /usr/share/selinux/refpolicy/policygentool mydaemon /usr/sbin/mydaemon
> +# make -f /usr/share/selinux/refpolicy/Makefile
> +m4 /usr/share/selinux/refpolicy/include/all_perms.spt /usr/share/selinux/refpolicy/include/loadable_module.spt /usr/share/selinux/refpolicy/include/misc_macros.spt
> +...
> +/usr/share/selinux/refpolicy/include/obj_perm_sets.spt mydaemon.fc > tmp/mydaemon.mod.fc
> +Creating targeted mydaemon.pp policy package
> +/usr/bin/semodule_package -o mydaemon.pp -m tmp/mydaemon.mod -f tmp/mydaemon.mod.fc
> +rm tmp/mydaemon.mod.fc tmp/mydaemon.mod
> +# semodule -i mydaemon.pp
> +# restorecon -v /usr/sbin/mydaemon
> +restorecon reset /usr/sbin/mydaemon context user_u:object_r:sbin_t->system_u:object_r:mydaemon_exec_t
> +# setenforce 1
> +# service mydaemon restart</command>
> +</screen>
> </answer>
> </qandaentry>
> <qandaentry>
> @@ -1552,6 +1688,12 @@
> ext2/ext3, XFS has recently added support for the necessary
> labels.
> </para>
> + <para>
> + Note that XFS SELinux support is broken in upstream kernel
> + 2.6.14 and 2.6.15, but fixed (worked around)
> + in 2.6.16. So, make sure your kernel includes this fix if
> + you choose to use XFS.
> + </para>
> </answer>
> </qandaentry>
> <qandaentry>
> @@ -1636,10 +1778,11 @@
> url="mailto:fedora-selinux-list@redhat.com">fedora-selinux-list(a)redhat.com</ulink>)
> for discussion.
> </para>
> + <!-- Add policy modules section -->
> + <!-- Add managed policy section -->
> </answer>
> </qandaentry>
> </qandadiv>
> </qandaset>
> </section>
> </article>
> -
>
> --
> Fedora-docs-commits mailing list
> Fedora-docs-commits(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-docs-commits
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Content Services Fedora Documentation Project
http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
18 years, 2 months
Re: selinux-faq/it selinux-faq-it.xml,1.1,1.2
by Karsten Wade
Francesco:
BTW, there is someone working on the FC5 version right now. You may
want to wait until he has the content updated before translating. There
is a freeze date for guides to be translated for FC5, which is 10
February.
- Karsten
On Sat, 2006-02-04 at 12:25 -0500, Francesco Tombolini wrote:
> Author: tombo
>
> Update of /cvs/docs/selinux-faq/it
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11306
>
> Modified Files:
> selinux-faq-it.xml
> Log Message:
> updated path to FEDORA-ENTITIES-IT
>
>
> Index: selinux-faq-it.xml
> ===================================================================
> RCS file: /cvs/docs/selinux-faq/it/selinux-faq-it.xml,v
> retrieving revision 1.1
> retrieving revision 1.2
> diff -u -r1.1 -r1.2
> --- selinux-faq-it.xml 4 Feb 2006 14:45:42 -0000 1.1
> +++ selinux-faq-it.xml 4 Feb 2006 17:25:51 -0000 1.2
> @@ -3,7 +3,7 @@
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
>
> <!-- *************** Bring in Fedora entities *************** -->
> -<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
> +<!ENTITY % FEDORA-ENTITIES-IT SYSTEM "../../docs-common/common/fedora-entities-it.ent">
> %FEDORA-ENTITIES-IT;
>
> <!-- ************** local entities *********** -->
>
> --
> Fedora-docs-commits mailing list
> Fedora-docs-commits(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-docs-commits
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Content Services Fedora Documentation Project
http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
18 years, 2 months
Re: Another question
by Paul W. Frields
On Sat, 2006-01-28 at 02:10 -0500, Francesco Tombolini wrote:
> Il giorno ven, 27/01/2006 alle 10.16 -0800, Paul W. Frields ha scritto:
> > Would it be easier for translators if we
> > moved to using "rpm-info-en.xml", "rpm-info-de.xml", etc.? Comments
> > welcome.
>
> I think it would be more intuitive... than check for comments or tags in
> the xml file...
I am having some second thoughts about this. The lure of i18n'ing this
file just like all others is very strong, but there are some significant
problems it creates which weren't apparent to me at first blush. For
example, RPM changelogs also come out of this file for our packaging
process. Those are normally not translated. This would mean the
confusion created by requiring translators *not* to translate certain
parts of the new rpm-info-*.xml files would be roughly equal to the
situation we had before. Worse, though, it represents a possibility of
mismatch in the RPMs, or at least the appearance of mismatch when
translations are out of sync with the English versions at packaging
time.
More discussion is welcome, with an eye toward rolling some docs out the
door into Fedora Extras at or near FC5t3 release. Tommy normally
catches me when I think up Bad Ideas, so I could be wrong in thinking we
need to change course.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 2 months
Re: selinux-faq rpm-info.xml,1.1,1.2
by Tommy Reynolds
Uttered "Paul W. Frields" (pfrields) <fedora-docs-commits(a)redhat.com>, spake thus:
> Only use version number for doc revisions. This probably needs to be
> policed in the docs-common module. If you use the "make clog" target,
> you get nice prompts for everything, which reduces confusion for some
> people (YMMV).
> - <revision date="Fri Feb 3 2006" number="1.5-1" role="doc">
> + <revision date="Fri Feb 3 2006" number="1.5" role="doc">
This is why I liked my original one-edit,one-revision format w/o
the role attribute ;-)
Cheers
18 years, 2 months
