Hi,
Perhaps i am missing something but when i use zfs with pools do i always have to use dkms ?
Asking because every time a new kernel has to be compiled dkms is rather slow.
On cachy and manjaro there are pre-compiled modules like on cachy linux-cachyos-lts-zfs and on manjaro linux618-zfs
Looked into the eos repo but could not find pre-compiled zfs.
Is it possible for dev-ops to think about this for in the future ?
What kernel are you using?
Although I’m not sure that eliminates the need to compile that, and it’s also behind the current kernel release version 
It’d be simpler to stick with the DKMS version I think.
It’s in the chaotic aur which should be precompiled.
If using chaotic there could be differences in versions i guess. On cachy and manjaro the zfs kernel stuff comes with recent kernels. Perhaps it is policy of the devops eos i don’t know.
Hopefully in future there will be some sort of support i hope.
EndeavourOS is essentially Arch with a great installer and sane defaults.
Some additional management tools are provided out of the box, and zfs-dkms is included in the EndeavourOS repository. In effect, EndeavourOS is almost entirely dependant on the official Arch repositories with only minor exceptions.
Part of the issue is that providing a pre-compiled kernel module, requires tight release synchronisation with upstream Arch kernels, as such a module must be compiled for use by a specific kernel version. You would expect the compiled ZFS module to always lag behind its corresponding kernel release, causing ongoing update issues for users.
This is an issue even with the non-compiled version I linked above, which have fallen behind the current release kernels.
The other issue is providing non-official compiled binaries, introduces a requirement for trust that I’m not sure many people really appreciate.
Your best bet is to vote for the zfs-linux AUR package, and hope it’s picked up by an official Arch maintainer.