From: Hugo Mills <hugo@carfax.org.uk>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: test if a subvolume is a snapshot?
Date: Fri, 8 Sep 2017 16:24:23 +0000 [thread overview]
Message-ID: <20170908162423.GE23980@carfax.org.uk> (raw)
In-Reply-To: <CABB28Cx4zo1Pr7TbmxYgJAOmms3PrYftxcks8iHCQSx5a2Xq1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]
On Fri, Sep 08, 2017 at 05:12:11PM +0100, Tomasz Kłoczko wrote:
> On 8 September 2017 at 16:38, Hugo Mills <hugo@carfax.org.uk> wrote:
> [..]
> >> sometimes I'm really thinking about start rewrite btrfs-progs to make
> >> btrfs basic tools syntax as similar as it is only possible to ZFS zfs,
> >> zpool and zdb commands on using which in +90% cases you can guess how
> >> necessary syntax must look like without looking on man pages.
> >>
> >> Any volunteers want to join to help implement something like this?
> >> Maybe someone already started doing this?
> >
> > The main complaint that can be directed at the btrfs command is
> > that its output is rarely machine-processable. It would therefore make
> > sense to have a "--table" or "--structured" mode for output, which
> > would be more trivially parsable by shell tools.
>
> Output of the btrfs command it is coooooompletely different pair of shoes.
> On making btrfs tools similar to ZFS analogues *obviously* output
> should be as same similar.
> By this would possible to solve complains about unreadable output in one go.
>
> For example zfs command parseable output is possible to generate by
> add -p switch in those subcommands where it is needed (no --tables or
> --structures .. just one switch).
--tables _is_ one switch.
> Instead reinventing the wheel just please try to look first how it is
What in what I said was reinventing a wheel? Literally the *only*
thing I was suggesting was adding some option to make the btrfs tool
output more machine-parsable.
Call the option whatever you like. However, note that there are
probably very few single-letter options which are not used in at least
one of the btrfs tool subcommands.
Hugo.
--
Hugo Mills | How do you become King? You stand in the marketplace
hugo@... carfax.org.uk | and announce you're going to tax everyone. If you
http://carfax.org.uk/ | get out alive, you're King.
PGP: E2AB1DE4 | Harry Harrison
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-09-08 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 8:54 test if a subvolume is a snapshot? Ulli Horlacher
2017-09-08 11:37 ` Peter Grandi
2017-09-08 13:10 ` David Sterba
2017-09-08 15:25 ` Tomasz Kłoczko
2017-09-08 15:38 ` Hugo Mills
2017-09-08 16:12 ` Tomasz Kłoczko
2017-09-08 16:24 ` Hugo Mills [this message]
2017-09-08 16:39 ` David Sterba
2017-09-08 18:09 ` Tomasz Kłoczko
2017-09-08 18:44 ` David Sterba
2017-09-08 19:06 ` Austin S. Hemmelgarn
2017-09-08 20:54 ` Tomasz Kłoczko
2017-09-11 12:44 ` Austin S. Hemmelgarn
2017-09-08 16:27 ` David Sterba
2017-09-08 18:41 ` Ulli Horlacher
2017-09-08 18:53 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170908162423.GE23980@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=kloczko.tomasz@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox