From owner-freebsd-stable@FreeBSD.ORG Wed Aug 14 13:10:50 2013 Return-Path: Delivered-To: stable@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 2759EF8D; Wed, 14 Aug 2013 13:10:50 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A36B2A15; Wed, 14 Aug 2013 13:10:49 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.89,877,1367989200"; d="scan'208";a="38421709" Message-ID: <520B81D1.1010500@vangyzen.net> Date: Wed, 14 Aug 2013 08:10:41 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: stable@freebsd.org, Simon Gerraty , Hiroki Sato Subject: makefs Sparse Files: NetBSD CLI Compatibility Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Glen Barber X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Aug 2013 13:10:50 -0000 NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI compatibility with NetBSD. NetBSD committed first (by one month), and neither change has gone into a release yet, so we should change to match NetBSD. We should do it soon, too, since our change will go into 9.2-RELEASE. If we agree, I'll gladly make the patches, trivial though they'll be. Eric