From owner-svn-src-head@FreeBSD.ORG Wed Nov 6 20:03:26 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 9AC34E7E; Wed, 6 Nov 2013 20:03:26 +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 6F4CB29F9; Wed, 6 Nov 2013 20:03:26 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8F5BAB918; Wed, 6 Nov 2013 15:03:25 -0500 (EST) From: John Baldwin To: Peter Wemm Subject: Re: svn commit: r257696 - in head: libexec/rbootd share/man/man9 sys/compat/svr4 sys/net sys/sys Date: Wed, 6 Nov 2013 14:22:17 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <201311051029.rA5ATmmM017799@svn.freebsd.org> <527A80F4.1090405@wemm.org> In-Reply-To: <527A80F4.1090405@wemm.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201311061422.17627.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 06 Nov 2013 15:03:25 -0500 (EST) Cc: "svn-src-head@freebsd.org" , Adrian Chadd , Gleb Smirnoff , "src-committers@freebsd.org" , svn-src-all 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 20:03:26 -0000 On Wednesday, November 06, 2013 12:48:36 pm Peter Wemm wrote: > On 11/6/13, 9:00 AM, Adrian Chadd wrote: > > I think the important thing here is that there _are_ organisations > > that rely on some reasonable attempt at supporting historical APIs > > where needed. > > > > This IMHO should've explicitly gone into a compat macro for people who > > want support of this older stuff. > > > > My suggestion for a saner way to handle this deprecation schedule: > > > > * do the announce - I'd have to go looking for that, but we should be > > placing these somewhere obvious (like a wiki page that lists > > deprecated APIs in order, with the date/release they're going to be > > deprecated); > > * deprecate the userland use of the ioctl values first so they use the > > newer API; > > * deprecate the kernel API after the announced amount of time, hiding > > things behind COMPAT_xxx as appropriate. > > That's how it was before - behind COMPAT_43 etc and he removed it. > COMPAT_43 now does less than it did before. I think removing COMPAT_43 is a separate issue from removing what should be under COMPAT_FREEBSD9. I doubt much of anything is using COMPAT_43 ioctls, but there are likely things using the older version of the still-current ioctl that would need to be under COMPAT_FREEBSD[4-9]. -- John Baldwin