From owner-freebsd-hackers@freebsd.org Sun Sep 27 13:30:50 2020 Return-Path: Delivered-To: freebsd-hackers@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 EA4F93FBE4A for ; Sun, 27 Sep 2020 13:30:50 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4BzmkL03XLz3WJL for ; Sun, 27 Sep 2020 13:30:49 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f52.google.com with SMTP id h17so6998459otr.1 for ; Sun, 27 Sep 2020 06:30:49 -0700 (PDT) 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=Ys7I3Cx6DhiILAspgi43IHMXW+3o6pW614PXNLkELow=; b=B1TlBQHK0RTSFwG61WKGzvUGMzFfNTZqeoy2up49oWKy3hw8HGfQZNaK8znwozvI5s 0p9myXtbjGEi6OR5Fw/PJey0peO4M8yZE2Xu259a6gbePRSnVwsZ9yJ4AtsXt+Q1WZYR LSu0gOVxEaxEnNoMbRlf+MW06ePy+Qroe0ZJ5PQjevhvGMdAPRsZQvdTxhr/CaeXvweg 6tsb9WYpbGEeipho1NMCErCQjFeJG10tVusJVewUWKYSWUlXYGSUzqXI9bOz6FevhcRv AGlyZRhRQaZP88Lsg4uQU+so4vD0QSQj48amjFTBKviJGqrF7BEAWEu359oCGyHCuoMe CHsg== X-Gm-Message-State: AOAM531iutKW9jLROEYHsnbt0CUndYWDCmbylocbD4ygFaw7cz/GkVXm zbJ+aEcM2K1H9JVrRTmChDEt4CcEX3fS2heuM2H3oXRg X-Google-Smtp-Source: ABdhPJzmSckVUiByI+mqcROYDeZrv7ei+VrhvQFQzlpeF0P8fXwILfBbdPF0xm7ORv0pgYRG2z/VvtFauGkQ/WraOq0= X-Received: by 2002:a05:6830:1e30:: with SMTP id t16mr6233441otr.18.1601213448671; Sun, 27 Sep 2020 06:30:48 -0700 (PDT) MIME-Version: 1.0 References: <20200927062126.GE54660@bastion.zyxst.net> In-Reply-To: <20200927062126.GE54660@bastion.zyxst.net> From: Alan Somers Date: Sun, 27 Sep 2020 07:30:37 -0600 Message-ID: Subject: Re: private freebsd-update server - possible with -current? To: tech-lists Cc: "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: 4BzmkL03XLz3WJL X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.52 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-0.92 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.52:from]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.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)[asomers@freebsd.org,asomers@gmail.com]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978]; NEURAL_HAM_LONG(-1.01)[-1.013]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_SPAM_SHORT(0.07)[0.075]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.52:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Sep 2020 13:30:51 -0000 On Sun, Sep 27, 2020 at 12:22 AM tech-lists wrote: > Hi, > > I'm not altogether sure which list this question should go to, so please > accept my apologies in advance if this is the wrong place to ask and > direct me > elsewhere. > > What I'd like to do is to run a freebsd-update server for some low-power > boards that are tier2 or tier3 arches *and* for various attached hardware > reasons need to run -current (nodebug). I'd like to have the > freebsd-update functionality missing from -current as it stands, so that a > full rebuild of the image isn't needed. > > I read with interest > https://www.freebsd.org/doc/en/articles/freebsd-update-server > the article is old but the start of it says it was last updated recently > (2020-06-28), so still valid? so I'd like to ask the experts here: > > 1. would this be expected to work with -current? Looking through the page > it > there's lots of use of patches that pertain to following releng. My use > case > doesn't require that. [1] > > 2. will the server build/run under other arches? I'm interested in arm64 > for > this. [1] > > 3. can it be made to cross-compile with native-xtools? [1] > > ultimately what i'd like to have is a freebsd-update server on rpi4/arm64 > building for arm[6,7] arm64 and mips64. On the low power board, run > freebsd-update as usual, apply updates, reboot. > > [1] right now I'm only asking if it's possible or if my idea is flawed, or > if > theres a better idea. > > thanks, > -- > J. > I don't see why it shouldn't. I'm currently a private freebsd-update server on 12-STABLE. The catch is that freebsd-update refuses to run on anything it thinks isn't an official release. So I have to make my own releases. To distinguish them from official ones, I name them something like "12.1-MYNAME1", and then I have to modify the freebsd-update script to thing that "MYNAME1" indicates an official release. -Alan