Summary: | Installing grub should be more detailed to avoid errors | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | Aquila <bart.braem> |
Component: | Handbook | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | docs-team |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aquila
2004-01-17 08:40:18 UTC
Normally grub should give an error if it doesn't succeed... It didn't at my system, and it took some time to find out the real source. The problem is the disk naming schema grub uses, I made a little mistake there. Anyway I think telling users to get the succeeded message is not unnecessary, but if I'm the only one who's ever had this problem this bug can be closed. (I just thought I'd give my experience with a reinstall to the community, improving to docs is always necessary) I'll let this one linger here until someone tests (and gives some output if appropriate) grub commands. I'm currently limited to a single system and don't want to try anything on it (too important :) I've just tried making many errors during the grub installation (wrong device, invalid kernel image, even pointing to a file that isn't a kernel) and it always resulted in an error. Perhaps it was an error in grub itself that is fixed now? I'm marking this one as WORKSFORME... |