On Nov 8, 2013, at 10:59 AM, Goffredo Baroncelli <kreij...@inwind.it> wrote: >> >> Now I don't know what snapshot that is, since it's just renamed to >> some non-descriptive name like "root" which happens to, by >> convention, always be the active root. This is the problem with using >> user domain to store contextual metadata. We need another way to do >> this, rather than inject these changes into filename/foldername which >> are primarily user domain. And we need agreement on a right way to do >> this rather than distribution convention. > > Put all the required information in an xattr... > >> >> We need some distribution collaboration in this area, or this is >> going to turn into an end-user pain point, with multiboot users top >> on the list of the injured. > > I fully agree: whatever solution we found, it has to be shared across > all distributions.
Yes although not merely shared. But designed and agreement by. Otherwise this becomes worse than the linux multiboot situation, which today is pretty much a broken mess in which linux distributions break the bootability of the existing linux OS installation, and do so by default. It's an ironic case where a linux distro is friendly to co-existing with Windows and OS X, but typically is downright hostile to fellow linux OS installations. Now if we want to admit that the different distros are in effect all hostile competitor OS's to each other, then I guess a free for all where an open filesystem like Btrfs effectively becomes proprietary due to highly complex and variable layouts required to support snapshot system rollbacks is what we'll just have to expect. In which case multiboot on Btrfs is dead in the water. Each distro would have to have their own volume, not their own subvolumes. Chris Murphy-- 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
