From owner-freebsd-fs@FreeBSD.ORG Thu May 13 11:44:42 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E7771065672; Thu, 13 May 2010 11:44:42 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 60E6A8FC21; Thu, 13 May 2010 11:44:42 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id EAB2D46B92; Thu, 13 May 2010 07:44:41 -0400 (EDT) Received: from John-Baldwins-Macbook-Pro.local (localhost [IPv6:::1]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 204478A01F; Thu, 13 May 2010 07:44:41 -0400 (EDT) Message-ID: <4BEBE634.4080102@FreeBSD.org> Date: Thu, 13 May 2010 07:44:52 -0400 From: John Baldwin User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Boris Kochergin References: <4BEB40EB.2030206@acm.poly.edu> In-Reply-To: <4BEB40EB.2030206@acm.poly.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 13 May 2010 07:44:41 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-fs@freebsd.org Subject: Re: ZFS and __FreeBSD_version X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2010 11:44:42 -0000 Boris Kochergin wrote: > Hi. Can __FreeBSD_version be bumped if ZFS's userland API is ever > changed again? I got slightly bitten by the > state_to_name()-to-zpool_state_to_name() change from version 6 to > version 13 and would like a reliable way of keeping track of this type > of stuff in the future. Thanks. Yes, it should be bumped anytime the API changes. That is definitely a bug that it wasn't done properly last time. -- John Baldwin