From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 17 01:25:53 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E61A10656C7; Sat, 17 Jan 2009 01:25:53 +0000 (UTC) (envelope-from andrew.hotlab@hotmail.com) Received: from col0-omc1-s13.col0.hotmail.com (col0-omc1-s13.col0.hotmail.com [65.55.34.23]) by mx1.freebsd.org (Postfix) with ESMTP id 446FB8FC12; Sat, 17 Jan 2009 01:25:53 +0000 (UTC) (envelope-from andrew.hotlab@hotmail.com) Received: from COL112-W17 ([65.55.34.9]) by col0-omc1-s13.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 17:25:53 -0800 Message-ID: X-Originating-IP: [217.133.1.92] From: Andrew Hotlab To: Date: Sat, 17 Jan 2009 01:25:53 +0000 Importance: Normal In-Reply-To: References: Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 17 Jan 2009 01:25:53.0465 (UTC) FILETIME=[89F79A90:01C97842] X-Mailman-Approved-At: Sat, 17 Jan 2009 01:52:45 +0000 Cc: freebsd-i386@freebsd.org, freebsd-amd64@freebsd.org, freebsd-arch@freebsd.org Subject: RE: Cross compiling FreeBSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2009 01:25:57 -0000 > Date: Fri=2C 16 Jan 2009 11:56:55 +0100 > From: ck-lists@cksoft.de > > On Fri=2C 16 Jan 2009=2C Andrew Hotlab wrote: > >> Sorry for my stupid question: I'll do the right thing if I'll build an i= 386 jail chroot/jail on the >> amd64 builder host with the following commands? (grabbed from the FreeBS= D Handbook) >> # cd /usr/src >> # make buildworld TARGET=3Di386 >> # make installworld TARGET=3Di386 DESTDIR=3D/path-to-jail >> # cd etc/ >> # make distribution DESTDIR=3D/path-to-jail >> # mount -t devfs devfs /path-to-jail/dev > > yes that should do it but I think you can skip the cd etc/ part. > make distribution should work from /usr/src > >>> The hack to enable building in an i386 chroot is to set UNAME_m >>> and UNAME_p to i386. I use following in the chroots .cshrc >>> [...] >>> This of course only works for the amd64=2C i386 combination. >> Wonderful=2C I'll try this as soon as possible. Thank you! > > let us know if it works out. I've build and exported RELENG_7_0 into an i386 jail running on amd64 hardw= are=2C then I mounted sources and binaries on a RELENG_6_4/i386 machine and I have been a= ble to successfully upgrade without any trouble!! (only some warnings were display= ed installing the kernel=2C but that's a correct behaviour of the upgrade procedure=2C as= pointed out in this post: http://lists.freebsd.org/pipermail/freebsd-current/2005-November/0579= 63.html) Thank you so much=2C Christian! I'm thinking that it would be a great thing to prepare some materials expla= ining the methods for maintaining a managed FreeBSD infrastructure in a corporate production = environment. A lot of sysadmins are afraid that they'll have to spend so much time in soft= ware management tasks if they put FreeBSD in production for business applications=2C but it= seems that only a little of knowledge is required to manage such and environment obtaining a good TC= O. At present time I'm too much engaged with a lot of projects to be able to p= roduce any docs=2C but I'll surely advocate FreeBSD in such business scenarios! _________________________________________________________________ More than messages=96check out the rest of the Windows Live=99. http://www.microsoft.com/windows/windowslive/=