docs February 2009

docs@lists.fedoraproject.org

36 participants
62 discussions

[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 479470] New: cobbler kssendmac and breed suse
by Red Hat Bugzilla 05 Aug '09

05 Aug '09

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: cobbler kssendmac and breed suse https://bugzilla.redhat.com/show_bug.cgi?id=479470 Summary: cobbler kssendmac and breed suse Product: Fedora Hosted Projects Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: Deployment_Guide AssignedTo: mhideo(a)redhat.com ReportedBy: quenzler(a)us.ibm.com QAContact: rlerch(a)redhat.com CC: fedora-docs-list(a)redhat.com Classification: Fedora Target Release: --- Description of problem: breed = suse /boot/grub/menu.lst contains kssendmac Version-Release number of selected component (if applicable): cobbler-1.2.9-1.fc9.noarch How reproducible: Install a SuSE client Actual results: kssendmac exists as a boot parameter on a SuSE client Expected results: No kssendmac boot parameter Additional info: Find a way to avoid adding kssendmac to the kernel_options string if it's not applicable to the breed. Hack (since I'm only installing SuSE clients): # diff utils.py utils.py.ori 478,479c478,479 < # if len(kernel_txt) < 244: < # results["kernel_options"]["kssendmac"] = None --- > if len(kernel_txt) < 244: > results["kernel_options"]["kssendmac"] = None -- 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.

1 4

[Fedora Release Notes] #29: Remove whitespace trigger ugly PDF formatting
by fedora-badges 02 May '09

02 May '09

#29: Remove whitespace trigger ugly PDF formatting ---------------------+------------------------------------------------------ Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: RC-ready Component: Content | Version: 10 Keywords: | ---------------------+------------------------------------------------------ Just in case we cannot get this fixed in the PDF toolchain, we need to remove all the leading whitespace for tags that display CDATA or other content verbatim. This could be done as part of a general run of a tool such as docbook-lint or xmlformat. Before doing that, we need to assess the risk of the tool chaining line numbers and causing translation stats to go fuzzy. -- Ticket URL: <https://fedorahosted.org/release-notes/ticket/29> Fedora Release Notes <https://fedorahosted.org/release-notes/> Fedora Release Notes

2 4

[Fedora Release Notes] #30: Links to Feature pages for all features discussed
by fedora-badges 02 May '09

02 May '09

#30: Links to Feature pages for all features discussed ---------------------+------------------------------------------------------ Reporter: quaid | Owner: quaid Type: task | Status: new Priority: major | Milestone: PR-ready Component: Content | Version: 10 Keywords: | ---------------------+------------------------------------------------------ ... even the features that weren't complete but still have useful content. We were inconsistent with this. Hopefully we can just tag a <para><ulink/></para> block on the end without disturbing the l10n stats. -- Ticket URL: <https://fedorahosted.org/release-notes/ticket/30> Fedora Release Notes <https://fedorahosted.org/release-notes/> Fedora Release Notes

2 1

Re: Linux Start Pack Review
by A. Mani 28 Feb '09

28 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christos Bacharakis <cmpahar(a)gmail.com> wrote: >> I read over the Linux Start Pack at >> http://www.tuxradar.com/linuxstarterpack . >> This magazine is published by Linux Format. >> > What is a user guide? Maybe some docs putted and linked together in a form > which is more friendly with screenshots and tips? > I think there is a huge power at Docs and L10n project and the material is > really good. So, for start we can try to put together all the stuff and > reconfigure it (screenshots, tips) in a more "user friendly" way. > If we have good written, user friendly docs in many languages we don't have > to do something from scratch. There is a big difference between a user guide for people new to Linux and PCs, documentation for others and a starter pack for migrating users from other OSs. As it is the user guide has plenty of references to 'things in M$Windows'. I think it will be a better idea to transfer those to a starter pack. The user guide can then be used by people new to Linux and PCs ...or should we split the latter function as well? >> It would be large project but worthwhile for getting >> the word out about Fedora. > > > Small touches, small entries and the guide will be ready on a sec! :) Many parts require modification. It is biased towards Gnome. Best A. Mani -- A. Mani Member, Cal. Math. Soc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmqx/gACgkQunMISzvdfU6QigCfXHXT5KLW3O2F80EDNyOwk4pw 0cYAmwVqjluOBdY23h7sQjC9SvHFwM40 =G+iY -----END PGP SIGNATURE-----

1 0

Steps for Thunderbird migration from Windows Vista to Fedora
by Kirk 27 Feb '09

27 Feb '09

I've written the steps needed to migrate Thunderbird Profile Data from Windows XP. I don't have access to Vista. Could someone read over this section for me that's more familiar with Vista and let me know if different steps are required? https://fedoraproject.org/wiki/User_Guide_-_Communications#Moving_Your_Thun… Thanks, -Kirk

4 8

Linux Start Pack Review
by Kirk 27 Feb '09

27 Feb '09

I read over the Linux Start Pack at http://www.tuxradar.com/linuxstarterpack . This magazine is published by Linux Format. I liked it because its very user-friendly, therefore, a good sales tool for people thinking about switching from Windows to Linux. The majority of the article is a comprehensive User Guide. The magazine came with a Live CD for Ubuntu so folks could follow along with the user guide and really get a feel for Linux and the distro. The article is 130 pages with about 85% - 90% being the user guide. We should consider doing something like this when we can. We could follow a similar format and put it out in magazine form, if we have the resources, put it on the web, or both. It would be large project but worthwhile for getting the word out about Fedora. Browse through it if you get a chance and see what you think. -Kirk

