From: Stuart D Gathman <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: giovanni_re <john_re@fastmail.us>
Subject: Re: [linux-lvm] Disk Partitioning tools, - for having multi distros bootable - GUI preferably- best for LVM Logical Volume Management ; jor
Date: Wed, 28 Jul 2010 14:10:15 -0400 [thread overview]
Message-ID: <4C507287.7050007@bmsi.com> (raw)
In-Reply-To: <1280183526.18769.1386844083@webmail.messagingengine.com>
On 07/26/2010 06:32 PM, giovanni_re wrote:
> Not as Virtual Machines (VMs), so must be what you are calling "bare
> metal".
>
> Ie, booting up into GRUB should show:
> sda1 - linux distro 1
> sda2 - linux distro 2
> sda?? - in the sda4 LVM, linux distro 3
> sda??+1 - in the sda4 LVM, linux distro 4
> etc.
>
>
> SDA4 LM currently has a /home data partition, & free space
>
> The only place I see to put another distro partition is in the sda4 LVM.
> Based on your discussion following your post, with Stuart, is that still
> true?
>
>
> In any case, now that Logical Volume technology exists, in addition to
> the previous Extended Partition technology, what is the way to configure
> the partitions with LVs to have multiple partitions available to GRUB to
> boot from?
>
Use a large /boot partition. The last time I used Ubuntu, it did not
easily support having a separate /boot filesystem (instead making the
root fs bootable), so that could be a problem, unless Ubuntu also
supports grub 2 (with LVM support).
So, with distros that support separate /boot (e.g. Fedora and EL), just
share the /boot partition between them (they should name the files to
avoid conflicts). Each grub entry specifies the root filesystem, which
can be a LV.
There can be multiple instances with the same kernel version (e.g. F12
before scary update, F12 after scary update).
With distros that don't support /boot, but *do* support grub 2 (and you
have grub 2), then grub entries refer to kernel files in LVs for the distro.
With distros that support both, do it either way.
With OS that do not support LVM (E.g. Windows), you will have to have a
partition and chain load in grub.
prev parent reply other threads:[~2010-07-28 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 3:28 [linux-lvm] Disk Partitioning tools, GUI preferably- best for LVM Logical Volume Management ; jor giovanni_re
2010-07-24 4:39 ` Stuart D. Gathman
2010-07-24 16:54 ` Harald Heigl
2010-07-26 8:45 ` Bryn M. Reeves
2010-07-26 12:16 ` Stuart D. Gathman
2010-07-26 12:43 ` Bryn M. Reeves
2010-07-26 13:59 ` Stuart D. Gathman
2010-07-26 14:04 ` Bryn M. Reeves
2010-07-26 16:48 ` Stuart D. Gathman
2010-07-26 22:32 ` [linux-lvm] Disk Partitioning tools, - for having multi distros bootable - " giovanni_re
2010-07-28 18:10 ` Stuart D Gathman [this message]
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=4C507287.7050007@bmsi.com \
--to=stuart@bmsi.com \
--cc=john_re@fastmail.us \
--cc=linux-lvm@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).