http://bugzilla.novell.com/show_bug.cgi?id=513004 User suse@tlinx.org added comment http://bugzilla.novell.com/show_bug.cgi?id=513004#c3 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|NORESPONSE | --- Comment #3 from L. A. Walsh <suse@tlinx.org> 2009-09-19 17:43:06 MDT --- The reason I didn't respond, was I didn't think I had the logs you wanted. Yast seems to overwrite logs on each invocation, and I already had tried other options running yast to get it to work. So how could I return the logs you wanted? However, FYI, this bug is related to bug#512695 (https://bugzilla.novell.com/show_bug.cgi?id=512695) -- they were different manifestations of the same underlying problem -- grub wasn't booting (and wasn't being updated to boot) from the correct Partition -- and Yast2 didn't see any problem, as it only saw the new partition and all looked fine -- but grub ignored anything Yast2 did, as it was fixated on the old partition). Note -- if lilo was used and was called to update the new boot parms, none of this happens. As I note in the other bug, grub has other problems, which, instead of "disqualifying grub' as being incompatible and inferior to previous functionality, instead, disqualifies other working systems (like yast2 from working on the real boot partition, and "xfs" not being officially supported...)... If grub is too hard to fix, or the maintainers can't fix these problems, then suse should go back to lilo as it *works* -- and move to elilo for the new boot spec (which my machines (I think) support, but was told would require full reformats due to incompatibility). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.