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: Wed, 22 Jul 2009 19:22:58 +0200 [thread overview]
Message-ID: <20090722172258.GD8706@thorin> (raw)
In-Reply-To: <d7ead6de0907181428t5a73e6c2w9317f29c864bf746@mail.gmail.com>
On Sat, Jul 18, 2009 at 11:28:58PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > I don't understand what you mean here.
> Let's take a common example of cdrom. Most of the users and developers
> are accustomed to a cdrom holding one filesystem. On macs however cds
> are partitioned and not being able to access all the partitions is a
> problem for end user. Such situations are probably common. If we ditch
> has_partitions altogether the only negative side effect will be that
> in some weird configurations unpartitioned media may appear to have
> partitions but whole media is still accessible. Additionally it
> simplifies and makes kernel smaller
I'm not sure they're so weird. But we could still do it. Pavel, what do
you think?
> >> > 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.
> >> The approach proposed by Collin avoids such problems since correct
> >> pc_partition_map is always detected as such.
> >
> > I haven't looked at the source code, but what he said is we can determine if
> > an MBR is valid by checking the bootable flag, and this is not always so.
> I don't see any problem. He said: checking that bootable flags of all
> partitions are either set (0x80) or unset (0x0) and not another value
Oh, that's different. I think it's fine provided that:
- None of the commonly used free partitioning tools uses an illegal value.
- We fail gracefully and let the user know why.
--
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-22 17:23 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
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 [this message]
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=20090722172258.GD8706@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.