From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix when installing on pationless but partionable medium
Date: Sat, 18 Jul 2009 20:42:55 +0200 [thread overview]
Message-ID: <20090718184255.GG8867@thorin> (raw)
In-Reply-To: <d7ead6de0907170941v377b4a95x283714d43fe6d885@mail.gmail.com>
On Fri, Jul 17, 2009 at 06:41:59PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Sometimes a media that can be partioned isn't really partioned. E.g.
> usb sticks. This is a patch to handle this situation.
But we had a check for this already, is it not working?
if (! dest_dev->disk->has_partitions)
{
grub_util_warn ("Attempting to install GRUB to a partitionless disk. This is a BAD idea.");
goto unable_to_embed;
}
> Unfortunately
> such medium is often formated with a flavour of FAT which shares its
> signature with MBR so it may be easily misidentified as
> pc_partition_table. Furthermore the same signature is shared with
> bootsectors including grub. One possibility is to try interpret disk
> as known filesystems and see if we succeed. But the problem is that
> the check for FAT are light and may result in false positives too. The
> only more or less advanced check there is a check for FATXX string.
> But I was about to propose to eliminate this check since I encountered
> a FAT filesystem without this string on friend's SD card formatted
> with symbian which he wanted to use as liveusb. Does anyone has a
> better idea?
I'm not sure there's much we can do about this. Using heuristics sounds like
it will make the solution worse than the problem. I don't care much about
Microsoft filesystems, but I'd hate to see GRUB fail on a completely sane
ext3 inside msdos label because it happened to look like FAT in raw disk at
the same time.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-18 18:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 16:41 [PATCH] Fix when installing on pationless but partionable medium Vladimir 'phcoder' Serbinenko
2009-07-17 16:51 ` Colin Watson
2009-07-18 18:45 ` Robert Millan
2009-07-18 19:01 ` Vladimir 'phcoder' Serbinenko
2009-07-18 19:17 ` Robert Millan
2009-07-19 10:07 ` Colin Watson
2009-07-22 17:16 ` Robert Millan
2009-07-22 17:36 ` Pavel Roskin
2009-07-22 17:43 ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:46 ` Pavel Roskin
2009-07-26 12:53 ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:42 ` Robert Millan [this message]
2009-07-18 19:00 ` Vladimir 'phcoder' Serbinenko
2009-07-18 19:22 ` Robert Millan
2009-07-18 21:28 ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:22 ` Robert Millan
2009-07-22 17:45 ` Pavel Roskin
2009-07-26 13:54 ` Vladimir 'phcoder' Serbinenko
2009-07-28 17:33 ` Robert Millan
2009-07-28 21:42 ` Vladimir 'phcoder' Serbinenko
2009-07-31 15:43 ` Robert Millan
2009-07-19 10:02 ` Colin Watson
2009-07-22 17:24 ` Robert Millan
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=20090718184255.GG8867@thorin \
--to=rmh@aybabtu.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.