[lkml]   [2017]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux & FAT32 label
On Sunday 05 November 2017 15:35:42 Theodore Ts'o wrote:
> 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?

Easy way how to achieve this situation:

1. use mkdosfs to format hard disk to FAT32 with label LABEL42

2. boot Windows 10 (or XP) and set label of that FAT32 partition to
empty (via Explorer GUI)

3. profit

You would have stored LABEL42 in boot sector and no label in root
directory. Windows handle this situation as there is no label.

Pali Rohár

 \ /
  Last update: 2017-11-05 22:13    [W:0.145 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site