That's a workaround at best, not a solution. The scripts aren't configured with the Debian package so the macros are not expanded. The update-defaults command doesn't get run on new systems, nor do we get any upstream modifications or fixes. It seems to be a well-done patch for an officially supported init system, I haven't heard any reason yet to not merge it.
Sent from my iPhone > On Jun 25, 2018, at 17:23, Antonio Russo <antonio.e.ru...@gmail.com> wrote: > > [snip] >> I shouldn’t have to keep building custom versions so my pools import on >> boot... > > If you just install the regular Debian zfs packaging, and then make sure the > init > scripts are installed an enabled, they will stay enabled. (upgrading the zfs > packaging won't disable init scripts it knows nothing about). > > As frustrating as this all is, you do not need to rebuild the package just to > install a few init scripts once per machine. If you're provisioning a large > number > of machines regularly, I also sympathize, but it's still just a couple more > lines > in Ansible.
