From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([65.50.211.133]:37795 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751659AbdGESLO (ORCPT ); Wed, 5 Jul 2017 14:11:14 -0400 Date: Wed, 5 Jul 2017 11:11:13 -0700 From: Christoph Hellwig To: Jan Tulak Cc: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-xfs Subject: Re: [proposal] making filesystem tools more machine friendly Message-ID: <20170705181113.GA20326@infradead.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-btrfs-owner@vger.kernel.org List-ID: Hi Jan, I really like the idea out json output for fs/block tools. nvme-cli has been doing it for a while, and that has been very useful. It comes with it's own little handrolled json output helpers: https://github.com/linux-nvme/nvme-cli/blob/master/json.c so it doesn't introduce any new dependencies. If you want to parse input as well a library might be a better approach, though. I really don't like the shared object evms model mention in the thread, as that creates hard ELF dependencies.