Bug 451561

Summary: memtest-setup should create Memtest86+ entry at end, not at beginning of grub.conf
Product: [Fedora] Fedora Reporter: Andre Robatino <robatino>
Component: memtest86+Assignee: Paulo Roma Cavalcanti <promac>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 11   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 489110 (view as bug list) Environment:
Last Closed: 2009-09-17 13:42:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andre Robatino 2008-06-15 20:47:48 UTC 
Description of problem:
After installing memtest86+ and running memtest-setup, the Memtest86+ entry is
the first entry in grub.conf.  This makes no sense since each time a new kernel
is installed, IT becomes the first entry and all other entries, including the
Memtest86+ one, move down.  Eventually the Memtest86+ entry is below all the
Fedora kernel entries, but above any other OS entries.  It would be more
sensible to place the Memtest86+ entry at the bottom instead, where it would
stay permanently.  Also, a memory check is normally done rarely so it makes more
sense for it to be at the bottom.

Version-Release number of selected component (if applicable):
memtest86+-2.01-3.fc9.i386

How reproducible:
always

Steps to Reproduce:
1.  Install memtest86+.
2.  Run memtest-setup.
  
Actual results:
Memtest86+ entry first in grub.conf.

Expected results:
Memtest86+ entry last in grub.conf.
Comment 1 Fedora Admin XMLRPC Client 2009-03-11 01:15:16 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Jarod Wilson 2009-09-17 13:42:06 UTC 

*** This bug has been marked as a duplicate of bug 489110 ***