Description of problem:
There are typos in the description of the kernel-xen RPM, and
it could use clarification.
This package includes a version of the Linux kernel which runs in Xen VM. It
works for both priviledged and unpriviledged hosts.
Suggest SHOULD READ:
This package includes a Xen hypervisor and a version of the Linux kernel which
can run Xen VMs for privileged hosts and unprivileged paravirtualized hosts.
Version-Release number of selected component (if applicable):
Reassigning to the package maintainer.
Fair enough, I'll post this change for 5.3.
Out of curiosity, was this a customer request or something you noticed. Just
wondering if I should go proof read the other descriptions too for proper English.
A customer and I discovered the description problem with the xen package
reported in bug #249719 during a training class, which led us to look at the
kernel-xen description, which led us to this bug.
If we can mess these up, my guess is that there are other descriptions that are
off; up to y'all to figure out how high a priority it is to do an editing
pass/bug hunt. :) I wonder if there's a way to run Summary and Description
through a spelling checker in a useful way when we QA?
hmm. Spell checking is an interesting idea for rpmdiff maybe. But I am all for
improving the text if it helps people understand the packages easier.
Sometimes it is the little things that makes Red Hat provide a better service. :-)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
You can download this test kernel from http://people.redhat.com/dzickus/el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.