From owner-freebsd-stable@FreeBSD.ORG Sat Jun 16 23:30:57 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12CC016A400 for ; Sat, 16 Jun 2007 23:30:57 +0000 (UTC) (envelope-from moruku@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id 86C4013C45E for ; Sat, 16 Jun 2007 23:30:56 +0000 (UTC) (envelope-from moruku@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1335473mue for ; Sat, 16 Jun 2007 16:30:55 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=fdIofO9FesEuDRwxf58hOACowwJK5Yhmx9teGFpa2ijAT7ObgrqW4y+Om9CyFcnLNj8lVjYL+c5+YiWY8zRJ0lCxw5WbL7cw1YX9kbTFM3rEqx0z+O7iTorvPNtkbLeBQ9aSGw+qwaVj6Ky/KxoNl0B4HwTnJbWbTPy+RWDoans= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=mGDSJZRLSMugQXx2lUSarcbGSx9I0CsujFFUMEeI/F6w2h7Kay+Kxoe8xHipU/V3FF9Q2I2/xlZRlBtXX4T7h/eOXPXkWr2AfMtIKww4bS9Rk3to2P7597aEfASpUSfUJaXt6qK8ITI6polxnUeEDq1YaE+6P/ODSNch8VfDIFM= Received: by 10.82.189.6 with SMTP id m6mr8503247buf.1182034925872; Sat, 16 Jun 2007 16:02:05 -0700 (PDT) Received: by 10.82.164.4 with HTTP; Sat, 16 Jun 2007 16:02:05 -0700 (PDT) Message-ID: <94e0cac00706161602r2c5a6e56if7c714b0341cec4@mail.gmail.com> Date: Sun, 17 Jun 2007 01:02:05 +0200 From: "Marcus Kaatari" Sender: moruku@gmail.com To: "Kris Kennaway" In-Reply-To: <20070616222413.GA29804@rot13.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6f50eac40706151829g64b8a8abg798f97449c05888f@mail.gmail.com> <20070616030328.GA17075@rot13.obsecurity.org> <20070616201921.GA29173@rot13.obsecurity.org> <20070616205234.GN2268@deviant.kiev.zoral.com.ua> <20070616222413.GA29804@rot13.obsecurity.org> X-Google-Sender-Auth: 7153087e92c29b4b Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Upgrading to amd64 requires recompilation of ports? 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: Sat, 16 Jun 2007 23:30:57 -0000 On 17/06/07, Kris Kennaway 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 > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > 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: moruku@moruku.org website: moruku.org () ascii ribbon campaign - against html mail /\ - against microsoft attachments