2 1

Install Guide now in Publican
by Ruediger Landmann 27 Feb '09

27 Feb '09

Hey all, just letting you know that the Installation Guide is now fully "Publicanized". I can confirm that every language version of the guide builds in html, html-single, and PDF, with only one exception -- Chinese Simplified. I /can/ confirm that Chinese Simplified builds in html and html-single, but I haven't been able to confirm that it builds in PDF [1]. RPM building also works. I've placed the publicanized version of the guide in the master branch of the repo, and the f10 version in its own branch. There are small structural changes between the f10 version of the files and the files in the current master branch, specifically: * the Guide now includes Publican's standard Preface, which explains the typographic conventions used in the document * by default, Publican places the "Feedback" section in the Preface, so I've moved it there from its previous position in the "Introduction" * the "Colophon" wasn't really a colophon; I've renamed it to "Contributors and production methods", which is what it actually contains. The "Contributors" section within this now includes a full list of the community translators who have worked on the guide (I drew these from the translation files). * the Tamil translation file didn't actually contain any translations; I've removed it for the moment. * I've removed most of the entities that were used in the document; not only were they a real mess, but they were going to create significant problems when positioning the guide upstream of the RHEL Installation Guide * I've added country codes to folders containing translation files for certain languages, so Publican can take advantage of the Common Content already built into Publican for these languages. Note that these folders are named according to the IETF RFC 4646 standard that XML uses for language and country codes, not the GNU hybrid of "ISO 639-2 language code and two-letter ISO 3166 country code separated by an underscore". Publican expects to see the RFC 4646 version. I'm aware that the inclusion of a country code is a contentious area for some translators, and have filed a bug about this [2]. Note that this issue doesn't presently affect languages that we don't have any Common Content for, but I've also renamed the Serbian-with-Latin-alphabet folder in compliance with RFC 4646. Some urgent action is now needed on the localization front: * f10 needs to be presented as a valid branch in the Transifex system; and the separate .po files of the Publicanized version need to be made available to translators * Publican includes two "Common Content" files that need translation into languages that Red Hat doesn't support. They are "Conventions" (which explains the document conventions) and "Feedback" [3]. The great news here is that once these have been translated into any given language, they will be available for /all/ Publicanized Fedora docs produced in that language, since the .po files can be built into the Fedora brand that installs with Publican. I've generated .pot files for these three sections. Other than approaching translators directly, is there another way to bring these to community attention? On the RPM front: * What needs to happen to get an RPM of this document approved for inclusion in Fedora? What I'm doing next: * working out how content can be merged between the Fedora and Red Hat Enterprise Linux Installation Guides, which will allow the Fedora version to be positioned upstream Cheers Rudi [1] on my machine, the build process finishes successfully and generates a PDF file, but the body text contains nothing but whitespace (although the chapter and section headings render correctly). I suspect this is simply a problem on my machine, however, and haven't tested it on anyone else's yet. [2] https://bugzilla.redhat.com/show_bug.cgi?id=487256 [3] the Installation Guide doesn't use the Common "Feedback" section – it has its own, custom "Feedback" section instead. We still need to get this translated into as many languages as possible ASAP, both for the sake of other Fedora Docs, and in case we want future versions of the Installation Guide to line up with what's in the docs that /are/ using the standard "Feedback" section.

4 8

Linux Starter Pack
by Kirk 26 Feb '09

26 Feb '09

1 0

Docs team meeting 2009-02-25 summary
by Karsten Wade 25 Feb '09

25 Feb '09

Attendees ========= John J. McDonough (jjmcd) Kirk Ziegler (kirkz) Karsten Wade (quaid) Paul W. Frields (stickster) Susan Lauber (laubersm) Matthew Daniels (danielsmw) Simon Birtwistle (itbegins_) Toshio Kuratomi (abadger1999) IRC log ======= https://fedoraproject.org/wiki/Meeting:Docs_IRC_log_20090225 http://www.redhat.com/archives/fedora-docs-list/2009-February/msg00170.html Summary ======= * New meeting time * 0000 UTC Thu. == 1600 PST Wed. == 1900 EST Wed. == 1000 BNE Thu. * Starting 05 March 0000 UTC (04 March) * Need to confirm that this can work for ryanlerch * FIXED TIME -- Does not change with daylight savings time in a few weeks * Feature freeze is next week * https://fedoraproject.org/wiki/Category:Docs_Project * Progress made on [[Docs Project]] * The file docsproject.psv was cleaned and found useful * More work to be done, not difficult just tedious ** Help wanted * A clean PSV == potentially good wikibot results * wikibot would have been a big tedium breaker ** Need wikibot for wider adoption of page renaming * Package maintainer and draft pages are proceeding * Marketing is working on their pages, also a focus on [[*Events]] by StabbyMc (Scott McBrien) * CMS packaging is moving ahead, ke4qqq needs to update his review request * itbegins may use some help with theme/CSS finishing; taking it to fedora-websites-list if he needs it * Packaging needed to reinstall test instance * itbegins still needs to do the docs build scripts * Docs can potentially start loading content and structure, have it appear live in the final production instance * Release notes * F10 update help needed; jjmcd to work with quaid on CVS check-in issues * Recruitment plan for new beat writers? ** 18 March is the next release team meeting, good time to ask for beat help where we've already tried other methods

1 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 February 2009