Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 600568 (5to6kexecTools) - RHEL5->RHEL6 kexec-tools forward-port
Summary: RHEL5->RHEL6 kexec-tools forward-port
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: 5to6kexecTools
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kexec-tools
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Cong Wang
QA Contact: Han Pingtian
URL:
Whiteboard:
Depends On: 592312 600566 600572 600574 600575 600578 600579 600583 600584 600585 600589 600590 600591 600597 600600 600601 600604 600605 600606 600607 600610 600611 600613 602785 602905
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-05 04:25 UTC by Qian Cai
Modified: 2013-09-30 02:14 UTC (History)
5 users (show)

Fixed In Version: kexec-tools-2_0_0-79_el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 14:42:41 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Qian Cai 2010-06-05 04:25:38 UTC
Description of problem:
This is track patches in RHEL5 kexec-tools are missing in RHEL6.

Comment 1 Qian Cai 2010-06-07 00:26:54 UTC
For every single fix in RHEL5 mentioned here, I have examined the current RHEL6 code to make sure the patch did not there, also I am somehow familiar with RHEL5 and RHEL6 differences, so make sure only list here the ones that affect RHEL6 code-base. For example, there were bugs that only affect critical_disks, and I knew they are probably not applicable in RHEL6 and not listed here.

If there are fixes that not needed for the DEV point of view, we can certainly remove them.

Yes, there looks like 5 or 6 to fix documentation bugs and enhancement.

Comment 10 releng-rhel@redhat.com 2010-11-11 14:42:41 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.