Re: Migrating from x86 (32) to amd64
Danny Braniss wrote: > try > make buildkernel TARGET_ARCH=amd64 KERNCONF=YOUR_KERNEL_HERE Yes, that's better :) signature.asc Description: OpenPGP digital signature
Re: Migrating from x86 (32) to amd64
On Sat, 10 Mar 2007 13:57:09 +0200 Danny Braniss <[EMAIL PROTECTED]> wrote: > > Yoshihiro Ota wrote: > > > About one year ago, I was able to do the regular procedure after enabling > > > i386 compat. > > > It was just another make world for me. > > > > > > options COMPAT_IA32 > > > > > > What I mean is: > > > > > > # 1. `cd /usr/src' (or to the directory containing your source > > > tree). > > > # 2. `make buildworld' > > > # 3. `make buildkernel KERNCONF=3DYOUR_KERNEL_HERE' (default is > > > GENERIC). > > > > But if you already have an i386 kernel running, wouldn't running "make > > buildkernel" just make another i386 kernel? > > try > make buildkernel TARGET_ARCH=amd64 KERNCONF=YOUR_KERNEL_HERE > > works for me, > danny > I believe I have done with TARGET_ARCH=amd64 or something on the line. As I've done it about a year ago, I don't recall some of these details. After a couple of months, I decided to switch back to i386. It was just to experiment amd64. I share the same executables among multiple systems (although there are only 2 or 3) to sync software versions. (It is not often but having diffrent versions of the same software causes some problems.) Since I have i386 machines, I cannot share amd64 binraries. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
> Yoshihiro Ota wrote: > > About one year ago, I was able to do the regular procedure after enabling > > i386 compat. > > It was just another make world for me. > > > > options COMPAT_IA32 > > > > What I mean is: > > > > # 1. `cd /usr/src' (or to the directory containing your source > > tree). > > # 2. `make buildworld' > > # 3. `make buildkernel KERNCONF=3DYOUR_KERNEL_HERE' (default is > > GENERIC). > > But if you already have an i386 kernel running, wouldn't running "make > buildkernel" just make another i386 kernel? try make buildkernel TARGET_ARCH=amd64 KERNCONF=YOUR_KERNEL_HERE works for me, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
Yoshihiro Ota wrote: > About one year ago, I was able to do the regular procedure after enabling > i386 compat. It was just another make world for me. > > options COMPAT_IA32 > > What I mean is: > > # 1. `cd /usr/src' (or to the directory containing your source tree). > # 2. `make buildworld' > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). But if you already have an i386 kernel running, wouldn't running "make buildkernel" just make another i386 kernel? signature.asc Description: OpenPGP digital signature
Re: Migrating from x86 (32) to amd64
About one year ago, I was able to do the regular procedure after enabling i386 compat. It was just another make world for me. options COMPAT_IA32 This is interesting. I have setup and amd64 box with this option enabled. And i am sure i have to leave foreve, since some client have their binaries w/o sources and they need to run anyway. The quesiton, does this option have any perfomance impact? -- Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
About one year ago, I was able to do the regular procedure after enabling i386 compat. It was just another make world for me. options COMPAT_IA32 What I mean is: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. & 4. can be combined by using the "kernel" target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster' # 10. `reboot' There are some risks doing this way, though. Regards, Hiro On Sat, 10 Mar 2007 00:24:51 -0600 "Matthew D. Fuller" <[EMAIL PROTECTED]> wrote: > On Fri, Mar 09, 2007 at 08:54:42PM +0300 I heard the voice of > Artem Kuchin, and lo! it spake thus: > > > > Theoretically, what would be the procedure? > > - Do a full cross-build of the amd64 world/kernel. > - newfs your swap partition (or an extra partition/drive). > - installworld/kernel the amd64 stuff onto that. > - Boot into that temporary amd64 world. > - installworld/kernel the amd64 stuff onto your main partition. > - Boot back normal-like, re-enable swap. > > You should be able to do that in an hour hands-on easily. > > > -- > Matthew Fuller (MF4839) | [EMAIL PROTECTED] > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ >On the Internet, nobody can hear you scream. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
On Fri, Mar 09, 2007 at 08:54:42PM +0300 I heard the voice of Artem Kuchin, and lo! it spake thus: > > Theoretically, what would be the procedure? - Do a full cross-build of the amd64 world/kernel. - newfs your swap partition (or an extra partition/drive). - installworld/kernel the amd64 stuff onto that. - Boot into that temporary amd64 world. - installworld/kernel the amd64 stuff onto your main partition. - Boot back normal-like, re-enable swap. You should be able to do that in an hour hands-on easily. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
On 2007-Mar-09 22:16:36 +0300, Artem Kuchin <[EMAIL PROTECTED]> wrote: >Is there way to more or less sefely migrade to AMD64 arhitecture via >csup and >source build? >>... >>>Damn it. Then i guess i need to do some experimenting myself. >> >>Definitely. >> >>>Theoretically, what would be the procedure? >> >>1) Backup system. >>2) Download amd64 install ISO and burn to CD >>3) Boot from CD >>4) Follow instructions for fresh install >>5) Restore/merge configuration from backups. >> >>If you have a spare amd64 system and most of the content is static, >>you could reduce downtime by doing steps 4 thru 5 on the second system >>and either swapping the disk(s) or the entire system. > >no, that's no what i ment. I mean the procedure to source build/install >amd64 on x86 and make it work. Just theoretically, I presume you've read the bottom bit of /usr/src/UPGRADING You should be able to cross-build an amd64 world with: # make TARGET_ARCH=amd64 buildworld # make TARGET_ARCH=amd64 KERNCONF=YourKernel buildkernel (I'm confident this will work but watch out for CPU or architecture-specific flags in your /etc/make.conf) # mkdir /lib32 /usr/lib32 # cp -p /lib/* /lib32 # cp -p /usr/lib/* /usr/lib32 # cp -p /var/run/ld-elf.so.hints /var/run/ld-elf32.so.hints # cp -p /libexec/ld-elf.so.1 /libexec/ld-elf32.so.1 These steps setup the i386 emulation infrastructure (some of these steps may be overkill) # make TARGET_ARCH=amd64 KERNCONF=YourKernel DESTDIR=/ installkernel I think this will work. Reboot to single user mode (shouldn't have any problems) Mount /usr /var and anything else needed for the install # mergemaster -p # make TARGET_ARCH=amd64 DESTDIR=/ installworld These steps are probably the riskiest because you are relying on tricking the amd64 kernel into believing your i386 world is an i386 emulation. If anything goes wrong here, you will probably need to restore from backups because you can't run on the old kernel once you've started installing amd64 binaries. I haven't tried running an amd64 kernel with an i386 userland but after symlinking /lib32 -> lib and /usr/lib32 -> lib and copying the ld-elf.so files in my i386 filesystems, I can chroot into it whilst running my amd64 kernel and execute commands. # make delete-old # mergemaster These steps should be OK Note that I wouldn't attempt to try going from 5.4/i386 to 6.2/amd64 in one step. You want to minimise the things that can go wrong... -- Peter Jeremy pgp02GwLpUBHf.pgp Description: PGP signature
Re: Migrating from x86 (32) to amd64
Is there way to more or less sefely migrade to AMD64 arhitecture via csup and source build? ... Damn it. Then i guess i need to do some experimenting myself. Definitely. Theoretically, what would be the procedure? 1) Backup system. 2) Download amd64 install ISO and burn to CD 3) Boot from CD 4) Follow instructions for fresh install 5) Restore/merge configuration from backups. If you have a spare amd64 system and most of the content is static, you could reduce downtime by doing steps 4 thru 5 on the second system and either swapping the disk(s) or the entire system. no, that's no what i ment. I mean the procedure to source build/install amd64 on x86 and make it work. Just theoretically, -- Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
On 2007-Mar-09 20:54:42 +0300, Artem Kuchin <[EMAIL PROTECTED]> wrote: >>>Is there way to more or less sefely migrade to AMD64 arhitecture via >>>csup and >>>source build? ... >Damn it. Then i guess i need to do some experimenting myself. Definitely. >Theoretically, what would be the procedure? 1) Backup system. 2) Download amd64 install ISO and burn to CD 3) Boot from CD 4) Follow instructions for fresh install 5) Restore/merge configuration from backups. If you have a spare amd64 system and most of the content is static, you could reduce downtime by doing steps 4 thru 5 on the second system and either swapping the disk(s) or the entire system. -- Peter Jeremy pgpcE3zNJGkFJ.pgp Description: PGP signature
Re: Migrating from x86 (32) to amd64
Is there way to more or less sefely migrade to AMD64 arhitecture via csup and source build? AFAIK nobody has lived to tell the tale (or at least I didn't see any followups from people who claimed they'd try it). In any case it would be better to migrate it via binary reinstall (the same as installing from scratch, using the boot CD...). Damn it. Then i guess i need to do some experimenting myself. Theoretically, what would be the procedure? Any recomendations? Try using PAE, but read up on possible problems. No, just not PAE. Tried it on 6.2, felt all the pain, cried outloud and went back to simple plain 32 bit. As it has been told - PAE IS AN UGLY HACK. -- Regards Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Migrating from x86 (32) to amd64
Artem Kuchin wrote: > Is there way to more or less sefely migrade to AMD64 arhitecture via > csup and > source build? AFAIK nobody has lived to tell the tale (or at least I didn't see any followups from people who claimed they'd try it). In any case it would be better to migrate it via binary reinstall (the same as installing from scratch, using the boot CD...). > Any recomendations? Try using PAE, but read up on possible problems. signature.asc Description: OpenPGP digital signature
