docs December 2008

docs@lists.fedoraproject.org

37 participants
69 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

[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

Man page coverage
by Basil Mohamed Gohar 04 Jan '09

04 Jan '09

I'm really sorry I'm so late on all of this, but just after Karsten admitted me to the Docs project, I caught a fever, cough, indigestion - the whole nine yards. Soon after I recovered, the submarine cables connecting Egypt (where I am for a few months) were cut, so we were having very unreliable Internet service for the following weekend. Anyway, excuses aside, the task I was hoping to tackle involved establishing a sub-project to do complete man-page coverage of existing packages & applications within Fedora. The discussion started over on the fedora-devel list, and it seemed that I was the most enthusiastic about undertaking the project, so that's what I'd like to propose, but here within the Docs project. I outlined a few general steps, and you can read up here: https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00023.ht… To save you a trip, I'll repost the steps here: 1) Identify which packages are missing man pages altogether in Fedora -- these should get top priority -- we can see if Debian or other projects already have some -- acceptable-licensing-pending, of course 2) Identify which packages having sub-par man pages -- after fulfilling 1), this should be the next priority -- similar methodology to 1), find ones that already exist first 3) Develop a "stub" template for packages that have no man pages available -- at least we can include command-line arguments, authorship, web links for more info, etc. -- at first this isn't much better than -h/--help, but we can at least let it be a start 4) Once we have all of this information prepared, then we can get to work on forming a project around this group, preparing a page in the wiki with the packages that need man pages or whose man pages need improvement, etc. 5) ??? 6) Profit! So, right now, I'm very green when it comes to working on open-source projects. I've been using Fedora for a while, but I still can be somewhat ignorant when it comes to doing some things. I'm a PHP developer by trade, so I'm not clueless, but you get my point. What I could use help with from the more experienced would be, for example, a way to identify the existence of man pages for packages. For example, is it enough to have a single man page for a package, or do we want a man page for every executable file? I'm willing to do a fair share of the work, but I also hope some others are willing to help out where they can as well. ;) Okay, that's enough for one e-mail. I just wanted to get the ball rolling and get started on some of these steps, and see what else anyone else would like to share in terms of ideas.

1 1

December 31st Hackfest Prep
by Matthew Daniels 31 Dec '08

31 Dec '08

