https://bugzilla.redhat.com/show_bug.cgi?id=982444
Bug ID: 982444
Summary: 1.1 - region and language
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:
Sys admin guide information regarding region and language doesn't specify which
desktop environment is assumed to find the region and language. Also to find
region and language in KDE, you click on the applications launcher, go to
applications --> settings --> system settings, but it's also set as a favourite
by default in F19 so can be found under favourites. Also in KDE, under system
settings, the 'region and language' settings are under 'locale',
'country/region and language'.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982500
Bug ID: 982500
Summary: 2.1 Using the Date and Time Configuration Tool
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:
Gnome settings menu location has changed in 3.8.3:
Activities --> Applications --> Utilities --> Settings
This is not reflected in section 2.1
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1018500
Bug ID: 1018500
Summary: There's no section in the documentation for NFS, after
Fedora 14
Product: Fedora Documentation
Version: devel
Component: storage-administration-guide
Assignee: ddomingo(a)redhat.com
Reporter: david.jones74(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, zach(a)oglesby.co
Description of problem:
There's no section in the documentation for current Fedora versions, about how
to configure NFS. There's SAMBA and FTP, but no NFS.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Search or browse documentation.
2.
3.
Actual results:
Can find scattered information about configuring NFS, but no consolidated
section.
Expected results:
Section for configuring NFS clients and servers.
Additional info:
There are many changes in NFS configuration since Fedora 14. There's a
different init system with different service names, There's also a new firewall
manager. I'm just guess at a lot of the details, and it's pretty frustrating.
Why does SAMBA have a large detailed section, and NFS has nothing? This is
Linux, right? Is the Fedora Project moving to SAMBA as the preferred file
sharing method?
--
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=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=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=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=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-l…
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=979158
Bug ID: 979158
Summary: Windows Virtio Drivers version 1-59 blue screens
windows when you hot add virtio drives
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-guide
Severity: high
Priority: unspecified
Assignee: lbailey(a)redhat.com
Reporter: robert.rupert(a)servicemesh.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lbailey(a)redhat.com
Description of problem:
Windows Blue Screens in KVM when using the latest virtio driver 1-59. When hot
adding scsi drive
Version-Release number of selected component (if applicable):
How reproducible:
fresh install with virtio scsi driver 1-59,=. Then hot add virtio scsi driver
in windows 7, 2008r2 and 2012
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
using the previose version 1-52 works fine
--
You are receiving this mail because:
You are the QA Contact for the bug.