docs January 2009

docs@lists.stg.fedoraproject.org

45 participants
80 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

Fedora 11 Schedules
by John Poelstra 03 Feb '09

03 Feb '09

I have complete a draft of the translation schedule for Fedora 11. It is based on the documentation schedule (which to date I have not received any feedback). http://poelstra.fedorapeople.org/schedules/f-11/f-11-trans-tasks.html http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html A new report I am still ironing out (huge credit goes to Ben Kahn for creating it for me) is a combined view of the Docs and Translations schedule with different color codings for each team. http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-and-trans-tasks.h… Please review the reports in detail to make sure I have the correct dates and task durations. If you like we can schedule a time to meet on IRC or phone to work out any remaining changes. We will also touch on some of these tasks at the release readiness meeting. If I do not hear any feedback by Monday, February 2, 2009, I will assume that both the Documentation and Translation schedules are correct. Thanks, John

4 6

CMS discussions yet again
by David Nalley 03 Feb '09

03 Feb '09

Sparks, jsmith and I were talking in IRC and I thought the conversation should have a bit wider audience. I think that while kbase and housing documentation for packaging guidelines and legal are excellent use cases for a CMS, I wonder if by trying to use it for everything we are not trying to use a hammer to drive a screw. My reason for saying that is that it seems like we are trying to push all of our non-wiki documentation into the CMS, which at least from my perspectives means we, to one degree or another, are abandoning DocBook. For our 'heavy' documents, such as Release Notes, User Guide, and Security Guide, I don't see an escape from DocBook - it provides a lot of advantages that just don't exist in a CMS. It does have disadvantages to be sure, but I guess the question in my mind is with all of the talk of moving to a CMS are we really prepared to ditch DocBook and it's benefits? Or is the CMS a solution for things like Legal and Packaging Guidelines, and potentially a knowledgebase, and not more? Thoughts, Comments, Flames?

7 9

F11 Release Notes Beat Writers
by Eric Christensen 03 Feb '09

03 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's that time of year, again! Time to hit the streets to get all the new Fedora goodness documented! There are two kinds of people receiving this message. The first kind of recipient are those that had a beat assignment for F10. If you are one of these please go over to the wiki[1] and verify that your assignment is still correct. While you are over there please remove the "*" from your name so we know you are still on board. The second kind of recipient are those that were not on the beat list but probably should be. If you are one of these please go over to the wiki[1] and sign up for one of the open slots. Don't wait around because the best slots go fast! [1] https://fedoraproject.org/wiki/Documentation_Beats Thanks, Eric Christensen E-Mail: sparks(a)fedoraproject.org GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl2Zz4ACgkQfQTSQL0MFMGY0gCfSTpt7D3Bzli8wzbh4Mr5gFBA lsEAnjLFKUkzBjWUaLyAV86VtGFn/3qY =6xb4 -----END PGP SIGNATURE-----

5 5

Preparing for F11 Release Notes
by John J. McDonough 02 Feb '09

02 Feb '09

In going through the wiki removing hash marks, I noticed that there are a number of places where there is content that we want to keep for F11, so I guess we probably don't want to be too reckless in the pre-F11 cleanup. On the other hand, I was reminded while doing that is that one reason that we may want to issue an F10 update is that some F9 content, which was inappropriate for F10, made it into the F10 release notes. So we definitely want to be a little more thorough in our scrubbing. --McD

6 11

PackageMaintainers wiki cleanup update
by Susan Lauber 31 Jan '09

31 Jan '09

Greetings to the authors/maintainers of Package Maintainer wiki pages, I introduced myself last week [1] and since then I have dug into the pages and set up a task table [2] I have already added a category to most pages so they can all be found together [3]. If there are others or if you create a new page just add the string [[Category:Package Maintainers]] to the bottom of the page. The next step is renaming so that pages are easier to find in a search. It will also make the category page easier to use. I have started making suggested in the packagemaintainers.psv [4] file in the wikirename.git repo and ***I encourage others to check the proposed names and offer additional suggestions.*** I would like to have this file ready for the wikibot by the end of the week (Feb 7). Lack of response will be seen as a vote of confidence :) Thanks, Susan [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01545.html [2] https://fedoraproject.org/wiki/Docs_tasks_for_Packaging_Guide_and_related_m… [3] https://fedoraproject.org/wiki/Category:Package_Maintainers [4] http://git.fedorahosted.org/git/?p=wikirename.git;a=blob_plain;f=packagemai… with naming instructions at https://fedoraproject.org/wiki/Help:Wiki_structure -- Susan Lauber, (RHCX, RHCA, RHCSS) Lauber System Solutions, Inc. http://www.laubersolutions.com gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974

1 0

Docs Project contributor group in FAS
by Eric Christensen 31 Jan '09

31 Jan '09

If you are a member of the Docs Project please make sure you are in the Docs Project contributor group in FAS. If you have any problems with this please contact me. Thanks, Eric Christensen Fedora Docs Project Fedora Talk: 5102043 Phone: 919-424-0063 x 5102043 E-Mail/SIP Address: sparks(a)fedoraproject.org IRC: Sparks on freenode.net GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1

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 January 2009