January 2015 - docs-qa - Fedora Mailing-Lists

[Bug 1098298] New: Some problems in "Chapter 11. Storage pools"

by Red Hat Bugzilla

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_Adminis... 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.

8 years, 4 months

1
1
0 / 0

[Bug 990252] New: incomplete index for Virtualization Administration Guide

by Red Hat Bugzilla

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_Adminis... 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.

8 years, 4 months

1
1
0 / 0

[Bug 1180524] New: confining users section unclear

by Red Hat Bugzilla

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.

8 years, 6 months

1
3
0 / 0

[Bug 1180142] New: issues in the introduction of selinux-user-guide

by Red Hat Bugzilla

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.

8 years, 6 months

1
2
0 / 0

[Bug 1008149] New: Contraficting info about the need of shared storage for storing guest images to be migrated

by Red Hat Bugzilla

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... 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.

8 years, 7 months

1
2
0 / 0

[Bug 1180202] New: Overlap with uefi-secure-boot-guide

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1180202 Bug ID: 1180202 Summary: Overlap with uefi-secure-boot-guide Product: Fedora Documentation Version: devel Component: multiboot-guide Assignee: chris.roberts(a)croberts.org Reporter: fweimer(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: chris.roberts(a)croberts.org With the recent updates, there is now some overlap with the UEFI Secure Boot guide. I'm not sure the current state of Secure Boot is useful for non-dual-boot systems, considering the feature loss and the lack of additional security due to buggy kernels and permissive signed bootloaders from other vendors. Perhaps merging the UEFI Secure Boot guide into the multiboot guide makes sense? -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 7 months

1
1
0 / 0

[Bug 1086052] New: Include a section on using the Live media for rescue

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1086052 Bug ID: 1086052 Summary: Include a section on using the Live media for rescue Product: Fedora Documentation Version: devel Component: install-guide Assignee: pbokoc(a)redhat.com Reporter: sanjay.ankur(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: The install guide contains a section that documents how one can use the rescue mode off the dvd. It doesn't document how one can use the live media for simple rescue operations. The most common use case is when people install Window after installing Fedora off a live media. They lose grub, and they can't figure out how to use the live media to reinstall it. There are a couple of blog posts that document it. For example: http://thecreationist.expertscolumn.com/article/recover-grub-using-fedora... It would maybe be a good idea to have a section in docs that provides hints on how the live cd can be used for basic rescue operations. Thanks, Warm regards, Ankur -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 7 months

1
5
0 / 0

[Bug 1162233] New: http://beeblebrox.org/ appears to be dead

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1162233 Bug ID: 1162233 Summary: http://beeblebrox.org/ appears to be dead Product: Fedora Documentation Version: devel Component: readme-burning-isos Assignee: zach(a)oglesby.co Reporter: rbiba(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: stickster(a)gmail.com, zach(a)oglesby.co Description of problem: HashTab can't be downloaded from http://beeblebrox.org/ because the page fails to load. It seems the site has been decommissioned. The software is now available from https://itunes.apple.com/us/app/hashtab/id517065482 or http://implbits.com/products/hashtab/. Note that implbits.com is also the first Google search result for beeblebrox.org or hashtab. -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 7 months

1
3
0 / 0

[Bug 982906] New: 7.3.2. Establishing a Wireless Connection

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=982906 Bug ID: 982906 Summary: 7.3.2. Establishing a Wireless Connection Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: unspecified Priority: unspecified Assignee: jhradile(a)redhat.com Reporter: im_dracula(a)hotmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com Description of problem: Section 7.3.2 under the heading: 'Saving Your New (or Modified) Connection and Making Further Configurations' it states: "You can further configure an existing connection by selecting it in the Network Connections window and clicking Edit to return to the Editing dialog." This could be clarified by stating that network connections can be found under: activities --> applications --> sundry --> network connections -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 7 months

1
4
0 / 0

[Bug 1152883] New: Local replication of Product installation trees

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1152883 Bug ID: 1152883 Summary: Local replication of Product installation trees Product: Fedora Documentation Version: devel Component: install-guide Assignee: pbokoc(a)redhat.com Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co It doesn't look like there will be a DVD image, the traditional source in our instructions for site-provided installation repos. Consider conjuring up a procedure explaining how an administrator could obtain a mirror of the installation tree for each Product (whatever anaconda is pointed at for the netinstalls) without having to pull in the entire repo. -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 7 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa January 2015