|
Bugzilla – Full Text Bug Listing |
| Summary: | bootloader: grub.conf not preserved | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Michal Svec <msvec> |
| Component: | YaST2 | Assignee: | Olaf Dabrunz <odabrunz> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P4 - Low | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michal Svec
2005-10-24 09:42:27 UTC
*** Bug 130235 has been marked as a duplicate of this bug. *** The reason is that YaST fetches the important information from grub.conf (which is where to install the bootloader and how to install it) and when storing the settings, creates the file from these settings. The lines which YaST doesn't understand aren't stored anywhere, so the changes (unless you change eg. the bootloader location) get lost. I don't know if it's worth to make YaST (or more precisely perl-Bootloader) keep these changes. I don't know if it makes sense to edit something else than YaST offers (and make YaST understand the options), especially as other distros do not have equivalend of this file and just store the loader location somewhere instead. Torsten, what's your opinion? Please don't try to interpret /etc/grub.conf, consider it one big string. IMHO the expert user is free to create any setup that he thinks fit his system. Only create one for a new installation, otherwise leave it untouched, please. At best, you could see whether it exactly matches one of Yast's patterns, and then feed it as defaults into the dialog(s). Reasigning to new maintainer Will look into this for next version. This is fixed since Beta1. |