All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arvin Schnell <aschnell@suse.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: [proposal] making filesystem tools more machine friendly
Date: Fri, 30 Jun 2017 12:22:49 +0200	[thread overview]
Message-ID: <20170630102249.GA1112@suse.com> (raw)
In-Reply-To: <CACj3i70p=ybXZWRncseqwnbs7HAYu-SL02+cj--7T5YnqcwVKQ@mail.gmail.com>


Hi Jan,

I appreciate your proposal and I'm all for it!

Working on the storage part of YaST I face similar problems with
parsing the output of many different programs. Having a common
JSON output will certainly help to make the code simpler and more
robust.

Currently some parsers are very difficult, esp. when the output
attributes contain the chars used as a separator. Some tools even
have machine friendly output but it is still error
prone. E.g. parted does not protect a ':' in the partition name
of its machine friendly output. (Just an example, your proposal
is not about parted.)

ciao
  Arvin

-- 
Arvin Schnell, <aschnell@suse.com>
Senior Software Engineer, Research & Development
SUSE Linux GmbH, GF: Felix Imendï¿œrffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nï¿œrnberg)
Maxfeldstraï¿œe 5
90409 Nï¿œrnberg
Germany

  reply	other threads:[~2017-06-30 10:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  8:17 [proposal] making filesystem tools more machine friendly Jan Tulak
2017-06-30 10:22 ` Arvin Schnell [this message]
2017-06-30 13:58 ` Emmanuel Florac
2017-06-30 15:29 ` Theodore Ts'o
2017-07-03 11:52   ` Jan Tulak
2017-07-03 15:07     ` Theodore Ts'o
2017-07-03 17:37       ` Darrick J. Wong
2017-07-04 13:57         ` Jan Tulak
2017-07-04 19:07           ` Theodore Ts'o
2017-07-12  8:42             ` Jan Tulak
2017-07-05 18:11 ` Christoph Hellwig
2017-07-12 13:00   ` Jan Tulak
2017-07-12 17:10 ` Richard W.M. Jones
2017-11-27 14:57 ` Andrew Price
2017-11-27 15:38   ` Jan Tulak
2017-11-27 16:24     ` Andrew Price
2017-11-27 16:42       ` Jan Tulak

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=20170630102249.GA1112@suse.com \
    --to=aschnell@suse.com \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.