June 2013 - docs - Fedora Mailing-Lists

[Bug 755744] New: typo in PV-Configuring_Additional_Devices

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: typo in PV-Configuring_Additional_Devices https://bugzilla.redhat.com/show_bug.cgi?id=755744 Summary: typo in PV-Configuring_Additional_Devices Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: virtualization-guide AssignedTo: docs(a)lists.fedoraproject.org ReportedBy: shaiton(a)fedoraproject.org QAContact: nobody(a)fedoraproject.org CC: kwade(a)redhat.com, oglesbyzm(a)gmail.com Classification: Fedora Story Points: --- Type: --- >From the file available in transifex, Now you can configure the new network interfaces using <command>redhat-config-network</command> or Red Hat Enterprise Linux3 or <command>system-config-network</command> on Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5. that should be "on" Red Hat. I could have corrected that now that I have git access, but this git is still for F14… There were plenty of update about virt since F14, is it outdated? http://fedoraproject.org/wiki/Docs_Project_meetings#Guides -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

6 years, 8 months

2
7
0 / 0

[Bug 693536] New: How to increase the number of configured loop devices

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: How to increase the number of configured loop devices https://bugzilla.redhat.com/show_bug.cgi?id=693536 Summary: How to increase the number of configured loop devices Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: virtualization-guide AssignedTo: fedora-docs-list(a)redhat.com ReportedBy: apevec(a)redhat.com QAContact: nobody(a)fedoraproject.org CC: stickster(a)gmail.com, kwade(a)redhat.com, oglesbyzm(a)gmail.com Classification: Fedora Story Points: --- Description of problem: http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/s... Number of loop devices cannot be changed via modprobe.conf since loop is not a kernel module anymore: # grep DEV_LOOP /boot/config-2.6.34.8-68.fc13.x86_64 CONFIG_BLK_DEV_LOOP=y -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

6 years, 8 months

2
7
0 / 0

