I don't have much to say about most of this, but noticed this bit: On Thu, Oct 17, 2019 at 09:48:42PM -0500, Richard Laager wrote: > The same implementation could (and if I have my way, will) be used to > provide a features=grub mask. This would be used for the boot pool > (bpool) to limit it to the features supported by GRUB. This would avoid > the dangerous message in "zpool status" which tells you to run "zpool > upgrade" on your bpool which would then break booting from it.
Isn't that a dubious and confusing way to spell it? After all, like any other ZFS implementation, GRUB's ZFS implementation has gained features over time, and it wouldn't surprise me if it continued to do so. It sounds like you'd need a set of versioned features for this as well as for features=portable; but it's not clear how the decision of when to promote a feature set to the unversioned level would be made, particularly given GRUB's rather slow and unpredictable release cycle and the widespread practice of backporting features by distribution maintainers. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
