Bug 223810 - SELinux: Deployment_Guide still referencing to system-config-securitylevel instead of -selinux
Summary: SELinux: Deployment_Guide still referencing to system-config-securitylevel in...
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: Deployment_Guide   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: David O'Brien
QA Contact:
Keywords: Documentation
Depends On: 223823
Blocks: 214350
TreeView+ depends on / blocked
Reported: 2007-01-22 16:20 UTC by Daniel Riek
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version: RC2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-08 06:47:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Daniel Riek 2007-01-22 16:20:12 UTC
In the Security And Authentication section the Deployment Guide still refers to
system-config-securityleve for setting SELinux Booleans although that
functionality has been moved to system-config-sellinux!

Comment 5 Michael Hideo 2007-01-24 10:56:33 UTC
[mhideo@engineering ~]$ brew latest-pkg dist-5E-qu-candidate Deployment_Guide
Build                                     Tag                   Built by
----------------------------------------  -------------------- 
----------------Deployment_Guide-5.0.0-18                 dist-5E-qu-candidate 

Comment 7 Michael Hideo 2007-01-31 13:40:40 UTC
Fix was performed in English. However, this caused English to appear in the
other languages.

This version contains the fallback plan.

[mhideo@engineering Deployment_Guide]$ make brew_report
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
Deployment_Guide-5.0.0-19                 dist-5E-qu-candidate  mhideo

If there is another respin, please include. If not, will issue as erratta.

Comment 8 David O'Brien 2007-02-01 01:06:38 UTC
Mike, what's the status of this?  Do I need to action it at all?

Comment 10 Michael Hideo 2007-02-08 06:36:06 UTC
Fix is in, resolving.

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