From owner-freebsd-questions@freebsd.org Fri Jul 10 01:55:07 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 2422439B7 for ; Fri, 10 Jul 2015 01:55:07 +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 ED7E41F13 for ; Fri, 10 Jul 2015 01:55:06 +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 991873F6F8 for ; Thu, 9 Jul 2015 21:55:05 -0400 (EDT) Message-ID: <559F25F8.1030508@sneakertech.com> Date: Thu, 09 Jul 2015 21:55:04 -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> In-Reply-To: <559ED47E.8050905@hiwaay.net> 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 01:55:07 -0000 >>> 2) How do I get freebsd-update to install only specific patches or >>> updates instead of everything? > > Given the integration of base system packages & kernel, I don't think > you would want to do this. This actually sounds kinda .... dare I say it > (?) .... *linuxy* .... ick The main rationale here is that updates can occasionally cause behavior changes which can negatively interact with 3rd party software. If we're trying to test new patches for compatibility issues or we're seeing a bug that seems dependent on patch level, it's kind of a requirement to be able to step though the updates one by one.