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. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
