linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Libvolume incorrectly detects FAT32
Date: Mon, 06 Mar 2006 21:59:31 +0000	[thread overview]
Message-ID: <200603062259.32462.mbuesch@freenet.de> (raw)
In-Reply-To: <20060306215704.35f12840@silver>

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

On Monday 06 March 2006 21:57, iSteve wrote:
> Hello,
> I'm having one silly partition, which has remnants of previous FAT32 filesystem
> on it, a LILO bootloader on it and ext2 filesystem spaning all over the
> partition.
> 
> The first 512B look exactly like a valid FAT partition header would, except the
> magic is "LILO". 
> 
> I've looked at the sources for FAT detection, and I noted that when a FAT-like
> filesystem misses magic, it's still considered valid, since as comment says,
> some old floppies may lack it. I consider this point valid, however, this
> causes my partition to be detected, incorrectly, as FAT32.
> 
> My proposed solution is to compare magic if FAT32 is assumed, and if magic will
> not match for FAT32, consider it a failure; floppies that old that they lack
> any magic will most likely not be formatted in FAT32.
> 
> Trivial patch is attached, comments/complaints?:)

Yes, I fear users of stupid digicams may get hit by this.
The Formating option on cheap digicams may sometimes be buggy implemented.
I think you should instead do a
dd if=/dev/zero of=/dev/partition bs=512 count=1
and reformat your partition.

-- 
Greetings Michael.

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

  reply	other threads:[~2006-03-06 21:59 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 [this message]
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
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=200603062259.32462.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).