Hello,
> dd@home.dk wrote:
> On 08/21/2012 10:46 AM, arkascha wrote:
>> what a constructive help this is.
>
> when you do things that no one here [or in written documentation or
> how-tos] suggests, approves of, or supports–we can only assume you have
> not read enough and therefore don’t know how to do correctly.
>
> therefore, his (unstated advice) to learn how to do it so you do know
> what you are doing, is very sound and extremely constructive indeed.
Why does the fact that I did not following any of the typical usage cases
automatically mean that I do not know what I am doing ?
In my eyes one of the strong things about Linux is that unlike other systems
you are allowed to do what you want with it. Not only what someone else
tells you what is allowed. Am I wrong with that?
I am not trying to get help from some support line that has clear guidelines
what usage case is supported by them and what not. I just ask around in a
forum trying to find someone who has got an idea what might be wrong on my
system.
I never claimed the openSUSE project team did something wrong and now has to
solve my problems. I never claimed the software is buggy because it did not
do what I expected when I did that ‘upgrade’.
I just asked if someone has got an idea.
Sorry if that is wrong in your view.
>> Please note that there are reasons for this shift. Though I do agree that
>> this shift is probably not really called an ‘upgrade’
>
> if you have problems because you do not follow instructions/guides/best
> practices it is difficult for us to even begin to figure out what causes
> your current problem, or the same problem you had when you
> wrote “when upgrading to openSUSE-12.1”
That is currect, I will do my best to provide information in the hope that
someone here more familiar with the boot aspects has an idea for me. Thanks
for giving it a try!
> …]
> which of these three (only three supported ways) did you follow
> precisely to get from what previous version of openSUSE to 12.1?:
> …]
Right, clearly my mistake:
I actually did not upgrade to 12.1, but I “upgraded” / made the switch
from openSUSE-12.1 to openSUSE-Tumbleweed. This was when I first
experienced these problems: for a certain period of time all kernel upgrades
(quite frequent in Tumbleweed) produced these empty menu.lst files. As
written that problem did not accur any more over the last month.
I did that switch by replacing two or three repository urls with the
corresponding tumbleweed alternatives. I did that using yast2 software
management. For all the upgrades afterwards I used plain zypper up calls.
When now switching to openSUSE-12.2 again I did the same:
changed the repository urls to the openSUSE-12.2 alternatives and ran a
distribution upgrade (zypper dup). Afterwards I manually switched some
packages between repositories to reduce the wild mixture. For example I
switched all kde related packages to the KDE-4.9 repository (using yast2’s
“switch to this repository” feature).
After the switch to 12.2 I found a new (additional) grub2 entry in the boot
menu. That entry (autogenerated during the upgrade) did not work (halted
before any boot messages were written). So i ignored it and used the “old”
entries still there, note that these were upgraded to the new kernel
versions as provided by 12.2. These entries did work, those were grub1
entries as far as I can tell.
During my attempts to give grub2 a try I reinstalled the bootloaded
(yast2>bootloader>“Ok”). This was when suddenly the boot menu contained no
entry any more and I had the problem to get the system back. I succeeded
using a rescue disk and restoring a backup version if the menu.lst file. I
did that cause I noticed that indeed that file had been stripped of any
entries. And because I had that similar issue ealier (as written) I recalled
some steps. With that restored menu.lst file the system boots fine.
I completely failed to get grub2 to work. This might be because I have a
MacBook Pro using EFI. Since grub1 works fine I decided to stay with it,
deinstalled grub2 using yast2, but still these empty files are written. Note
that I did not force any package deinstallation. Yast2 offered
desinstallation, and I only accepted. zypper tells all package dependencies
are satisfied. But obviously I cannot tell if there are any packages still
left related to grub2. I chose the files I deinstalled by package name and
description. I did that because I assumed there are conflicts between grub1
and grub2 packages.
–
arkascha
