Hi,
M3 is expected to be released tomorrow July 14 or later this week. How do I update/upgrade from M2?
Also, how do I update the repositories?
Thanks for your help.
Once the repo Index of /factory-snapshot/repo/oss is updated :
# # echo Download all the packages first on Console, remote or in GUI
# zypper ref && zypper -q dup -d
# init 3
# zypper dup --download-in-advance
# shutdown -r now "To complete kernel upgrade"
That’s assuming you haven’t added any repos, if you have then disable those first. You are likely to need lots of diskspace to get the packages, the problem with DownloadAsNeeded option is you are more likely to get stuck between versions should the net let you down. --download-in-advance is the default, so if you haven’t tinkered with options “zypper dup” suffices.
A non-live install using boot from Net CD would also be possible (and theoretically surer than upgrade of a running system); it uses less disk space to because it can use “DownloadAsNeeded”.
On Wed, 13 Jul 2011 12:36:03 +0000, taytong888 wrote:
> M3 is expected to be released tomorrow July 14 or later this week. How
> do I update/upgrade from M2?
>
I see robopensuse has provided an answer for how to update but I’ll be
making a clean install after downloading and burning a DVD instead of
adding updates to an existing installation. One reason for this is to see
whether there are any problems with the installation process. For
instance, with 11.4, problems with GRUB showed up late in its development
cycle. The other is that my M2 installation has been screwed by a recent
update. 
–
Graham Davis, Bracknell, Berks.
openSUSE 11.4; KDE 4.6.5; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210; Sound: ATI SBx00 Azalia (Intel HDA);
Wireless: BCM4306
I actually will be doing similar, but with Net Install CD of 64 bit, and I use a big proxy cache to accelerate multiple installs. I did test 11.4 RC (I think a mid range milestone) and I did not hit the GRUB bug, despite having quite complicated multi-disk setups, with Windows knocking about to.
As I expect to move onto “factory-tested” repo Index of /factory-tested after, so I can get new breakage. This release it seems like the installer has (again) been disappointingly stable… that UI surely offers easy improvment with thought, lots of tweaks were made from feedback for 11. when it got fair amount of work for 11.2 IIRC).
The old practices of running in Virtual box a live CD install to check out applications, seems less useful, than actually running Tumbleweed on real desktop for me. But that’s another low risk way to test package intergration if you are power user of some packages.
On Wed, 13 Jul 2011 15:36:02 +0000, robopensuse wrote:
> I did test 11.4 RC (I think a mid range milestone) and I did not hit
> the GRUB bug, despite having quite complicated multi-disk setups, with
> Windows knocking about to.
With 11.4 and GRUB, the M-series were OK; the bug didn’t appear (if my
memory is right) until RC1 when Windows systems weren’t recognised. That
was fixed in RC2 but at the expense of other Linux systems which then
became invisible. “It’s all part of life’s rich pageant.”
–
Graham Davis, Bracknell, Berks.
openSUSE 11.4; KDE 4.6.5; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210; Sound: ATI SBx00 Azalia (Intel HDA);
Wireless: BCM4306
Yep, I don’t think releases are worth the drama. What I’d like is a bullet proof core install environment providing fall back kernels that gets the very basics running; then add all the “sugar”. All the packages I really use heavily seem to get updated anyway, so what’s the point of installing them before they’re needed? Especially now with Tumble not using delta rpms.
I installed RC1 and it was recognised, though I had 2 disks installing away from the 'dows disk. Probably didn’t bother with RC2 because it was too late by that stage anyway to make a difference to the release.
Rob