Bug 52980 - grubby doesnt add default properly
grubby doesnt add default properly
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mkinitrd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-08-31 17:33 EDT by Adrian Likins
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-02 17:10:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
grub.conf that fails to have it's "default=X" param set (636 bytes, text/plain)
2001-08-31 17:34 EDT, Adrian Likins
no flags Details

  None (edit)
Description Adrian Likins 2001-08-31 17:33:28 EDT
Description of Problem:

grubby seems to fail to add a "default=X" entry to the /boot/grub/grub.conf

Version-Release number of selected component (if applicable):

How Reproducible:
see soon to be attached grub.conf
try running:

grubby --set-default /boot/vmlinuz-2.4.7-0.9.1 

And see that the grub.conf does not include a default=X line.

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Comment 1 Adrian Likins 2001-08-31 17:34:27 EDT
Created attachment 30415 [details]
grub.conf that fails to have it's "default=X" param set
Comment 2 Jeremy Katz 2001-08-31 17:49:35 EDT
grubby didn't exist until mkinitrd 3.2 or so... this case should be fixed as of
mkinitrd 3.2.4
Comment 3 Joshua Jensen 2004-02-02 16:32:27 EST
This is STILL BROKEN, even in RHEL3.  Please please fix!
Comment 4 Joshua Jensen 2004-02-02 17:10:23 EST
I'll pull my foot out of my mouth... and say that the above example
does work.

*However*, this doesn't:

grubby --set-default 2.4.7-0.9.1

Turns out, grubby from RHL 7.3 says STRING when explaining what should
come after --set-default.  RHEL3's --help and man page now says
"kernel path".  That's cool.

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