On Fri, 2012-02-10 at 17:20 +0100, Kim Leyendecker wrote:

On 10.02.2012 00:24, Togan Muftuoglu wrote:

...

In-Reply-To:

On 02/09/12 at 10:54pm, Jos Poortvliet wrote:

...

On Tue, Feb 7, 2012 at 2:27 AM, Koushik Kumar Nundy wrote:

...

On 7 February 2012 02:26, Jos Poortvliet wrote:

...

If I don't reply to mails in the next hours - I'm attempting an in-place upgrade of my 32-bit system to 64. Just to see if Zypper et all. like me :D

Please document the process. I would like to do something like that on my Li-f-e box too.

My advice: don't.

Ok, I managed, but only with an openSUSE DVD and quite a few hours of un-breaking my system ;-)

The idea is that you first do the kernel, than reboot, do zypper/rpm/etc and the rest. But after doing the kernel it missed the modules to mount my root so game over there... Interesting, I have done it many times with no side effects as yet. I start with editing /etc/zypp/zypp.conf where it describes the architecture which is normally autodetected there I put x86_64 then run zypper ref followed by zypper dup and finaly reboot with 64.

Togan

Do you think this also works from x86_64 to i586?

thanks, --kdl

If there are things to document, we should add it to http://upgrade.opensuse.org. Much of what we've pointed out on this thread on how to do upgrades is already mentioned on this page. But as always, it needs to be regularly polished. In fact, looking at it right now, I see 12.1 is not listed as one of the "tested" versions. Bryen M Yunashko openSUSE Project -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 02/10/2012 05:20 PM, Kim Leyendecker wrote:

...

Togan

Do you think this also works from x86_64 to i586?

Can't tell I never did that way maybe it would work -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 10.02.2012 17:08, Bryen M Yunashko wrote:

On Fri, 2012-02-10 at 17:20 +0100, Kim Leyendecker wrote:

...

On 10.02.2012 00:24, Togan Muftuoglu wrote:

...

In-Reply-To:

On 02/09/12 at 10:54pm, Jos Poortvliet wrote:

...

On Tue, Feb 7, 2012 at 2:27 AM, Koushik Kumar Nundy wrote:

...

On 7 February 2012 02:26, Jos Poortvliet wrote:

...

If I don't reply to mails in the next hours - I'm attempting an in-place upgrade of my 32-bit system to 64. Just to see if Zypper et all. like me :D

Please document the process. I would like to do something like that on my Li-f-e box too.

My advice: don't.

Ok, I managed, but only with an openSUSE DVD and quite a few hours of un-breaking my system ;-)

The idea is that you first do the kernel, than reboot, do zypper/rpm/etc and the rest. But after doing the kernel it missed the modules to mount my root so game over there... Interesting, I have done it many times with no side effects as yet. I start with editing /etc/zypp/zypp.conf where it describes the architecture which is normally autodetected there I put x86_64 then run zypper ref followed by zypper dup and finaly reboot with 64.

Togan

Do you think this also works from x86_64 to i586?

thanks, --kdl

If there are things to document, we should add it to http://upgrade.opensuse.org. Much of what we've pointed out on this thread on how to do upgrades is already mentioned on this page. But as always, it needs to be regularly polished.

In fact, looking at it right now, I see 12.1 is not listed as one of the "tested" versions.

Bryen M Yunashko openSUSE Project

a 12.1 test machine for my experiment is already installing I'll report ASAP. thanks, --kdl -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

Le 10/02/2012 20:06, Christian Boltz a écrit :

In other words: Don't try this at home ;-)

somebody seems to have a clean way to do this, have to be documented after tests jdd -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 02/10/12 at 08:11pm, jdd wrote:

Le 10/02/2012 20:06, Christian Boltz a écrit :

...

In other words: Don't try this at home ;-)

somebody seems to have a clean way to do this, have to be documented after tests

I tend to go with the suggestion of Christian and therefore I have not entered in to the wiki. I also, like Christian, have done upgrades from 11.1 to 12.1 as well ( but I cheated with upgrading to milestone in the between ;) and lots of devel repos being used also) yet the question is when something goes of then one has to know enough to recover from the situation. For the newcomers I do not think that is the best solution. They should follow the distro recommended ways until they gain sufficient knowledge of the system Togan -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On Fri, Feb 10, 2012 at 08:11:16PM +0100, jdd wrote:

Le 10/02/2012 20:06, Christian Boltz a écrit :

...

In other words: Don't try this at home ;-)

somebody seems to have a clean way to do this, have to be documented after tests

There is no 'clean', 'simple', or 'easy' way of doing a shift from a 32 to a 64 bit install while the system is in operation. You can do it half way clean remotly by booting the 64bit install initrd and kernel. Then your 32bit root fs isn't found and you have to tell YaST to show all partitions and select the one in question. This is the very short version. You have to deal with your network configuration and have to be aware that the existing ssh keys aren't used (yes, the feature request to allow the usage of an existing ssh key got filed some time back; I consider this more and more less important as this might already be scriptable for enhanced users and we have AutoYaST). Not to talk about potential migration issues with data used and served by daemons. Oh well, there are many other ways to get a working 64bit libzypp stack. And all offer multiple pitfalls to get lost. We have 75834 open issues and a lot of missing documentation. Why not working on the more important and even more obvious stuff? Trying a move from 32 to 64 bit or from libc5 to libc6 while the system is live offers many learning opportunities. But these aren't things we should waste our valueable main project time for. And this is nothing we should lead our users via the wiki to! Risk³. Instead stay focussed and have a nice weekend. ;) Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Fri, 2012-02-10 at 22:16 +0100, Lars Müller wrote:

We have 75834 open issues and a lot of missing documentation. Why not working on the more important and even more obvious stuff?

Valid point. Though people tend to focus on issues they see immediately relevant in front of them. Thus, what is deemed "more important" by some may not be the case for others, not by actual importance but by obviousness to themselves. Maybe a solution to getting things that *should be higher priority* is to come up with an actual prioritization list? I think people tend to react more efficiently that way. I'd be curious to see if we could somehow group the 75,834 open issues that are low-hanging fruits we can quickly take a stab at. Bryen -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

If someone is interested in writing such an article on the wiki, for what ever reason, a tutorial about how to keep .thunderbird, .firefox and .kde files and install a fresh system. This would be very interesting and really help people. thanks in advance, --kdl -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On Friday, February 10, 2012 17:41:39 Togan Muftuoglu wrote:

On 02/10/2012 09:07 AM, jdd wrote:

...

Le 10/02/2012 00:24, Togan Muftuoglu a écrit :

...

Interesting, I have done it many times with no side effects as yet. I start with editing /etc/zypp/zypp.conf where it describes the architecture which is normally autodetected there I put x86_64 then run zypper ref followed by zypper dup and finaly reboot with 64.

seems very good. Is this documented on the wiki? if not can you build a SDB page? I'm sure many people will be interested!

thanks jdd

Oops just to make it complete I also have the following in my /etc/zypp/zypp.conf

commit.downloadMode = DownloadInAdvance

This way if there is a problem with the mirrors or with network I make sure all the packages are actually downloaded before the install process starts

The interesting thing is that this is the approach I wanted to take but AJ (I BLAME HIM) told me it's a bad idea: he was afraid RPM and other core stuff would get updated at some point in the process and as the 64 bit binary wouldn't run on the 32bit system, the upgrade would break and leave the system in an un-boot-able state.

Togan