|
Bugzilla – Full Text Bug Listing |
| Summary: | No Control Over Boot on Update | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Rebecca Walter <rwalter> |
| Component: | Update Problems | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | YaST2 logs | ||
|
Description
Rebecca Walter
2005-08-11 08:03:11 UTC
Created attachment 45688 [details]
YaST2 logs
I didn't have control over my boot and it didn't do what I wanted. My system used to boot to my other root partition by default (hda7). Now it boots to hda8. I am additionally concerned that more is wrong. 9.3 appeared to be preselected in the boot screen. I touched nothing but it booted into 10.0. The already attached logs are for the completed installation. The main problem is that I cannot read the bootloader settings from the target system during the update proposal (because there is an incompatible version of the system installed). So I don't know how to give you this control (without very crude hacks). I will check the logs to find whether I can help you somehow... YaST didn't match the old sections from 9.3 with the ones to be created for 10.0. Fixed in SVN, will go to Beta2. Xen section wasn't created correctly, also fixed in SVN. *** Bug 104104 has been marked as a duplicate of this bug. *** |