[Bug 450331] New: lack of documentation on restoring from bare-metal (UUID problem)
by Red Hat Bugzilla
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.
10 years, 8 months
[Fedora Release Notes] #29: Remove whitespace trigger ugly PDF formatting
by fedora-badges
#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
14 years, 7 months
Re: Some thoughts on beat writing
by John J. McDonough
Paul I appreciate the feedback.
I do have a few thoughts on specific ways things might be made better for
new beat writers, but I also imagined that if other beat writers engaged in
the conversation, better ideas would emerge.
A little shooting from the hip:
1) Seed the beats, especially the untouched beats, with the information
available from yum. This can be done programatically, and I would be
willing to work on that, but I suspect that there may be a better way, and
in any case, the mapping of packages to beats is something that probably
needs to be easily editable, and that raises some issues I haven't
reconciled.
2) Provide some relatively automatic way for a beat writer to know what has
changed within his domain without grazing all 11K packages. I will do this
for myself for F11, whether I can do it in a way that is appropriate in a
production environment, I'm less sure. (I'm a big fan of really grody
hacks).
3) Provide new beat writers with an assigned mentor, preferably someone with
at least some familiarity with the beat content, as well, of course, as the
process.
I'm pretty sure other beat writers out there have much better ideas but they
are keeping their mouths shut. Perhaps I should have waited a few more
days. Indeed, with the holiday fast upon us, many of the stateside beat
writers are probably already headed off to their turkeys, leaving their
laptops alone and lonely over the long weekend. On the other hand, perhaps
some will emerge from their tryptophan haze in a talkative mood!
--McD
15 years
wiki Releases/10
by Dale Bewley
I hope I didn't step on some S.O.P., but I noticed /Releases/10 did not
exist, so I added it and revised /Releases.
http://fedoraproject.org/wiki/Releases/10
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
15 years
Fedora HW requirements
by Adam Pribyl
I am just bit surprised that Fedora hardware requirements remain same thru
release notes from Fedora Core 2 (almost 5 years) ut to Fedora 10.
http://docs.fedoraproject.org/release-notes/f10/en_US/What_is_New_for_Ins...
I think we should consider to review this, as this is really getting
outdated. I know that Fedora can run on P200MHz with 64MB RAM, but it's
not usefull for work, and I would really not consider something like
PII400MHz with 256MB of RAM as recommended hardware. I personaly start to
feel slowness on PIII800MHz with 512MB of RAM with default Gnome, KDE4 is
not possible use on this HW due to unresponsive GUI. I know this is much
about the feeling, but recommended I would consider (looking into smolt
results) something around 2GHz CPU and 1GB of RAM. For 64bit I think there
should be mentioned that you need to have a CPU with either AMD64 or EM64T
technology, the RAM and gigahertz may remain the same..
Thanks for attention
Adam Pribyl
15 years
self introduction
by Shajia Khan
Hello Everyone,
My name is Shajia Khan . I am a student of Technical Communication, Seneca
College, Toronto. From the January 2009 till April 2009 I will have my co-op
semester and I am planning to work with Fedora project in the area of
documentation writing and editing to gain my co-op experience.
My educational background is basically in English. I have done my bachelors
in English language and literature. Then I worked as a news paper reporter
for a while and then worked as language teacher in middle school. After
that, I did my M.A. in Applied Linguistics from Carleton University, Ottawa.
I worked for a linguistic consultant for a company in Calgary for a year. I
worked as a teacher in various educational settings. Then I enrolled in
Seneca College to make a career change. I am planning to become a technical
writer because I believe as a teacher my main object was to convey complex
ideas to my students in simple terms. Here as a technical writer I will be
doing the same.
I have summed up my experiences and knowledge which will bring result to
Fedora project:
My working experience as a writer: I wrote in news paper articles. As a
teacher I wrote handouts, course outlines and even teaching units which are
very similar to the technical documents.
My experience in editing: As a teacher I had to review my students writing
and help them to write in correct English. Moreover the course in Editing
and Style in Seneca had brushed up those editing skills and taught me some
tools especially on how to edit in an electronic document.
The technical know -how: The technical communication course in Seneca
taught me some key concept in documentation. For example, task analysis,
user analysis, writing a procedure, technical description, technical
specification, software lifecycle etc. It will enable me to be familiarized
in the term.
Communication Skills: As I mentioned earlier, as a teacher my key
responsibility was to explain complex ideas into simple terms. I believe
that is very crucial when someone works as a technical writer.
I will be able to work full time for Fedora, so I am looking for lots and
lots of works!
Regards
Shajia
15 years
moving content off of the draft wiki
by Murray McAllister
Hi!
I think there are some great documents on /wiki/Docs/Drafts/, but
these are hard to find:
1. <http://fedoraproject.org/>
2. Click "Docs"
3. I might be impatient, but I can't actually find the link to the
drafts (I know it is there somewhere though)
4. phail :-)
Ubuntu:
1. http://www.ubuntu.com/
2. support -> documentation
3. Admire pretty list of documentation that desktop users and
non-Linux people probably want to know.
openSuSE:
1. http://www.opensuse.org/en/
2. Click Discover it
3. Click Documentation (lots of clutter, but I found it easy to find).
4. Nice list of links. Looks pretty
<http://en.opensuse.org/Documentation> rocks!
It seems the Fedora process is too formal and too hung up on having
'professional documentation', that all the useful information gets
left behind on wiki drafts where people aren't going to look. Maybe
instead of the fedora admin guide , the drafts sections could be
turned into mini howtos?
Sorry if I sound grumpy :-)
I would be happy to convert
<http://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/Permissions>
to DocBook if it could be placed somewhere other than in the drafts
section.
Cheers.
15 years
heads up
by Valent Turkovic
Hi,
I mooved this page:
FedoraLiveCD/USBHowTo to new page:
https://fedoraproject.org/wiki/Fedora_LiveCD_USB_HowTo
why? I saw this:
https://fedoraproject.org/wiki/Help:Wiki_structure#General_naming_rules
And the funny thing is that the exaple given is this one and it wasn't
changed before, why?
Cheers,
Valent.
--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
15 years
Re: heads up
by Kam Salisbury
http://counter.li.org.
> ICQ: 2125241, Skype: valent.turkovic
>
I also found on this page some broken links:
https://fedoraproject.org/wiki/Features/LivePersistence
should I report broken links on this page as a bug? What is the best
thing to do? What would you do?
Cheers,
Valent.
--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-docs-list
--- message truncated ---
Valent, you have the skill set to help the Ambassadors (and the docs group too) do some much needed wiki gardening. Please keep going this direction in your efforts.
Most folks experiment a little till they find a technique and strategy that fits their abilities and time constraints.
For example, I joined the docs group and subscribed to the docs list so I can understand what is going on from time to time. I found out that I don't usually have enough free time to do more than wiki garden so I look for weeds (broken links, out of date content or hard to understand technical references) then prune or replant elsewhere as necessary.
Wiki gardening is important now more than normally because a new release of Fedora may have caused more pages needing updated than normal.
--
Kam
http://kamsalisbury.com
GPG key: FAF1751E
15 years
