From: Karel Zak <kzak@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Andreas Bombe" <aeb@debian.org>,
util-linux@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Andrius Štikonas" <andrius@stikonas.eu>,
"Curtis Gedak" <gedakc@gmail.com>, "Pavel Machek" <pavel@ucw.cz>
Subject: Re: Linux & FAT32 label
Date: Thu, 9 Nov 2017 12:02:54 +0100 [thread overview]
Message-ID: <20171109110254.to37iuydtbpqypjy@ws.net.home> (raw)
In-Reply-To: <20171109085909.b6b5m35qeul3orrx@pali>
On Thu, Nov 09, 2017 at 09:59:09AM +0100, Pali Rohár wrote:
> What about exporting e.g. BOOT_LABEL field from libblkid for vfat disks?
> LABEL (which is shown to user, e.g. in GUI) would be that one from root
> directory (same which is used by label on MS-DOS and Windows) and
> BOOT_LABEL would be from boot sector. If somebody really needs to know
> current label stored in boot sector he would be able to do it via blkid.
> Also it would be possible then via blkid to read exact label stored in
> root directory and also read what is stored in boot sector. Because
> currently it is not possible to know from which location LABEL comes
> from.
This is good idea, there is no problem to export additional
information about filesystems. We already use it for another
filesystems too. Note, these details are visible for low-level
probing (blkid -p) and udev only. The high-level API follows
LABEL only.
Maybe it would be better to use LABEL_BOOT= or LABEL_FATBOOT= as name.
The important thing is the default behavior of the LABEL, this is what
use mount(8) and another tools.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-11-09 11:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 15:33 Linux & FAT32 label Pali Rohár
2017-10-11 21:24 ` Pali Rohár
2017-10-11 21:29 ` Pali Rohár
2017-10-11 21:44 ` Pali Rohár
2017-10-12 8:56 ` Karel Zak
2017-10-12 9:21 ` Pali Rohár
2017-10-12 10:13 ` Karel Zak
2017-10-12 20:49 ` Pali Rohár
2017-10-16 1:12 ` Andreas Bombe
2017-10-16 7:28 ` Pali Rohár
2017-10-30 15:29 ` Pali Rohár
2017-10-31 8:35 ` Andy Shevchenko
2017-11-05 13:39 ` Pali Rohár
2017-11-05 13:56 ` Andy Shevchenko
2017-11-05 14:07 ` Pali Rohár
2017-11-05 14:25 ` Andy Shevchenko
2017-11-05 14:34 ` Pali Rohár
2017-11-05 14:51 ` Andy Shevchenko
2017-11-05 14:56 ` Pali Rohár
2017-11-06 10:14 ` Karel Zak
2017-11-09 8:59 ` Pali Rohár
2017-11-09 11:02 ` Karel Zak [this message]
2017-11-05 20:35 ` Theodore Ts'o
2017-11-05 21:12 ` Pali Rohár
2017-11-07 17:28 ` Theodore Ts'o
2017-11-09 9:01 ` Pali Rohár
2017-11-09 16:21 ` Theodore Ts'o
2017-11-09 17:33 ` Pali Rohár
2017-11-05 14:12 ` Andrius Štikonas
2017-10-15 6:59 ` Pavel Machek
2017-10-15 22:04 ` Pali Rohár
2017-10-16 1:12 ` Andreas Bombe
2017-11-05 13:06 ` Pali Rohár
2017-11-09 21:21 ` Pali Rohár
2017-11-19 12:44 ` Pali Rohár
2017-11-20 11:12 ` Karel Zak
2017-11-22 8:52 ` Pali Rohár
2017-11-22 11:03 ` Karel Zak
2017-11-22 14:29 ` Andrius Štikonas
2017-11-23 9:01 ` Pali Rohár
2017-11-26 19:19 ` Pali Rohár
2017-11-27 12:13 ` Karel Zak
2018-02-14 21:52 ` Pali Rohár
2018-02-14 21:54 ` Pali Rohár
2018-02-15 10:21 ` Karel Zak
2018-03-07 8:28 ` Pali Rohár
2017-11-29 23:21 ` Pali Rohár
2018-01-29 16:49 ` Pali Rohár
2017-12-16 22:45 ` 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=20171109110254.to37iuydtbpqypjy@ws.net.home \
--to=kzak@redhat.com \
--cc=aeb@debian.org \
--cc=andrius@stikonas.eu \
--cc=andy.shevchenko@gmail.com \
--cc=gedakc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--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).