I had time to revisit this. I think the user property thing is the way to go. The installer would just mark the entire pool as a pool that is considered bootable.
kyle@optional:~$ zfs get zsys:bootable rpool NAME PROPERTY VALUE SOURCE rpool zsys:bootable - - kyle@optional:~$ sudo zfs set zsys:bootable=YES rpool [sudo] password for kyle: kyle@optional:~$ zfs get zsys:bootable rpool NAME PROPERTY VALUE SOURCE rpool zsys:bootable YES local kyle@optional:~$ So then the grub update script could just check for that property instead of looking for a child dataset that matches some expectation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850003 Title: /etc/grub.d/10_linux_zfs doesn't skip non-linux zpools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1850003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
