Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: lack of documentation on restoring from bare-metal (UUID
Product: Fedora Documentation
Description of problem:
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):
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.
Hi Docs Team,
During the Fedora 9 release Paul helped me craft a schedule of docs
tasks which we published here:
For the Fedora 10 release I re-worked the underlying TaskJuggler file to
optimize reporting and the ability to allocate resources in the future.
As a result I've lost some of the dependencies that were built in and
am having a hard time reconnecting them. Also as I look at some of the
tasks I'm wondering if they still apply or not.
I'd love your help reviewing the schedule here:
and telling me:
1) Which tasks no longer apply and should be removed
2) New tasks which should be added
3) Existing tasks that are wrong
--please provide the task that comes before and after along with the
correct dates so I can build the right dependency logic.
----- "Karsten 'quaid' Wade" <kwade(a)redhat.com> wrote:
> From: "Karsten 'quaid' Wade" <kwade(a)redhat.com>
> To: fedora-docs-list(a)redhat.com
> Sent: Thursday, August 28, 2008 6:28:00 AM GMT +10:00 Brisbane
> Subject: Re: Week 35 - Linux Security Guide and Linux Deployment Guide
> About $subject ...
> The generic "Linux ... Guide" titles cover a lot of ground.
> I don't really imagine any of us covering other Linuxes, though.
> clearly outside of the Fedora Docs purview.
> Naturally we can just set the scope of the book to use Fedora as the
> canonical example. But there seems clear room for brand confusion.
> Wouldn't a Linux Security Guide be about Linux and not just Fedora et
> General question for the list and specifically for Michael:
> Should these be "Fedora ... Guide" instead?
This documentation effort is about Linux, not just Fedora/Red Hat. I'm pulling in some writers from Novell-Suse and Ubuntu to contribute to these fedora hosted projects. We all agree that the way to make Linux survive is to join our lamps together for greater illumination through procedural instruction.
I wondered what was happening with the FUG/DUG these days? And perhaps
more generally, what was happening with Docs Project? I've only been
following along loosely, and should probably check the archives, but I
was thinking about taking a crack at writing some stuff over the next
Does someone want to fix our Fedora template or tell me what to use
instead of seg lists here:
I'm starting to get more data in there but the seg lists aren't coming out
right and sometimes I get a:
WARNING: Unknown tag: seg. This tag may not be displayed correctly
My name is John McDonough and I am a retired computer professional living in
Midland, Michigan. I write ocasionally, have an online tutorial on PIC
microcontrollers, the occasional amateur radio magazine article, and even a
Six Sigma article. I have used Fedora since FC1, although I don't always
keep up with every release.
I feel a certain obligation to contribute, but although I program from time
to time I can't really see myself being able to commit the time nor
intensity needed to develop. However, I believe I have a better than
average command of the English language, and when first Paul Frields and
then Karsten Wade mentioned the need for beat writers, it seemed to me that
this might be a way I could give something back.
Looking at the list of open slots, it seems as if I could add something in
the gcc arena or possibly Development Tools. I use gcc regularly, mostly C
or C++, but I'm not above writing the occasional line of Fortran or Ada. At
this point, though, it isn't entirely clear how a writer learns what is
going on for subjects that don't have a PoC. Wade through subversion
Hmmm ... the SelfIntroduction page says you might want to know more about
me. Well, although I programmed for many moons, my real interest has been
the software process. After retiring I did a little consulting on Six Sigma
as applied to software development at some very large firms on three
continents. Prior to retiring my role was to provide the technical guidance
on large (>1MM USD) software projects. I was (thankfully) insulated from
many of the administrative burdens, although I did play a major role in our
On the personal side, I am an amateur radio operator, in fact, Radio Officer
for the state of Michigan, which means I spend a lot of time with the state
police. I like grody technical stuff, build radios, play with
microcontrollers, all that geeky stuff. Still, if one looks at my history,
both at work and at play, the people skills are not entirely absent.
With David Nalley's help I got signed up to FAS, did the CLA thing, now it
looks like I have a heck of a lot to read!
Today I am embracing both the moniker "Docs" and the new naming
scheme for the wiki. The time has come to rename all of the DocsProject
project space to come in line with the new naming conventions. This way
we'll be a reference implementation before we start asking others to do
Here is the process I've thought of. Suggestions?
1. Start with DocsProject and click through to each first link.
2. In each subsequent page, pull up the page of what links here.
3. Move the page then edit each of the what-links-here pages.
4. Ensure each page is in Category:Docs Project.
4.1. Make other improvements
5. Wash, rinse, repeat
I'm commencing immediately, unless anyone stops me. ;-D
cheers - Karsten
In professional technical writing, there is 'documentation' and the
'documentation project.' *yawn* I'm over that inconsistency. General
techies say 'docs', Fedora says 'docs', and 'Docs Project' we are.
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
A request was canceled from 1.
If you did not request this, it could be either an honest
mistake or someone attempting to break into your Red Hat Bugzilla account.
Take a look at the information below and forward this email
to bugzilla-owner(a)redhat.com if you suspect foul play.
Token Type: password
Issue Date: 2008.08.26 22:35:53
Event Data: 1
Canceled Because: You have requested cancellation.