Hello, On Wed, 23 Jul 2014, Cristian Rodríguez wrote:

El 23/07/14 09:44, Mark Hounschell escribió:

...

Is doing an UPDATE from 12.3 (32 bit) to 13.1 (64 bit) supported.

Supported ? no.. though if you do it carefully it might actually work. If I recall correctly, someone "documented" how to do it in a mailing list post a while ago, not sure exactly if it was on this list or in -factory.

That should've been me, here ;) Mind you: _DO HAVE A BOOTABLE INSTALL MEDIUM READY_ and be prepared to start from scratch. In a nutshell: - make a full backup or rsync the system to a second partition, which you can then use as the base for the upgrade and still have the original system fully functional. E.g.: rsync -auxlPRAXSHD --delete / /NEW_ROOT (this assumes that you do not have a seperate /usr, /var etc.) - Edit /NEW_ROOT/etc/fstab, /NEW_ROOT/boot/grub/menu.lst or /NEW_ROOT/etc/grub2/... to refer to the partition on which NEW_ROOT is. - Add an entry for NEW_ROOT in the already installed grub(2). E.g. if you now have e.g. title openSUSE 12.3 - 3.1.10-1.29 root (hd0,0) kernel /boot/vmlinuz-3.1.10-1.29-default root=/dev/disk/by-label/ROOT ... initrd /boot/initrd-3.1.10-1.29-default add an entry like e.g. title TOBE openSUSE 13.1 - 3.1.10-1.29 root (hd1,0) kernel /boot/vmlinuz-3.1.10-1.29-default root=/dev/disk/by-label/NEW_ROOT ... initrd /boot/initrd-3.1.10-1.29-default your kernel-version will be different, I still run 12.1 ;) - Reboot to verify your old system is still running ok - Reboot from NEW_ROOT by using the TOBE oS 13.1 entry - verify grub-config, /etc/fstab - edit /etc/zypp.conf arch = i586 *MUST* be changed as the first step to arch = x86_64 also, it's wise to have download.media_preference = volatile and commit.downloadMode = DownloadInAdvance - change the Repos: perl -pi.bak -e 's/_12.3/_13.1/g' *.repo Think about downloading the 13.1 ISO in advance and add that as a repo, it speeds up the upgrade a lot. Also, have a look at the Repo-Prios. It should be: Packman < Update < ISO < oss/non-oss - zypper clean - zypper ref - zypper dup - if all goes well, you should get new entries in the grub-config of NEW_ROOT. CHECK the bootloader config _before_ you reboot! Copy that entry to the grub of the old ROOT (unless you switch the bootloader). - add a "chainloader" entry for NEW_ROOT to the existing bootloader (from the old system), so you can test that booting with that works too - Reboot to NEW_ROOT as before and check all is working. - install the bootloader from NEW_ROOT, so that it is the default. Add entries for the old ROOT to the new bootloader. Once you're satisfied all is running well, you can scratch the old ROOT (or keep it as a backup), and use it as the NEWNEW in the next iteration. I probably have forgotten something. Even important. Make sure beforehand, that the NEW_ROOT is a copy to play with. Restart with another rsync from the old system when something gets hosed and you want to try again. Any questions? -dnh -- "I stopped at Land's End, because to go any further would have been Scilly." -- Robert Billing -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-07-23 a las 11:10 -0400, Cristian Rodríguez escribió:

Supported ? no.. though if you do it carefully it might actually work. If I recall correctly, someone "documented" how to do it in a mailing list post a while ago, not sure exactly if it was on this list or in -factory.

I did, years ago. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPQ7toACgkQja8UbcUWM1x7vQD/dQh/QHI7Isc8m88K1khd+yzK ppOUIONfWIXHFxugniIBAJyQTd9LQ5Rl/KTDMCYjsUwo90I1N3tiE8aXGsrSA1+8 =F83n -----END PGP SIGNATURE-----