From nobody Sat Jan 15 07:31:18 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E501E19441E2 for ; Sat, 15 Jan 2022 07:31:21 +0000 (UTC) (envelope-from SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JbVGJ4GhDz3mPJ for ; Sat, 15 Jan 2022 07:31:20 +0000 (UTC) (envelope-from SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl) Date: Sat, 15 Jan 2022 08:31:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1642231878; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=UpWxjSlJ9piFmOj9v9rXBuWCIzsURTREMZ71qXRz+Dc=; b=hs476emJ5BPoZIRm+EI5DNAkf6iYmY/ptYyIxeBdiLDhGuf9yZia/kh1vDTzWdzVlxlDSl yVpFhrhhm5Ou24jkpAAP6ykVBsKyqsqrWUyRi5+XTQ/pTxrzY8MlLVzi3PgJgTsce89ZzT emKb3mqpDMA90rDpyiF9dGqs9jiaw/+YYRLdWQwF6HkqdE8SvpOcXhGfiUAyQJzUUhm7q1 ATq1+yDNvIrioIVqOPoRfgyzA2aIOfXJA1MrBXplmGda/8T266vwDf8M2To+XvMWTd0n6Q W7hOtbRoSXAMxfVLvuzP4FYwcYUBL7yQGmdcyL8HgIIYdmpK2Wf3kg4yfZ1jug== From: Ronald Klop To: tech-lists , freebsd-arm@freebsd.org Message-ID: <1726339166.2813.1642231878969@localhost> In-Reply-To: <1454203050.2487.1642231086632@localhost> Subject: Re: freebsd-update and arm64.aarch64 (rpi4) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2812_1458802041.1642231878964" X-Mailer: Realworks (590.253.ec54157) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4JbVGJ4GhDz3mPJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=hs476emJ; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.07 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; NEURAL_HAM_LONG(-0.87)[-0.869]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; RCPT_COUNT_TWO(0.00)[2]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; MLMMJ_DEST(0.00)[freebsd-arm]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=NeFn=R7=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N Status: O Content-Length: 3585 Lines: 107 ------=_Part_2812_1458802041.1642231878964 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit This is the command I have in cron on my rpi3b+. @daily freebsd-update cron && freebsd-update updatesready > /dev/null && freebsd-update install This is silent if nothing happens and generates an email if updates are installed. Only a manual reboot needed, but I first read the announcements before doing that. Works pretty fine since 13.0. Regards, Ronald Van: Ronald Klop Datum: 15 januari 2022 08:18 Aan: tech-lists , freebsd-arm@freebsd.org Onderwerp: Re: freebsd-update and arm64.aarch64 (rpi4) > > > > Yes. I use it. > > > Van: tech-lists > Datum: 14 januari 2022 23:50 > Aan: freebsd-arm@freebsd.org > Onderwerp: freebsd-update and arm64.aarch64 (rpi4) > >> >> Hi, >> >> Now that aarch64 is tier1, is freebsd-update expected >> to work (following 13-RELENG)? I've not seen anything >> yet confirming this. >> >> thanks, >> -- >> J. >> >> >> >> >> > > > > > > ------=_Part_2812_1458802041.1642231878964 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
This is the command I have in cron on my rpi3= b+.

@daily freebsd-update cron && freebsd-upd= ate updatesready > /dev/null && freebsd-update install

This is silent if nothing happens and generates an email if upd= ates are installed. Only a manual reboot needed, but I first read the annou= ncements before doing that.

Works pretty fine si= nce 13.0.

Regards,
Ronald

Van: Ronald Klop <ronald-lists@klop.ws>= ;
Datum: 15 januari 2022 08:18
Aan: tech-lists <tech-lists@zyxst.net>, freebsd-arm@freebsd.org
= Onderwerp: Re: freebsd-update and arm64.aarch64 (rpi4)

Yes. I use it. 

Va= n: tech-lists <tech-lists@zyxst.net>
Datum: 14 januari 2022 23:50
Aan: freebsd-arm@freebsd.= org
Onderwerp: freebsd-update and arm64.aarch64 (rpi4= )

Hi,

Now that aarch64 is tier1, is freebsd-update expected
to work (following 13-RELENG)? I've not seen anything
yet confirming this.

thanks,
-- 
J.






------=_Part_2812_1458802041.1642231878964--