[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, 2 months
[Bug 479470] New: cobbler kssendmac and breed suse
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.
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.
13 years, 10 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, 1 month
CMS discussions yet again
by David Nalley
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?
14 years, 4 months
F11 Release Notes Beat Writers
by Eric Christensen
-----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-----
14 years, 4 months
Preparing for F11 Release Notes
by John J. McDonough
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
14 years, 4 months
Docs Project contributor group in FAS
by Eric Christensen
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
14 years, 4 months