docs March 2012

docs@lists.fedoraproject.org

17 participants
27 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 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 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

[Bug 595695] New: Direct links to RNs broken.
by Red Hat Bugzilla 31 Aug '12

31 Aug '12

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Direct links to RNs broken. https://bugzilla.redhat.com/show_bug.cgi?id=595695 Summary: Direct links to RNs broken. 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: eric(a)christensenplace.us QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com Classification: Fedora Description of problem: * Previously, the release notes were located at http://docs.fedoraproject.org/release-notes/ * Their location has changed to release specific URLs. * A link to the release notes is provided in fedora-bookmarks. * fedora-bookmarks are imported by the browser only on *first launch* so as to not overwrite user modifications. The new bookmarks layout causes two problems: 1. Nobody filed a fedora-bookmarks bug so Fedora 13 (and anyone on F-11 or F-12 etc) will default to going to http://docs.fedoraproject.org/release-notes/ which is a 404. Since the bookmarks can only be imported on first launch, we cannot push an update to fix this if the user has launched the browser (which is extremely likely). 2. Even if I were to fix the bookmarks page to point directly to a specific release version (which again would take effect only if someone would yum update before launching Firefox), then if anyone updated to F-14, the bookmark would not change and would still point to e.g. F-13. So, I do not think that we should put version specific information into our bookmarks URLs. To solve both of the above problems, I believe we should try to do some User-Agent detection and redirection. Fedora browsers have an RPM NVR attached to them. For example: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.4) Gecko/20100517 Fedora/3.6.4-1.fc13 Firefox/3.6.4 This tells us that the user's installed language is es-ES and it's a Fedora browser, specifically running F-13. We should then redirect queries to http://docs.fedoraproject.org/release-notes/ to http://docs.fedoraproject.org/es-ES/Fedora/13/html/Release_Notes/index.html If we cannot figure any information out about the Fedora release or language (or there are no relnotes in that language), I propose the default redirect should be to the en-US version of the latest Fedora release notes. -- 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

Installation Quick Start Guide
by Daniel Cabrera 08 Apr '12

08 Apr '12

Hi guys, A couple of questions about this guide: (i) In tx.net for the Spanish translations we are using the language code 'es', but this guide is using 'es_ES'. I pulled all the 'es_ES' translations, copied them into an 'es-ES' folder inside the guide directory, but when I tried to upload them into tx.net as 'es' ($ tx push -t -l es), I get this error: Warning: No mapping found for language code 'es-ES'. KeyError: 'es-ES' ii) After cloning the repo of this guide [2], there are 114 *.xml 'en-US' files against 84 resources in tx.net. Is this correct? [1] http://fedora.transifex.net/projects/p/fedora-ins-quick-start-guide/ [2] http://git.fedorahosted.org/git/?p=docs/installation-quick-start-guide.git Regards, logan

2 2

Anaconda logging in Installation guide
by Pete Travis 29 Mar '12

29 Mar '12

Hey Jack, I've been thinking more about expanding the logging features covered in the IG. Currently, this is addressed in adminoptions.xml, along with boot options, but I think the breadth of information available justifies breaking out logging into it's own set of files: 1)intro and includes 2)log types, loglevels, formats 3)runtime logs and post-install files 4)serial console / logging 5)rsyslog, examples 6)virtio logging, examples The wiki page is fairly comprehensive, so I think I can work it out over the weekend. Any thoughts on this structure? --Pete

2 2

Updated Release Noter
by John J. McDonough 28 Mar '12

28 Mar '12

I would like to have the updated release notes available on the repos for F17 Beta release, so please, give karma! https://admin.fedoraproject.org/updates/fedora-release-notes-16.96.0-1.fc17 - Added list of writers - Added Desktop section - Added index entries - Added note on btrfs Thanks --McD

1 1

A random laundry list of some significant f17 changes that should be documented
by Adam Williamson 28 Mar '12

