https://bugzilla.redhat.com/show_bug.cgi?id=1021605
Bug ID: 1021605
Summary: No Default Syslog
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: brentrbrian(a)gmail.com, johannbg(a)gmail.com,
jreznik(a)redhat.com, kvolny(a)redhat.com,
mattdm(a)redhat.com, pbokoc(a)redhat.com,
yjcoshc(a)gmail.com, zach(a)oglesby.co, zbyszek(a)in.waw.pl
Depends On: 967521, 998573
Blocks: 1001355, 1001356
+++ This bug was initially created as a clone of Bug #998573 +++
This is a tracking bug for Change: No Default Syslog
For more details, see: http://fedoraproject.org//wiki/Changes/NoDefaultSyslog
No longer install a traditional syslog service by default. (Specifically,
remove rsyslog from the @core or @standard groups in comps.)
--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2013-10-08 15:22:54
EDT ---
http://cgit.freedesktop.org/systemd/systemd/commit/?id=2b8f6883a17b
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:44:57 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
--- Additional comment from Matthew Miller on 2013-10-15 14:38:53 EDT ---
The basic change to implement this went in, although quite a few packages still
bring in rsyslogd as a dependency. I think this feature is fine as it is, and
we'll detangle that as part of making separate, targeted Fedora products.
--- Additional comment from Jaroslav Reznik on 2013-10-16 06:56:42 EDT ---
Ok, thanks, moving to ON_QA.
--- Additional comment from Karel Volný on 2013-10-21 08:27:14 EDT ---
just FTR, journal brings bug #967521 - how could we switch to this nonsense if
that one is still unresolved?
well, in fact, how could we even have this activated by default, maybe I'm just
out of luck googling, but I see no approval for journal to be used?
--- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 08:59:21 EDT
---
Just an FYI This feature is not as simple as no default syslog. We need to fix
the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
distribution, come up with virtual provide ( to sub package or not to sub
package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
proposal on how to do so has been stuck with FPC for 2 years now and until that
has been done and fixed this feature can never be considered 100% complete...
--- Additional comment from Matthew Miller on 2013-10-21 09:10:10 EDT ---
(In reply to Jóhann B. Guðmundsson from comment #6)
> Just an FYI This feature is not as simple as no default syslog. We need to
> fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
> distribution, come up with virtual provide ( to sub package or not to sub
> package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
> proposal on how to do so has been stuck with FPC for 2 years now and until
> that has been done and fixed this feature can never be considered 100%
> complete...
I agree that that's the target, and also that it will continue to be
slow-moving. This feature was intentionally meant to slice off and accomplish a
small portion of that.
--- Additional comment from Brent R Brian on 2013-10-21 09:42:27 EDT ---
My comments are not intended to be a remedy, fix, enoursement of a fix/remedy
or anything other than a "data point".
If you guys need a "lab rat", let me know.
B
--- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 11:10:22 EDT
---
(In reply to Matthew Miller from comment #7)
> (In reply to Jóhann B. Guðmundsson from comment #6)
> > Just an FYI This feature is not as simple as no default syslog. We need to
> > fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
> > distribution, come up with virtual provide ( to sub package or not to sub
> > package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
> > proposal on how to do so has been stuck with FPC for 2 years now and until
> > that has been done and fixed this feature can never be considered 100%
> > complete...
>
> I agree that that's the target, and also that it will continue to be
> slow-moving. This feature was intentionally meant to slice off and
> accomplish a small portion of that.
That is one of the core problem people really as in that feature and related
work are just implemented up to the point it serves the feature requester need
( and is labelled as 100% feature completed ) as opposed to the actual work
required to implement properly into the distribution.
What we need to do is to keep distribute wide changes as these in a separated
branch and switch all the components at the same time when the feature actually
is 100% feature complete
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=967521
[Bug 967521] /var/log/journal breaks system startup
https://bugzilla.redhat.com/show_bug.cgi?id=998573
[Bug 998573] No Default Syslog
https://bugzilla.redhat.com/show_bug.cgi?id=1001355
[Bug 1001355] No Default Syslog
https://bugzilla.redhat.com/show_bug.cgi?id=1001356
[Bug 1001356] No Default Syslog
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1175759
Bug ID: 1175759
Summary: Checksum validation in PowerShell is wrong
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: gliverma(a)westga.edu
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
I tried to use the info at
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-…
and found that the commands did not work due to missing quotes and case
sensitivity.
Version-Release number of selected component (if applicable):
Fedora 21
How reproducible:
Every time for me.
Steps to Reproduce:
1. Download ISO
2. Download checksum file
3. Use code on
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-…
Actual results:
PS D:\Downloads> $image = "Fedora-Live-Workstation-x86_64-21-5.iso"
PS D:\Downloads> $checksum_file = "Fedora-Workstation-21-x86_64-CHECKSUM.md5"
PS D:\Downloads> $sha256 = New-Object -TypeName
System.Security.Cryptography.sha256CryptoSer
viceProvider
PS D:\Downloads> $exepected_checksum = ((Get-Content $checksum_file |
Select-String -Pattern
$image) -split " ")[0]
PS D:\Downloads> $download_checksum =
[System.BitConverter]::ToString($sha256.ComputeHash([S
ystem.IO.File]::ReadAllBytes($PWD\$image)))
At line:1 char:109
+ ... adAllBytes($PWD\$image)))
+ ~
Missing ')' in method call.
At line:1 char:109
+ ... adAllBytes($PWD\$image)))
+ ~~~~~~~
Unexpected token '\$image' in expression or statement.
At line:1 char:116
+ ... tes($PWD\$image)))
+ ~
Unexpected token ')' in expression or statement.
At line:1 char:117
+ ... es($PWD\$image)))
+ ~
Unexpected token ')' in expression or statement.
At line:1 char:118
+ ... s($PWD\$image)))
+ ~
Unexpected token ')' in expression or statement.
+ CategoryInfo : ParserError: (:) [],
ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingEndParenthesisInMethodCall
Expected results:
No errors in console
Additional info:
I fixed the code and made the output more readable. Below is what I think
should be posted on that page of the docs:
$image = "Fedora-Live-Workstation-x86_64-21-5.iso"
$checksum_file = "Fedora-Workstation-21-x86_64-CHECKSUM"
$sha256 = New-Object -TypeName
System.Security.Cryptography.sha256CryptoServiceProvider
$expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern
$image) -split " ")[0].ToLower()
$download_checksum =
[System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes("$PWD\$image"))).ToLower()
-replace '-', ''
if ( "$download_checksum" -eq "$expected_checksum" ) {
echo "Checksum test passed!"
} else {
echo "Checksum test failed."
}
echo "Download Checksum: $download_checksum"
echo "Expected Checksum: $expected_checksum"
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008207
Bug ID: 1008207
Summary: FreeIPA OTP UI
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nathaniel(a)natemccallum.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, tbabej(a)redhat.com,
zach(a)oglesby.co
Depends On: 998526
+++ This bug was initially created as a clone of Bug #998526 +++
This is a tracking bug for Change: FreeIPA OTP UI
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI
FreeIPA will gain a user interface for managing users' OTP tokens.
--- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
------------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008206
Bug ID: 1008206
Summary: FreeIPA OTP UI
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: jreznik(a)redhat.com, nathaniel(a)natemccallum.com,
relnotes(a)fedoraproject.org, tbabej(a)redhat.com,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998526
+++ This bug was initially created as a clone of Bug #998526 +++
This is a tracking bug for Change: FreeIPA OTP UI
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI
FreeIPA will gain a user interface for managing users' OTP tokens.
--- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
----------------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h…
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008191
Bug ID: 1008191
Summary: Apache OpenOffice
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998511
+++ This bug was initially created as a clone of Bug #998511 +++
This is a tracking bug for Change: Apache OpenOffice
For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice
Add Apache OpenOffice, the free productivity suite, to Fedora.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008190
Bug ID: 1008190
Summary: Apache OpenOffice
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: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998511
+++ This bug was initially created as a clone of Bug #998511 +++
This is a tracking bug for Change: Apache OpenOffice
For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice
Add Apache OpenOffice, the free productivity suite, to Fedora.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021570
Bug ID: 1021570
Summary: OS Installer Support for LVM Thin Provisioning
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlehman(a)redhat.com, jreznik(a)redhat.com,
pbokoc(a)redhat.com, zach(a)oglesby.co
Depends On: 998527
Blocks: 998532, 1008211, 1008212
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:45:46 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
--- Additional comment from Jaroslav Reznik on 2013-10-21 10:13:43 EDT ---
I see 958464 in POST state but probably without profiles. Is it acceptable to
consider this Change completed without it or not? FESCo asked me to finish
review of Changes this week. Thanks.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=998527
[Bug 998527] OS Installer Support for LVM Thin Provisioning
https://bugzilla.redhat.com/show_bug.cgi?id=998532
[Bug 998532] Snapshot and Rollback Tool
https://bugzilla.redhat.com/show_bug.cgi?id=1008211
[Bug 1008211] OS Installer Support for LVM Thin Provisioning
https://bugzilla.redhat.com/show_bug.cgi?id=1008212
[Bug 1008212] OS Installer Support for LVM Thin Provisioning
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008211
Bug ID: 1008211
Summary: OS Installer Support for LVM Thin Provisioning
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: dlehman(a)redhat.com, jreznik(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 998527
Blocks: 998532
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html
Please document this Change in the Release Notes
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008212
Bug ID: 1008212
Summary: OS Installer Support for LVM Thin Provisioning
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlehman(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998527
Blocks: 998532
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1162045
Bug ID: 1162045
Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep
State
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Severity: low
Assignee: yruseva(a)redhat.com
Reporter: redzilla.coralnut(a)xoxy.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
F20 Power Management Guide does not address the hooks into the sleep system
provided by systemd. Ever since p,m-utils was deprecated there have been no
Fedora/RHAT resources available that discuss how to utilize the hooks into the
sleep system to prevent entry into the sleep state.
Example: in the era of pm-utils (going back to what, F15?) one could write
scripts to suppress the transition to S3 if a desirable network connection were
established that should not be interrupted. All that was required was to place
the script in /etc/pm/sleep.d/ and have it issue a non-zero exit code if sleep
should be suppressed. When the goto sleep process prepared for sleep by
executing the script, the script could deliver a non-zero exit code and prevent
entry into the sleep state.
Now that pm-utils has been deprecated and replaced with systemd, Fedora now
ignores any/all scripts in /etc/pm/*. That isn't a problem. What *IS* a
problem, though, is that for the past 5 releases of Fedora, the Power
Management Guide has completely ignored the topic of how to use custom scripts
to prevent entry into the sleep state. As a result, our only options are to
look for help and examples in other distributions.
Version-Release number of selected component (if applicable):
F20, F21
How reproducible:
N/A. The documentation doesn't address the problem.
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=1080006
Bug ID: 1080006
Summary: Incorrect command for multi-core power saving
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
In section 4.2
[https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guide/…]
there's a list of commands that can be executed to save some power. The
command listed for "enable multi-core power-saving (part of the
laptop-battery-powersave profile)" is a duplicate of the previous command and
is therefore incorrect.
Version-Release number of selected component (if applicable):
1.1-0
The command is given as:
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
Which is the command for enabling audio codec power saving, not for enabling
multi-core power saving.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1036886
Bug ID: 1036886
Summary: Incorrect command to start tuned at boot in Power
Management Guide
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: stevenhrosenberg(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
On this page --
http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s…
-- the command to start the tuned utility at boot has two words transposed:
Specifically right here --
http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s…:
How it reads:
To enable tuned to start every time the machine boots, type the following
command:
systemctl tuned enable
But it should be:
To enable tuned to start every time the machine boots, type the following
command:
systemctl enable tuned
As you can see, the last two words of the command need to be transposed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008872
Bug ID: 1008872
Summary: CPUfreq documentation for F19 lacks information on the
new intel_pstate driver and its governors
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: mail2benny(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
https://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/…
only documents governors for the acpi-cpufreq driver but not for the new
intel_pstate driver.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=973950
Bug ID: 973950
Summary: Type in Chapter 1.2
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Severity: low
Priority: unspecified
Assignee: r.landmann(a)redhat.com
Reporter: swierckx(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com,
r.landmann(a)redhat.com
Description of problem:
In chapter 1.2 of the power management guide there is a type in the fedora
version mentioned
"The kernel used in releases of Fedora prior to Fedora 8 used a periodic timer
for each CPU. This timer prevents the CPU from truly going idle ..."
should probably be
""The kernel used in releases of Fedora prior to Fedora 18 used a periodic
timer for each CPU. This timer prevents the CPU from truly going idle ...""
I deducted this from the sentence a little further where it is mentioned that
only from Fedora 18 the idle CPU state is tickles
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=842190
Bug ID: 842190
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Cpufreq governor
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: h479627(a)rtrtr.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Description of problem:
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.
https://bugzilla.redhat.com/show_bug.cgi?id=832179
Bug ID: 832179
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: medium
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Power management guide is wrong for frequency scaling
in Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: jnm11(a)cam.ac.uk
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Description of problem:
Power management guide is wrong
https://docs.fedoraproject.org/en-US/Fedora/17/html/Power_Management_Guide/…
Version-Release number of selected component (if applicable):
Fedora 17
the location of the cpufreq directory is misspecified
it is
/lib/modules/3.4.0-1.fc17.x86_64/kernel/drivers/cpufreq
There are no modules
acpi-cpufreq or p4-clockmod available
is acpi-cpufreq directly compiled in.
the cpuspeed package is mentioned for the userspace governor but no package
exists in fedora 17.
I have been completely unable to figure out the following use case.
My laptop overheats and powers off if the cpu load is high for too long.
There should be a cpu governor or userspace daemon that reduces frequency when
the temperature gets too high.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=915751
Bug ID: 915751
Summary: Remove BuildArch: noarch from the meta package example
Product: Fedora Documentation
Version: devel
Component: software-collections-guide
Severity: high
Priority: high
Reporter: pkovar(a)redhat.com
Remove BuildArch: noarch from the meta package example in:
http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html…
(Changed in scl-utils-20121110.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml
https://bugzilla.redhat.com/show_bug.cgi?id=769438
Summary: [PATCH] Fix syntax of code examples within
rpm-guide-programming-python.xml
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: rpm-guide
AssignedTo: bcotton+fedora(a)gmail.com
ReportedBy: dmalcolm(a)redhat.com
QAContact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pkovar(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Created attachment 548940
--> https://bugzilla.redhat.com/attachment.cgi?id=548940
Patch to Rpm Guide to fix rpm-guide-programming-python.xml
Unfortunately the examples of Python code within the RPM guide have been
thoroughly broken since the initial conversion to DocBook, due to the way
Python treats leading whitespace as significant.
I'm attaching a patch which overhauls this page, so that the code examples are
syntactically valid. See the notes in the patch
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1163568
Bug ID: 1163568
Summary: POSIX capabilities "%caps" macro not mentioned
anyhwere
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Severity: medium
Assignee: bcotton+fedora(a)gmail.com
Reporter: matt(a)nightrealms.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
The RPM guide doesn't mention the "%caps" macro which can be used to set a
file's POSIX capabilities (see http://linux.die.net/man/7/capabilities) It
should go in chapter 9, section 5.4, at URL
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1115469
Bug ID: 1115469
Summary: Link to full documentation is incorrect
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: msuchy(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Description of problem:
This page:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
links to
/usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html
Which does not exist on recent Fedoras.
RPM API is documented at:
/usr/share/doc/rpm-apidocs/index.html
And I did not find documentation for rpm-python itself.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1025475
Bug ID: 1025475
Summary: typo in yum update for kexi-mysql
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: admin(a)velusuniverse.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Description of problem:
calligra-kexi-driver-mysql summary says mysqwl driver for kexi but shouldnt it
say mysql driver for kexi ??
Version-Release number of selected component (if applicable):
How reproducible:
use the yum extender andd look up calligra-kexi-driver-mysql
Steps to Reproduce:
1.
2.
3.
Actual results:
ummary says mysqwl driver for kexi
Expected results:
mysql driver for kexi
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1017792
Bug ID: 1017792
Summary: %verify doesn't know symlink, maj min
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: jskarvad(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Description of problem:
In the "Verifying the %files section" chapter of the RPM guide [1], there is
written "symlink", but it seems RPM uses "link" instead.
Also I had trouble with the "maj" and "min", I guess there is "rdev" used
instead.
Version-Release number of selected component (if applicable):
0.1
How reproducible:
Always
Steps to Reproduce:
1. See the "Verifying the %files section" chapter
Actual results:
There are symlink, maj and min
Expected results:
The link and probably rdev
Additional info:
[1]
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1003962
Bug ID: 1003962
Summary: RPM scriptlet -p option not documented
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: daniel.neuberger(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
The fedora RPM guide does not document the -p option that can be passed to the
RPM scriptlets. It should probably be located here
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…,
but I looked through the entire guide and couldn't find it.
The only only place I could find it documented is here
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets, but what it says is
wrong. It says:
"The basic syntax is similar to the %build, %install, and other sections of the
rpm spec file. The scripts support a special flag, -p which allows the
scriptlet to invoke a single program directly rather than having to spawn a
shell to invoke the programs. (ie: %post -p /sbin/ldconfig)"
A more accurate description is:
"The basic syntax is similar to the %build, %install, and other sections of the
rpm spec file.
The scripts support a special flag, -p which specifies the interPreter that
should be used to run the script (the default is /bin/sh). Sometimes the -p
option is used with no body in order to run a single command directly rather
than having to spawn a shell to invoke the programs (i.e. %post -p
/sbin/ldconfig). Note that this form requires that there be nothing but white
space (not even comments) until the next section begins."
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1057882
Bug ID: 1057882
Summary: Fedora - Installation Quick Start Guide - An update of
the Czech translation ready
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
Please publish an updated Czech version of the F20 Installation Quick Start
Guide
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Mostly grammar errors found in current version.
Expected results:
An updated Czech translation published - missing translation(s) added,
translation revision and precision.
Additional info:
If the bug BZ#1056196 is a serious obstacle, publish this update once the bug
is resolved.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1050903
Bug ID: 1050903
Summary: Fedora - burning ISO images to disc - Updated Czech
translation
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
Please publish an update of the Czech translation of Burning ISO images to disc
guide
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Translation update - missing translation, revision and precision.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=985020
Bug ID: 985020
Summary: explain types of rpm packages (what are they for)
Product: Fedora Documentation
Version: devel
Component: packager-guide
Severity: unspecified
Priority: unspecified
Assignee: pkovar(a)redhat.com
Reporter: bvoperdf21(a)mt2014.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkovar(a)redhat.com
Description of problem:
First I'd like to thank for the awesome documentaions available.
Also +1 for the export function (PDF,html-single,...).
Looking at the packagers guide I missed some information.
It would be nice if you also tell what kind of rpm packages are out there.
What I found so far:
.rpm
.src.rpm
.debugsource....
.debuginfo....
For example I still don't know if the debugsource is needed when using gdb for
debugging or if the debuginfo package is enough.
Version-Release number of selected component (if applicable):Edition 18.0.1
How reproducible:
Steps to Reproduce:
1.go to
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pac…
2.read everything
Actual results: no description of the defferent types of rpm packages
Expected results: find description of the defferent types of rpm packages and
what they are used for/by.
Additional info: would be nice to have this
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=959626
Bug ID: 959626
Summary: config_name mismatch in mock example
Product: Fedora Documentation
Version: devel
Component: packager-guide
Severity: low
Priority: unspecified
Assignee: pkovar(a)redhat.com
Reporter: axilleas(a)archlinux.gr
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: fnadge(a)redhat.com
Category: ---
Description of problem:
In section 2.4.3. Testing a Package with Mock, the last example uses the
epel-6-x86_64 config whereas Fedora 18 is referenced above.
According to the preamble, the example should read:
mock -r fedora-18-x86_64 ~/rpmbuild/SRPMS/eject-2.1.5-0.1.fc18.src.rpm
Link:
https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pa…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1198984
Bug ID: 1198984
Summary: firewalld: please improve documentation on using it on
a RedHat/Fedora/CentOS router
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: razvan.sandu(a)mobexpert.ro
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Hello,
Description of problem:
Even using the rich-language feature, it is still rather difficult to figure
out
how to use firewalld on a RedHat/Fedora/CentOS system that is used as a router
(a "transparent" system).
That's because:
a. administrators will need *different* sets of rules/restrictions for access
to the router itself and to the various services that run beyond the router
(using or non using NAT).
b. It is not very clear how/where the predefined firewalld zones implement
their policies (ACCEPT or DROP) and when these policies apply to traffic
bounded *to* the router system or to traffic that *traverses* the router.
For example, an administrator needs an *easy* method to restrict VNC access
*to* the router itself (INPUT), but may want free VNC access to some server
located *behind* the router (FORWARD). In the second case, forwarding may (or
may not) imply NAT, depending if he goes on the Internet via the external
interface or simply goes in another LAN segment beyond the router.
c. It is not very clear how/where the predefined firewalld zones implement
their trafic rules ( *exceptions* to ACCEPT or DROP default policies) and when
these rules apply to traffic bounded *to* the router system or to traffic that
*traverses* the router.
Additional info:
Even it is not dynamic, the Shorewall application (http://shorewall.net/) acts
as a higher-level language over iptables, offering the same concepts of "zones"
for interfaces. Much of its conceptual architecture is directly applicable
("portable") to firewalld, if accepted by developers.
Somewhat different from conceptual point of view, the "zones" are "levels of
trust surrounding the router", including thr FW zone for the router itself.
(unlike firewalld, the shorewall zones have no "sources" or "services" embedded
in them).
IPv4 and IPv6 zones are completely separated (they actually represent different
levels of trust).
Administrators may directly define policies, i.e. allow *default* actions to be
done when an packet travels from a zone to another (ACCEPT, REJECT). The most
sane policy between any two zones is REJECT (with further exceptions defined as
rules, see below).
Rules are *exceptions to policies* , explicitly defined (based on various
criteria such as source IP, destination IP, ports, etc.)
Rules may be expressed via predefined (or customised) "macros" (which are the
direct equivalent of firewalld's "services").
IPv4 and IPv6 policy and rules are completely separated (IMHO that's good,
since the use of global IPv6 addresses pose completely different security
problems than NATted & externally firewalled IPv4).
Best regards,
Răzvan
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008227
Bug ID: 1008227
Summary: SSD cache
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: agk(a)redhat.com, i.gnatenko.brain(a)gmail.com,
jeremy(a)goop.org, jreznik(a)redhat.com, kzak(a)redhat.com,
nobody(a)fedoraproject.org, rdieter(a)math.unl.edu,
rolf(a)rolffokkens.nl, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998543, 999690, 1000817, 1001120, 1003208, 1000078,
1003207
+++ This bug was initially created as a clone of Bug #998543 +++
This is a tracking bug for Change: SSD cache
For more details, see: http://fedoraproject.org//wiki/Changes/SSD_cache
Using recent kernel (3.9 and later) features for (fast) SSD caching of (slow)
ordinary hard disks.
--- Additional comment from Rolf Fokkens on 2013-08-21 13:35:33 EDT ---
I'll build a bcache-tools RPM and a dm-cache-utils rpm (actually bcache-tools
is already available here: bcache-tools-20130820-0.1.fc19.src.rpm).
I'll follow the procedure as described here:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
--- Additional comment from Rolf Fokkens on 2013-08-24 11:51:34 EDT ---
Tried to create a dmcache-utils package as well (Bug 1000078) but it doesn't
look really useful. So I'll focus on bcache-tools first. For that I still need
a sponsor.
--- Additional comment from Rolf Fokkens on 2013-08-27 06:52:40 EDT ---
I closed Bug 1000078 since good userland support requires LVM2 to support
dm-cache. Which will happen 'in the future', but F20 doesn't look feasible to
me.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:21:30 EDT ---
Create Bug 1003207 (bcache support for dracut) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:25:06 EDT ---
Create Bug 1003208 (bcache support for anaconda) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-09-09 04:18:18 EDT ---
Test day planned: https://fedorahosted.org/fedora-qa/ticket/415
--------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185336.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1058066
Bug ID: 1058066
Summary: new virt-xml functionality coming from upstream
libvirt should be documented
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
There is a new tool called `virt-xml` that will end up in Fedora soon[1]. It
looks very useful, and should be documented.
[1] https://www.redhat.com/archives/libvir-list/2014-January/msg01226.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=980931
Bug ID: 980931
Summary: The Virtualization Administration Guide Still Uses
UNIX System V Commands
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Keywords: Documentation
Severity: medium
Priority: unspecified
Assignee: lnovich(a)redhat.com
Reporter: jhradile(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com, me(a)petetravis.com
Description of problem:
The Virtualization Administration Guide for Fedora 18 [1] still uses UNIX
System V commands “service” and “chkconfig”. Although these commands still work
and will continue to work in the foreseeable future, users are strongly advised
to learn and use the new command that is shipped with systemd and is part of
the Fedora distribution since version 15.
Version-Release number of selected component (if applicable):
Fedora-Virtualization_Administration_Guide-18-en-US-1.0-1
How reproducible:
Always.
Steps to Reproduce:
Read section 14.3, “Starting and stopping the daemon” [2], to learn how to
configure the vhostmd service to start automatically at boot time.
Actual results:
/sbin/chkconfig vhostmd on
Expected results:
systemctl enable vhostmd.service
Additional info:
http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
-----
[1]
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad…
[2]
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1095977
Bug ID: 1095977
Summary: RFE: static IP assignment
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Static IP addresses are crucial for applications like DHCP servers or other
infrastructure that can't rely on external assignment. They're also helpful for
home users that want to predictably locate their Fedora installation.
Explain the use case for this and some alternative methods, then the procedure
for setting a setting a static IP using both ifcfg files and graphical methods.
Each method could be explained in a separate article; ie "... on the command
line" and "... with GNOME" and "... with KDE" and so on.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1101798
Bug ID: 1101798
Summary: RFE: Captive portal
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Create a recipe for configuring a simple captive portal with Fedora that will
require users to acknowledge a terms of use message before allowing connections
to pass.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1101796
Bug ID: 1101796
Summary: RFE: NAT router
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Create a recipe for using Fedora as a NAT router using Firewalld and
NetworkManager.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096394
Bug ID: 1096394
Summary: RFE: Thin Client (Tracking Bug)
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Fedora can be used as a server and client environment for a thin client
deployment. Document the required procedures to do this.
Because of the broad scope and number of procedures involved, this should be
split up into recipes addressing component tasks. This bug will be used to
track the overall progress; please block this bug with any new bugs created for
the purpose.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1095945
Bug ID: 1095945
Summary: RFE: disabling head parking on spinning drives
Product: Fedora Documentation
Version: devel
Component: cookbook
Assignee: docs(a)lists.fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
Some drives have aggressive APM, and the resulting frequent head parking can
negatively impact access latency and produce an annoying clicking sound.
Explain the theory, benefits, procedure, and risks of adjusting APM settings
with hdparm.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982899
Bug ID: 982899
Summary: 7.3.1. Establishing a Wired (Ethernet) 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:
In section 7.3.1:
Default connection no longer called 'em1'
No field for 'connection name'
you can add new settings for the network under different profiles by selecting
'add profile...'
you can remove/reset a profile by going to the 'options' button under the
profile and selecting the 'reset' item on the left, and then choosing to either
'reset' or 'forget'
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1198643
Bug ID: 1198643
Summary: Append parameters to grub.cfg
Product: Fedora Documentation
Version: devel
Component: virtualization-guide
Assignee: docs(a)lists.fedoraproject.org
Reporter: geanceretta(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org, lnovich(a)redhat.com,
zach(a)oglesby.co
Description of problem: The instructions[1] of how to append parameters to
Grub's grub.config file is obsolete on recent releases of Fedora. The file
/boot/grub/grub.conf doesn't exist anymore.
The way to do it now is (tested on Fedora 20):
1 - Edit /etc/default/grub
2 - Append information at the line GRUBCMDLINELINUX=" ... console=tty0
console=ttyS0,115200 ... ")
3 - Regenerate the /boot/grub2/grub.cfg file with the command "grub2-mkconfig
-o /boot/grub2/grub.cfg"
Link:
[1]
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
Additional info: The documentation is refered to version 18 where it should
work, but as we don't have a documentation in a most atual release of Fedora
for that subject, you can write a note for the users of most recent releases of
Fedora that came with Grub2, where the procedure is according with that listed
above.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001344
Bug ID: 1001344
Summary: Allow kdump on secureboot machines
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
vgoyal(a)redhat.com, zach(a)oglesby.co
Depends On: 998565
+++ This bug was initially created as a clone of Bug #998565 +++
This is a tracking bug for Change: Allow kdump on secureboot machines
For more details, see:
http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot
Currently kexec/kdump is disabled on machines with secureboot enabled. This
feature aims to enable kexec/kdump on such machines.
--- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT ---
I think first thing is to include a new package ima-evm-tools in F20. I am not
sure how to do it.
--- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT ---
(In reply to Vivek Goyal from comment #1)
> I think first thing is to include a new package ima-evm-tools in F20. I am
> not sure how to do it.
Vivek, create Package Review -
http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and
block this bug on the created review bug. After review, add it to comps.
Thank you.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.h…
Please assess existing documentation for the impact of this Change
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001343
Bug ID: 1001343
Summary: Allow kdump on secureboot machines
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: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
vgoyal(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998565
+++ This bug was initially created as a clone of Bug #998565 +++
This is a tracking bug for Change: Allow kdump on secureboot machines
For more details, see:
http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot
Currently kexec/kdump is disabled on machines with secureboot enabled. This
feature aims to enable kexec/kdump on such machines.
--- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT ---
I think first thing is to include a new package ima-evm-tools in F20. I am not
sure how to do it.
--- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT ---
(In reply to Vivek Goyal from comment #1)
> I think first thing is to include a new package ima-evm-tools in F20. I am
> not sure how to do it.
Vivek, create Package Review -
http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and
block this bug on the created review bug. After review, add it to comps.
Thank you.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=977042
Bug ID: 977042
Summary: GUI examples presume GNOME without stating it is GNOME
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
The System Administrator's Guide references a number of GUI utilities, many of
which are specific to GNOME. It isn't immediately obvious to the uninitiated
that this is the case, causing non-GNOME users to find fault with the guide.
I suggest an admonition in the preface along the lines of "Some of the
graphical procedures and menu locations are specific to GNOME, but most command
line instructions will be universally applicable" Comprehensively
differentiating between GNOME procedures, procedures for other DEs, and
universal procedures would probably be prohibitively time consuming.
--Pete
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=997219
Bug ID: 997219
Summary: No "Write to Disk" option for ISO images in Fedora 19
Product: Fedora Documentation
Version: devel
Component: readme-burning-isos
Assignee: oglesbyzm(a)gmail.com
Reporter: sirjake(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, stickster(a)gmail.com
Description of problem:
Guide says that you can right click on a ISO image and choose "Write to disc."
This is not true, at least with Fedora 19.
Version-Release number of selected component (if applicable):
19
How reproducible:
Always, at least in 32 bit.
Steps to Reproduce:
1.
http://docs.fedoraproject.org/en-US/Fedora/19/html/Burning_ISO_images_to_di…
2. Insert a DVD.
3. Attempt to follow the directions above. No "Write to disk" option exists.
Actual results:
No obvious way to burn ISO images in Fedora Linux 19.
Expected results:
Directions to burn ISO disk in Fedora Linux 19
Additional info:
I had a new-to-me computer that I assumed would not support 64 bit, but after
installing 32 bit found out that 64 was supported by my processor. I downloaded
64 ( Fedora-Live-Desktop-x86_64-19-1.iso ), and wanted to burn a disk of it,
but the option was not available and the directions online did not help. I had
to go back to Windows on a different machine to burn it.
Note: I do have a DVD burner on this machine. The same thing occurs with CD's
in the burner.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=948823
Bug ID: 948823
Summary: Need a search solution for docs.fedoraproject.org
Product: Fedora Documentation
Version: devel
Component: project-tracking
Severity: unspecified
Priority: unspecified
Assignee: nobody(a)fedoraproject.org
Reporter: sparks(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, sparks(a)redhat.com,
stickster(a)gmail.com
Category: ---
Description of problem: Due to the removal of Google search feature (see bug
616876) we no longer have a search solution for docs.fp.o.
We need to investigate an alternate solution and bring the search feature back.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1002573
Bug ID: 1002573
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: security-guide
Keywords: Tracking
Assignee: sparks(a)redhat.com
Reporter: sparks(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, me(a)petetravis.com,
nobody(a)fedoraproject.org, pkennedy(a)redhat.com,
security-guide-list(a)redhat.com, sparks(a)redhat.com,
steved(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 984718, 998566, 1001346
+++ This bug was initially created as a clone of Bug #1001346 +++
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982914
Bug ID: 982914
Summary: 7.4.1. Configuring 802.1x Security
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:
In section 7.4.1 under 'Procedure 7.8. For a wired connection...', '
Procedure 7.9. For a wireless connection...':
The 'Network Connections' dialogue can be accessed via:
activities --> applications --> sundry --> network connections, or via
nm-connection-editor
This is not specified at all in this section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982911
Bug ID: 982911
Summary: 7.3.3. Establishing a Mobile Broadband 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:
Under section 7.3.3, in 'Procedure 7.3. Adding a New Mobile Broadband
Connection', 'Procedure 7.4. Editing an Existing Mobile Broadband Connection':
network connection editor can also be found at:
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=982910
Bug ID: 982910
Summary: 7.3.5. Establishing a DSL 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:
In section 7.3.5 under 'Procedure 7.6. Adding a New DSL Connection', 'Procedure
7.7. Editing an Existing DSL Connection':
These procedures could also specify that the network connections editor can be
accessed from:
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=1003065
Bug ID: 1003065
Summary: images missing from document
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: jhradile(a)redhat.com
Reporter: mordred(a)warpmail.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
in document:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
missing following 5 images under:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
images/authconfig-ui.png
images/authconfig-local.png
images/authconfig_LDAP.png
images/authconfig_nis.png
images/authconfig_winbind.png
Version-Release number of selected component (if applicable): n/a
How reproducible: n/a
Steps to Reproduce: n/a
Actual results:
Expected results: n/a
Additional info: n/a
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987307
Bug ID: 987307
Summary: Section 11.1.2.4 Figure 11.2 requires updating
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Created attachment 777222
--> https://bugzilla.redhat.com/attachment.cgi?id=777222&action=edit
layout of ldap/kerberos options in authentication dialog
Description of problem:
Figure 11.2 in section 11.1.2.4 no longer looks like this as there is a third
'password options tab' on this dialog
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987301
Bug ID: 987301
Summary: Section 11.1.1 Figure 11.1 missing
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
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 11.1.1 has a missing screenshot (Figure 11.1)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=983366
Bug ID: 983366
Summary: Cover Page says "Fedora 17" in 'header' logo
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:
Header logo on cover page of System Administrators guide says "Fedora 17" above
first line of text
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982894
Bug ID: 982894
Summary: 7.2.4. User and System Connections
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:
the network settings dialogue does not have tabs, instead, the identity section
of the dialogue is concerned with setting the connection to be available to all
users (or not)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982510
Bug ID: 982510
Summary: 4.3. Using the User Manager 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:
In section 4.3, the location of the user manager tool has changed in Gnome
3.8.3:
Activities --> Applications --> Sundry --> Users and Groups
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982504
Bug ID: 982504
Summary: 4.2. Using the User Accounts 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:
section 4.2 Using the User Accounts Tool
related to bug 982500
location of the settings dialog is:
activities --> applications --> utilities --> settings
Further:
The 'User Accounts' tool is called 'Users' in Gnome 3.8.3
--
You are receiving this mail because:
You are the QA Contact for the bug.
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=1136030
Bug ID: 1136030
Summary: Need a new chapter about upgrading Fedora
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
The current upgrade chapter is pretty much completely useless. We need a new
one that would cover:
* Automatic upgrades with FedUp, including how to prepare and how to clean up
after the update finishes
* Manual upgrade (or reinstall) - manually booting the installer on an existing
system and using the normal installation process to overwrite the root
filesystem while keeping the rest of the system (/home and any other separate
filesystems) intact.
There should be ample documentation on FedUp on the Fedora Wiki.
--
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=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=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=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=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.
https://bugzilla.redhat.com/show_bug.cgi?id=1193135
Bug ID: 1193135
Summary: Review Comments on Multiboot Guide version 0.1
Product: Fedora Documentation
Version: devel
Component: multiboot-guide
Severity: low
Assignee: chris.roberts(a)croberts.org
Reporter: scmccann2000(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: chris.roberts(a)croberts.org
Created attachment 992259
--> https://bugzilla.redhat.com/attachment.cgi?id=992259&action=edit
smccann comments to multiboot guide.
Attaching a pdf with a few comments from the perspective of a newbie to both
Fedora and multiboot. In general, very readable and understandable guide!
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
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=1192174
Bug ID: 1192174
Summary: Unhelpful links on LXDE spin page
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: jhhaynes(a)earthlink.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Several "how to use this file" links on the LXDE spins web page simply point
to the top Fedora documentation page. This is unhelpful when you need to know
how to use this file.
Version-Release number of selected component (if applicable):
F21
How reproducible:
always
Steps to Reproduce:
1.Bring up F21 LXDE spin web page
2.Click on any "how to use this file link"
3.
Actual results:
Gets to top of Fedora documentation tree
Expected results:
Should tell exactly how to use this file
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=999762
Bug ID: 999762
Summary: Java FAQ
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: low
Assignee: relnotes(a)fedoraproject.org
Reporter: pcsnow(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem: Parts of Java FAQ may need some updates.
https://fedoraproject.org/wiki/Java/FAQ?rd=JavaFAQ
Version-Release number of selected component (if applicable):19
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
1. JPackage does not seem updated since 2009
2. Intelllij complains that non-sun version has performance problems during
install and recommends against use of OpenJDK.
3. It might be helpful to provide some assistance in docs to allow easy
integration of Oracle Java using system-switch-java.
The FAQ does not mention switch-java as an option.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001342
Bug ID: 1001342
Summary: Fedora 20 Boost 1.54 Uplift
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
pmachata(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001341
Bug ID: 1001341
Summary: Fedora 20 Boost 1.54 Uplift
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: jreznik(a)redhat.com, pmachata(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001346
Bug ID: 1001346
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, steved(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001345
Bug ID: 1001345
Summary: Enable SELinux Labeled NFS Support
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: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
steved(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008221
Bug ID: 1008221
Summary: Ryu Network Operating System
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
ymht.fedora(a)gmail.com, zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008220
Bug ID: 1008220
Summary: Ryu Network Operating System
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: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, ymht.fedora(a)gmail.com,
zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
-----------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=846864
Bug ID: 846864
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: docs(a)lists.fedoraproject.org
Assignee: laine(a)redhat.com
Summary: Need a list of toolsets and when they are appropriate
in the virt Getting Started guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: laine(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-getting-started-guide
Product: Fedora Documentation
The Getting Started Guide needs an overview of all the different toolsets, and
when each would be appropriate. In particular I'm talking about the following:
1) gnome-boxes
2) virt-manager
3) virsh, virt-install
4) ovirt
5) Should we point some people to OpenStack?
I will write up a first draft of this, and hand it to a qualified docs person
to edit and correctly place in the guide.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=846184
Bug ID: 846184
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: low
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: New Russian translation for Fedora Resource Management
Guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Created attachment 602635
--> https://bugzilla.redhat.com/attachment.cgi?id=602635&action=edit
Russian translation of Fedora 17 Resource Management Guide
The patch providing Russian translation of the guide is attached.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=829952
Bug ID: 829952
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: Outdated information about cgconfig service in
Resource Management Guide for Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Description of problem:
The Resource Management Guide for Fedora 17 contains outdated information about
cgconfig service in section 2.1 "The cgconfig Service"
The guide states that the cgconfig service is not started by default in Fedora
17. It is not true. In addition, the guide contains phrase "When you start the
service with chkconfig" that is wrong for any release. For Fedora 17 is should
be "When you start the service with the <command>systemctl start</command>
command".
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1197237
Bug ID: 1197237
Summary: mancata conferma cambio password utente
Product: Fedora Documentation
Version: devel
Component: security-guide
Severity: low
Assignee: sparks(a)redhat.com
Reporter: bagigis(a)tiscali.it
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, security-guide-list(a)redhat.com,
sparks(a)redhat.com, zach(a)oglesby.co
Created attachment 996206
--> https://bugzilla.redhat.com/attachment.cgi?id=996206&action=edit
allegato
Description of problem:
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1018053
Bug ID: 1018053
Summary: New nmcli features should be documented
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
nmcli in Fedora 20 can now add, delete, edit, activate, and deactivate
connections, probably including bridge and Bond devices. This functionality
should be represented in the SysadminGuide.
http://fedoraproject.org/wiki/Networking/CLI is a start.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001349
Bug ID: 1001349
Summary: NetworkManager Bridging Support
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: jreznik(a)redhat.com, psimerda(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 998568
+++ This bug was initially created as a clone of Bug #998568 +++
This is a tracking bug for Change: NetworkManager Bridging Support
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerBridging
NetworkManager should be able to configure bridge interfaces with commonly used
options and recognize their existing configuration on startup without
disrupting their operation.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186536.html
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001352
Bug ID: 1001352
Summary: NetworkManager Bridging Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
psimerda(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998568
Blocks: 1001349
+++ This bug was initially created as a clone of Bug #998568 +++
This is a tracking bug for Change: NetworkManager Bridging Support
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerBridging
NetworkManager should be able to configure bridge interfaces with commonly used
options and recognize their existing configuration on startup without
disrupting their operation.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186536.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206806
Bug ID: 1206806
Summary: convert yum commands to dnf commands - Virtualization
Deployment and Administration Guide
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(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/Vir…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206804
Bug ID: 1206804
Summary: convert yum commands to dnf commands - Security Guide
Product: Fedora Documentation
Version: devel
Component: security-guide
Assignee: sparks(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, security-guide-list(a)redhat.com,
sparks(a)redhat.com, zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206803
Bug ID: 1206803
Summary: convert yum commands to dnf commands - Packager's
Guide
Product: Fedora Documentation
Version: devel
Component: packager-guide
Assignee: pkovar(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkovar(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/Pac…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206800
Bug ID: 1206800
Summary: convert yum commands to dnf commands - Networking
Guide
Product: Fedora Documentation
Version: devel
Component: networking-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/Net…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206799
Bug ID: 1206799
Summary: convert yum commands to dnf commands - Musicians'
Guide
Product: Fedora Documentation
Version: devel
Component: musicians-guide
Assignee: christopher(a)antila.ca
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: christopher(a)antila.ca, zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/index.ht…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206798
Bug ID: 1206798
Summary: convert yum commands to dnf commands - Installation
Guide
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206797
Bug ID: 1206797
Summary: convert yum commands to dnf commands - Documentation
Guide
Product: Fedora Documentation
Version: devel
Component: documentation-guide
Assignee: sparks(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com, pkovar(a)redhat.com,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Document URL:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Doc…
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206796
Bug ID: 1206796
Summary: convert yum commands to dnf commands - Cloud Guide
Product: Fedora Documentation
Version: devel
Component: cloud-guide
Assignee: docs(a)lists.fedoraproject.org
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
Convert all yum commands to dnf commands:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Clo…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1206795
Bug ID: 1206795
Summary: convert yum commands to dnf commands - Amateur Radio
Guide
Product: Fedora Documentation
Version: devel
Component: amateur-radio-guide
Assignee: wb8rcr(a)arrl.net
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: sparks(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
Convert all listed yum commands to dnf commands within the documentation.
http://docs.fedoraproject.org/en-US/Fedora/14/html/Amateur_Radio_Guide/inde…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1202475
Bug ID: 1202475
Summary: "tunnel" misspelled in ip link manpage
Product: Fedora Documentation
Version: devel
Component: docs-requests
Severity: low
Assignee: nobody(a)fedoraproject.org
Reporter: chris(a)dotson97.org
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
Document URL: man ip link
Section Number and Name: DESCRIPTION section
Describe the issue: The word "tunnel" is misspelled several times as "tuunel"
in the English man pages for "ip link".
Suggestions for improvement: Correct to English spelling "tunnel".
Additional information:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1084400
Stephen Wadeley <swadeley(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2015-03-06 01:33:22
--- Comment #28 from Stephen Wadeley <swadeley(a)redhat.com> ---
Hello
After lots of testing, I decided to drop the init=bin/sh method in favour of
the boot from installation disk or image method and have the rd.break method as
an alternative for those without boot media.
Please see:
http://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Gu…
Thank you
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1005479
Bug ID: 1005479
Summary: Need references for YUM
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
I noted the following
Within
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/s1-pk…
In the Note
Only one desktop environment can be selected at install time. To install
additional environments once Fedora is installed, use the *Software*
tool or the yum groupinstall| command.
I do not recall a previous mention of yum in this guide. We who are
familiar with Fedora know yum as the command line system software tool
that accompanies Fedora. Perhaps we need to elaborate with a footnote,
about yum and where to visit to fetch the yum documentation.
Version-Release number of selected component (if applicable):
Refer to the link.
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=1060216
Bug ID: 1060216
Summary: RELNOTES - Summarize the release note
suggestion/content
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: limburgher(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Blocks: 168083 (fc5-relnotes-traqr)
gpodder is being upgraded from 2.20.3 to 3.5.2. There is a configuration and
date storage change between these versions. After upgrading the RPM, any user
on the system who uses gpodder, prior to opening it, should run
/usr/bin/gpodder-migrate2tres, which will migrate the user's data and
configuration to the new format, including all subscribed feeds and downloaded
podcasts.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=168083
[Bug 168083] FC5 release notes tracker bug
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1150394
Bug ID: 1150394
Summary: Please update I18n Documentation Beat for Fedora 21
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: psatpute(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
We recently update http://fedoraproject.org/wiki/Documentation_I18n_Beat for
google-noto-fonts which added 44 new subpackages to cover Unicode.
Please update it to your latest notes.
Version-Release number of selected component (if applicable):
How reproducible:
Everytime
Steps to Reproduce:
1.
2.
3.
Actual results:
Not updated
Expected results:
Should have latest Documentation_I18n_Beat
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=928623
Bug ID: 928623
Summary: Need to explain HOW to try different desktop
environments in live image
Product: Fedora Documentation
Version: devel
Component: readme-live-image
Severity: unspecified
Priority: unspecified
Assignee: docs(a)lists.fedoraproject.org
Reporter: mike(a)thosehallidays.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nathan(a)afternoondust.co.uk, oglesbyzm(a)gmail.com
Description of problem:
Chapter 6 says "You can use the live image to try different desktop
environments such as GNOME, KDE, Xfce, or others" but does not explain HOW to
do that (or provide a contextual reference).
Version-Release number of selected component (if applicable):
Fedora 18
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=1174734
Bug ID: 1174734
Summary: grub can't be insntalled like that for UEFI network
installation
Product: Fedora Documentation
Version: devel
Component: installation-quick-start-guide
Assignee: pbokoc(a)redhat.com
Reporter: quintela(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Instructions in page:
https://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/s1-n…
don't work. grubx64.efi is not able to boot through the network. What you
need is something more similar to:
grub2-mknetdir --net-directory /var/lib/tftpboot/uefi/ --subdir x64-efi
and change:
filename "pxelinux/bootx64.efi";
to (with the paths that I showed):
filename "uefi/x64-efi/core.efi"
Configuration file is searched as:
file /mnt/mirror/tftp/efi-x64/grub.cfg-01-3c-97-0e-da-28-fb not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A80ACB not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A80AC not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A80A not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A80 not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A8 not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0A not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C0 not found
file /mnt/mirror/tftp/efi-x64/grub.cfg-C not found
file /mnt/mirror/tftp/efi-x64/grub.cfg not found
(change /mnt/mirror/tftp/ for whatever is your tftpboot)
And format of the file is something like:
set timeout=1
menuentry 'Fedora 21' {
linuxefi fedora/21/x86_64/vmlinuz
ks=http://mirror.mitica/kickstart/x86_64-21-standalone.cfg ksdevice=link
initrdefi fedora/21/x86_64/initrd.img
}
And I haven't found any use for efidefault, not being able to use pxelinux from
inside grub (in efi systems).
If you have any questions, please, let me know.
Thanks, Juan.
PD. I use dnsmasq instead of dhcp-server, but it shouldn't be a different for
this.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=959681
Pete Travis <me(a)petetravis.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed| |2015-03-04 11:27:12
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1198224
Bug ID: 1198224
Summary: where is this document for f20 in git repository.
Product: Fedora Documentation
Version: devel
Component: installation-quick-start-guide
Assignee: pbokoc(a)redhat.com
Reporter: elf(a)poyo.jp
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
I can't make transated this book for f20 by git.
Before. I found this book in English on docs.fedoraproject.org.
But I couldn't find branch for f20 in git. So I made branch of f20 from master.
and I pubished the book in Japanese.
But actually, Pubished book is for f17. Where is docbook for f20?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. git clone
ssh://git.fedorahosted.org/git/docs/installation-quick-start-guide.git
2. cd installation-quick-start-guide
3. unzip ja-JP.zip
4. publican build --embedtoc --publish --formats epub,html,html-single,pdf
--langs
Actual results:
publican build the book for f17.
Expected results:
publican will build the book for f20.
Additional info:
I made branch of "f20" from branch of "master". but It actualy is for f17. So I
have to make branch of f20 again from somewhere...
--
You are receiving this mail because:
You are the QA Contact for the bug.