On Monday 13 October 2008, r wrote:

writes:

...

I have upgraded from 9.3 -> 10 -> 10.2 -> 10.3 -> 11, the most serious issue was a reiserfs bug causing system hangs.

Whats the cause ? How did you solved it. ( I use reiserfs too )

You need to update the kernel from the update repository for the fix.

...

If you're fairly experienced with linux, it's the best option in my opinion (you need to update RPM first).

what dou you mean " you need to update RPM first ". The rpm package itself ?

Yes, opensuse 11 RPM packages are incompatible with earlier RPM versions. I forgot to mention that I was upgrading from the repositories in most cases with Yast. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 13 October 2008, r wrote:

writes:

...

...

Whats the cause ? How did you solved it. ( I use reiserfs too )

You need to update the kernel from the update repository for the fix.

So I update rpm, upgrade to 11.0 and then update the kernel from the Yast2 openSuSE basic repositry ??

Well, if you feel adventurous you may add the update repository and install the patches from there when upgrading. If you upgrade from a DVD, I expect Yast to handle everything, however I have no experience with the process.

...

I forgot to mention that I was upgrading from the repositories in most cases with Yast.

Do you mean online upgrade ?? I was thinking to dowload openSuSE 11.0 dvd and upgrade from that ( local dvd ). Then update the kernel from the online repository.

I have never upgraded using disc media, I prefer upgrading straight from a fast mirror. I have no reason to believe it would be much different, just be certain that you check the packages that Yast will remove because of dependency problems. Having a list of installed packages beforehand with rpm - qa > package-list.txt would also help. Regards Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-13 at 11:25 -0000, r wrote:

Do you mean online upgrade ?? I was thinking to dowload openSuSE 11.0 dvd and upgrade from that ( local dvd ). Then update the kernel from the online repository.

Yes, upgrading booting the install DVD is the recommended method to do upgrades. Safer and "supported", in as much as anything is supported here. I have done that procedure since 5.3 up to 11.0, with only one major problem from 7.3 to 8.1, which forced me to install fresh. I had no problems going from 10.3 to 11.0 worth mentioning. Well, perhaps... if you have encrypted partitions they might not be recognized during the upgrade: mine weren't, but worked fine after the first boot. Might be a problem if your home or root are encrypted, I guess. Recommendation: Do a full backup first. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjzRhIACgkQtTMYHG2NR9XbaQCfdZV1pCJth+9PZSxh4V/X5Zr3 aQUAmwYP7bS5huzipujRdxlmk9axmkGh =nU7H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-13 at 09:46 -0400, Larry Stotler wrote:

On Mon, Oct 13, 2008 at 8:58 AM, Carlos E. R. <> wrote:

...

I have done that procedure since 5.3 up to 11.0, with only one major problem from 7.3 to 8.1, which forced me to install fresh.

I just recently ran into that as well on an old laptop I was playing with. The 8.1 upgrade broke the install. I thought it was just a fluke, but I guess it was more serious. Hadn't even used that old of a version for a long time.

- From 7.x to 8.x yast was changed into yast2, and it had bugs. In my case, yast forgot to mount all needed partitions (/usr, /opt...) and ran out of space during the upgrade. You can guess the disaster... Now, I always double check in a console. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjzYLoACgkQtTMYHG2NR9Xm2wCeLuxtbVBgSFqmgVkeS6AW3TC3 7mQAn1dEIS0sXT7iPhwOz1LxOxMF2nmH =Youq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-10-13 at 13:56 -0000, r wrote:

Carlos E. R. writes:

...

Yes, upgrading booting the install DVD is the recommended method to do upgrades. Safer and "supported", in as much as anything is supported here.

ok but : is there difference between an online upgrade and a dvd-iso-image local upgrade ??

Yes, a few. The main one is that, with a dvd upgrade, the main system is stopped, and the job is done from another linux. It can write anywhere without problems, there are no complications of a program being running at the same time that its libraries are being replaced with new ones. It works because the program is fully loaded in memory, but weird things can happen (like trying to run a program with a mixture of libraries and kernel modules). For example, the problem of having to upgrade first rpm does not exist. Nor any similar problem. Disadvantages? Probably slower, a part of the memory is occupied with a ramdisk, and things are read from a slow dvd instead of HD. I prefer not running the risk on my "production" or main partition. However, I do run "zypper dup" on a chrooted factory, and that is also risky. But being the factory partition, it doesn't matter if it is screwed. I don't even bother to back it up, except a few configuration files and data. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjzYCEACgkQtTMYHG2NR9XtLwCdF2oHJZB7Yk3KuAfhyhqdFSNC RM0AnAkopI6uYYKKobscW2oJcjAQ14iG =HVNT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Oct 13, 2008 at 6:05 AM, wrote:

I have upgraded from 9.3 -> 10 -> 10.2 -> 10.3 -> 11, the most serious issue was a reiserfs bug causing system hangs.

What bug was this? I never ran across it..... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Oct 13, 2008 at 10:00 AM, wrote:

On Monday 13 October 2008, Larry Stotler wrote:

...

On Mon, Oct 13, 2008 at 6:05 AM, wrote:

...

I have upgraded from 9.3 -> 10 -> 10.2 -> 10.3 -> 11, the most serious issue was a reiserfs bug causing system hangs.

What bug was this? I never ran across it.....

It's https://bugzilla.novell.com/show_bug.cgi?id=389656. Beagle would trigger it frequently.

Ah. No wonder. Since I don't install that dog, I never had a problem..... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Oct 13, 2008 at 3:26 PM, Carlos E. R. wrote:

On Monday, 2008-10-13 at 13:07 -0400, Andrew Joakimsen wrote:

...

On Mon, Oct 13, 2008 at 4:26 AM, wrote:

...

I'm wondering if upgrade from 10.3 to 11.0. Is the Yast2 upgrade sure ?? Does anyone did try the upgrade ?? Will I have problems ?? Is there a better way than yast2 ?

FWIW if you have any packages from a repository that is not suse-oss or non-oss I would suggest you remove them before the install. The installer has messed up systems (to the point they will not boot and the installer cannot "repair" them) due to dependency hell caused by e.g. Packman packages.

I think removing the extra repos might be enough. Then tell the installer to change the vendors of everything to suse.

I don't think that would have helped. IIRC when the installer loads (I did this booting from the CD or DVD) it does not load the additional repositories. The installed packages are the ones that created a conflict. I think this was doing an upgrade from 10.1 > 10.2. Now I'm too paranoid to try any upgrade again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org