Sigh. So copying and pasting commands from the internet doesn't solve my problem. This means I'm going to have to actually try and /understand/ what's wrong. I didn't sign up for this.
@hl@xdydx#FreeBSD has only support for SMBv1, which you should absolutely avoid for security reasons, although you can probably configure #samba to still allow it ... but ... don't. Nowadays I'd prefer to say FreeBSD does not support mounting SMB shares.
There are some ports available implementing "modern" SMB (v2/v3) on top of #fuse, which might be an option, but in my experience, they're not perfectly reliable and performance isn't the greatest either.
If ever possible, work on the server side and see whether you can share via #NFS instead. Either #NFSv3 (which is only "secure" as long as your network is perfectly secure and you control all participating machines, but at least it doesn't pretend to do anything else), or #NFSv4 with #kerberos security.
Are "hard links" important or a nice to have in a filesystem?
I'm trying to assess possible feature compromises for a #decentralized / #p2p based #filesystem that can be mounted on multiple machines, so any views on the usefulness of hard links with examples would be appreciated.
One such compromise here is merging of changes made from different devices, that will be much harder with hard linking.
Anyone familiar with Syncer, a virtual disk written in Rust?
It's a massive virtual disk with #POSIX interface that can be mounted locally using #FUSE.
Written in #Rust, the architecture and backend mean it could be adapted to a decentralised backend, something I looked into in the past and an revisiting.
I'm wondering if anyone else is interested in this potential, and if anyone knows the author or second contributor.