From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] try to avoid false positives on FAT filesystem
Date: Fri, 06 Feb 2009 07:07:05 +0100 [thread overview]
Message-ID: <498BD389.60902@gmail.com> (raw)
In-Reply-To: <1233866360.3426.31.camel@fz.local>
If I understood you correctly you propose to use partition table
information to determine filesystem. I'm personally against it. First of
all it isn't portable - it probably wouldn't work on GPT. Second if you
just do mkfs.* <device> the partition type isn't changed. Linux ignores
partition type and so if your patch is applied there will be many bug
reports like "hey, *FS isn't detected". Finally sometimes you
intentionally change partition type in the technics like partition
hiding. IMO the correct solution to this problem is to make sure that
fat and ntfs are probed at last. Should we add a priority field for this?
Thanks
Vladimir 'phcoder' Serbinenko
Felix Zielcke wrote:
> Here's a little patch to check if
> bpb.version_specific.fat12_or_fat16.fstype or
> bpb.version_specific.fat32.fstype has the string FAT12/FAT16/FAT32
> As can be seen on [0] and [1] Dell PCs have a small FAT partition
> containing some utilities.
> It seems like mkfs.ext2 isn't always clearing the first 512 bytes.
> Good for us is that fstype is set to .AT16 on these Dell partitions, so
> it can be easily avoided.
> Are there any objections?
>
> [0] http://bugs.debian.org/514263
> [1] http://bugs.debian.org/505137
next prev parent reply other threads:[~2009-02-06 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 20:39 [PATCH] try to avoid false positives on FAT filesystem Felix Zielcke
2009-02-06 6:07 ` phcoder [this message]
2009-02-06 15:46 ` Felix Zielcke
2009-02-06 18:31 ` phcoder
2009-02-07 19:32 ` Felix Zielcke
2009-02-07 22:52 ` Robert Millan
2009-02-08 9:03 ` Felix Zielcke
2009-02-08 18:02 ` Robert Millan
2009-02-08 19:18 ` Felix Zielcke
2009-02-08 19:56 ` Robert Millan
2009-02-08 19:59 ` Felix Zielcke
2009-02-09 14:07 ` Robert Millan
2009-02-09 14:17 ` Felix Zielcke
2009-02-09 14:40 ` Robert Millan
2009-02-09 14:49 ` Felix Zielcke
2009-02-09 17:06 ` Robert Millan
2009-02-09 18:01 ` Felix Zielcke
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=498BD389.60902@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.