util-linux.vger.kernel.org archive mirror
 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 19:48:54 +0200	[thread overview]
Message-ID: <201707101948.55088@pali> (raw)
In-Reply-To: <20170710115236.c45ivf43w5cjvfxm@ws.net.home>

[-- Attachment #1: Type: Text/Plain, Size: 1646 bytes --]

On Monday 10 July 2017 13:52:36 Karel Zak wrote:
> On Mon, Jul 10, 2017 at 01:15:09PM +0200, Pali Rohár wrote:
> > 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?
> 
> It seems blkid_probe_set_version() is nowhere used for UD now, so we
> have absolute freedom to use it in some way.
> 
> > 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.
> 
> Yes, sounds good.
> 
>     Karel

https://github.com/karelzak/util-linux/pull/483

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2017-07-10 17:48 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
2017-07-10 11:52     ` Karel Zak
2017-07-10 17:48       ` Pali Rohár [this message]

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=201707101948.55088@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).