All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Absence notice
Date: Sat, 04 Jul 2009 00:40:01 -0400	[thread overview]
Message-ID: <1246682401.2544.26.camel@mj> (raw)
In-Reply-To: <d7ead6de0907031035o5a0f88e8o77912c7d8ead50d9@mail.gmail.com>

On Fri, 2009-07-03 at 19:35 +0200, Vladimir 'phcoder' Serbinenko wrote:

> >> > I don't think
> >> > there are any objections against supporting nested partitions.
> >> Yes but I thought someone may have comments like "let's shave ths part
> >> from the kernel". The patch doesn't increase the core.img because
> >> increase of kernel size is compensated by pc.mod/bsdlabel.mod split.
> >> It the cases when bsdlabel.mod is used usually no modules like raid or
> >> lvm are used
> >
> > Such objections may be raised once there is a patch that compiles.
> > Distributors must consider worst case scenarios.
> >
> If worst-case scenarios don't fit into mbr gap we may consider another
> approaches
> 1) progressive loading (e.g. FS-parsing bootsectors in worst case
> bring some kind of stage1.5 back)

I don't think this would be very popular.

> 2) replace lzma with xz

I'm afraid it's the same thing essentially.

> 3) use another embedding areas. E.g. lvm has to divide PV in PE of
> equal length. This often results in last block of space being smaller
> then PE. This space is reported by pvdisplay as unusable and we may
> use it w/o problems. I'm not an lvm expert though so don't rely on my
> word

Or just use a separate partition.

Actually, it's a fair game not to support some especially convoluted
configurations.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2009-07-04  4:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 21:02 Absence notice Vladimir 'phcoder' Serbinenko
2009-07-02 22:08 ` Pavel Roskin
2009-07-02 23:29   ` Vladimir 'phcoder' Serbinenko
2009-07-03 17:22     ` Pavel Roskin
2009-07-03 17:35       ` Vladimir 'phcoder' Serbinenko
2009-07-04  4:40         ` Pavel Roskin [this message]
2009-07-04 20:27         ` Robert Millan
  -- strict thread matches above, loose matches on Subject: below --
2009-05-02 18:53 absence notice Vesa Jääskeläinen
2009-05-02 20:01 ` Vladimir 'phcoder' Serbinenko
2009-05-02 21:42   ` Vesa Jääskeläinen
2009-05-03  4:38 ` Colin D Bennett
2009-05-03  4:44   ` Bean

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=1246682401.2544.26.camel@mj \
    --to=proski@gnu.org \
    --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.