From owner-freebsd-current@freebsd.org  Sat Apr 23 03:17:23 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 0D962B19D06
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat, 23 Apr 2016 03:17:23 +0000 (UTC)
 (envelope-from lyndon@orthanc.ca)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "orthanc.ca", Issuer "Let's Encrypt Authority X1" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id ECF07134B
 for <freebsd-current@freebsd.org>; Sat, 23 Apr 2016 03:17:22 +0000 (UTC)
 (envelope-from lyndon@orthanc.ca)
Received: from minnie ([72.143.234.25]) (authenticated bits=0)
 by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id u3N3HK56022752
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-current@freebsd.org>; Fri, 22 Apr 2016 20:17:22 -0700 (PDT)
 (envelope-from lyndon@orthanc.ca)
Date: Fri, 22 Apr 2016 20:17:15 -0700 (PDT)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
X-X-Sender: lyndon@minnie.bitsea.ca
To: freebsd-current@freebsd.org
Subject: why 100 packages are evil
In-Reply-To: <7c84f388-21dc-419f-70ce-c5369e294dab@freebsd.org>
Message-ID: <alpine.OSX.2.00.1604222009300.15755@minnie.bitsea.ca>
References: <E1asbZj-0003Ra-Qs@rmm6prod02.runbox.com>
 <76093.1461096570@critter.freebsd.dk> <5716AD65.8070007@shrew.net>
 <BF66EA01-E073-45F0-8F9E-22D57E8871B0@bsdimp.com>
 <5716FA70.4080604@freebsd.org> <57170E5D.1090701@freebsd.org>
 <5524F499-5042-407E-9180-43D15A53F3F0@FreeBSD.org>
 <7621BDAB-A409-456A-A3F1-A6CD9B371DBC@rdsor.ro>
 <20160420094806.GJ6614@zxy.spb.ru>
 <7c84f388-21dc-419f-70ce-c5369e294dab@freebsd.org>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
Organization: The Frobozz Magic Homing Pigeon Company
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Apr 2016 03:17:23 -0000

Here's a real example.

I have n Centos servers. Cron, once or twice a day, updates our local 
cache of the yum repos. Then nagios comes along and flags 35 packages out 
of date.

An hour later, management comes along asking questions about the security 
implications of those packages.  An hour later we finish trolling through 
and say 'no worries'.

Repeat.  Every day.

With freebsd-update, an announcement comes out that says 'update'!.  So we 
do.  Move from 10.2-p11 to 10.2-p12.  There is a very clear track record 
of why and how this happened.

What will be the new update frequency with >100 base packages?  How will 
that impact people running productions systems.  I know rebooting the 
mysql servers is an amount of pain that everyone below the VP level 
doesn't want to have anything to do with it; explaining to the VP that is.