Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 129709 - SELinux FAQ for Fedora Core 2 ready for posting to Fedora docs page
SELinux FAQ for Fedora Core 2 ready for posting to Fedora docs page
Product: Fedora Documentation
Classification: Fedora
Component: selinux-faq (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tammy Fox
Tammy Fox
: FutureFeature
Depends On:
Blocks: fedora-docs-ready
  Show dependency treegraph
Reported: 2004-08-11 18:43 EDT by Karsten Wade
Modified: 2007-04-18 13:10 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-13 12:22:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karsten Wade 2004-08-11 18:43:43 EDT
Description of problem:

The SELinux FAQ for Fedora Core 2 is ready for posting on the proper
Fedora docs pages, http://fedora.redhat.com/docs.  This document
should be grouped on that page with the version 2 documents, as it is
specifically different from the version 3 document.

I'm comfortable keeping the fast-moving, test-based FAQ at my people
pages, but that is obviously not the optimal solution.  In the past,
we mainly wanted speed and flexibility, which we go with the people
page.  Soon I'd like to place a redirect at that page (or something)
that points to the proper Fedora docs page.

Version-Release number of selected component (if applicable):

This is available in one of two locations:


CVS -> fedora-docs/selinux-faq

I will be filely a separate ticket asking to have this forked to
selinux-faq-FC2 (???), then I can begin to commit the FC3test1 code to
selinux-faq as the head.
Comment 1 Tammy Fox 2004-08-13 12:22:41 EDT
Great! This should appear on the website within the hour.

Note You need to log in before you can comment on or make changes to this bug.