docs November 2012

docs@lists.fedoraproject.org

16 participants
28 discussions

[Bug 755744] New: typo in PV-Configuring_Additional_Devices
by Red Hat Bugzilla 01 Sep '17

01 Sep '17

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.

2 7

[Bug 693536] New: How to increase the number of configured loop devices
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

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/sec… 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.

2 7

[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide
by Red Hat Bugzilla 18 Jun '15

18 Jun '15

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.

1 5

[Bug 627417] New: docs.fp.o landing page needs 'Start here' note!
by Red Hat Bugzilla 21 Jan '15

21 Jan '15

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.

1 11

[Bug 654484] New: New Bugzilla component for Storage Administration Guide
by Red Hat Bugzilla 15 Dec '14

15 Dec '14

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.

1 6

[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 15 Oct '14

15 Oct '14

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/Configurin… 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/Identity_… 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.

1 7

#5214: Setup koji tags and repo for Docs
by Fedora Release Engineering 21 Jan '14

21 Jan '14

#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

1 15

[Bug 833223] New: Adding lang_map to docsite-publican
by Red Hat Bugzilla 17 Jun '13

17 Jun '13

https://bugzilla.redhat.com/show_bug.cgi?id=833223 Bug ID: 833223 QA Contact: docs(a)lists.fedoraproject.org Severity: unspecified Version: devel Priority: unspecified CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com, stickster(a)gmail.com Assignee: nobody(a)fedoraproject.org Summary: Adding lang_map to docsite-publican Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: kev.raymond(a)gmail.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: docs-requests Product: Fedora Documentation docsite-publican still not use the config_map syntax in .tx/config file. See http://fedoraproject.org/wiki/Setting_up_a_document_with_Transifex#Step_5:_… -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 450331] New: lack of documentation on restoring from bare-metal (UUID problem)
by Red Hat Bugzilla 03 Apr '13

03 Apr '13

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=450331 Summary: lack of documentation on restoring from bare-metal (UUID problem) Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: docs-requests AssignedTo: kwade(a)redhat.com ReportedBy: czar(a)acm.org QAContact: stickster(a)gmail.com CC: fedora-docs-list(a)redhat.com Description of problem: ref: https://bugzilla.redhat.com/show_bug.cgi?id=449299 There is a lack of documentation on restoring a system from bare metal. I have found (see reference) that restore the root ("/") is not as simple as as just executing the restore command when running in rescue mode. With the current emphasis being place on use of UUIDs in both Fedora and RHEL, the whole business of UUIDs need to be better documented. Version-Release number of selected component (if applicable): Fedora 9 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 14

install guide notes: bootloader
by Adam Williamson 04 Dec '12

04 Dec '12

Hey, folks (Jack especially). I have it on my (very long) todo list to look through the changes to the installation guide and see if I can contribute anything, but we were talking about this in #anaconda this morning and I thought I'd outline it for the install guide before I forget the plan again. Handling of bootloader install is somewhat different in newUI. This is all about BIOS - UEFI is completely different. So what newUI is capable of is either installing the bootloader to a partition MBR, or not installing the bootloader at all. Currently there is no option to install bootloader to a partition, which was possible in oldUI. Installing the bootloader to a partition is done only by those who multiboot various OSes using a 'chainload' system - they have a bootloader in the MBR which 'chainloads' bootloaders for each of their OSes, each of which resides in the / or /boot partition for that OS. The plan is for those who have such setups to just not install a bootloader at all, and then do their bootloader configuration manually post-install. Anyone who for some reason doesn't want a bootloader installed to an MBR gets to do their own configuration. In the UI you are able to specify which disk the bootloader should be installed to (or that it shouldn't be installed at all). You do this on the 'disk selection' screen - the first screen you see after clicking on the 'Installation Destination' spoke. You have to click on 'Full disk summary and options...' and you get a dialog that lets you pick the target disk for the bootloader. To set it to not install a bootloader at all, right now, this is the procedure: "highlight whatever disk has the bootloader check, click the button, and it'll unset that device for receiving the bootloader. Thus, you should not get a bootloader installed." clumens notes that this isn't the best UI, but changing it would break string freeze. See https://bugzilla.redhat.com/show_bug.cgi?id=867469 for details. If you do not select a target disk, anaconda will default to installing the bootloader to the MBR of the first disk (of those selected as 'install target disks' on the picker screen) that appears to be a viable target, in enumeration order (so it'll try sda, then sdb, then sdc, and so on, and the first one which passes the 'bootloader target' tests gets the bootloader). This part is unchanged from F17. Hope that's useful! Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs November 2012