[opensuse] Migrate from 32bit to 64bit?
Is there a "decent way" to migrate a fully operational 32-bit installation of openSuSE 10.3 to the x86_64 version? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I would just 'upgrade' it with the 64bit DVD. B-) On Friday 22 February 2008 9:59:52 am Anders Norrbring wrote:
Is there a "decent way" to migrate a fully operational 32-bit installation of openSuSE 10.3 to the x86_64 version?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 February 2008 09:14, Brad Bourn wrote:
I would just 'upgrade' it with the 64bit DVD.
!!! Danger, Will Robinson !!! We've been told many times (including from the "horse's mouth") that this will not work and will render your system inoperable!
B-)
On Friday 22 February 2008 9:59:52 am Anders Norrbring wrote:
Is there a "decent way" to migrate a fully operational 32-bit installation
of openSuSE 10.3 to the x86_64 version?
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 February 2008 09:14, Brad Bourn wrote:
I would just 'upgrade' it with the 64bit DVD.
!!! Danger, Will Robinson !!!
We've been told many times (including from the "horse's mouth") that this will not work and will render your system inoperable!
Which in other words (and my findings) means do a reinstall, reconfigure and all that.. *sigh* Anders.
B-)
On Friday 22 February 2008 9:59:52 am Anders Norrbring wrote:
Is there a "decent way" to migrate a fully operational 32-bit installation
of openSuSE 10.3 to the x86_64 version?
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
__________ Information from ESET NOD32 Antivirus, version of virus signature database 2896 (20080222) __________
The message was checked by ESET NOD32 Antivirus.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anders Norrbring schreef: |> On Friday 22 February 2008 09:14, Brad Bourn wrote: |>> I would just 'upgrade' it with the 64bit DVD. |> !!! Danger, Will Robinson !!! |> |> We've been told many times (including from the "horse's mouth") that |> this will not work and will render your system inoperable! | | | Which in other words (and my findings) means do a reinstall, reconfigure and all that.. *sigh* | | Anders. | | Far out the best option, besides that, you will have a lot of extra fun, and able to install the apps yourealy need, and more of these convenient side-effects, good luck, and happy install ;) - -- Have a nice day, M9. Now, is the only time that exists. ~ Besturingssysteem: Linux 2.6.22.17-0.1-default x86_64 ~ Current user: monkey9@AMD64x2-sfn1 ~ System: openSUSE 10.3 (x86_64) ~ KDE: 4.0.1 (KDE 4.0.1) "release 9.1" ~ OS: Linux 2.6.22.17-0.1-default x86_64 ~ Huidige gebruiker: monkey9@AMD64x2-sfn1 ~ Systeem: openSUSE 10.3 (x86_64) ~ KDE: 3.5.7 "release 72.6" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHvwvYX5/X5X6LpDgRAk5rAKCnMejXkiPydk3E1amhYZoEhnnnugCgurk6 dWLiZYmye968DF7g/xMQZXk= =JePj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 February 2008 18:32:41 Anders Norrbring wrote:
On Friday 22 February 2008 09:14, Brad Bourn wrote:
I would just 'upgrade' it with the 64bit DVD.
!!! Danger, Will Robinson !!!
We've been told many times (including from the "horse's mouth") that this will not work and will render your system inoperable!
Which in other words (and my findings) means do a reinstall, reconfigure and all that.. *sigh*
reinstall yes, but not a reconfigure. The configuration files don't differ between the 32 and 64 bit versions (things like ld.so.config excepted, because it points to lib64 as well as lib, but the config files that give direct paths to libraries are few and far between), so just be sure to back them all up, and restore them after the reinstall, and you should be good to go Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring wrote:
On Friday 22 February 2008 09:14, Brad Bourn wrote:
I would just 'upgrade' it with the 64bit DVD. !!! Danger, Will Robinson !!!
We've been told many times (including from the "horse's mouth") that this will not work and will render your system inoperable!
Which in other words (and my findings) means do a reinstall, reconfigure and all that.. *sigh*
Great part of the configuration resides in users' $HOME directories - so if you manage not to destroy them during new installation, chances are pretty high, you'll end up with a working system with similar look & feel. As for system configuration you may try to save /etc/sysconfig directory from the old system and merge it (manualy) with the freshly installed one. 'vimdiff {/path/to/32bit,}/etc/sysconfig/file' or any other utility for sycnchronizing files will be your friend then, yet *be aware* that some knowledge of the operating system will be needed (to judge where you can just overwrite the changes). Best regards Petr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-02-22 at 18:32 +0100, Anders Norrbring wrote:
On Friday 22 February 2008 09:14, Brad Bourn wrote:
I would just 'upgrade' it with the 64bit DVD.
!!! Danger, Will Robinson !!!
We've been told many times (including from the "horse's mouth") that this will not work and will render your system inoperable!
Which in other words (and my findings) means do a reinstall, reconfigure and all that.. *sigh*
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning). If you did this the previous time (when you installed the 32-bit system) It is merely making a backup of you precious data, and re-install the system with the 64-bit version, but this time feed the autoinstaller with the old xml-file. needles to say that that xml-file should be kept on a different media :-)) One might even tweak that xml-file (for adjusting partitionsize, other filesystems....) BTW, if you don't have that xml-file, it is possible to generate it with YAST, (that one even includes all the additional changes you've done with yast) remember all other (manual) changes, you have to replay manually again hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
...
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning).
I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
If you did this the previous time (when you installed the 32-bit system) It is merely making a backup of you precious data, and re-install the system with the 64-bit version, but this time feed the autoinstaller with the old xml-file.
Is this XML configuration file updated as you modify your system configuration along the way?
needles to say that that xml-file should be kept on a different media :-)) One might even tweak that xml-file (for adjusting partitionsize, other filesystems....)
If YaST doesn't keep it updated to reflect configuration changes made as the system's configuration evolves, it's of limited usefulness when upgrading months or years down the line...
BTW, if you don't have that xml-file, it is possible to generate it with YAST, (that one even includes all the additional changes you've done with yast)
OK. That's good. I looked around in YaST (on my 10.3 system) and didn't see this function. No doubt I just don't know what it's called. Where is it accessed?
remember all other (manual) changes, you have to replay manually again
Eh? By "manual" do you mean direct configuration file editing not mediated by a YaST module?
hw
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
...
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning).
I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....)
If you did this the previous time (when you installed the 32-bit system) It is merely making a backup of you precious data, and re-install the system with the 64-bit version, but this time feed the autoinstaller with the old xml-file.
Is this XML configuration file updated as you modify your system configuration along the way?
needles to say that that xml-file should be kept on a different media :-)) One might even tweak that xml-file (for adjusting partitionsize, other filesystems....)
If YaST doesn't keep it updated to reflect configuration changes made as the system's configuration evolves, it's of limited usefulness when upgrading months or years down the line...
BTW, if you don't have that xml-file, it is possible to generate it with YAST, (that one even includes all the additional changes you've done with yast)
OK. That's good. I looked around in YaST (on my 10.3 system) and didn't see this function. No doubt I just don't know what it's called. Where is it accessed?
With 10.3 autoinstall in not installed by default, you can still add it on later. yast -> miscellaneous -> autoinstallation -> tools -> create reference profile Select what to want to detect file is written (after a save) under: /var/lib/autoinstall/repository/<yourfilename>
remember all other (manual) changes, you have to replay manually again
Eh? By "manual" do you mean direct configuration file editing not mediated by a YaST module?
Yes, For instance, untill recently there was no yast-module for sshd. So just plain good ol' vi..... Perhaps tweaks is inittab or fstab. I used both methods to create a library of xml-files for any sort of machine/xen-image i have to deploy. Only word on caution is when using xml-file generated for older versions. For instance, since 10.3 they have threads and you can define additional repo's (local update-server!) before installing. But within the same release, from 32->64 it will be safe. Save me a huge amount of time -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 February 2008 15:28, Hans Witvliet wrote:
...
yast -> miscellaneous -> autoinstallation -> tools -> create reference profile
Select what to want to detect file is written (after a save) under: /var/lib/autoinstall/repository/<yourfilename>
Cool. I don't feel dense not having found _that_ particular corner of YaST!
...
Eh? By "manual" do you mean direct configuration file editing not mediated by a YaST module?
Yes, For instance, untill recently there was no yast-module for sshd. So just plain good ol' vi..... Perhaps tweaks is inittab or fstab.
I used both methods to create a library of xml-files for any sort of machine/xen-image i have to deploy.
Only word on caution is when using xml-file generated for older versions. For instance, since 10.3 they have threads and you can define additional repo's (local update-server!) before installing. But within the same release, from 32->64 it will be safe.
Save me a huge amount of time
No doubt. Thanks for the information. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans Witvliet wrote:
On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning). I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....) Are you going to add that there ? Or is bugzilla just a dump, in too many cases ?
If you did this the previous time (when you installed the 32-bit system) It is merely making a backup of you precious data, and re-install the system with the 64-bit version, but this time feed the autoinstaller with the old xml-file. Is this XML configuration file updated as you modify your system configuration along the way?
needles to say that that xml-file should be kept on a different media :-)) One might even tweak that xml-file (for adjusting partitionsize, other filesystems....) If YaST doesn't keep it updated to reflect configuration changes made as the system's configuration evolves, it's of limited usefulness when upgrading months or years down the line...
BTW, if you don't have that xml-file, it is possible to generate it with YAST, (that one even includes all the additional changes you've done with yast) OK. That's good. I looked around in YaST (on my 10.3 system) and didn't see this function. No doubt I just don't know what it's called. Where is it accessed?
With 10.3 autoinstall in not installed by default, you can still add it on later. Is it called "autoyast2" ? Why is it not installed by default ?
Kind regards Philippe --
yast -> miscellaneous -> autoinstallation -> tools -> create reference profile Select what to want to detect file is written (after a save) under: /var/lib/autoinstall/repository/<yourfilename>
remember all other (manual) changes, you have to replay manually again Eh? By "manual" do you mean direct configuration file editing not mediated by a YaST module?
Yes, For instance, untill recently there was no yast-module for sshd. So just plain good ol' vi..... Perhaps tweaks is inittab or fstab.
I used both methods to create a library of xml-files for any sort of machine/xen-image i have to deploy.
Only word on caution is when using xml-file generated for older versions. For instance, since 10.3 they have threads and you can define additional repo's (local update-server!) before installing. But within the same release, from 32->64 it will be safe.
Save me a huge amount of time
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philippe Landau wrote:
Hans Witvliet wrote:
On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning). I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention. Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....) Are you going to add that there ? Or is bugzilla just a dump, in too many cases ?
Andreas Jaeger wrote:
see control.xml:
false We disabled it by purpose since it takes time and it was considered benefecial in general for enterprise server environments but not in general for openSUSE users. It's easy to change it - the question is: Does it make sense to change it for everybody by default? How much time does it take ?
Kind regards Philippe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 02/23/2008 09:41 PM, Philippe Landau wrote:
Andreas Jaeger wrote:
see control.xml:
false We disabled it by purpose since it takes time and it was considered benefecial in general for enterprise server environments but not in general for openSUSE users. It's easy to change it - the question is: Does it make sense to change it for everybody by default?
How much time does it take ?
Kind regards Philippe
To make the change, or answer all the questions and address all the problems created by it with users who are really just "having fun"? ;-) -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2008-02-23 at 14:41 +0100, Philippe Landau wrote:
Philippe Landau wrote:
Hans Witvliet wrote:
On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning). I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention. Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....) Are you going to add that there ? Or is bugzilla just a dump, in too many cases ?
Andreas Jaeger wrote:
see control.xml:
false We disabled it by purpose since it takes time and it was considered benefecial in general for enterprise server environments but not in general for openSUSE users. It's easy to change it - the question is: Does it make sense to change it for everybody by default? How much time does it take ?
hard to give an exact number, depends on the speed of you cpu... But i would say, less than one minute. I know, every second is precious, so don't waste any time. But doing an installation manually takes considerably more time So by using the xml-file once, you have gained already (besides the assurance that it is installed identically) To give you a comparison, Installing an default kde-system from DVD on an HP-DL360 manually, all the key-cliks and rpm-installation is about two hours, plus needing to update. Using an pxe-boot & xml-file, it takes 15 minutes, from reboot to fully installed & updated system, And in those 15 minutes, the HP-bios needs 5 minutes... Autoyast is great! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2008-02-23 at 12:59 +0100, Philippe Landau wrote:
With 10.3 autoinstall in not installed by default, you can still add it on later. Is it called "autoyast2" ? Why is it not installed by default ?
Kind regards Philippe
Thankfully, not everything possible to install gets installed **sigh of relief ** If you want it, install it, if you don't know what it is, there is no need to install it, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans Witvliet
On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
...
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning).
I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....)
see control.xml:
Hans Witvliet
writes: On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
...
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning).
I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....)
see control.xml:
false We disabled it by purpose since it takes time and it was considered benefecial in general for enterprise server environments but not in general for openSUSE users. It's easy to change it - the question is: Does it make sense to change it for everybody by default?
Most likely no. I used it frequently on SLES, but rarely in openSuSE. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
[8<]
I used both methods to create a library of xml-files for any sort of machine/xen-image i have to deploy.
Only word on caution is when using xml-file generated for older versions. For instance, since 10.3 they have threads and you can define additional repo's (local update-server!) before installing. But within the same release, from 32->64 it will be safe.
Save me a huge amount of time
Hans, That's all and well.. I've created the xml file (config.xml), but I can't get it to be used by autoyast at installation time after I renamed it to "autoinst.xml". No matter if I try to read it from floppy "autoyast=floppy" or via http "autoyast=http://192.168.22.34/". It fails in all attempts with a message saying "A profile for this machine could not be found or retrieved." Etc, etc.. Are there any specific things I need to edit in the file generated to make it work? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Feb 24, 2008 at 5:48 PM, Anders Norrbring
Hans, That's all and well.. I've created the xml file (config.xml), but I can't get it to be used by autoyast at installation time after I renamed it to "autoinst.xml". No matter if I try to read it from floppy "autoyast=floppy" or via http "autoyast=http://192.168.22.34/". It fails in all attempts with a message saying "A profile for this machine could not be found or retrieved." Etc, etc..
Are there any specific things I need to edit in the file generated to make it work?
Not that it is helpful, but my experience also says the same. I remember I read from some documentation that using autoyast=device://sdb1/autoyast.xml in the GRUB should be able to work. Sadly it didn't. IIRC, it gave a similar error as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I would just 'upgrade' it with the 64bit DVD.
Which unfortunately doesn't work.. It starts by showing no available partitions, then I "show all" and mark the system partition. I get a pop-up saying it will change the architecture, and I agree (naturally). Upgrade process starts, and I end up with the 32-bit system anyway. Anders.
B-)
On Friday 22 February 2008 9:59:52 am Anders Norrbring wrote:
Is there a "decent way" to migrate a fully operational 32-bit installation of openSuSE 10.3 to the x86_64 version?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
__________ Information from ESET NOD32 Antivirus, version of virus signature database 2896 (20080222) __________
The message was checked by ESET NOD32 Antivirus.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brad Bourn escribió:
I would just 'upgrade' it with the 64bit DVD.
No way, that will never work. You have to backup your data and configuration files, then reinstall a clean copy of the OS. -- "Morality is merely an interpretation of certain phenomena — more precisely, a misinterpretation." - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring wrote:
Is there a "decent way" to migrate a fully operational 32-bit installation of openSuSE 10.3 to the x86_64 version?
Anders, I can only give you my experience, which was NOT good. I tried it on 1 box only. Yast simply can't handle resolving all of the conflicts with an upgrade. Also, those application that place some pits and pieces of software in the user's /home/? dir. will often get messed up. What I did, was to keep the /home/? dirs, but clean out any such software AND the .kde dir. Not deleting or cleaning out the later caused problem even with a clean install. I'd recommend that you delete all dirs. mentioned and format all partitions during a clean install but /home. Fred -- "Security" in Windows comes from patching a sieve. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (13)
-
Anders Johansson
-
Anders Norrbring
-
Andreas Jaeger
-
Brad Bourn
-
Chee How Chua
-
Cristian Rodríguez
-
Fred A. Miller
-
Hans Witvliet
-
Joe Morris
-
M9.
-
Petr Cerny
-
Philippe Landau
-
Randall R Schulz