From Fedora Project Wiki

No edit summary
No edit summary
Line 28: Line 28:
* http://searchenterpriselinux.techtarget.com/columnItem/0,294698,sid39_gci1253747,00.html Five ways SELinux may surprise you
* http://searchenterpriselinux.techtarget.com/columnItem/0,294698,sid39_gci1253747,00.html Five ways SELinux may surprise you
* http://www.tresys.com/selinux
* http://www.tresys.com/selinux
* http://www.nsa.gov/selinux/
* http://www.nsa.gov/research/selinux/
* [[Selinux_grammar| Grammar for policy language]]
* [[Selinux_grammar| Grammar for policy language]]


If you want to work on formal documentation, you can use the [[Docs/Drafts/SELinux| Docs/Drafts/SELinux]]  namespace.  When you are done editing the draft, it can migrate to [[Docs/SELinux| Docs/SELinux]] .  Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace
If you want to work on formal documentation, you can use the [[Docs/Drafts/SELinux| Docs/Drafts/SELinux]]  namespace.  When you are done editing the draft, it can migrate to [[Docs/SELinux| Docs/SELinux]] .  Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace

Revision as of 22:25, 8 June 2009

Fedora SELinux Project Pages

Topics

Documentation

If you want to work on formal documentation, you can use the Docs/Drafts/SELinux namespace. When you are done editing the draft, it can migrate to Docs/SELinux . Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace