From owner-freebsd-arm@FreeBSD.ORG Fri Aug 8 14:57:07 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 756CE7B6 for ; Fri, 8 Aug 2014 14:57:07 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A2D82D7B for ; Fri, 8 Aug 2014 14:57:06 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id f8so2664937wiw.3 for ; Fri, 08 Aug 2014 07:57:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=DQlS1MrHAEMgApoKMyDHcAhwZl8OBG/NoOnEYAfeoYQ=; b=pdNyAJwtv/kkNwKSnYxXXvX4Ka0TUCUDgvZkSTgz/gKNJF8ljLZjirH1UD8JSc+DQh BVL2RlshS/jf2WCOV46RCBFq4dnXjbSFu7ipFFfrxhPZsd0MFsV0joWmgG3lrjrT0B4u 46qaJfqB0/+x/5QAhwlj/21eNOc/FDhgSiE4CsKUwQPo4yNSFA49iRFP7Ri0byffj7Us QiWwpDkVXOm2cj3ZClhjt6Om2+tAo5MAR8k0EvPcAHzSOX+K0icy/PYrPVdpkgY9xA21 QEQ4EN9xuRuZiHVPnkF3tKiNwxf1JSyNmENghRVHKAiJzQ1QjEa0tAHzl2lkFX0d11Az +Aog== X-Received: by 10.180.99.65 with SMTP id eo1mr4981487wib.12.1407509825247; Fri, 08 Aug 2014 07:57:05 -0700 (PDT) Received: from ?IPv6:2001:1620:ff0:c51:434:a679:7428:2e35? ([2001:1620:ff0:c51:434:a679:7428:2e35]) by mx.google.com with ESMTPSA id eb4sm7881926wic.16.2014.08.08.07.57.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Aug 2014 07:57:04 -0700 (PDT) Message-ID: <53E4E53F.30905@gmail.com> Date: Fri, 08 Aug 2014 16:57:03 +0200 From: Mattia Rossi User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 CC: freebsd-arm Subject: Re: What platform do you use? References: <7EC2AB25-5949-40BF-A5AA-BF4C98F3F640@bsdimp.com> <20140805182438.GP88623@funkthat.com> <53E3E2C7.9000802@hot.ee> <24403276-D738-4CB1-A3BE-BBB72D4370C6@bsdimp.com> <724D10EE-F6DF-4366-91CF-AE4419847389@gromit.dlib.vt.edu> In-Reply-To: <724D10EE-F6DF-4366-91CF-AE4419847389@gromit.dlib.vt.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 14:57:07 -0000 Am 08.08.2014 15:35, schrieb Paul Mather: > On Aug 7, 2014, at 5:34 PM, Warner Losh wrote: > >> On Aug 7, 2014, at 2:34 PM, Sulev-Madis Silber (ketas) wrote: >> >>> On 2014-08-05 21:24, John-Mark Gurney wrote: >>>> I also have a BBW that I occasionally test w/ but since I haven't got >>>> it netbooting, the cost of building an entire image and writing it to >>>> SLOW microsd prevents me from testing as much... >>> I wonder why people like to update their embedded systems by taking card >>> out, completely overwriting it with new data and putting card back in. >>> No wonder that it's slow, complex & heedlessly wears out your flash. >>> >>> If I do this in my BBB I would get myself pissed very soon because of >>> the effort required. I never bothered to netboot too, because I wanted >>> to test it in insecure network conditions. >>> I mean, I don't remember a case where I needed to take HDD to another >>> machine for upgrade. The issue where it's not practical to compile >>> something locally is completely unrelated with this, too. >> make installworld works too, as does extracting the binary sets. The new installer >> should work, but I’ve not tried it. > It would be handy for those of us wanting to cross-build FreeBSD/arm > for someone who is familiar with the build process to give a quick > example of how to update a FreeBSD/arm installation that is cross-built > on another system. In the past, I've had the impression that the build > infrastructure on the target system sometimes needs to be in alignment > with the new kernel/world you're trying to install, and so NFS-mounting > /usr/src and /usr/obj or copying it to the target system fails to yield > a successful "make installworld" on the target system. Maybe this is > no longer the case, as I believe great strides have been made in the > realm of cross-building. > > Up to now, I have largely used Crochet to build images for my R-PI and > BBB. That's okay for initial install, but I'm much more familiar with > updating from source and would like to do that from then on. In the > past, FreeBSD/arm has been too flaky for me to do a native build (I've > posted here about that in the past), but, besides that, it would be > nice to cut down the long native build times by cross-building on a > much faster system. > > I have an R-PI and BBB and would like to cross-build (for update > purposes) on my FreeBSD/amd64 10-STABLE system. Could you post a known > way to do this? I can NFS-mount from the FreeBSD/amd64 or else have it > put /usr/src and /usr/obj on an USB external hard drive that I can then > connect to my R-PI or BBB for updating. Either is okay with me. > > Thanks in advance. > > The way I do it is cross-compiling everything needed on an ssh enabled remote machine, and installing it into a folder on that machine with DESTDIR= On my arm machine then as root I do "cd /" and "chflags -R noschg *" and "ssh user@host tar -cpf - /destdirfolder/* | tar -xpf - " And voilà, world is installed. I then copy the kernel from the obj dir to my boot partition via scp and reboot. Usually this works. Cheers, Mat