From owner-svn-src-head@FreeBSD.ORG Wed Nov 6 19:18:20 2013 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B704F756; Wed, 6 Nov 2013 19:18:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8E4402646; Wed, 6 Nov 2013 19:18:20 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 794E1B94A; Wed, 6 Nov 2013 14:18:19 -0500 (EST) From: John Baldwin To: Gleb Smirnoff Subject: Re: svn commit: r257696 - in head: libexec/rbootd share/man/man9 sys/compat/svr4 sys/net sys/sys Date: Wed, 6 Nov 2013 10:24:08 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <20131106062029.GP7577@FreeBSD.org> In-Reply-To: <20131106062029.GP7577@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201311061024.09200.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 06 Nov 2013 14:18:19 -0500 (EST) Cc: svn-src-head@freebsd.org, Adrian Chadd , src-committers@freebsd.org, svn-src-all@freebsd.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 19:18:20 -0000 On Wednesday, November 06, 2013 1:20:29 am Gleb Smirnoff wrote: > John, Adrian, > > On Tue, Nov 05, 2013 at 05:18:26PM -0500, John Baldwin wrote: > J> Mmmm, people run older versions of binaries (even open source ones) on newer OS's > J> perhaps more often than you think. The COMPAT_43 stuff can be dropped certainly, > J> but people will almost certainly do rolling upgrades where they upgrade the OS > J> on their machines before they upgrade their packages. > > On Tue, Nov 05, 2013 at 02:25:13PM -0800, Adrian Chadd wrote: > A> My main worry about this kind of work is that you're just steamrolling > A> through stuff that yes, should be done, but with little warning and no > A> API deprecation schedule. > A> > A> I'd much rather see this stuff handled more formally - we mark the API > A> as deprecated and remove it in the next release. > A> > A> I really don't like seeing steamrolling through the kernel and > A> deprecating APIs with minimal warning and having no (optional) > A> backwards compatibility implementations. That's what made us stand out > A> from Linux - we kept old APIs around as much as we could. Linux wasn't > A> terribly good at this. > > One reply to both of you. The schedule is the following: we are compatible > with previous major version. The interface had changed in early > 10.0-CURRENT, and during the entire 10.0-CURRENT life it has supported the > new and the old interface and this went into stable/10. When doing the change, > I have pronounced this deprecation schedule. > > If anyone upgrades to next major: 9.x -> 10.x, or 10.x -> 11.x, including > package sets, then everything will be working for him. As I said, you ignore users who run older binaries on a large cluster of machines while doing staged OS upgrades. By your logic, we shouldn't have any COMPAT_FREEBSD options at all except for . The presence of such options would seem to indicate that your assumption is incorrect. -- John Baldwin