> The only way is to do a new installation. There is a lot of pitfalls,
> e.g. post/pre install scripts don't need to work,
I see. I actually tried to replace the packages from rescue (tried this
on a base 32-bit 10.3/Gnome installation inside VMware):
* Start with a 32-bit opensuse 10.3 installation
* boot into 64-bit rescue
* mount the 32-bit 10.3 filesystem (e.g. under /mnt)
* mount the media with the 64-bit rpm packages
* find all installed 32-bit packages (rpm -q -a)
* for each 32-bit package ($pkg32), find the appropriate
64-bit package ($pkg64)
* then update and cleanup db
rpm -r /mnt --nodeps --noscripts --ignorearch -Uhv $pkg64
rpm -r /mnt --nodeps --noscripts --justdb -e ${pkg32}.i586
* finally install all 32-bit compatibility packages (necessary?):
rpm -r /mnt -Uhv *-32bit-*.rpm
* chroot to /mnt and run depmod, add noresume to grub's menu.lst and
call mkinitrd to rebuild a 64-bit initrd
* reboot
The system came up then, I was able to login but there were some (many?)
glitches, probably due to the pre/post-scripts you mentioned.
> not all on-disk formats survive
> the switch, especially home-grown databases.
Thanks for the reminder to dump all sql/ldap/etc databases!
> That's why we do not provide this functionality.
I was just curious if there was an unsupported path, like something above
having a sticker "you may try it but don't ask us if it breaks"...
A fresh installation is always possible.
Regards, Walter
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
