From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] nested partitions
Date: Fri, 22 Jan 2010 17:53:00 +0100 [thread overview]
Message-ID: <20100122165300.GA14428@thorin> (raw)
In-Reply-To: <d7ead6de0908251412we8e0d3fy7c7b79be2e8df90a@mail.gmail.com>
I haven't checked the specific details, but I think this approach is fine IF
we only recurse for partition types where this makes sense. This includes:
- BSD partition types inside MSDOS labels
- Solaris partition type inside MSDOS labels
This can be done by extending "has_partitions" to be set to "yes" in those
specific partition types. The implementation should be the least intrusive
possible, taking into account that this kind of situations are an oddity
rather than the norm.
As for the other situations, the more I think about this, the more convinced
I am that this whole "partition nesting" concept is a broken mess. I think I
already explained why in this list, but I can rehash the reasons if anyone's
interested. I don't want to compromise on such part of GRUB core for the sake
of supporting this kind of layouts.
The only reason I'm open to implementing these two cases [1] is that they seem
to be inmensely popular among *BSD systems and Solaris derivatives.
As for *BSD and Solaris who read this, my advice is to step away, ditch the
whole MSDOS label burden and just settle on a clean label without the limits
DOS ones have. If you strive for compatibility, GPT is a good choice IMO (and
the rest of the free world seems to be moving in this direction thanks to 2 TiB
limit).
[1] I know the first one is already implemented, but your approach makes it
less ad-hoc and splits code off part_msdos.mod, which is an improvement.
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2010-01-22 16:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 15:51 [PATCH] nested partitions Vladimir 'phcoder' Serbinenko
2009-07-16 20:52 ` Vladimir 'phcoder' Serbinenko
2009-07-31 7:58 ` Marco Gerards
2009-07-31 9:39 ` Vladimir 'phcoder' Serbinenko
2009-07-31 19:48 ` Vladimir 'phcoder' Serbinenko
2009-07-31 20:25 ` Vladimir 'phcoder' Serbinenko
2009-08-02 22:17 ` Robert Millan
2009-08-02 22:36 ` Vladimir 'phcoder' Serbinenko
2009-08-02 22:02 ` Robert Millan
2009-08-02 22:09 ` Vladimir 'phcoder' Serbinenko
2009-08-02 22:25 ` Robert Millan
2009-08-02 22:44 ` Vladimir 'phcoder' Serbinenko
2009-08-04 20:15 ` Robert Millan
2009-08-17 13:00 ` Vladimir 'phcoder' Serbinenko
2009-08-17 14:06 ` Robert Millan
2009-08-17 14:34 ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:57 ` Vladimir 'phcoder' Serbinenko
2009-08-24 13:39 ` Vladimir 'phcoder' Serbinenko
2009-08-25 20:14 ` Vladimir 'phcoder' Serbinenko
2009-08-25 23:07 ` Robert Millan
2009-08-25 23:13 ` Vladimir 'phcoder' Serbinenko
2009-08-26 0:50 ` Robert Millan
2009-08-25 20:35 ` Seth Goldberg
2009-08-25 21:12 ` Vladimir 'phcoder' Serbinenko
2010-01-22 16:53 ` Robert Millan [this message]
2010-01-22 18:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-24 20:41 ` Robert Millan
2010-01-24 21:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-25 7:23 ` Robert Millan
2010-01-25 0:38 ` Bruce Dubbs
2010-01-25 4:56 ` Michal Suchanek
2010-01-25 7:31 ` Robert Millan
2010-01-25 7:52 ` Robert Millan
2010-01-25 8:25 ` Grégoire Sutre
2010-01-22 18:43 ` Seth Goldberg
2010-01-24 20:44 ` 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=20100122165300.GA14428@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.