From owner-freebsd-questions@freebsd.org Fri Jul 10 02:28:51 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFB743F8B for ; Fri, 10 Jul 2015 02:28:51 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF1EA123F for ; Fri, 10 Jul 2015 02:28:51 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 7C1793F734 for ; Thu, 9 Jul 2015 22:28:50 -0400 (EDT) Message-ID: <559F2DE1.3010708@sneakertech.com> Date: Thu, 09 Jul 2015 22:28:49 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: FreeBSD questions Subject: Re: Questions about freebsd-update References: <559C6B73.8050509@sneakertech.com> <559EA8B8.8080701@sneakertech.com> <559ED47E.8050905@hiwaay.net> <559F25F8.1030508@sneakertech.com> <20150710040626.6cdf28d2.freebsd@edvax.de> <559F2A4C.7070509@sneakertech.com> In-Reply-To: <559F2A4C.7070509@sneakertech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2015 02:28:52 -0000 >>> The main rationale here is that updates can occasionally cause behavior >>> changes which can negatively interact with 3rd party software. >> >> This is correct, but so can selectively applying updates... > > FWIW, I'm not really too concerned with the ability to apply patches > piecemeal. Applying them all in order is fine as long as it's one at a > time. Although my last email used the example 'freebsd-update install > patch_file', some flavor of 'freebsd-update install > specific_date_or_revision' would work too for this case. I guess part of it is that I'm slightly paranoid about patches against freebsd-update itself, and don't entirely trust it to apply those as early as possible.