3 ms·
> on Debian this means using Backports which is not something any sensible sysadmin wants to do because it introduces the hell of having a mismatch of all sorts
by oarsinsync 2y ago
> on Debian this means using Backports which is not something any sensible sysadmin wants to do because it introduces the hell of having a mismatch of all sorts of software unless you spend your life defining exclusions in the apt config.
root@nas:/etc/apt/preferences.d# cat 80_kernel
Package: linux-image-amd64 linux-headers-amd64 linux-kbuild-*
Pin: release n=bullseye-backports
Pin-Priority: 1000
root@nas:/etc/apt/preferences.d# cat 90_zfs
Package: libnvpair* libuutil* libzfs* libzpool* spl-dkms zfs-* zfsutils-linux zfsutils-linux-dev
Pin: release n=bullseye-backports
Pin-Priority: 1000
root@nas:/etc/apt/preferences.d# cat 1000_backports
Package: *
Pin: release n=bullseye-backports
Pin-Priority: 10
Pretty sure this is well documented in many places, I definitely didn’t invent this wheel myself. Been running zfs on Debian this way for the last 3 releases. Had one instance of drama when the kernel was updated before the zfs package was updated, making me need to downgrade the kernel, which was a faff for sure.
The benefits of using ZFS in my environment greatly outweigh the downsides of using backports. I vastly prefer Debian to alternatives, so here we are (for me).