On Wed, Jun 20, 2012 at 10:22 AM, H. Peter Anvin <h...@zytor.com> wrote: > a. Make a snapshot of the current root; > b. Mount said snapshot; > c. Install the new distro on the snapshot; > d. Change the bootloader configuration *inside* the snapshot to point > to the snapshot as the root; > e. Install the bootloader on the snapshot, thereby making the boot > block point to it and making it "live".
IMHO a more elegant solution would be similar to what (open)solaris/indiana does: make the boot parts (bootloader, configuration) as a separate area, separate from root snapshots. In solaris case IIRC this is will br /rpool/grub. A similar approach should be implementable in linux, at least on certain configurations, since if you put /boot as part of "/" (thus, also on btrfs), AND you don't change the default subvolume, AND the roots are on their own subvolume, the paths to vmlinuz and initrd on grub.cfg will have subvols name in it. So it's possible to have a single grub.cfg having several entries that points to different subvols. So you don't need to install a new bootloader to make a particular subvol live, you only need to select it from the boot menu. I'm doing this currently with ubuntu precise, but with manually-created grub.cfg though. Still haven't found a way to manage this automatically. -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