According to the Hackfest page, December 31st is the scheduled day for the conversion for the F9 User Guide to XML. The transition to F9 for the User Guide in wiki form isn't totally done yet, but I'll be working on it tonight and hope to stay ahead of the tide tomorrow while they convert it. If anyone can let me know when we plan to do this conversion (time of day), that would be fantastic. Also, anyone who happens to be running F9 (which I'm not) is welcome to fact check the user guide for me. :-) -Matthew

2 2

Spark's New Crypto
by Eric Christensen 30 Dec '08

30 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tis the season for new crypto... - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.9 (GNU/Linux) mQGhBElaqs8RBADPMQoF/FANHsIhKdxwHmFqN1zeV7BuFURyKJJlbamfn6/uMRvy SSR1ydXbVTzXZ//5ihjPtBfT/nbiqhSpl1MeCdZFudM+FYMrBImYpuHTlNZJf04X QcNcm681Wa+huuoJ4TSsCbz52T2jnsqB8jeY9iVU0wpGNtiYmNtXkXmHmwCg04KO ViiFih5LF+YlmBTFeNBxHmcEAMC4vf+5kfip6fo/mPPHCQAz+Uz2AMoOQnhi5xtB /UGsghzKd+0riaDrdHWv45239mb7AtJWtQAIFzL3/AQwWQBkJaJFGrjRi40sy6wz aftZ0E5Pc96biISeqsZpqODiP2sGhJjneIBo8if3/K2DXatN04Yo77mKw44gLNMm O5bVA/d1y0E1BYLR9RXPEoeFNSzRmgmZX39gLOO4ol3ahkrxNKd/HVfXry/wFgN/ dqTqIwG2w/H0rSVIKaZzJb21eTCQv2OoBvA0zmZSyxMQSASQGOc2ffFNIQ9wC//j zaX6drNiembLQFiedfRuiD/zOIL2ve4lJG/QU9xMCHG1AUd9tDJFcmljIEhhcmxh biBDaHJpc3RlbnNlbiA8ZXJpY0BjaHJpc3RlbnNlbnBsYWNlLnVzPohmBBMRAgAm BQJJWqrPAhsDBQkB4oUABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQfQTSQL0M FMG7LwCfbCBeckFkuXML+kz1adUwyuSYY4QAniUEUGFs/226f7ODo1JUSbppHzM0 tEpFcmljIEhhcmxhbiBDaHJpc3RlbnNlbiwgVzRPVE4gKEFtYXRldXIgUmFkaW8p IDxyYWRpb0BjaHJpc3RlbnNlbnBsYWNlLnVzPohmBBMRAgAmBQJJWqz4AhsDBQkB 4oUABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQfQTSQL0MFMGl9gCeKlPQiGEq dO9HBx/5myNNrgwS1G8AoJV8t20qLMTvxrNJs2cTAIYCOUnHtENFcmljIEhhcmxh biBDaHJpc3RlbnNlbiwgTk5OMEhLRCAoTmF2eSBNQVJTKSA8bm5uMGhrZEBuYXZ5 bWFycy5vcmc+iGYEExECACYFAklarSMCGwMFCQHihQAGCwkIBwMCBBUCCAMEFgID AQIeAQIXgAAKCRB9BNJAvQwUwdQBAJ4yy1C1rL8rJ+pyKjsM662E09xX3wCfV6GA hz8wsncuXwPDZGTTbJZlbTm0V0VyaWMgSGFybGFuIENocmlzdGVuc2VuIChOZXdw b3J0IERpc3RyaWN0IFNLWVdBUk4gV2VibWFzdGVyKSA8d2VibWFzdGVyQG1oeHNr eXdhcm4ub3JnPohmBBMRAgAmBQJJWq1WAhsDBQkB4oUABgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQfQTSQL0MFMHn2gCfdv9ZkChOuxXJ5p5W8S2cZbW5CuYAoIHE CK0xql6IgCN7XRFKxMraLPnRtDRFcmljICJTcGFya3MiIENocmlzdGVuc2VuIDxz cGFya3NAZmVkb3JhcHJvamVjdC5vcmc+iGYEExECACYFAklarZwCGwMFCQHihQAG CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRB9BNJAvQwUwas8AJ4iQaRUTkU4kdyX JmJ0bmuD+DwpywCeNCFTJW+CsoeAp2difp1C6hse/Nm5Ag0ESVqqzxAIAKpo028j QVVgQOMQFoJq1ISaI8tD9fBRTHb5VzDjf0cD9+yO4va0frIuoFWmNmEWP0Ie/BLK pJApXuNl9hfPYmX0z+8R3SAnJ11Frk+q4BBjNave866xwxrfw2es+ClR3WhZNDZ2 Z37wpva5WRuqC5BxXLrktI4w4SrF8sdnz1p/+DNQFruMdFrvDRhl/AzRv6nZPRjO tt5EJTA48Zm5FSSuiuPw8DmOWjkYwct2c3wUpOkmPCmF9ZAspoDyKrxH1GXftwza x4RUO4U+eF4mTKn1R1MbDKoVKOsar+uDF5zgfxPyAeFoupmHw1U+fEE4400owM+F CzMfFfKT5NFfaj8AAwUH/RTuWsjUH4MYcWZRLnTVkhufOuAZztPPBttWSHXrHHBY qEQoNTwbzhtGhqqgR9KF0q4f0KMK1ap0pqVuvYq67+7mXMsSJsh4rXSk21QTXjil XbkRMSV8FWjhktPtuoExI1YrSfKRkQOCPXhRHP/T6IwptImGcNkNgNn9bsc7X5VT OMTEzeG66m2nK1inatvAakkId/aNPUp5VcM3UzbALEurj/dJ9qMojvTiUPr8dvnp 9c+5xzdaJJdPs1sdyrAK7JJS2zE08sPgkBlPg/bCmVrwqJWexNuEfH1UjZmMl8eQ QONFqmmwlVa037pXfSUv/fuf1t8/JyM+zChX6NyMg+uITwQYEQIADwUCSVqqzwIb DAUJAeKFAAAKCRB9BNJAvQwUwXfJAJ9iZEbcUiE/EIt2IdPQSuzVAk7UHgCePDkX iG4EEcFcnQREDu2pDfJUnKU= =ee1u - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklasdcACgkQfQTSQL0MFMHIcwCdFJx33CRmsdKS43+QWcPy86rn oKIAoJonxcTZSz4HI31Jl537CVzj3zcx =O3mv -----END PGP SIGNATURE-----

1 0

Invitation from josemanimala@gmail.com
by Jose Manimala 30 Dec '08

30 Dec '08

1 0

Re: Man page coverage
by A. Mani 29 Dec '08

29 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Basil Mohamed Gohar wrote: > 1) Identify which packages are missing man pages altogether in Fedora > 2) Identify which packages having sub-par man pages If we require that each man page should contain a few examples of usage, then we will find a lot more. Many KDE applications lack proper man pages. Maybe #man for those should call #khelpcenter help:/ or offer to install them (in case they are missing). OR do we consider the reverse conversion 2man??. Again there is the kde developer documentation (can be handled as well with man 1,2,...) > What I could use help with from the more experienced would be, for > example, a way to identify the existence of man pages for packages. For > example, is it enough to have a single man page for a package, or do we > want a man page for every executable file? Ideally references should be complete and every executable covered. Take k3b for example. Its manual (GUI or CLI) does not get dynamically updated with the addition of executables (relevant ones). Best A. Mani -- A. Mani Member, Cal. Math. Soc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJWPN6oIK4BlImohYRAo8jAJoCPwZL6YLY/4zwjzess86W83FJZACfVsiP 2rT2apgcXq5+iWKPhN5dxp0= =R/y0 -----END PGP SIGNATURE-----

