Date: Sat, 16 Jun 2007 21:20:13 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Marcus Kaatari <moruku@moruku.org> Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Upgrading to amd64 requires recompilation of ports? Message-ID: <20070617012013.GA32410@rot13.obsecurity.org> In-Reply-To: <94e0cac00706161602r2c5a6e56if7c714b0341cec4@mail.gmail.com> References: <6f50eac40706151829g64b8a8abg798f97449c05888f@mail.gmail.com> <f4veun$kq4$2@sea.gmane.org> <20070616030328.GA17075@rot13.obsecurity.org> <f50dkg$m71$1@sea.gmane.org> <20070616201921.GA29173@rot13.obsecurity.org> <20070616205234.GN2268@deviant.kiev.zoral.com.ua> <20070616222413.GA29804@rot13.obsecurity.org> <94e0cac00706161602r2c5a6e56if7c714b0341cec4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2007 at 01:02:05AM +0200, Marcus Kaatari wrote: > On 17/06/07, Kris Kennaway <kris@obsecurity.org> 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.. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070617012013.GA32410>