All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: libblkid: ID_FS_VERSION
Date: Mon, 10 Jul 2017 13:15:09 +0200	[thread overview]
Message-ID: <20170710111509.GB560@pali> (raw)
In-Reply-To: <20170710110828.r6dr6buolw4xtgpm@ws.net.home>

On Monday 10 July 2017 13:08:28 Karel Zak wrote:
> On Wed, Jul 05, 2017 at 01:49:26PM +0200, Pali Rohár wrote:
> > Hi! What is the meaning of the ID_FS_VERSION attribute? I'm trying to 
> > find documentation about libblkid attributes, but seems there is none.
> 
> libblkid/src/superblocks/superblocks.c
> 
>    * @VERSION: filesystem version
> 
> :-)

That does not provide more information :-)

> Well, the field is to provide more details about the filesystem, for
> example we have VERSION="FAT16" TYPE="vfat", and so on. Note that TYPE
> is usually name used by kernel (to be usable for "mount -t <type>").
> 
> I guess the VERSION is used by some userspace stuff (udisks?) to get
> more information (or provide more details to end-users). It's probably
> nothing critical.

I'm thinking if we can provide UDF revision/version of UDF filesystem to
userspace and looks like ID_FS_VERSION is good candidate for it...

What do you think?

E.g. Linux kernel is able to read UDF filesystem up to revision 2.50 and
has read-write support up to revision 2.01. So for userspace this
information can be useful.

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2017-07-10 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 11:49 libblkid: ID_FS_VERSION Pali Rohár
2017-07-10 11:08 ` Karel Zak
2017-07-10 11:15   ` Pali Rohár [this message]
2017-07-10 11:52     ` Karel Zak
2017-07-10 17:48       ` Pali Rohár

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=20170710111509.GB560@pali \
    --to=pali.rohar@gmail.com \
    --cc=kzak@redhat.com \
    --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 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.