Bug 371981 - Typo in section 18.10 may cause confusion
Summary: Typo in section 18.10 may cause confusion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: doc-Virtualization_Guide
Version: 5.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Christopher Curran
QA Contact: Don Domingo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-08 22:48 UTC by Troels Arvin
Modified: 2009-08-20 04:01 UTC (History)
0 users

Fixed In Version: 5.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-23 05:13:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Troels Arvin 2007-11-08 22:48:29 UTC
At
https://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Virtualization_Guide/ch-virt-selinux-considerations.html
there is a recipie for making a block device (such as a logical volume) ready
for xen guest usage. One of the steps is described as:
semanage fcontext -a -t xen_image _t -f -b /dev/sda2

However, the space between "xen_image" and "_t" makes the command fail, and the
problem is hard to spot.

Comment 1 Christopher Curran 2008-01-29 05:12:14 UTC
This bug has occurred in an older version of the Virtualization Guide. The new
version of the Red Hat Enterprise Linux Virtualization Guide will not be based
on this version. The Virtualization Guide will be rewritten and re-based off the
present Virtualization Cookbook.

We may not have time to fix this bug in previous versions.

Comment 2 Troels Arvin 2008-07-22 07:12:24 UTC
This bug was recently closed, assumingly because the latest version of the
virtualization guide was fixed.
However, the exact same bug exists in the later version of the guide! (This
time, the relevant section is numbered 29.9):
https://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Virtualization/sect-Virtualization-How_To_troubleshoot_Red_Hat_Virtualization-SELinux_considerations.html

Please: It's a one-character fix, which can really save time people who aren't
proficient in SELinux.

Comment 3 Christopher Curran 2008-11-07 01:37:59 UTC
Turns out this isn't the right way to manage SELinux contexts with virtualization. The entire section is being rewritten. Thank you for your diligence in spotting the bug, twice :)


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