All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Remove has_paritions
Date: Sun, 30 Aug 2009 15:33:29 +0200	[thread overview]
Message-ID: <20090830133329.GA17120@thorin> (raw)
In-Reply-To: <d7ead6de0908281225p3f83624fg6b6bdecfe024d28@mail.gmail.com>

On Fri, Aug 28, 2009 at 09:25:15PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> diff --git a/disk/lvm.c b/disk/lvm.c
> index 126b494..59bf2d7 100644
> --- a/disk/lvm.c
> +++ b/disk/lvm.c
> @@ -97,7 +97,6 @@ grub_lvm_open (const char *name, grub_disk_t disk)
>    if (! lv)
>      return grub_error (GRUB_ERR_UNKNOWN_DEVICE, "Unknown LVM device %s", name);
>  
> -  disk->has_partitions = 0;
>    disk->id = lv->number;
>    disk->data = lv;
>    disk->total_sectors = lv->size;

Why would LVM users want to nest partition maps in them?

This makes me think removing has_partitions is not such a good idea.

Actually, LVM is a partition map of sorts.  If we're going to refurbish our
partition handling model, I think we should contemplate the possibility of
LVM (and perhaps swRAID) becoming less ad-hoc.

But that is more an idea for 2.0.  What are our inmediate needs?

-- 
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."



  reply	other threads:[~2009-08-30 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28 19:25 [PATCH] Remove has_paritions Vladimir 'phcoder' Serbinenko
2009-08-30 13:33 ` Robert Millan [this message]
2009-08-30 13:44   ` Vladimir 'phcoder' Serbinenko

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=20090830133329.GA17120@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.