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: Thu, 9 Nov 2017 11:21:25 -0500 [thread overview]
Message-ID: <20171109162125.ixpymbeiovpsj7mc@thunk.org> (raw)
In-Reply-To: <20171109090145.lffuluwm3sxanfzu@pali>
On Thu, Nov 09, 2017 at 10:01:45AM +0100, Pali Rohár wrote:
> > > You would have stored LABEL42 in boot sector and no label in root
> > > directory. Windows handle this situation as there is no label.
> >
> > But why should we *care*?
>
> FAT is Microsoft's filesystem and the only usage of it on Linux is due
> to interoperability with different non-Linux systems. So here we should
> implement FAT in the similar/same way as other systems. It does not make
> sense to implement it differently and specially in non-compatible way.
> Because it lost reason what is primary usage of the FAT on Linux.
The primary usage of FAT on Linux is for data interchange, primarily
with USB sticks. I'm still failing to see how it might "spoil some
vast eternal plan"[1] if a USB stick which Windows would show as
having no label, blkid/udev showed as having the label "LABEL42"?
[1] to quote the song "If I were a rich man"
I'm just trying to understand why this specific detail of bit-for-bit
compatibility is so important.
- Ted
next prev parent reply other threads:[~2017-11-09 16:21 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
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 [this message]
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=20171109162125.ixpymbeiovpsj7mc@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).