[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.
11 years, 1 month
[Bug 595695] New: Direct links to RNs broken.
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: Direct links to RNs broken.
https://bugzilla.redhat.com/show_bug.cgi?id=595695
Summary: Direct links to RNs broken.
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: eric(a)christensenplace.us
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com
Classification: Fedora
Description of problem:
* Previously, the release notes were located at
http://docs.fedoraproject.org/release-notes/
* Their location has changed to release specific URLs.
* A link to the release notes is provided in fedora-bookmarks.
* fedora-bookmarks are imported by the browser only on *first launch* so as to
not overwrite user modifications.
The new bookmarks layout causes two problems:
1. Nobody filed a fedora-bookmarks bug so Fedora 13 (and anyone on F-11 or F-12
etc) will default to going to http://docs.fedoraproject.org/release-notes/
which is a 404. Since the bookmarks can only be imported on first launch, we
cannot push an update to fix this if the user has launched the browser (which
is extremely likely).
2. Even if I were to fix the bookmarks page to point directly to a specific
release version (which again would take effect only if someone would yum update
before launching Firefox), then if anyone updated to F-14, the bookmark would
not change and would still point to e.g. F-13.
So, I do not think that we should put version specific information into our
bookmarks URLs. To solve both of the above problems, I believe we should try to
do some User-Agent detection and redirection. Fedora browsers have an RPM NVR
attached to them.
For example:
Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.4) Gecko/20100517
Fedora/3.6.4-1.fc13 Firefox/3.6.4
This tells us that the user's installed language is es-ES and it's a Fedora
browser, specifically running F-13. We should then redirect queries to
http://docs.fedoraproject.org/release-notes/ to
http://docs.fedoraproject.org/es-ES/Fedora/13/html/Release_Notes/index.html
If we cannot figure any information out about the Fedora release or language
(or there are no relnotes in that language), I propose the default redirect
should be to the en-US version of the latest Fedora release notes.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
11 years, 9 months
[Bug 504066] New: CMS for docs.fp.org
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: CMS for docs.fp.org
https://bugzilla.redhat.com/show_bug.cgi?id=504066
Summary: CMS for docs.fp.org
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: project-tracking
AssignedTo: kwade(a)redhat.com
ReportedBy: mel(a)redhat.com
QAContact: kwade(a)redhat.com
CC: fedora-docs-list(a)redhat.com
Classification: Fedora
Zikula chosen, working on test instances and project plan with Zikula team
--
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.
12 years, 11 months
[Bug 513907] New: SRPMs fail to build in Koji
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: SRPMs fail to build in Koji
https://bugzilla.redhat.com/show_bug.cgi?id=513907
Summary: SRPMs fail to build in Koji
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: high
Component: publican
AssignedTo: jfearn(a)redhat.com
ReportedBy: eric(a)christensenplace.us
QAContact: extras-qa(a)fedoraproject.org
CC: jfearn(a)redhat.com, fedora-docs-list(a)redhat.com,
mmcallis(a)redhat.com
Classification: Fedora
Description of problem: SRPMs fail to build in Koji due to the following error:
Processing files: fedora-security-guide-en-US-1.0-16.fc12.noarch
error: Two files on one line: /usr/share/applications/Fedora
error: File must begin with "/": Projectfedora-security-guide-en-US.desktop
Version-Release number of selected component (if applicable): 0.44-0.fc11
Possible Fix: Remove the %{?vendoropt} from
desktop-file-install %{?vendoropt}
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop
or remove %{vendor} all together.
I'll be testing this soon to see if I can provide a patch.
--
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, 6 months
[Bug 504063] New: Toolchain next steps
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: Toolchain next steps
https://bugzilla.redhat.com/show_bug.cgi?id=504063
Summary: Toolchain next steps
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: project-tracking
AssignedTo: kwade(a)redhat.com
ReportedBy: mel(a)redhat.com
QAContact: kwade(a)redhat.com
CC: fedora-docs-list(a)redhat.com
Classification: Fedora
Sorting out what fedora-doc-utils does, where to use Publican, etc. --
Principals to discuss status, progress, direction on IRC.
--
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, 7 months
Self-Introduction
by Юрий Хабаров
- Name : Yuri Khabarov
- Projects where I worked before: http://forweb.su
At this project for web-designers and developers I was writing a technical
notes about SQL and web-servers, such as Apache and Microsoft IIS.
- I think, that I have not a bad level of working on computer. So, I can
build a web-server based on Fedora with apache-mysql-php. Working in bash is
my commonplace. Also I have a certificate of MySQL administration (
http://www.intuit.ru/diploma/r0lySLZGyvu6/A00074937/), I think that my
knowledge maybe useful.
- Such as other my people skills, I can find a common language with every
person. I'm a very friendly person :)
- Why I want to work with docs? Every day on some linux-forums I see
posts from users, who can't find some documentation for some programm,
HOWTO-pages in russian language. In my town not so much people, who use
linux, because a lot of users think that it is very difficult OS for them.
- Other question: why I chose a Fedora? Because my father and I think
that "right" linux is a linux, which based on RedHat distributive :) I'm
using Fedora starting 4-th version, and I want to enjoy it more.
- My GPG-key fingerprint:
[b00blik@fedorahost ~]$ gpg --fingerprint 2A567AE7
pub 2048R/2A567AE7 2010-07-31
Key fingerprint = F105 949F D450 9D15 B554 EDF3 BDAC 86DF 2A56 7AE7
uid Yuri A. Khabarov (The Man) <madb00blik(a)gmail.com>
sub 2048R/C1374D9C 2010-07-31
13 years, 10 months
Introduction- Greg Krpan
by Greg Krpan
Hello fellow contributors.
My name is Greg Krpan and I am looking to contribute to the
Documentation Project.
In the past, most of my work has been as a SysAdmin, but I have also
performed a number of documentation roles as well. My early
documentation work was to document servers and data center
configurations for disaster recovery planning, I have also been
involved in the creation of a user manual to assist in employee
migration from Novell Groupwise to Lotus Notes, along with associated
training in order to familiarize users with the new application. I
have been published twice for my work designing and constructing a
Beowulf-class supercomputer for geographic modelling for the USGS.
My skill level with computers is high. I am comfortable with most any
hardware configurations from PC's to mainframe, and anything in
between. Most of my experience has been supporting midrange systems,
primarily Dell PowerEdge (RHEL) IBM RS/6000 (AIX) and Sun UltraSPARC
(Solaris). I build my own PC's for home use, and most recently
operated my own computer consulting business where I promoted Fedora
as the primary operating system.
In the role of a SysAdmin, I have had heavy interaction with users,
and am able to communicate on any level from "newbie" to expert with
confidence. I have also had call center experience, in which patience
and the ability to calm a customer was paramount to providing a
pleasant experience for the customer.
I am a good fit for the documentation project as I believe in
providing the most complete documentation possible in order to allow
users to become more self sufficient with their use of the Fedora and
it's integrated components. I can break down a problem quickly and
efficiently in order to develop and document a solution, and can
relate that solution to any level of audience required.
GPG Information:
pub 1024D/3F96CEEB 2010-07-31
Key fingerprint = DC43 D213 A907 1D33 F355 D969 6DB9 5A33 3F96 CEEB
uid Greg Krpan <gjkrpan43(a)gmail.com>
sub 2048g/C7338FE4 2010-07-31
--
---------------------------------------------------------------------------
In honor of those who lost their lives exploring the final frontier:
Apollo 1; January 27, 1967 Virgil "Gus" Ivan Grissom, Edward Higgins
White II, Roger Bruce Chaffee
Space Shuttle Challenger, Mission STS-51-L; January 28, 1986 Francis
R. Scobee, Michael J. Smith, Judith A. Resnik, Ellison S. Onizuka,
Ronald E. McNair, Gregory B. Jarvis, Sharon Christa McAuliffe
Space Shuttle Columbia, Mission STS-107; February 1, 2003 Rick D.
Husband, William C. McCool, Michael P. Anderson, Kalpana Chawla, David
M. Brown, Laurel Blair Salton Clark, Ilan Ramon
13 years, 10 months
Script for Beat Writing
by A. Mani
I think a script for collecting basic info in the following format
would be useful for beat writers.
1. Collect a subset of packages by tag from package database
2. browse one level below the names of packages and extract description
3. Extract names of latest versions with occurrence of fc14, fc13
4. reach Koji and extract latest 6 entries of changelog
5. continue
6. write all the info in seq order
Best
A. Mani
--
A. Mani
ASL, CLC, AMS, CMS
http://www.logicamani.co.cc
13 years, 10 months
Release Notes Schedule
by John J. McDonough
I mentioned earlier that I put an annotated schedule at
https://fedoraproject.org/wiki/Release_Notes_schedule
What I failed to mention, and should have .... THIS IS A WIKI!
If you have comments, concerns, good ideas, please don't be shy about
adding them so we can all benefit.
Note that the left 2 columns are from poelcat's schedule (well, the item
field may have been shortened to fit my to-do list), but the right two
columns provide a space to keep notes about what we intend to do, or
what we did, and perhaps more important, what we didn't think of and
should try to remember next time.
--McD
13 years, 10 months
