Re: [gentoo-user] Gentoo x86 to AMD64
Volker Armin Hemmann wrote: why downtime? just create a directory, install the 64bit gentoo in that directory. Tar everything up, boot from livecd, untar the tar into the old system. Done. Downtime depends on the speed of your harddisks. Something between 5 and 30minutes. Top. So effectivly the same as the original post, just with all the setup bits in th process rather than keeping the config in place.Hmmm... Btw, why mailserver? Why not? :) It's also a webserver, svn server, and a few other things.
Re: [gentoo-user] Gentoo x86 to AMD64
Alan McKinnon wrote: On Friday 22 August 2008 17:48:32 Anthony Metcalf wrote: What about re-building every single package, and re-installing it isn't a complete -reinstall? I can understand that this wouldn't work without the re-boot to live cd step, as you would end up with incompatible libraries/binaries, and with a 32bit kernel trying to run 64bit apps and crap.but this should avoid all that, with minimal downtime. Looks easy right? So, what tool chain on this 32 bit machine are you going to use to build the 64 bit binaries you actually want to output? You know you are going to do heaps of setup actions, build a new tool chain then essentially do emerge -e world. Much easier to just copy stuff off a 64-bit stage3 then do emerge -e world. Easier, probably, but I am bothered about downtime on this machine too, it doesn't do anything vital, but it is a mail server..From other responses though, it looks like it may be better to just get VMWare accepting that it is running on a 64bit CPU.. Thanks for all the rsponses! signature.asc Description: PGP signature
Re: [gentoo-user] Gentoo x86 to AMD64
On Sonntag, 24. August 2008, Anthony Metcalf wrote: Alan McKinnon wrote: On Friday 22 August 2008 17:48:32 Anthony Metcalf wrote: What about re-building every single package, and re-installing it isn't a complete -reinstall? I can understand that this wouldn't work without the re-boot to live cd step, as you would end up with incompatible libraries/binaries, and with a 32bit kernel trying to run 64bit apps and crap.but this should avoid all that, with minimal downtime. Looks easy right? So, what tool chain on this 32 bit machine are you going to use to build the 64 bit binaries you actually want to output? You know you are going to do heaps of setup actions, build a new tool chain then essentially do emerge -e world. Much easier to just copy stuff off a 64-bit stage3 then do emerge -e world. Easier, probably, but I am bothered about downtime on this machine too, it doesn't do anything vital, but it is a mail server..From other responses though, it looks like it may be better to just get VMWare accepting that it is running on a 64bit CPU.. Thanks for all the rsponses! why downtime? just create a directory, install the 64bit gentoo in that directory. Tar everything up, boot from livecd, untar the tar into the old system. Done. Downtime depends on the speed of your harddisks. Something between 5 and 30minutes. Top. Btw, why mailserver?
Re: [gentoo-user] Gentoo x86 to AMD64
On Freitag, 22. August 2008, Anthony Metcalf wrote: Hi, I have a system that started out running on an AMD K6II 450MHz processorAbout 3 months ago, it was upgraded to a Phenom. The process was pretty painless, recompile kernel, install new hardware, reboot, rebuild network drivers etc alter C(XX)FLAGS and emerge -e world Now I have a system that flies, but I want to be able to use 64Bit VMware guests...so, I am quite sure I need to have a 64bit system for VMWare server to allow this... I have two theories about how to go about this.no1, install esx 3i on a spare drive, make a 32bit Linux guest and point it's drives at the raw partitions I have now :) no2, alter make.conf to 64bit flags, and emerge -e world --buildpkgonly then reboot into a 64bit live cd, and emerge -e world --usepkgonly which should give me a working systemObviously the kernel and network drivers would also need rebuilding at this point again Will no 2 work? no. Easiest way: complete reinstall.
Re: [gentoo-user] Gentoo x86 to AMD64
Hi Anthony, on Fri, Aug 22, 2008 at 04:01:42PM +0100, you wrote: I have two theories about how to go about this.no1, install esx 3i on a spare drive, make a 32bit Linux guest and point it's drives at the raw partitions I have now :) no2, alter make.conf to 64bit flags, and emerge -e world --buildpkgonly then reboot into a 64bit live cd, and emerge -e world --usepkgonly which should give me a working systemObviously the kernel and network drivers would also need rebuilding at this point again Will no 2 work? I'm not sure I understood #1 correctly but it sounds like neither will work. Going 32-64bit (or vice versa) always requires a fresh install. What I *think* you could do to reduce the hassle of updating all your configs is to start off with a partition with your 32bit system on it and use that for the regular Gentoo install procedure, i.e. slap the tarballs on top and then do all the emerging. But it would certainly leave some garbage around in /lib etc. so I wouldn't recommend it. If you didn't actually change the hardware so you don't have to reconfigure your kernel and stuff, a fresh install using your old world file shouldn't take more than a day. cheers, Matthias -- I prefer encrypted and signed messages. KeyID: FAC37665 Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665 pgpUICGvv1mya.pgp Description: PGP signature
Re: [gentoo-user] Gentoo x86 to AMD64
On Fri, 2008-08-22 at 17:27 +0200, Volker Armin Hemmann wrote: Easiest way: complete reinstall. Probably. You also get the feeling of knowing no old cruft is looming out there to eventually give you a migraine. Having said that I did a migration from x86 to amd64 a few years back and blogged about it here: http://starship.python.net/crew/marduk/blog/entry/1112117933.9,14473
Re: [gentoo-user] Gentoo x86 to AMD64
Volker Armin Hemmann wrote: no. Why? Easiest way: complete reinstall. What about re-building every single package, and re-installing it isn't a complete -reinstall? I can understand that this wouldn't work without the re-boot to live cd step, as you would end up with incompatible libraries/binaries, and with a 32bit kernel trying to run 64bit apps and crap.but this should avoid all that, with minimal downtime.
Re: [gentoo-user] Gentoo x86 to AMD64
2008/8/22 Anthony Metcalf [EMAIL PROTECTED] Hi, I have a system that started out running on an AMD K6II 450MHz processorAbout 3 months ago, it was upgraded to a Phenom. The process was pretty painless, recompile kernel, install new hardware, reboot, rebuild network drivers etc alter C(XX)FLAGS and emerge -e world Now I have a system that flies, but I want to be able to use 64Bit VMware guests...so, I am quite sure I need to have a 64bit system for VMWare server to allow this... Not exactly. For CPU w/ vm support, one can run 64 bit guest on 32 host. At least work for Core 2 CPU. I have two theories about how to go about this.no1, install esx 3i on a spare drive, make a 32bit Linux guest and point it's drives at the raw partitions I have now :) no2, alter make.conf to 64bit flags, and emerge -e world --buildpkgonly then reboot into a 64bit live cd, and emerge -e world --usepkgonly which should give me a working systemObviously the kernel and network drivers would also need rebuilding at this point again Will no 2 work? I don't really want to go the route of 1 as I will need a windows box for the esx admin, and if I was putting esx on this machine, I would want to have more storage first and manage the esx storage properly, rather than using raw drives... Comments? Ideas? Anthony -- Zhixu Liu
Re: [gentoo-user] Gentoo x86 to AMD64
Albert Hopkins wrote: On Fri, 2008-08-22 at 17:27 +0200, Volker Armin Hemmann wrote: Easiest way: complete reinstall. Probably. You also get the feeling of knowing no old cruft is looming out there to eventually give you a migraine. Having said that I did a migration from x86 to amd64 a few years back and blogged about it here: http://starship.python.net/crew/marduk/blog/entry/1112117933.9,14473 Thanks, I'll have a look
Re: [gentoo-user] Gentoo x86 to AMD64
Matthias Bethke wrote: I'm not sure I understood #1 correctly but it sounds like neither will work. Going 32-64bit (or vice versa) always requires a fresh install. What I *think* you could do to reduce the hassle of updating all your configs is to start off with a partition with your 32bit system on it and use that for the regular Gentoo install procedure, i.e. slap the tarballs on top and then do all the emerging. But it would certainly leave some garbage around in /lib etc. so I wouldn't recommend it. If you didn't actually change the hardware so you don't have to reconfigure your kernel and stuff, a fresh install using your old world file shouldn't take more than a day. cheers, Matthias #1 would definitely work, my current system would just become another guest in the esx server.Which isn't bad, but like I say, it's a bad use of resources and makes implementing other VMs more painful than it could be.
Re: [gentoo-user] Gentoo x86 to AMD64
On Freitag, 22. August 2008, Anthony Metcalf wrote: Volker Armin Hemmann wrote: no. Why? Easiest way: complete reinstall. What about re-building every single package, and re-installing it isn't a complete -reinstall? I can understand that this wouldn't work without the re-boot to live cd step, as you would end up with incompatible libraries/binaries, and with a 32bit kernel trying to run 64bit apps and crap.but this should avoid all that, with minimal downtime. because it isn't done with simple rebuilding. You have to change the chost, you need to cross compile. At the end it is just FASTER to reinstall.
Re: [gentoo-user] Gentoo x86 to AMD64
Quoting Anthony Metcalf [EMAIL PROTECTED]: Now I have a system that flies, but I want to be able to use 64Bit VMware guests...so, I am quite sure I need to have a 64bit system for VMWare server to allow this... VMware will accept _and_ run x86_64 guest in x86 hosts. Regards, Norberto This message was sent using IMP, the Internet Messaging Program.
Re: [gentoo-user] Gentoo x86 to AMD64
On Friday 22 August 2008 17:48:32 Anthony Metcalf wrote: What about re-building every single package, and re-installing it isn't a complete -reinstall? I can understand that this wouldn't work without the re-boot to live cd step, as you would end up with incompatible libraries/binaries, and with a 32bit kernel trying to run 64bit apps and crap.but this should avoid all that, with minimal downtime. Looks easy right? So, what tool chain on this 32 bit machine are you going to use to build the 64 bit binaries you actually want to output? You know you are going to do heaps of setup actions, build a new tool chain then essentially do emerge -e world. Much easier to just copy stuff off a 64-bit stage3 then do emerge -e world. -- alan dot mckinnon at gmail dot com
