[Bug 987664] New: Guide intro references documnetnation that is not available for Fedora
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=987664
Bug ID: 987664
Summary: Guide intro references documnetnation that is not
available for Fedora
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Created attachment 777453
--> https://bugzilla.redhat.com/attachment.cgi?id=777453&action=edit
Patch commenting out unavailable guides.
The introduction to the Virtualization Deployment and Administration Guide
references related documentation that has been developed for RHEL/RHEV but is
not maintained for Fedora. The attached patch comments out those sections so
that only guides that are currently maintained for Fedora will be referenced.
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 5 months
[Bug 831619] New: Inaccuracy in Fedora 17 “Power Management Guide”
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831619
Bug ID: 831619
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: low
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Inaccuracy in Fedora 17 “Power Management Guide”
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: vaskodd(a)yahoo.com
Type: Bug
Documentation: ---
Hardware: x86_64
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Created attachment 591487
--> https://bugzilla.redhat.com/attachment.cgi?id=591487&action=edit
The problem description in .pdf format - easy to follow
Hi,
First I want to notice I am a Linux newbie and my English is not that good.
Now straight to the point! (The same description is available in the attached
pdf file and is more easy to follow)
I've noticed some inaccuracy in Fedora 17 “Power Management Guide” (Fedora
Documentation), particularly in section “2.5. Tuned and ktune” including
“2.5.1. The tuned.conf file” and “2.5.2 Tuned-adm”.
In section “2.5. Tuned and ktune” right bellow the “yum install tuned”
command it's written:
“Installing the tuned package also sets up a sample configuration file at
/etc/tuned.conf and activates the default profile.”
There is no such file in /etc. I found a /etc/tuned/active_profile file
containing the following: “/usr/lib/tuned/balanced/tuned.conf”. I'm not sure
this file (/etc/tuned.conf) is missing only on my system or it has a new
location by default for each profile - /usr/lib/tuned/profileX/tuned.conf.
Bellow in this section and in “2.5.1. The tuned.conf file” it is pointed again
that the default location for the tuned.conf file is /etc/tuned.conf.
In section “2.5.2 Tuned-adm” in the first paragraph it is written “Fedora 17
includes a number of predefined profiles for typical use cases...”. Just to be
precise it is good to be mentioned that these profiles are not installed by
default with “yum install tuned” command (tuned-2.0.1-1.fc17 package), but can
be found in tuned-profile-compat-2.0.1-1.fc17 package (I found it in Gnome
Package Manager).
Another thing in this section is in the last third of the page where it is
written:
“All the profiles are stored in separate subdirectories under
/etc/tune-profiles. So /etc/tune-profiles/desktop-powersave contains all the
necessary files and settings for that profile. Each of these directories
contains up to four files:”
There /etc/tune-profiles directory does not exist. Instead I found the profiles
stored in /run/lib/tuned.
Each directory for the corresponding profile typically contains only 2 files -
script.sh and tuned.conf. The presence of script.sh is not mentioned in the
directories contains description – it is mentioned ktune.sh insetad.
That's all. I hope this is helpful.
Best regards
Vasil Draganov
Fedora 17 3.4.0-1.fc17.x86_64
P.S. “Power Management Guide” is great. It's really useful. The moment i run
tuned service i noticed how quieter my laptop became (less heat – less fan
needed :) ). The first thing I noticed about new Fedora installation was that
the laptop was noisier in comparison to Win7 (I dual-boot with Win7). Tuned
just fixed that :)
Many thanks to the creators of Fedora Documentation!!!
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 6 months
[Bug 1011418] New: alias bondN bonding not required for bonding configuration
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1011418
Bug ID: 1011418
Summary: alias bondN bonding not required for bonding
configuration
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: john.haxby(a)oracle.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Description of problem:
In the F18 System Administrators Guide (and shouldn't that have an apostrophe
after the 's'?), §8.2.3 it says:
-----------------------
For a channel bonding interface to be valid, the kernel module must be loaded.
To ensure that the module is loaded when the channel bonding interface is
brought up, create a new file as root named bonding.conf in the
/etc/modprobe.d/ directory. Note that you can name this file anything you like
as long as it ends with a .conf extension. Insert the following line in this
new file:
alias bondN bonding
Replace N with the interface number, such as 0. For each configured channel
bonding interface, there must be a corresponding entry in your new
/etc/modprobe.d/bonding.conf file.
------------------------
This is not true. The network scripts in /etc/sysconfig/network-scripts
define the function install_bonding_driver which is called whenever a bonding
slave or master is detected.
Version-Release number of selected component (if applicable): F18
How reproducible: Always
Steps to Reproduce:
1. Configure a bond
2. Miss out the step that adds "alias bondN bonding" to a modprobe conf file
3. Notice that bonding actually works (NetworkManager notwithstanding)
Actual results: works as expected when ignoring the documentation
Expected results: works as expected when not ignoring the documentation
Additional info:
The install_bonding_driver has been around for a while, but the final piece of
code to make it reliable comes from, I think,
* Mon Aug 15 2011 Petr Lautrbach <plautrba(a)redhat.com> 9.03.24-1
...
- make sure the bond exists when we bring up the slaves. (#694501)
(commit id 3de0e06afda2e572d0952941498446fdda7f3f42)
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 7 months
[Bug 1021132] New: Shared Certificate Tools
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1021132
Bug ID: 1021132
Summary: Shared Certificate Tools
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: herrold(a)owlriver.com, jreznik(a)redhat.com,
relnotes(a)fedoraproject.org, stefw(a)redhat.com,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998546
+++ This bug was initially created as a clone of Bug #998546 +++
This is a tracking bug for Change: Shared Certificate Tools
For more details, see:
http://fedoraproject.org//wiki/Changes/SharedCertificateTools
Fedora now has infrastructure for sharing system trusted certificates between
the various crypto libraries.
--- Additional comment from Stef Walter on 2013-08-29 08:32:51 EDT ---
Substantiably testable using p11-kit-0.19.4 which is in Fedora 20.
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:46:13 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
----------------
Tracking bug for representation in the Release Notes.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=998546
[Bug 998546] Shared Certificate Tools
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 7 months
[Bug 929426] firewalld: forward chain
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=929426
--- Comment #5 from Alexander Seleznev <SeleznevRU(a)gmail.com> ---
(In reply to Frank Ansari from comment #4)
> Only solution so far is to add an iptables rule doing something like this:
>
> ip6tables -I FORWARD 7 -p tcp --dport 22 -j ACCEPT;
>
> Is thre no way doing this with firewall-cmd?
Why you don't use this command?
firewall-cmd --direct --add-rule ipv6 filter FORWARD 1 -p tcp --dport 22 -j
ACCEPT
Also, under Fedora 20 the "--permanent" key works fine for me.
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 7 months
[Bug 1017078] New: Docimentation in fb2 format
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1017078
Bug ID: 1017078
Summary: Docimentation in fb2 format
Product: Fedora Documentation
Version: devel
Component: about-fedora
Severity: medium
Assignee: stickster(a)gmail.com
Reporter: arthur-fayzullin(a)yandex.ru
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: stickster(a)gmail.com, zach(a)oglesby.co
Description of problem:
The only avaible formats for documentation are:
* html
* html-single
* epub
* pdf
That is good :) but most of these formats are good for reading from desktop
monitor. But I have got problems with eyes. So the only variant is e-book
readers with e-paper. May be epub is good variant, but I did not meet any
reader that works fine with it :(
So, if it is possible, please, add for example fb2-format for documentation!
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.
10 years, 7 months
[Bug 1014447] New: Lilypond's vim syntax files in old vim73 directory
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1014447
Bug ID: 1014447
Summary: Lilypond's vim syntax files in old vim73 directory
Product: Fedora Documentation
Version: devel
Component: about-fedora
Severity: medium
Assignee: stickster(a)gmail.com
Reporter: kevin(a)imbedwithlinux.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: stickster(a)gmail.com, zach(a)oglesby.co
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101
Firefox/23.0 SeaMonkey/2.20
Build Identifier:
after installing Fedora 19 and then Lilypond 2.16.2 syntax highlighting does
not work. Lilypond syntax files are found in the now old vim73 directory.
Reproducible: Always
Steps to Reproduce:
1. Install Fedora 19 with Vim
2. Install Lilypond
3.
Actual Results:
No syntax highlighting in vim of lilypond files.
[kevin@kevinburo ~]$ rpm -ql lilypond | grep vim
/usr/share/vim/vim73
/usr/share/vim/vim73/compiler
/usr/share/vim/vim73/compiler/lilypond.vim
/usr/share/vim/vim73/ftdetect
/usr/share/vim/vim73/ftdetect/lilypond.vim
/usr/share/vim/vim73/ftplugin
/usr/share/vim/vim73/ftplugin/lilypond.vim
/usr/share/vim/vim73/indent
/usr/share/vim/vim73/indent/lilypond.vim
/usr/share/vim/vim73/syntax
/usr/share/vim/vim73/syntax/lilypond-words
/usr/share/vim/vim73/syntax/lilypond-words.vim
/usr/share/vim/vim73/syntax/lilypond.vim
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 7 months