https://bugzilla.redhat.com/show_bug.cgi?id=1146950
Bug ID: 1146950
Summary: Test Bug
Product: Fedora Documentation
Version: devel
Component: system-administrator's-reference-guide
Assignee: jhradile(a)redhat.com
Reporter: jhradile(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
This is just a test bug. Please, feel free to ignore it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1098298
Bug ID: 1098298
Summary: Some problems in "Chapter 11. Storage pools"
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Assignee: lnovich(a)redhat.com
Reporter: bughunt(a)gluino.name
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
In:
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
I want to create storage pools using virsh.
Corrections:
Create the storage pool definition
- - - - - - - - - - - - - - - - - -
"The path to a file system directory for storing guest image files. If this
directory does not exist, virsh will create it."
This is incorrect. "You have to create it afterwards using virsh" is correct.
Create the local directory
- - - - - - - - - - - - - -
I create the directory under "/home"
Documentation shows that "ls -la /guest_images" shows the directory having
permissions "700". This is incorrect, the permissions are "755" (at least for
me)
Improvement: Maybe one should also add the output of
ls --lcontext -la /guest_images/
drwxr-xr-x. 2 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 ..
The wrong permissions error is repeated under "6. Verify the storage pool
configuration":
ls -la /guest_images/
total 8
drwxr-xr-x. 2 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 root root 4096 May 15 18:50 ..
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1068889
Bug ID: 1068889
Summary: Remove references to version numbers in package
documentation directories
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: sclark(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Created attachment 866496
--> https://bugzilla.redhat.com/attachment.cgi?id=866496&action=edit
The attached archive contains patches to implement this change
Following instructions in
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs remove the version
number from the directory name for all references to any package documentation
directory in /usr/share/doc , leaving just the package's name.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=990252
Bug ID: 990252
Summary: incomplete index for Virtualization Administration
Guide
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Assignee: lnovich(a)redhat.com
Reporter: stephent98(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Description of problem:
The index for the Virtualization Administration Guide has only three entries.
Specifically, I was trying to find information on host memory requirements.
Version-Release number of selected component (if applicable):
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1214964
Bug ID: 1214964
Summary: Hold Option to select boot source on Mac hardware
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: beland(a)alum.mit.edu
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
I'm not sure where to find the draft of the Fedora 22 Installation Guide, but I
went through the Fedora 21 version steps in order to install the beta today.
One suggestion for the new version of this page:
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/chap-…
I recommend adding something like "On Mac hardware, hold down Option to enter
the boot media selection menu." Mac hardware with Intel chips is rather common
now, so I hope a significant number of people would be aided by that addition.
I spent several hours trying to figure that out the first time I put Fedora on
a Macbook.
Thanks!
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180524
Bug ID: 1180524
Summary: confining users section unclear
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
The section 6 (confining users) in Fedora 21 documentation of SELinux is very
unclear.
1. What does confining mean actually? How are they confined? What capabilities
these user lose? These are crucial information, never discussed in the text.
2. In fedora with "seinfo -u" I see several selinux users. These, along with
the limitation each has, are never discussed.
3. "6.5. xguest: Kiosk Mode": I miss some technical info on the restrictions of
the xguest account. What that user can't do and what can it do. Without that
information the text could just say, trust us we've done everything for you
(nothing bad with it, except that in technical documentation you expect more).
4. I miss a "confining a server process/app" section. This is a very common
usage for selinux but no information is provided about that at all. Can I put
some server in a confined state, as the documentation discusses with the user?
Do we provide some preconfigured selinux users, roles, types for that purpose?
What about the sandbox tool we ship? That would be the information I'd expect
from such a section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180142
Bug ID: 1180142
Summary: issues in the introduction of selinux-user-guide
Product: Fedora Documentation
Version: devel
Component: selinux-user-guide
Assignee: mprpic(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
[Originally sent to authors of the document]
I was trying to understand selinux using that guide, and had quite some issues
in the introduction. I send you my issues in the hope they will help to improve
the text.
-------------------------------------------------------------
Chapter 2. Introduction to SELinux:
I couldn't really understand what is selinux based on this section. It
says it is mandatory access control mechanism, and then it goes into
length explaining the 'Discretionary Access Control (DAC) system' used
typically in Linux. That's nice if you already know what selinux is,
because you can see the difference, but the opposite what I'd expect at
the moment since I have no idea what selinux is.
My suggestion would be to add the description I saw in
https://www.imperialviolet.org/2009/07/14/selinux.html
"SELinux is fundamentally about answering questions of the form “May x
do y to z?” and enforcing the result (x is subject, z is object) ...
The action (y) boils down to a class and a permission. Each class can
have up to 32 permissions (because they are stored as a bitmask in a
32-bit int). Examples of classes are FILE, TCP_SOCKET and X_EVENT. For
the FILE class, some examples of permissions are READ, WRITE, LOCK etc."
At least for me that was all the information that I needed to understand
what I can do with SELinux. A complete pictures may require to go into a
bit more length with explaining what can be a subject, object and
actions. Then mentioning about MAC and explaining it in addition to DAC
will be more natural IMO.
---------------------------------------------------------------------
2.1. Benefits of running SELinux
This is section vaguely defines domain. I reached "3.1. Domain
Transitions" and didn't know what a domain was.
Maybe add a definition of domain in 3.1 or earlier in the introduction.
---------------------------------------------------------------------
Chapter 3. SELinux Contexts
level:
It explains that in Fedora there is a single sensitivity and multiple
categories. I miss what are these categories intended to be used to? An
example with two different categories would be helpful.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008149
Bug ID: 1008149
Summary: Contraficting info about the need of shared storage
for storing guest images to be migrated
Product: Fedora Documentation
Version: devel
Component: virtualization-getting-started-guide
Assignee: dayleparker(a)redhat.com
Reporter: jrodrigosm(a)yahoo.es
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org
Hi,
In the Fedora 19 "Virtualization Getting Started Guide", section 2.2 ("What is
migration?"), URL
http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting_S…
In the paragraph right before the 2.2.1 title, it is stated that "In Fedora 19,
shared storage is not necessary for storing guest images to be migrated. With
live storage migration [...]".
But in the last paragraph of the page, right before the note, it is stated that
"Shared, networked storage must be used for storing guest images to be
migrated. Without shared storage, migration is not possible."
These two statements seem contradictory to me. I just started learning about
virtualization, so I am unable to propose an alternative. But I do think some
clarification is needed.
Thanks,
Rodrigo
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206351
Bug ID: 1206351
Summary: dnf conversion tracker bug
Product: Fedora Documentation
Version: devel
Component: docs-requests
Assignee: nobody(a)fedoraproject.org
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Additional information:
Tracker for individual documentation blockers.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206805
Bug ID: 1206805
Summary: convert yum commands to dnf commands - System
Administrators Guide
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Sys…
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.