From owner-freebsd-stable@FreeBSD.ORG Wed Jul 16 23:00:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC1F71065681 for ; Wed, 16 Jul 2008 23:00:38 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.182]) by mx1.freebsd.org (Postfix) with ESMTP id A09E38FC16 for ; Wed, 16 Jul 2008 23:00:38 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAEABQafkhMCqa7/2dsb2JhbACLXaUVAw X-IronPort-AV: E=Sophos;i="4.31,199,1215403200"; d="scan'208";a="24442628" Received: from not.enough.unixsluts.com (HELO kevin) ([76.10.166.187]) by ironport2-out.teksavvy.com with ESMTP; 16 Jul 2008 19:00:37 -0400 From: "Kevin K" To: "'H. Wade Minter'" , "'FreeBSD Stable'" References: <806C9CF5-A9DD-4C7D-94A9-07724B731D74@lunenburg.org> In-Reply-To: <806C9CF5-A9DD-4C7D-94A9-07724B731D74@lunenburg.org> Date: Wed, 16 Jul 2008 19:00:20 -0400 Message-ID: <009701c8e797$b8d05c80$2a711580$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acjnll6zuWv8chRfT26bgcUh+PtzLQAASFKw Content-Language: en-us Cc: Subject: RE: Switching from 32 to 64 bit with freebsd-update? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 23:00:38 -0000 > I have a 64-bit system that had the 32-bit version of 6.3 installed on > it. Is it possible to use freebsd-update (or another somewhat > painless method) to switch the system to 64-bit? > > We're running into the 4GB memory limit. > > --Wade I believe this is possible but you will come into a lot of trouble with statically linked libraries -- a much more reliable and secure would be to build a clean amd64 on a separate system and re-compile the needed software and move the files from i386 over after it has been tested.