docs November 2011

docs@lists.fedoraproject.org

32 participants
50 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

Proposal for a new process for publishing Fedora docs translations
by Petr Kovar 17 Jan '12

17 Jan '12

Hi Fedora docs translators and writers, After a discussion with shaiton following today's Fedora docs meeting, I propose to formalize the process of publishing Fedora docs translations. BACKGROUND Currently, we don't have in place a formal process for publishing docs translations. This means that we don't make it clear enough to our guide owners and translators what and when should be published. PROPOSAL The proposal is to create a new Bugzilla component and a group of default assignees for publishing translations to docs.fedoraproject.org. The group is consisted of members of the docs-publishers group (and possibly also other people interested). To get the translations published, Fedora translators are first required to file a bug against the proposed component. This applies to any translation of any document hosted on docs.fedoraproject.org. Then the members of the proposed group resolve the bug by publishing the requested translation. RATIONALE By using Bugzilla for the purposes of publishing translations, we can easily keep track of what translations the translators actually want to publish, at what time, and who is working with translators on publishing the translations. This makes the whole publishing process much more transparent. At the same time, we satisfy the demand from some of our community members to integrate the Bugzilla tool more deeply into our docs workflow. To reduce a maintenance burden for individual docs owners, translators don't file a bug directly against the relevant guide component in the Fedora Documentation product. REQUIREMENTS FOR TRANSLATORS This requires each of the Fedora translation teams to have at least one member communicating with the proposed docs publishers group in Bugzilla. However, translators don't have to learn new tools and rather complex processes specifically for Fedora docs, like working with Git, setting up an environment for syncing translations between Transifex.net and Git, or publishing to docs.fedoraproject.org with Publican. NOTE This proposal doesn't necessarily affect the translation teams that are already publishing their docs translations. They can continue with their existing workflow if it suits them and they have the manpower to do so. In other words, this proposed process is completely optional for them. COMMENTS Your comments, thoughts, or ideas are most welcome! Thanks, Petr Kovar

11 13

Re: [web] Added Burning ISOs Readme
by Tadashi Jokagi 11 Jan '12

11 Jan '12

