All of lore.kernel.org
 help / color / mirror / Atom feed
From: roopa <roopa@cumulusnetworks.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Robert Urban <urban@unix-beratung.de>,
	bwh@kernel.org, netdev@vger.kernel.org
Subject: Re: parsing the output of ethtool programmatically
Date: Mon, 07 Sep 2015 19:52:54 -0700	[thread overview]
Message-ID: <55EE4D86.5080902@cumulusnetworks.com> (raw)
In-Reply-To: <1441446794.13323.8.camel@decadent.org.uk>

On 9/5/15, 2:53 AM, Ben Hutchings wrote:
> On Thu, 2015-06-25 at 03:28 +0200, Robert Urban wrote:
>> Hello,
>>
>> there doesn't seem to be any flag to request ethtool to present its output in a
>> script-friendly form.  Things like:
>>>          Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>>                                               100baseT/Half 100baseT/Full
>>>                                               1000baseT/Full
>> are kind of pain to parse.
>>
>> Something to consider?
> Or write a library for using SIOCETHTOOL.  The interface is fairly well
> documented now and there are other users besides the ethtool utility.

one of the requests which we usually get is ethtool output in json 
format. since iproute2 tools are already getting
an option to print in json format, would be nice if we considered an 
option to print in json for ethtool too.

  reply	other threads:[~2015-09-08  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  1:28 parsing the output of ethtool programmatically Robert Urban
2015-09-05  9:53 ` Ben Hutchings
2015-09-08  2:52   ` roopa [this message]
2017-10-26  0:21     ` Robert Urban

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=55EE4D86.5080902@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=ben@decadent.org.uk \
    --cc=bwh@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=urban@unix-beratung.de \
    /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.