From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Libvolume incorrectly detects FAT32
Date: Tue, 07 Mar 2006 21:47:25 +0000 [thread overview]
Message-ID: <200603072247.25615.mbuesch@freenet.de> (raw)
In-Reply-To: <20060306215704.35f12840@silver>
[-- 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 --]
next prev parent reply other threads:[~2006-03-07 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 20:57 Libvolume incorrectly detects FAT32 iSteve
2006-03-06 21:59 ` Michael Buesch
2006-03-06 22:37 ` Kay Sievers
2006-03-07 17:01 ` iSteve
2006-03-07 17:15 ` Kay Sievers
2006-03-07 17:32 ` iSteve
2006-03-07 21:47 ` Michael Buesch [this message]
2006-03-08 5:57 ` iSteve
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=200603072247.25615.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=linux-hotplug@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).