Bug 451561 - memtest-setup should create Memtest86+ entry at end, not at beginning of grub.conf
memtest-setup should create Memtest86+ entry at end, not at beginning of grub...
Status: CLOSED DUPLICATE of bug 489110
Product: Fedora
Classification: Fedora
Component: memtest86+ (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Paulo Roma Cavalcanti
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-06-15 16:47 EDT by Andre Robatino
Modified: 2009-09-17 09:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 489110 (view as bug list)
Last Closed: 2009-09-17 09:42:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andre Robatino 2008-06-15 16:47:48 EDT
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):

How reproducible:

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-10 21:15:16 EDT
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 09:42:06 EDT

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

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