Updating FreeBSD 12.0 on a raspberry pi 3 B+

[Karl Denninger]

On 6/7/2019 20:24, Nenhum_de_Nos wrote:
>
> On June 1, 2019 5:33:00 PM GMT-03:00, Jack Raats <mlist at nlned.nl> wrote:
>> Hi
>>
>>
>>
>> I want to update FreeBSD on a raspberry pi 3 B+
>>
>>
>>
>> On a VPS with lots of cores and RAM I build FreeBSD using crochet.
>> Every night I make an image, which can be downloaded at
>> www.jarasoft.net/rpi
>>
>> The raspberry pi is running FreeBSD 12.0-STABLE build a fee weeks ago
>> and now I want to update this working FreeBSD.
>>
>>
>>
>> I could make a new image and install everything from the start but that
>> will take a lot of time or can this be automated?
>>
>>
>>
>> On the other end I could use the builded binaries from my VPS, copy
>> them to the Pi and run make install kernel and make install world?
>>
>> Is this being done???
>>
>>
>>
>> Or is there another way?
> Jack, 
>
> Have you ever tried the official image for rpi3 b on them? 
>
> Cause I tried the default image on mine and it boots once every 5 or 6 attempts. 
>
> Do you have any idea what I could do? 
>
> Thanks, 
>
> Matheus 

IF you are using Crochet then there should be a separate /cfg filesystem
that is copied over to ramdisk during startup.  All volatile changes go
in there.

PROVIDED the new and old image sizes are identical *and* you can
dismount the card (that is, you can't do this while running unless you
have *two* running partitions, and the Pi has issues booting from the
second one in many cases -- there are workarounds but it's not as simple
as it is in the "old world" of setting the "active" flag) you can copy
over the new "a" partition and leave the /cfg partition alone.

IF the packages in both are compatible (or there are none) this *should*
work.  I have an embedded application that works this way -- it requires
paying attention as the system partitions must be of identical size and
you have to make sure the loads are compatible across the config
directory (that is, what's in /cfg and will wind up in /etc is "ok" with
both loads) but provided you can do that this is an option.

-- 
Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4897 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20190611/d57d539c/attachment.bin>