From owner-freebsd-arm@freebsd.org Wed Dec 4 15:12:34 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 58EF91C629A; Wed, 4 Dec 2019 15:12:34 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f175.google.com (mail-il1-f175.google.com [209.85.166.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Sj5F3Nj7z3x8d; Wed, 4 Dec 2019 15:12:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f175.google.com with SMTP id b15so6978563ila.7; Wed, 04 Dec 2019 07:12:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wuXLtsMCRWyZB+j+m7AILi8FRKCPJBsyuC3QO1wJesI=; b=fFIX5hne8dCAFY0FUeue6fSM0QUEZr+92sKAv0yX66XEZvs4kVr/a+b6PfHfRHMtcx tuWxqJ14Z3XT7hD96vi7G/dWuvq+AaW5bFG+IZy1LdP9vLT8PqWK+cgIYzceKTx3JVg7 /Ym9Xg3EZTtlXQfF2FHoN+6l3xfisDmPJvJXpu8BpNbgnWoNnCGzOx1111yYYVS4/aoE ofRDlbZnn/rTtVTh2c4YnCgBx6zFRrQTkCFInSjfSslxJx06RsZw3ftSJKUxPye83vyG nAq8bA1BQoZWOY+m4H8gMLBqdzihddJM6wcgpu7IKICNPyQKA+DruzXHumAmWIhVZr2/ ZwHg== X-Gm-Message-State: APjAAAX4UfCytWIa+KOfzhMzoCjzXQGrewWjYcywXWCAXBvY89NeRUAg TsVb4/cY/kvk8u0k6pPwm1pYFyGugvWPYfGv6yOqav/m X-Google-Smtp-Source: APXvYqwfrFJk/vuA4glhMIz9mD1fv6KCMnv7p/IFSnJhbLWKzPHixQ+a+64ySUKF5XpJCzOt9zkEDdMoGDbYBhOpx74= X-Received: by 2002:a92:4647:: with SMTP id t68mr3765839ila.18.1575472352050; Wed, 04 Dec 2019 07:12:32 -0800 (PST) MIME-Version: 1.0 References: <17938.1575444597@critter.freebsd.dk> In-Reply-To: <17938.1575444597@critter.freebsd.dk> From: Ed Maste Date: Wed, 4 Dec 2019 06:26:02 -0500 Message-ID: Subject: Re: arm64 as Tier 1 for FreeBSD 13 To: Poul-Henning Kamp Cc: freebsd-arch , freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Sj5F3Nj7z3x8d X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.175 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.05 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[175.166.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.05)[ip: (-5.13), ipnet: 209.85.128.0/17(-3.15), asn: 15169(-1.93), country: US(-0.05)]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[175.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2019 15:12:34 -0000 On Wed, 4 Dec 2019 at 02:30, Poul-Henning Kamp wrote: > > -------- > In message , Ed Maste writes: > > >> Binary updates and source patches for Security Advisories and Errata > >> Notices will be provided for supported releases. > > > >We don't do this today, but have the ability to do so for arm64 server > >platforms. (Due to its design, freebsd-update does not work > >particularly well on devices with slow root filesystems such as SD > >cards.) > > I don't think storage-technology should be used as a discriminant here. > > First because it is quite trivial to plug in a quality USB SSD (WD > passport for instance) and use that as root filesystem. > > Second, just because freebsd-update takes a day to run, doesn't mean > that people would not want it. That's fair, although maybe I could have been more clear. My point is that arm64 server-class hardware like Ampere eMAG and Marvell ThunderX/ThunderX2 generally looks just like an x86 server from a storage perspective, and freebsd-update would work just as well as it does on x86. Devices do exist with slow SD card root filesystems. Running freebsd-update on them might take a very long time and might be a poor user experience. None of that implies that FreeBSD/arm64 cannot be Tier-1.