Hi Eric, (2011/11/08 23:12), Eric Christensen wrote: > commit 5be99fa3211845582d57caa7018e12116f25c872 > Author: Eric 'Sparks' Christensen<sparks(a)fedoraproject.org> > Date: Tue Nov 8 09:11:28 2011 -0500 > > Added Burning ISOs Readme I tried creation of ja-JP version. However, I can create only the Draft version. publican was not output the error during work. Don't you understand causes? ===== Cut Here ===== Cut Here ===== Cut Here ===== Cut Here ===== $ git clone ssh://git.fedorahosted.org/git/docs/readme-burning-isos.git Initialized empty Git repository in /home/elf/workspaces/oss/fedora/docs/f16/a/readme-burning-isos/.git/ Enter passphrase for key '/home/elf/.ssh/id_rsa': remote: Counting objects: 6018, done. remote: Compressing objects: 100% (1570/1570), done. remote: Total 6018 (delta 4602), reused 5818 (delta 4439) Receiving objects: 100% (6018/6018), 8.22 MiB | 2.06 MiB/s, done. Resolving deltas: 100% (4602/4602), done. $ cd readme-burning-isos/ $ git checkout f16 Branch f16 set up to track remote branch f16 from origin. Switched to a new branch 'f16' $ tx pull -l ja Pulling new translations for resource fedora-readme-burning-isos.Validating (source: pot/Validating.pot) -> ja: ja-JP/Validating.po Pulling new translations for resource fedora-readme-burning-isos.Introduction (source: pot/Introduction.pot) -> ja: ja-JP/Introduction.po Pulling new translations for resource fedora-readme-burning-isos.Next (source: pot/Next.pot) -> ja: ja-JP/Next.po Pulling new translations for resource fedora-readme-burning-isos.Article_Info (source: pot/Article_Info.pot) -> ja: ja-JP/Article_Info.po Pulling new translations for resource fedora-readme-burning-isos.Downloading (source: pot/Downloading.pot) -> ja: ja-JP/Downloading.po Pulling new translations for resource fedora-readme-burning-isos.Revision_History (source: pot/Revision_History.pot) -> ja: ja-JP/Revision_History.po Pulling new translations for resource fedora-readme-burning-isos.Author_Group (source: pot/Author_Group.pot) -> ja: ja-JP/Author_Group.po Pulling new translations for resource fedora-readme-burning-isos.Burning (source: pot/Burning.pot) -> ja: ja-JP/Burning.po Pulling new translations for resource fedora-readme-burning-isos.Burning_ISO_images_to_disc (source: pot/Burning_ISO_images_to_disc.pot) -> ja: ja-JP/Burning_ISO_images_to_disc.po Done. $ publican build --embedtoc --publish --formats epub,html,html-single,pdf --langs ja-JP --QUIET Writing OEBPS/sect-Burning_ISO_images_to_disc-Downloading.html for section(sect-Burning_ISO_images_to_disc-Downloading) Writing OEBPS/sect-Burning_ISO_images_to_disc-Validating_the_Files.html for section(sect-Burning_ISO_images_to_disc-Validating_the_Files) Writing OEBPS/sect-Burning_ISO_images_to_disc-Burning.html for section(sect-Burning_ISO_images_to_disc-Burning) Writing OEBPS/sect-Burning_ISO_images_to_disc-Next_steps.html for section(sect-Burning_ISO_images_to_disc-Next_steps) Writing OEBPS/ar01s06.html for section Writing OEBPS/appe-Burning_ISO_images_to_disc-Revision_History.html for appendix(appe-Burning_ISO_images_to_disc-Revision_History) Writing OEBPS/index.html for article Writing OEBPS/toc.ncx Writing OEBPS/content.opf Writing META-INF/container.xml Writing sect-Burning_ISO_images_to_disc-Downloading-Choosing_the_ISO_Files.html for section(sect-Burning_ISO_images_to_disc-Downloading-Choosing_the_ISO_Files) Writing sect-Burning_ISO_images_to_disc-Downloading.html for section(sect-Burning_ISO_images_to_disc-Downloading) Writing sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_at_the_Windows_Command_Prompt.html for section(sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_at_the_Windows_Command_Prompt) Writing sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_in_Mac_OS_X.html for section(sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_in_Mac_OS_X) Writing sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_in_Linux.html for section(sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_in_Linux) Writing sect-Burning_ISO_images_to_disc-Validating_the_Files.html for section(sect-Burning_ISO_images_to_disc-Validating_the_Files) Writing sect-Burning_ISO_images_to_disc-Burning-OSX.html for section(sect-Burning_ISO_images_to_disc-Burning-OSX) Writing sect-Burning_ISO_images_to_disc-Burning-Linux-K3b.html for section(sect-Burning_ISO_images_to_disc-Burning-Linux-K3b) Writing sect-Burning_ISO_images_to_disc-Burning-Linux-Brasero.html for section(sect-Burning_ISO_images_to_disc-Burning-Linux-Brasero) Writing sec-Burning_ISO_images_to_disc-Burning-cmd-line.html for section(sec-Burning_ISO_images_to_disc-Burning-cmd-line) Writing sect-Burning_ISO_images_to_disc-Burning-Linux.html for section(sect-Burning_ISO_images_to_disc-Burning-Linux) Writing sect-Burning_ISO_images_to_disc-Burning.html for section(sect-Burning_ISO_images_to_disc-Burning) Writing sect-Burning_ISO_images_to_disc-Next_steps.html for section(sect-Burning_ISO_images_to_disc-Next_steps) Writing ar01s06.html for section Writing appe-Burning_ISO_images_to_disc-Revision_History.html for appendix(appe-Burning_ISO_images_to_disc-Revision_History) Writing index.html for article Making portrait pages on A4 paper (210mmx297mm) Nov 13, 2011 10:11:29 AM org.apache.fop.apps.FopFactoryConfigurator configure INFO: Default page-height set to: 240mm Nov 13, 2011 10:11:29 AM org.apache.fop.apps.FopFactoryConfigurator configure INFO: Default page-width set to: 120mm Nov 13, 2011 10:11:32 AM org.apache.fop.fonts.FontInfo notifyFontReplacement WARNING: Font 'IPAPGothic,normal,700' not found. Substituting with 'IPAPGothic,normal,400'. Nov 13, 2011 10:11:32 AM org.apache.fop.fonts.FontInfo notifyFontReplacement WARNING: Font 'Symbol,normal,700' not found. Substituting with 'Symbol,normal,400'. Nov 13, 2011 10:11:32 AM org.apache.fop.fonts.FontInfo notifyFontReplacement WARNING: Font 'ZapfDingbats,normal,700' not found. Substituting with 'ZapfDingbats,normal,400'. Nov 13, 2011 10:11:32 AM org.apache.fop.hyphenation.Hyphenator getHyphenationTree SEVERE: Couldn't find hyphenation pattern ja Nov 13, 2011 10:11:32 AM org.apache.fop.fonts.FontInfo notifyFontReplacement WARNING: Font 'ZapfDingbats,italic,400' not found. Substituting with 'ZapfDingbats,normal,400'. Nov 13, 2011 10:11:33 AM org.apache.fop.fonts.FontInfo notifyFontReplacement WARNING: Font 'IPAGothic,normal,700' not found. Substituting with 'IPAGothic,normal,400'. Nov 13, 2011 10:11:34 AM org.apache.fop.layoutmgr.table.TableLayoutManager getNextKnuthElements INFO: table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%" $ ls -lad publish/ja-JP/*/*/*/Burning_ISO_images_to_disc drwxrwxr-x 2 elf elf 4096 Nov 13 08:02 publish/ja-JP/Fedora/0.1/epub/Burning_ISO_images_to_disc drwxrwxr-x 4 elf elf 4096 Nov 13 08:02 publish/ja-JP/Fedora/0.1/html-single/Burning_ISO_images_to_disc drwxrwxr-x 4 elf elf 4096 Nov 13 08:02 publish/ja-JP/Fedora/0.1/html/Burning_ISO_images_to_disc drwxrwxr-x 2 elf elf 4096 Nov 13 08:02 publish/ja-JP/Fedora/0.1/pdf/Burning_ISO_images_to_disc ===== Cut Here ===== Cut Here ===== Cut Here ===== Cut Here ===== Regards, -- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi mailto:elf@elf.no-ip.org Twitter: http://bit.ly/a4DzKL Yokukitana III http://poyo.jp/ Yokukita blog http://blog.poyo.jp/ Yokukita wiki http://wiki.poyo.jp/ HotPHPPER News http://news.hotphppher.net/

