On Thursday 01 October 2009 02:01:23 am Peter Nikolic wrote:
Well just done a zypper up on my laptop running MS7.
i think "zypper dup" would have been more appropriate in this situation. when i ran it a couple hours ago, several kernel related packages were actually _downgraded_; "zypper up" doesn't do that.
it claims to have updated the kernel to 2.6.31-10.1 from 2.6.31-9 But i did not have -9 on the machine it was -8 on it .
strange; ive never seen zypper telling me from which version it upgraded to the new one. i just see info. about the new package being installed, not the old one being replaced.
Toward the end of the zypper session it threw up a large amount of reports attempting to carry out actions on deleted files then asked for the process to be re started
zypper does that nowadays: telling you which running processes are using files that have been deleted or replaced.
i just got the report nothing to do .
after a kernel update, you certainly should reboot.
This appears to not check what it is doing before it attempts to carry an action as exampled by the Kernel versions and the now failed sym links still booting 2.6.31-8 but installed 2.6.31-10.1
you may have to edit your boot configuration manually. i would try first "zypper dup", perhaps that fixes the situation. in my case the new boot menu entries were properly created, including command line options. the last time (M7) this did not happen.
i have saved the zypper.log and /var/log/zypp/history if they are of use .
not to me at this point; i'd suggest to run "zypper dup" and see what happens--or better, wait for one of the real experts here to confirm or correct what i wrote... -- phani. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org