From owner-freebsd-current@FreeBSD.ORG Sat Jun 8 20:18:58 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D84C178E; Sat, 8 Jun 2013 20:18:58 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) by mx1.freebsd.org (Postfix) with ESMTP id B0D641245; Sat, 8 Jun 2013 20:18:58 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MO300D009J7KM00@smtpauth2.wiscmail.wisc.edu>; Sat, 08 Jun 2013 14:18:50 -0500 (CDT) X-Spam-PmxInfo: Server=avs-2, Version=6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.6.8.190919, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-69-84.dsl.mdsnwi.sbcglobal.net [76.208.69.84]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MO3006VP9NC8B00@smtpauth2.wiscmail.wisc.edu>; Sat, 08 Jun 2013 14:18:49 -0500 (CDT) Message-id: <51B38398.8030509@freebsd.org> Date: Sat, 08 Jun 2013 14:18:48 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130420 Thunderbird/17.0.5 To: Glen Barber Subject: Re: 10-CURRENT i386 memstick snapshots broken? References: <20130607205129.GA1103@jmobile.jimmy.net> <20130607212256.GG38117@glenbarber.us> <20130608173411.GD13292@glenbarber.us> <926EF579-8AC9-4A98-8A81-4E978A627199@kientzle.com> <20130608191722.GE13292@glenbarber.us> In-reply-to: <20130608191722.GE13292@glenbarber.us> Cc: freebsd-current@FreeBSD.org, Jimmy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jun 2013 20:18:58 -0000 On 06/08/13 14:17, Glen Barber wrote: > On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote: >> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote: >> >>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote: >>>>> Has anyone else tried the i386 memstick and having the same problem? >>>>> >>>> Hmm. Thanks for the report. I'll take a look at the logs for i386, but >>>> they are generated the same way as the amd64, so in theory should not >>>> have any noticable difference. >>>> >>> For amd64 and i386, native binaries are built, and installed into >>> scratch directories; for powerpc and powerpc64, I just use the amd64 >>> binaries, because I cannot directly use the chroot binaries for >>> non-native architecture. >>> >>> The scripts chroot into the scratch directories, and run the "real" >>> release builds. >> Have you tried using Crochet for this sort of thing? >> >> Since it was designed from the ground up for cross-building >> bootable images, it should avoid these issues. >> > I have not, primarily because I was not aware of crochet when > I originally started this. Although, by using the release stuff from > the base system, we do get a weekly run-test of the 'make release' bits > in head/ and stable/9/, so in theory, there would be no surprises when > it is -RELEASE time. > >> The only fundamental limit right now is that Crochet uses >> the host system to build the UFS filesystems, so it can't >> build big-endian MIPS images on i386, for example. >> >> > Yes, I have this same issue with sparc64. > Why not use makefs? It can build cross-endian UFS images. -Nathan