2 2

[Bug 746672] New: typo: QEMU should be uppercase
by Red Hat Bugzilla 10 Jan '12

10 Jan '12

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: typo: QEMU should be uppercase https://bugzilla.redhat.com/show_bug.cgi?id=746672 Summary: typo: QEMU should be uppercase 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: --- In Virtualization.xml, I read Virtualization.xml: <primary>qemu</primary> Virtualization.xml: Update to qemu 0.15, refer upstream changes at <ulink Virtualization.xml: Xen support merged into qemu All QEMU references should be uppercase. Of course, the package name and the binary is lowercase. Please check qemu.org -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

Resource Management Guide and Cloud Guide
by Noriko Mizumoto 17 Dec '11

17 Dec '11

Hi Docs team Japanese team is looking at to translate the above guides. I can not locate Resource Manage Guide in Transifex. Can you point where to find? For Fedora Cloud Guide, I can see; https://www.transifex.net/projects/p/fedora-cloud-guide/r/all-resources/l/j…. Is this right place to download POs for translation? thanks noriko (2011年08月01日 00:11), Motohiro Kanda wrote: > 夏休みに気が向いたら、Resource Management Guide　と　Cloud Guide でも訳すか、 > と思いましたが、前者は、 transifex プロジェクトがない、後者は、 > https://www.transifex.net/projects/p/fedora-cloud-guide/r/all-resources/l/j… > それらしいのがあるけど、中身がない、 > 状態です。どなたか、PO ファイルを用意してもらえませんか。あるいは、誰にどう、 > コンタクトすればよいか教えて下さい。 >

7 19

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 2011