28 Mar '12

Hey, guys. I would love to do the right thing and actually write this stuff up and submit it properly, but I'm kind of overwhelmed at the moment and just wanted to dump it somewhere quick and hope it winds up in the right documentation :/ Much of this probably needs to go in the Release Notes, Install Guide, or both. I haven't checked at all if you've actually already done this, so apologies if it's already covered. Note that I could be somewhat wrong in my understanding of any of this stuff. If you're at all confused or thinking 'that doesn't sound right', poke Brian Lane (bcl on IRC) for clarification. CCing Brian so he can correct any really egregious mistakes in the below. # btrfs is not available as a target filesystem for installation in F17: https://bugzilla.redhat.com/show_bug.cgi?id=787341 . This is temporary. What happened is clumens rewrote the storage backend to handle btrfs much better, with support for its native volume management and mirroring / striping and all its other cool features. The plan was that the UI for this would be part of the big anaconda UI rewrite. However, the UI rewrite got delayed to F18. So F17 has the new backend but old UI code from the time when the backend treated btrfs as just a fairly 'dumb' filesystem like ext4. That combination results in a hard crash when trying to use btrfs at all. Instead of trying to revert the storage backend or hurriedly write new UI for btrfs in the old UI code, anaconda team decided to just disable btrfs support for one release. # The big 'noloader' change - https://fedoraproject.org/wiki/Anaconda/Features/NoLoader - has some consequences, many are documented at that feature page. the 'askmethod' parameter you used to be able to pass to anaconda so it would let you interactively select a remote repository during stage1 from which you could download stage2 and also packages for installation is now gone; with the new anaconda design it just doesn't fit in any more. there really isn't a stage split in anaconda any more, there's no 'mini-anaconda' that runs first in text mode and which could prompt you for where to get its bigger brother. So the remaining methods of repository selection are to use the 'repo=' parameter (or 'inst.repo=') at boot time or to do it interactively during the package selection phase of the install. If you're doing a direct kernel boot and need to pull anaconda itself from the network, the 'repo=' parameter is used to say where to find it. See https://bugzilla.redhat.com/show_bug.cgi?id=804506 and https://bugzilla.redhat.com/show_bug.cgi?id=805166 . Similar for 'asknetwork'. # Lots of anaconda parameters are spitting out a deprecation message saying that in future they should be prefixed with inst. e.g. passing 'repo=XXX' will spit out a message saying you should use 'inst.repo=XXX'. Brian, didn't we find that inst.repo was actually broken in some cases where repo= works, though? Or is that fixed now, and the notes should encourage people to use inst.foo forthwith? # This isn't actually new but it's something the Install Guide currently doesn't cover and should. The section on creating media with dd - https://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/Maki… - should note that, if you dd a DVD image to a USB stick, unless you pass a 'repo=hd:' parameter (or possibly 'inst.repo=hd:', see above...) pointing to the stick in some way (UUID, expected mount point, label, whatever), the stick will act like the boot.iso. That is, it won't actually use the packages on the stick. It'll require a network connection, and pull in all the packages remotely. If you use livecd-iso-to-disk (which really ought to get renamed...) to write the DVD ISO to a stick, it adds a repo= parameter to the config for you, which is one reason it's better to use l-i-t-d. # Bill Nottingham and I, somewhat sneakily, stuck NetworkManager into @core last week. Amazingly, the torch-and-pitchfork-bearing mob has not yet found us. See https://bugzilla.redhat.com/show_bug.cgi?id=693602 for details, including ass-covering statistics on why we did this (so the network actually freaking works out of the box on a minimal install), how many additional packages this causes to be installed (not many) and how much extra disk space it causes to be used (not much). You should still be able to install without NetworkManager if you really, really want to, by using a kickstart in which it's specifically excluded in the %packages section, and you can still 'yum remove' it. I feel like I had other things to mention but I forget them now. If they come to mind, I'll send another mail. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs March 2012