Summary: | grub: ${BOOT}/grub/default missing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | echtler |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | major | CC: | echtler |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
echtler
2007-10-08 15:00:15 UTC
Maybe you should read the fine manual and run `grub-set-default 0` or whatever else before filing bugs. (In reply to comment #1) > Maybe you should read the fine manual and run `grub-set-default 0` or whatever > else before filing bugs. Yes, I know that this is a fix and have already used it before filing the bug. But perhaps the ebuild should simply run this command at the end, because it would prevent a hard-to-track problem from occuring (the grub error message is confusing, to say the least). I know that in an ideal world, everybody reads the _fine_ manual before doing anything else, but still, people tend to forget things once in a while.. The ebuild shouldn't run anything like that at the end because it doesn't install any savedefault entry anywhere in grub.conf. If you are using one, you should know what to do. |