2 1

Hackfest: User Guide Updating
by Matthew Daniels 28 Dec '08

28 Dec '08

Good afternoon, everyone, Today's hackfest topic is scheduled for updated the the User Guide to F9 status so it can be XMLified in a few days by Betty. It really just needs to be cleaned up, fact checked, and updated on some of the topics that changed with the F9 release (especially the update to packagekit). As a result of bad planning on my part, I can't be online consistently until about 6 or 7 EST, but I'm going to do my best to be online sporadically until then and should be able to be online for a solid few hours somewhere between 2 and 6 EST. If you get a chance today, please stop by https://fedoraproject.org/wiki/User_Guide_tasks and do what you can. Some people have already been making some good changes in the past few days, so we're on our way there. If you have any questions, just shoot me an email or catch me in IRC whenever I am online. - Matthew PS: Hope everyone had a great holiday.

2 1

Looking for Ideas on a User-friendly Join Process
by Marc Ferguson 28 Dec '08

28 Dec '08

Hi, My name is Marc Ferguson. I recently joined the websites group for Fedora Project and I've been assigned to help figure out a very universal and user-friendly way to tweak http://fedoraproject.org/en/join-fedora. Can you please respond to this thread and let us know what your process is for people to join your group. In the end we want to make sure we're all "on the same page" and that the joining process is much easier, thus increasing the contributors to the project. Thanks. -- *Marc F.* www.fergytech.com "..Grace to you and peace from Him who is and who was and who is to come.." -Rev1:4 "When life gives me lemons... I make Linuxaide!" -Marc F.

4 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 December 2008