From owner-freebsd-current@freebsd.org Wed Mar 21 21:26:16 2018 Return-Path: Delivered-To: freebsd-current@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 D6B10F68B4E for ; Wed, 21 Mar 2018 21:26:15 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 27207694CF for ; Wed, 21 Mar 2018 21:26:14 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Wed, 21 Mar 2018 22:24:07 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B91B0524-6295-420C-AF34-06863F30B763.1 envelope-from (authenticated bits=0); Wed, 21 Mar 2018 22:23:56 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: freebsd-update: to a specific patch level - help please? From: Rainer Duffner In-Reply-To: Date: Wed, 21 Mar 2018 22:24:22 +0100 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Derek (freebsd lists)" <482254ac@razorfever.net> X-Mailer: Apple Mail (2.3445.5.20) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=12 total_conn=6 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 5154, bad: 2, connections: 5651, history: 5152, asn_score: 108, asn_connections: 115, asn_good: 108, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 21:26:16 -0000 > Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists) = <482254ac@razorfever.net>: >=20 > Hi! >=20 > I was surprised when using freebsd-update, that there was no way to = specify a patch level. AFAIK, the usual answer to these kinds of requests is: =E2=80=9ERun your = own freebsd-update server=E2=80=9C. Mirroring one of the existing ones is AFAIK neither guaranteed to work = nor desired by the current =E2=80=9Eadministration=E2=80=9C. I=E2=80=99ve contemplated doing both, but never had enough heart-ache to = do it and never thought the pay-off would be greater than the potential = problems. It=E2=80=99s also a somewhat transient problem now because - AFAIK - = FreeBSD will see packaged base and you can probably mirror those = packages and snapshot the directory at any point in time. And/Or it=E2=80=99s just easier to create these base-packages yourselves = vs. running your own freebsd-update server.