From owner-freebsd-questions@freebsd.org Thu Mar 15 20:26:54 2018 Return-Path: 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 C950DF5083F for ; Thu, 15 Mar 2018 20:26:54 +0000 (UTC) (envelope-from 482254ac@razorfever.net) Received: from pmta11.teksavvy.com (pmta11.teksavvy.com [76.10.157.34]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "*.teksavvy.com", Issuer "DigiCert SHA2 High Assurance Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F258768CA for ; Thu, 15 Mar 2018 20:26:54 +0000 (UTC) (envelope-from 482254ac@razorfever.net) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EqMgB41qpa/0StpUVeGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYIZgTcrPG2DeIsMjQUBQgEBAQEBBQGBAQskNwFjlg0KE4RzAYM?= =?us-ascii?q?+IjgUAQIBAQEBAQECA2goQg4BhH8VHlgCJgI7JA0IAQGFBw2vVIImhG6DcYIKE?= =?us-ascii?q?3mEIoMggkQMh1yDHoJhA5Ejhn0IAQKPIIFEAQ+GOxCFEoc+iGAMgSo1IoFSH1y?= =?us-ascii?q?DCJEIJIdDiR0BAQE?= X-IPAS-Result: =?us-ascii?q?A2EqMgB41qpa/0StpUVeGQEBAQEBAQEBAQEBAQcBAQEBAYI?= =?us-ascii?q?ZgTcrPG2DeIsMjQUBQgEBAQEBBQGBAQskNwFjlg0KE4RzAYM+IjgUAQIBAQEBA?= =?us-ascii?q?QECA2goQg4BhH8VHlgCJgI7JA0IAQGFBw2vVIImhG6DcYIKE3mEIoMggkQMh1y?= =?us-ascii?q?DHoJhA5Ejhn0IAQKPIIFEAQ+GOxCFEoc+iGAMgSo1IoFSH1yDCJEIJIdDiR0BA?= =?us-ascii?q?QE?= X-IronPort-AV: E=Sophos;i="5.48,312,1517893200"; d="scan'208";a="23495634" Received: from 69-165-173-68.dsl.teksavvy.com (HELO mail.razorfever.net) ([69.165.173.68]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Mar 2018 16:26:52 -0400 Received: from [127.0.0.1] (mail.razorfever.net [192.168.0.4]) by mail.razorfever.net (8.15.2/8.14.9) with ESMTP id w2FKQpgk034507 for ; Thu, 15 Mar 2018 16:26:52 -0400 (EDT) (envelope-from 482254ac@razorfever.net) X-Authentication-Warning: mail.razorfever.net: Host mail.razorfever.net [192.168.0.4] claimed to be [127.0.0.1] To: FreeBSD Mailing List From: "Derek (freebsd lists)" <482254ac@razorfever.net> Subject: freebsd-update: holding back patches, or to a specific version Message-ID: <50c78b4c-2832-acb2-4810-13f45794870c@razorfever.net> Date: Thu, 15 Mar 2018 16:26:51 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, FROM_STARTS_WITH_NUMS,RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.razorfever.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2018 20:26:55 -0000 Hiya! Was wondering if anyone knows a way to *not* update to the latest patch level, but a specific patch level with freebsd-update? I can see some docs available around rolling our own freebsd-update server, and that might be the route we go, but it would seem like I should be able to select a point-in-time, as long as it is ahead of where I am now? Any thoughts welcome, thanks! Derek