Re: Upgrade from 32bit Sarge to 64bit Etch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mitja Podreka wrote:
> Hello
>
> I've thought out my migration plan, but since the box in question is my
> computer at work, I cannot afford to "loose" it for long.
> I would like to ask you for opinion or suggestions.
>
> I was thinking to do it like this:
> 1. Upgrade my 32bit Sarge to 32bit Etch
> 2. Make a list of installed packages
> 3. On separate partition install a base 64bit Etch
> 4. Install the list of packages from 32bit Sarge
> 5. Replace the /etc folder with /etc folder from 32bit Etch version
> 6. Delete /home folder and mount /home partition in it's place
>
> Will it work?
>
> Thanks,
> Mitja
>
>
Yes and no.
1) Should be fine.
2) Should be fine.
3) Should be fine.
4) Here you could run into problems because some packages that are
available for 32-bit are not available for 64-bit, but there are not
many, and most of those packages are non-free so if you stick to
packages in main, you should be OK.
5) No, that would most surely break the system. Leave the 64-bit /etc
like it is, just modify the files that you need to change.
6) That should work, although you're not specifying which system the
/home is from. AFAIK, the configuration data in /home will be fine
migrating it from a 32-bit system to a 64-bit system as long as the
versions of the programs that use said data are the same.
Another way you might want to go about it, is to just upgrade a 32-bit
setup to a 64 bit one, rather than installing multiple versions. That
being said, I have both the 32-bit version and the 64-bit version
installed, but use the 32 bit version most of the time. I *could* use
the 64-bit version and chroot to the 32-bit apps that I need that are
not available for 64-bit, but it's not very often that I need the 64-bit
power and it IMO isn't worth the trouble of setting it all up.
Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGYUQ4iXBCVWpc5J4RAmW2AJ928No0eIPt+pEd4s/Y/MvGYLC2hACfcyyZ
Zjfwm0vWJUIA5CPPTdh9u8k=
=dHlh
-----END PGP SIGNATURE-----
Reply to: