From owner-freebsd-questions@freebsd.org  Wed Jun 12 14:12:05 2019
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31C9015B7EFB
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Wed, 12 Jun 2019 14:12:05 +0000 (UTC)
 (envelope-from joneum@FreeBSD.org)
Received: from toco-domains.de (mail.toco-domains.de
 [IPv6:2a01:4f8:151:4202::3])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 90B237741A
 for <freebsd-questions@freebsd.org>; Wed, 12 Jun 2019 14:12:04 +0000 (UTC)
 (envelope-from joneum@FreeBSD.org)
Received: by toco-domains.de (Postfix, from userid 65534)
 id 9BE1414FD3; Wed, 12 Jun 2019 16:12:02 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on toco-mail
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00
 autolearn=unavailable autolearn_force=no version=3.4.2
Received: from track.home.jochen-neumeister.de (p5B0FD431.dip0.t-ipconnect.de
 [91.15.212.49])
 by toco-domains.de (Postfix) with ESMTPA id 3DE7414FC0;
 Wed, 12 Jun 2019 16:11:59 +0200 (CEST)
Subject: Re: freebsd-update query
To: freebsd-questions@freebsd.org, tech-lists@zyxst.net
References: <20190612140736.GA76883@rpi3.zyxst.net>
From: Jochen Neumeister <joneum@FreeBSD.org>
Message-ID: <219135fc-d00e-c54d-d557-1294a982b0b1@FreeBSD.org>
Date: Wed, 12 Jun 2019 16:11:59 +0200
MIME-Version: 1.0
In-Reply-To: <20190612140736.GA76883@rpi3.zyxst.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: de-DE
X-Rspamd-Queue-Id: 90B237741A
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.99 / 15.00];
 local_wl_from(0.00)[FreeBSD.org];
 NEURAL_HAM_MEDIUM(-1.00)[-0.999,0];
 NEURAL_HAM_SHORT(-0.99)[-0.988,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0];
 ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2019 14:12:05 -0000

freebsd-update only work on i386 and amd64.

There are a lot of topics about this: 
https://www.google.com/search?q=freebsd+update+raspberry+pi+site:forums.freebsd.org

On 12.06.19 16:07, tech-lists wrote:
> Hello,
>
> context: FreeBSD 12.0-RELEASE r341666 GENERIC  arm
>
> Does freebsd-update only work with amd64?
>
> I tried using it on generic 12-R raspberry pi2b:
>
> # freebsd-update fetch
> src component not installed, skipped
> Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> Fetching public key from update1.freebsd.org... failed.
> Fetching public key from update4.freebsd.org... failed.
> Fetching public key from update2.freebsd.org... failed.
> No mirrors remaining, giving up.
>
> There's no mention of it being unavailable for certain architectures
> (where I'd expect to find this information:
> https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html 
>
> )
>
> what am I missing?
>
> thanks,