On 2012-10-27 19:22, Chris Murphy wrote: > > On Oct 26, 2012, at 9:03 PM, Fajar A. Nugraha <list@xxxxxxxxx> > wrote: > >> >> So back to the original question, I'd suggest NOT to use either >> send/receive or set-default. Instead, setup multiple boot >> environment (e.g. old version, current version) and let user choose >> which one to boot using a menu. > > Is it possible to make a functioning symbolic or hard link of a > subvolume? > > I'm fine with "current" and "previous" options. More than that seems > unnecessary. But then, how does the user choose? What's the UI? Is > this properly the domain of GRUB2 or something else? On my computer, when update-grub is called, it scans for all the subvolumes and show them in the menu, allowing the user to switch at boot time. [...] > > Example. The following are all subvolumes, subvolume set-default 0, > fstab uses subvol=home, subvol=root, subvol=boot for mount options. > > toplevel ├── boot ├── home ├── root ├── fedora18 │ ├── boot │ └── > root > > On this system, grub-mkconfig produces a grub.cfg only for the system > I'm currently booted from. It does not include any entries for > fedora18/boot, fedora18/root, even though they are well within the > normal search path. And the reference used is relative, i.e. the > kernel parameter in the grub.cfg is rootflags=subvol=root > > If it were to create entries potentially for every snapshotted > system, it would be a very messy grub.cfg indeed. I don't think so. If a subvolume has a /sbin/int and and /etc it would be suitable to be used as root filesystem. -- gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
