No,no, lklfuse still works with FreeBSD 13.0-RELEASE-p2
What I don't understand is why they include a module in a kernel just to blacklist it later on. Why not simply leave that module out?The counter intuitiveness comes from the numerous GNU/Linux distributions having their own kernel configuration but once you know what the kernel supports (either via loadable modules or builded ones directly onto the kernel) things got clearer.
Because it's much more convenient for the user to unblacklist a module than to build a custom kernel.Why not simply leave that module out?
rw
in a sudo mount -t ufs -o ufstype=ufs2,rw,user /dev/sdXX /media/somewhere
you get this in your syslog:
[19043.734096] ufs: ufs was compiled with read-only support, can't be mounted as read-write
/boot/loader.conf
in that on a working GNU/Linux ("Devuan 4") OS so as to reinstall on a borked FreeBSD OS.Well the most obvious reason is the "Linux-UFS" drivers only support read-mode. Which is which could be expected.
You will damage your UFS partition (and lose data) with rw. I had lost some myself. That's why most distros don't build their kernels with it by default. Even the option's name and description advise against it:No, there is a compile time option for read/write access.
UFS file system write support (DANGEROUS)
CONFIG_UFS_FS_WRITE:
Say Y here if you want to try writing to UFS partitions. This is experimental, so you should back up your UFS partitions beforehand.
So the OP's question of accessing UFS from linux passed by?
mount -t ufs -o loop,ro,ufstype=ufs2 /dev/nvme0n1p2 /media/p2