From: "Theodore Ts'o" <tytso@mit.edu>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Andreas Bombe" <aeb@debian.org>, "Karel Zak" <kzak@redhat.com>,
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@ucw.cz
Subject: Re: Linux & FAT32 label
Date: Sun, 5 Nov 2017 15:35:42 -0500 [thread overview]
Message-ID: <20171105203542.jgupce2usbtjhbg2@thunk.org> (raw)
In-Reply-To: <20171105140745.ze4ttkazeczrqsy7@pali>
On Sun, Nov 05, 2017 at 03:07:45PM +0100, Pali Rohár wrote:
>
> Current behavior of the last blkid and fatlabel tools is: Try to read
> label from the root directory. If it does not exist, then fallback to
> label stored in boot sector. And when fatlabel is changing label it
> updates both locations.
>
> So tools which already uses fatlabel for get & set operations should not
> be affected as setting new label makes boot and root in sync.
>
> New proposed behavior is: Try to read label from the root directory. If
> not exist, then treat disk as without label.
Why is it important to ignore the label from the boot sector? What is
the situation where if there is not a label in the root directory, and
there is a label in the boot sector, it is the Wrong Thing to return it?
For that matter, aside for a diskette from DOS 3.x (where using the
label from the boot sector *is* the right thing), why/when would we
ever have a label in the boot sector and not in the root director?
- Ted
next prev parent reply other threads:[~2017-11-05 20:35 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
2017-11-05 20:35 ` Theodore Ts'o [this message]
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=20171105203542.jgupce2usbtjhbg2@thunk.org \
--to=tytso@mit.edu \
--cc=aeb@debian.org \
--cc=andrius@stikonas.eu \
--cc=andy.shevchenko@gmail.com \
--cc=gedakc@gmail.com \
--cc=kzak@redhat.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).