Re: Libvolume incorrectly detects FAT32

[Michael Buesch <mbuesch@freenet.de>]

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Tuesday 07 March 2006 18:32, you wrote:
> So the bottom line is, "no, this idea won't make it"? How about, then, let the
> user of the lib (ie. the app using the lib) specify whether it wants a full
> match or not?

I think you misunderstand.
The lib (app) is about properly _creating_ the partition with
all magic. So basically every formating tool should zero out
parts of the partition and _then_ write the new magic there.
Obviously some tools fail to zero out the space. This is what needs
fixing.
Pushing the problem to kernel-space, by implementing a faulty-by-design
scoring system is IMHO not the way to go.

BTW:
I often saw this problem in the past, especially with swap and fat
related partitions. So I now always use dd to zero out the first
part of a partition before I reformat it.
That's a good workaround the broken format utilities.

To summerize: I don't think there is something broken in the kernel,
so I don't think we should go and fix nonbroken code. Fix the
broken code in userspace instead.

-- 
Greetings Michael.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]