Util-Linux package development
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: util-linux@vger.kernel.org
Subject: Re: unclear udev format output of blkid
Date: Fri, 02 Mar 2012 13:16:15 +0100	[thread overview]
Message-ID: <jiqdmf$cbi$1@dough.gmane.org> (raw)
In-Reply-To: <249be96a-803a-4d00-b5b1-ff3f18722a36@zmail01.collab.prod.int.phx2.redhat.com>

Am 02.03.2012 12:18, schrieb Balamurugan Arumugam:
> We are trying to parse blkid output in python for all devices and their attributes.

This sounds like a bad idea. Instead, you should write a python
extension using the Python C API that uses libblkid directly (unless you
plan to support other implementations than CPython).

> I found two strange things.
> 1. udev format output is grouped by empty newline, but I see an extra newline in between.

'udev' output format is deprecated and will be removed in a future
version of util-linux. Starting to support it now is a clear waste of time.

> 2. In udev format output for all devices, there is no devname displayed.  Without devname, its unclear grouping.  Is there a plan to add devname in udev format output?

For above reasons, unlikely.


  reply	other threads:[~2012-03-02 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f2c4b72-cda0-4618-ae7c-b89333c1d2b9@zmail01.collab.prod.int.phx2.redhat.com>
2012-03-02 11:18 ` unclear udev format output of blkid Balamurugan Arumugam
2012-03-02 12:16   ` Thomas Bächler [this message]
2012-03-02 13:24   ` Karel Zak
2012-03-03  3:28     ` Balamurugan Arumugam

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='jiqdmf$cbi$1@dough.gmane.org' \
    --to=thomas@archlinux.org \
    --cc=util-linux@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