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.
#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
#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
We could use someone to take full responsibility for the start to
publish for each of these guides, ongoing for now and possibly future
releases:
* Release Notes
* Installation Guide
* Packaging Guide
* User Guide
Interested? Want to hear more?
There are a few more out there (Virtualization Guide, RPM Guide) that
could be picked up as well.
https://fedoraproject.org/wiki/Docs_Project_content_tasks_for_experienced_c…
- Karsten
--
Karsten Wade, Community Gardener
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all!
My name is Justin Mitchell and I'm interested in helping with the
Fedora Docs project. I made the permanent switch back to Fedora and
open source software at the begin of this year after having Vista eat
my computer and using a variety of open source tools to recover data
and do my job that closed source tools couldn't do. By day I'm a
security engineer, using Fedora in a Windows environment and just had
to have tools that are reliable. I admit I still use XP running in
VMware, but that is more for Visio than anything else.
This is the first time I have ever joined an open source project in
any way at all. Usually, I'd just download my software, use it and not
give back. I figure it's time to change things and start contributing
to a product I love and recommend to others.
Justin
What other projects or writing have you worked on in the past?
This is my first project I have contributed to officially. I have
created documentation for end-users at my job as a systems
administrator.
What level and type of computer skills do you have?
I'm pretty much a power user (or at least like to think of myself as
one). I run fedora 9 as my primary desktop and use it to manage a
Windows-based server enivronment and Cisco equipment. I have my MCSA
Messenging 2003 and my CCSP. I love new challenges and sharing my
knowledge with others.
What other skills do you have that might be applicable? User interface
design, other so-called soft skills (people skills), programming, etc.
I have a lot of experience supporting end-users and explaining things
in a way that makes it easy for non-technical people to understand.
I've studied graphic design, and have experience with most professional tools.
What makes you an excellent match for the project?
At this point I have been using open source software on and off since
Red Hat 5 and am eager to start giving back to the community that has
created such a wonderful product and help others just starting out
with it.
pub 1024D/3C989C7A 2008-05-29
Key fingerprint = 743B 1E97 BDBF 4912 897B 8AD9 C101 316F 3C98 9C7A
uid Justin Grahm Mitchell
uid [jpeg image of size 3621]
sub 2048g/2B5B0D69 2008-05-29
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org
iEYEARECAAYFAkj1CGUACgkQwQExbzyYnHrq7QCdHvF1QWP7o2dRIsqirJ8lFpEf
omsAnROL3CvA9Rjg1gyK8MJcJKlLYPTc
=qNtT
-----END PGP SIGNATURE-----
#32: Probable typos in the F10 preview release notes
---------------------+------------------------------------------------------
Reporter: runab | Owner: quaid
Type: defect | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
---------------------+------------------------------------------------------
The following strings probably contain some minor typos:
string # 43:
"All of the packages from a DVD install can occupy over 9 GB of disk
space.
The final install size is determined by the installing spin and the
packages
selected during installation. Additional disk space is required during
installation to support the installation environment. The additional disk
space corresponds to the size of /Fedora/base/stage2.img plus the size of
the files in /var/lib/rpm on the installed system."
probable correction:
"filename" tags missing for "/Fedora/base/stage2.img" and "/var/lib/rpm".
Ref: string 32 and 321
string # 437:
"There is no support for Xen or kdump for the PowerPC architecture in
Fedora.
32-bit PowerPC does still have a separate SMP kernel."
probable correction:
"32-bit PowerPC does still have a separate SMP kernel." => "32-bit PowerPC
still has a separate SMP kernel."
string # 581:
"indhi" => should be "Sindhi"
string # 993:
"<ulink url=\"http://fedoraproject.org/wiki/ThomasCanniot\">
ThomasCanniot</
ulink> (translator - French)"
correction: A space missing between "Thomas" and "Canniot"
Thanks
Runa
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/32>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
#31: Internal communication included in the notes released for translation
---------------------+------------------------------------------------------
Reporter: runab | Owner: quaid
Type: defect | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
---------------------+------------------------------------------------------
The following messages in the release notes look like internal
communication between writers:
string # 286:
"Content pulled from wiki; changes to match Publican; cruft removed"
string # 292:
"Content changes for Publican 0.37 compatibility"
string # 296:
"Revised for Publican compatibility"
string # 297:
"These Notes are Placeholders"
string # 365:
"This list is automatically generated. It is not a good choice for
translation."
string # 932:
"This content not updated until after Preview Release occurs."
string # 933:
"We need to finish writing and translating the notes to know who has
worked
on them."
Thanks
Runa
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/31>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
The Release Notes titles are cute and all, but in a couple cases may
be a little arch ("Are There Hideous Bugs and Terrible Tigers") for
final release. Can we change them in those cases to something that's
easier for translators and readers?
Paul
#33: Issues in AGPBeta#Scheduling_Tasks
-------------------------+--------------------------------------------------
Reporter: amani | Owner: quaid
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
-------------------------+--------------------------------------------------
In https://fedoraproject.org/wiki/Docs/Drafts/AGBeta#Scheduling_Tasks and
https://fedoraproject.org/wiki/Docs/Drafts/AGBeta/Cron
no GUI tools are mentioned. Sysadmins need not necessarily use CLI
tools and in actual practice it is compulsory that they know.
So maybe the 'Additional Information' is in need of improvement.. But
the doc seems to be 'ready for editing' (?)
The first line "Fedora provides a cron facility for tasks
scheduling...." sounds odd. 'cron' is installed in the same way as in
many other distros.
Is the cron daemon a 'cron facility'? It should be rectified to
something like "The 'cron' daemon is the default CLI utility for
scheduling tasks".
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/33>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
In https://fedoraproject.org/wiki/Docs/Drafts/AGBeta#Scheduling_Tasks and
https://fedoraproject.org/wiki/Docs/Drafts/AGBeta/Cron
no GUI tools are mentioned. Sysadmins need not necessarily use CLI
tools and in actual practice it is compulsory that they know.
So maybe the 'Additional Information' is in need of improvement.. But
the doc seems to be 'ready for editing' (?)
The first line "Fedora provides a cron facility for tasks
scheduling...." sounds odd. 'cron' is installed in the same way as in
many other distros.
Is the cron daemon a 'cron facility'? It should be rectified to
something like "The 'cron' daemon is the default CLI utility for
scheduling tasks".
Best
A. Mani
--
A. Mani
Member, Cal. Math. Soc