[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide

by Red Hat Bugzilla

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 on the CC list for the bug.

8 years, 11 months

1
5
0 / 0

[Bug 627417] New: docs.fp.o landing page needs 'Start here' note!

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: docs.fp.o landing page needs 'Start here' note! https://bugzilla.redhat.com/show_bug.cgi?id=627417 Summary: docs.fp.o landing page needs 'Start here' note! Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric(a)christensenplace.us ReportedBy: nathan.thomas(a)peacenik.co.uk QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com, nb(a)fedoraproject.org Classification: Fedora Description of problem: We have a large variety of documentation guides serving a wide range of different users. It may be difficult for users arriving at docs.fp.o to know where to start, especially if they are new to Fedora/Linux and are unfamiliar with some of the technical terms. A note on the landing page suggesting a sensible starting point for new users could help alleviate this problem. Eg: "New to Fedora? You can try Fedora on your PC without touching your existing installation by following the Live Image Guide." The end of the Live Image guide helpfully points users to the Installation guide if they want to install :) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

9 years, 4 months

1
11
0 / 0

[Bug 654484] New: New Bugzilla component for Storage Administration Guide

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: New Bugzilla component for Storage Administration Guide https://bugzilla.redhat.com/show_bug.cgi?id=654484 Summary: New Bugzilla component for Storage Administration Guide Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric(a)christensenplace.us ReportedBy: r.landmann(a)redhat.com QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com, nb(a)fedoraproject.org Classification: Fedora Target Release: --- Please create a component for the Storage Administration Guide; default assignee should be ddomingo(a)redhat.com Cheers Rudi -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

9 years, 5 months

1
6
0 / 0

[Bug 839625] New: Configuring_an_IPA_Client_on_AIX instructs to configure sshd with 'GSSAPITrustDNS' which causes sshd to no longer start

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=839625 Bug ID: 839625 QA Contact: docs(a)lists.fedoraproject.org Severity: medium Version: devel Priority: medium CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com, stickster(a)gmail.com Assignee: nobody(a)fedoraproject.org Summary: Configuring_an_IPA_Client_on_AIX instructs to configure sshd with 'GSSAPITrustDNS' which causes sshd to no longer start Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: chorn(a)redhat.com Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: docs-requests Product: Fedora Documentation Description of problem: http://docs.fedoraproject.org/en-US/Fedora/17/html/FreeIPA_Guide/Configur... instructs to set 'GSSAPITrustDNS no' in /etc/ssh/sshd_config . Version-Release number of selected component (if applicable): current / fedora [15|16|17] instructions How reproducible: always Steps to Reproduce: 1. access webpage 2. implement change 3. try to start sshd Actual results: sshd no longer starts Expected results: sshd should start Additional info: - GSSAPITrustDNS is a ssh client option - its not mentioned in the manpage but recognized - http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Identit... mentions it as client option - http://freeipa.com/page/ConfiguringAixClients looks like the most current howto and does not mention the option at all. I think just removing the option from the webpage is the most simple way to resolve this (recheck whole howto with an AIX client for bonus) -- You are receiving this mail because: You are the QA Contact for the bug.

9 years, 7 months

1
7
0 / 0

[Fedora Infrastructure] #3860: Test box for Publican 3

by fedora-badges

#3860: Test box for Publican 3 ----------------------+----------------------------------- Reporter: sparks | Owner: sysadmin-main-members Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Systems | Version: Test Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | ----------------------+----------------------------------- The Docs Project needs a test system setup for our docs.fp.o replacement. It needs to be on a EL 6 box with the optional channel activated. -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3860> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

9 years, 12 months

1
14
0 / 0

#5214: Setup koji tags and repo for Docs

by Fedora Release Engineering

#5214: Setup koji tags and repo for Docs -----------------------------+------------------------ Reporter: crantila | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: docs | Blocked By: Blocking: | -----------------------------+------------------------ Posted here as per [https://fedorahosted.org/fedora- infrastructure/ticket/3320] '''phenomenon''' To support simpler and more robust updates to docs.fp.o, need to setup koji to handle a new tag and repo for Docs. '''implementation recommendation''' <Sparks> What would be required to stand up a separate instance of koji for Docs? <dgilmore> Sparks: why would you want a seperate instance? <dgilmore> Sparks: i dont see any valid reason to do so <Sparks> dgilmore: For the Docs website. Publican has the ability publish documentation from packages (separate repo from the Fedora repo) for the website. We want to replace the git repo that operates it now. <dgilmore> Sparks: and why does that need a seperate koji? <Sparks> The git repo has gotten HUGE and is becoming an issue. <dgilmore> Sparks: so, why does that mean a seperate koji instance <dgilmore> Sparks: we could use a seperate tag and targets in koji <dgilmore> i dont see why it would need its own koji <Sparks> dgilmore: It's either that or try to get everyone setup as packagers. <dgilmore> Sparks: get everyone setup as packagers <Sparks> dgilmore: Except that they really won't be packagers. <dgilmore> Sparks: though you dont need to be a a packager to get a koji cert <dgilmore> you just need fas <dgilmore> Sparks: what would be the workflow? <Sparks> dgilmore: Okay, and with that we can send packages through koji and tag them separately? <Sparks> dgilmore: Basically we just tell Publican to build the package and submit it to koji. The Publican software does all the work. <dgilmore> Sparks: I still really dont know what your trying to do. pretend im an idiot(not really that hard) and explain what it is and how it should work <Sparks> dgilmore: I'm not far off... <Sparks> dgilmore: So Publican will make an SRPM package, submit it to koji destined for a repo. Our Publican backend will install those packages and publish the data to the website. <Sparks> ...as I understand it <dgilmore> Sparks: so we would need to set up seperate tags and tagets for it, defining a koji policy allowing srpms to be built. likely we would add a new group to koji and add people allowed to build docs to it and limit access to the tags/targets to people in that group <dgilmore> Sparks: so its all doable <Sparks> dgilmore: Well that's a lot easier. :) <Sparks> dgilmore: We already have a group in FAS for people that should have access (docs- publishers). Should I open a ticket? <dgilmore> Sparks: koji doesnt know anything about fas <dgilmore> Sparks: please file a ticket. We wont be able to make changes until after f17 is done <Sparks> dgilmore: That's fine. We're not completely ready for the transition so after F17 would be good. <Sparks> dgilmore: Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5214> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 4 months

1
15
0 / 0

[Bug 928623] New: Need to explain HOW to try different desktop environments in live image

by Red Hat Bugzilla

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 assignee for the bug.

10 years, 10 months

1
9
0 / 0

New contributor for FreeIPA guide

by Martin Kosek

Hello docs! FreeIPA team would like to help Deon Lackey (CCed) with contributing to and publish upstream FreeIPA guide [1][2] for Fedora. I will be coordinating upstream contributions at this point. Can you please add me to docs-writers and docs-publishers groups? Thank you. [1] http://docs.fedoraproject.org/en-US/Fedora/17/html/FreeIPA_Guide/index.html [2] https://fedorahosted.org/freeipa-guide/ -- Martin Kosek <mkosek(a)redhat.com> Supervisor, Software Engineering - Identity Management Team Red Hat Inc.

10 years, 10 months

4
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs June 2013