From owner-freebsd-questions@FreeBSD.ORG Mon Feb 23 21:32:29 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1A85106564A for ; Mon, 23 Feb 2009 21:32:29 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email1.allantgroup.com (email1.emsphone.com [199.67.51.115]) by mx1.freebsd.org (Postfix) with ESMTP id 67B6F8FC23 for ; Mon, 23 Feb 2009 21:32:29 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email1.allantgroup.com (8.14.0/8.14.0) with ESMTP id n1NLWR1L034172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Feb 2009 15:32:27 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id n1NLWRo5096068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Feb 2009 15:32:27 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id n1NLWPfN096067; Mon, 23 Feb 2009 15:32:26 -0600 (CST) (envelope-from dan) Date: Mon, 23 Feb 2009 15:32:25 -0600 From: Dan Nelson To: Andrew Moran Message-ID: <20090223213225.GC45976@dan.emsphone.com> References: <20090223200512.GA47390@slackbox.xs4all.nl> <54B6CFF8-1C2C-40C6-AB90-AABA3ADFA0E7@forsythia.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54B6CFF8-1C2C-40C6-AB90-AABA3ADFA0E7@forsythia.net> X-OS: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) X-Virus-Scanned: ClamAV version 0.94.1, clamav-milter version 0.94.1 on email1.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (email1.allantgroup.com [199.67.51.78]); Mon, 23 Feb 2009 15:32:28 -0600 (CST) X-Scanned-By: MIMEDefang 2.45 Cc: freebsd-questions@freebsd.org Subject: Re: Upgrade from FreeBSD 7.1/i386 to FreeBSD 7.1/AMD64? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 21:32:29 -0000 In the last episode (Feb 23), Andrew Moran said: > I have 8 gigs of memory in this system, and I decided go to the ZFS route, > and am now getting kernel panics about kmem exhaustion. I know there are > some tweaks I can do to help alleviate these, but I want to address all my > memory before I increase the kernel memory. > > I don't need the ports to be 64-bit, but they SHOULD run just fine > without recompiling, yes? As long as you never recompile anything again, yes :) But as soon as you upgrade (say) libX11 to 64-bit, all dependant libraries and program will need to be brought up to 64-bit as well. You might as well do them all. I just did this 32->64 upgrade a few weeks ago, and since I had a ZFS root, I was able to do this: Snapshot+clone a new copy of my root filesystem (called root.amd64) Do a cross-build+installworld into that partition Install a 64-bit kernel into my /boot partition (installed as /boot/kernel.amd64 temporarily) Edit /boot/loader.conf and add vfs.root.mountfrom="zfs:local_pool/root.amd64" kernel="kernel.amd64" Edit /etc/fstab on root.amd64 to mount / from local_pool/root.amd64 Cross fingers, and reboot into amd64-land Portupgrade -fa (this step wan't flawless since I was also upgrading through the perl58 and gnome-2.24 updates, but still took less than 24 hours) All the while having my i386 kernel and root available to reboot back into if I screwed something up horribly :) If you use any programs that keep machine-dependant file formats (rrdtool data files, for example), export them to a portable format before the switch, and reimport them afterwards. When I was satisfied I had a stable system, I moved my 64-bit kernel into /boot/kernel, removed the kernel= line from boot.conf, promoted the cloned root.amd64 filesystem and destroyed the i386 root and the snapshot. -- Dan Nelson dnelson@allantgroup.com