Re: Upgrading to amd64 requires recompilation of ports?
On Sat, Jun 16, 2007 at 06:21:40PM -0400, Indigo 23 wrote: Does anyone think that its worth the hassle? If you do manage to get it up and running, will you see any noticeable advantages or is it better to just stick with i386? The only caveat that I can see is a recompilation of all the ports. Any thoughts? You don't really _need_ it unless you've got more than four gigs of RAM and are routinely running out of memory on i386. Then again, I installed amd64 instead of i386 because I could. :-) No regrets so far. Some stuff like binary drivers, flash player, is not available on amd64 (not necessarily a bad thing :-). I think i386 has more ports available as packages. Amd 64 will use some more disk space and RAM. Doing a clean reinstall instead of an upgrade will probably less of a hassle. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpAC0HPmdICd.pgp Description: PGP signature
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, 16 Jun 2007, Kris Kennaway wrote: I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. Yeah, that's a neat trick to remember. Another trick for doing i386-amd64 is to install your new world into a DESTDIR, tar it up, put the tarball onto the root filesystem, boot the new amd64 kernel into single-user mode and use /rescue/tar to spam the amd64 tarball over the i386 world. I've used the miniroot-on-swap approach before. Another trick I used this week (when I had to do four i386-amd64 migrations) was to build a netbootable amd64 system, PXE-boot that, and then installworld to the local disks that way. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, Jun 16, 2007 at 12:21:42PM +0200, Ivan Voras wrote: Kris Kennaway wrote: On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. That's good news. Are there any particular problems in the process or does it just work? I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, Jun 16, 2007 at 04:19:21PM -0400, Kris Kennaway wrote: On Sat, Jun 16, 2007 at 12:21:42PM +0200, Ivan Voras wrote: Kris Kennaway wrote: On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. That's good news. Are there any particular problems in the process or does it just work? I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. pgp9C5czq6I7W.pgp Description: PGP signature
RE: Upgrading to amd64 requires recompilation of ports?
Does anyone think that its worth the hassle? If you do manage to get it up and running, will you see any noticeable advantages or is it better to just stick with i386? The only caveat that I can see is a recompilation of all the ports. Any thoughts? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, Jun 16, 2007 at 11:52:34PM +0300, Kostik Belousov wrote: On Sat, Jun 16, 2007 at 04:19:21PM -0400, Kris Kennaway wrote: On Sat, Jun 16, 2007 at 12:21:42PM +0200, Ivan Voras wrote: Kris Kennaway wrote: On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. That's good news. Are there any particular problems in the process or does it just work? I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. Yeah, that's a neat trick to remember. Another trick for doing i386-amd64 is to install your new world into a DESTDIR, tar it up, put the tarball onto the root filesystem, boot the new amd64 kernel into single-user mode and use /rescue/tar to spam the amd64 tarball over the i386 world. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On 17/06/07, Kris Kennaway [EMAIL PROTECTED] wrote: On Sat, Jun 16, 2007 at 11:52:34PM +0300, Kostik Belousov wrote: On Sat, Jun 16, 2007 at 04:19:21PM -0400, Kris Kennaway wrote: On Sat, Jun 16, 2007 at 12:21:42PM +0200, Ivan Voras wrote: Kris Kennaway wrote: On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. That's good news. Are there any particular problems in the process or does it just work? I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. Yeah, that's a neat trick to remember. Another trick for doing i386-amd64 is to install your new world into a DESTDIR, tar it up, put the tarball onto the root filesystem, boot the new amd64 kernel into single-user mode and use /rescue/tar to spam the amd64 tarball over the i386 world. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] That is quite interesting, but, let's say 'world' would be quite large (although I know it's not all that huge..), isn't there a limit to how much data tar can handle? I believe myself to have encountered such a limit, at least with GNU tar on a Linux system.. -- email: [EMAIL PROTECTED] website: moruku.org () ascii ribbon campaign - against html mail /\- against microsoft attachments ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sun, Jun 17, 2007 at 01:02:05AM +0200, Marcus Kaatari wrote: On 17/06/07, Kris Kennaway [EMAIL PROTECTED] wrote: On Sat, Jun 16, 2007 at 11:52:34PM +0300, Kostik Belousov wrote: On Sat, Jun 16, 2007 at 04:19:21PM -0400, Kris Kennaway wrote: On Sat, Jun 16, 2007 at 12:21:42PM +0200, Ivan Voras wrote: Kris Kennaway wrote: On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. That's good news. Are there any particular problems in the process or does it just work? I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. Yeah, that's a neat trick to remember. Another trick for doing i386-amd64 is to install your new world into a DESTDIR, tar it up, put the tarball onto the root filesystem, boot the new amd64 kernel into single-user mode and use /rescue/tar to spam the amd64 tarball over the i386 world. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] That is quite interesting, but, let's say 'world' would be quite large (although I know it's not all that huge..), isn't there a limit to how much data tar can handle? I believe myself to have encountered such a limit, at least with GNU tar on a Linux system.. Maybe there is a limit on the order of terabytes or higher, but in practise it's not something to worry about. Linux has had issues with 2GB file size limits in various utilities even in recent years, but AFAIK FreeBSD has not had issues for more than a decade. World is only 100-200MB depending on architecture anyway. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
