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.
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.
Hello,
I am a final year undergraduate student from India and I plan to apply
for Google Summer of Code. I would like to implement a Docbook editor.
I discussed this idea with Mr. Yaakov Nemoy (cc'ed in this mail) who
has agreed and is guiding me through the process.
The Docbook editor will make it easy to write documentation through a
wysiwyg interface. Since Docbook has a great collection of XSLs[1] it
will be easy to convert it to HTML and write a web based editor.
My research has pointed me to Beacon[2], which is a similar editor for
GuideXML (Gentoo's documentation format). It uses an XSLT engine to
transform XML to HTML and vice versa. I contacted the developer of
this project and it seems like this project has been in hibernation
for couple of months or so. But the codebase is quite developed and
should be easy to work with. The developers were also making it a
generic plug-able framework for easy integration of other doc types.
Since it is a web-based editor, we can integrate this into the Fedora
documentation site for easy editing and creation.
It would be very nice if the Docs team could provide some feedback on
what they feel about a web-based GUI editor which would eliminate the
need for knowing the Docbook XML format. If I am given a go ahead, I
would like to put this up as a Feature.
Regards,
Satya Komaragiri
[1] Existing XSL for Docbook:
http://wiki.docbook.org/topic/DocBookXslStylesheets
[2] Beacon: http://beacon.kix.in/
I can't make tonight's meeting but I'll check out the logs -- I'm
interested in hearing how the release notes work went, since I was on
vacation and missed most of the fireworks. Well, except the fireworks
I saw. Which is a separate story. :-)
Paul
Is it too late to add release notes? I wanted to add a little warning
about GDB, but then when I looked I could not find any mention of GDB
in the release notes. (I expected the release notes from the Archer
project page to be automatically brought in... but I neglected to
check, sorry about that.)
If it is not too late, the notes from that page are still ok:
https://fedoraproject.org/wiki/Features/Archer#Release_Notes
The addition I wanted to make is a warning to the effect that the
Python API should be considered unstable. Something like:
WARNING: The Python API to GDB is still under development. We
cannot currently guarantee that future revisions to the API will
remain compatible.
thanks,
Tom
I've created a guide page[1] on the wiki that shows all the guides
that we are currently supporting. My plan is to include a list of all
the guides, a brief introduction paragraph, a sentence that tells
people how they can become involved, and where they can find the guide
(html, pdf, RPM, etc).
Please visit the page and provide that information on your guide.
[1] https://fedoraproject.org/wiki/Docs_Project_guides
Thanks,
Eric
#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
Hello,
I have noticed that some people are having troubles to submit the PO files
to SG doc on Tx.
As far as I could understand, it seems to be due the fact that you are
trying to upload to the target 'po/<LANG>.po'
That project doesn't have a po/ directory. You should commit the PO files in
the root of the repo. So the correct target is '<LANG>.po'
I just committed a pt_BR.po to serve as an example.
Anyway, we are working to make that clear in the future.
Regards
--
Diego Búrigo Zacarão
http://diegobz.net
Linux User #402589
USE SOFTWARE LIVRE
So I wanted to see what the interest level was in having a FAD
concentrating on Docs either before or after the Southeast Linuxfest.
Just to give you a heads up, the Southeast Linuxfest is June 13th at
Clemson University in South Carolina
More info here: http://southeastlinuxfest.org
A number of Docs contributors are in the Southeast, off the top of my
head they include:
*stickster
*jsmith
*Sparks
*laubersm (though she already has a conflict)
*ke4qqq
*danielsmw
*Eawest (though she will be very great with child or welcoming home a
newborn during SELF and thus unable to attend)
Some of the possible targets we could work on:
*Answer the Docs_decisions_for_F12
* Mint some new packagers within Docs
*Hack on some of the internal infrastructure
*Work on Zikula
I am sure there are other things, this event falls literally right
after the F11 release so it might be a good time to do some strategy
for the the coming year.
In possible anticipation - I have tentatively reserved the same
building SELF is being held in for our use on Sunday.
I welcome comments, enthusiastic comments, and flames