6 ms·
From the page: > I decided it was finally time to build a file server to centralize my files and guard them against bit-rot. Although I would have preferred to
by danielparks 4y ago
From the page:
> I decided it was finally time to build a file server to centralize my files and guard them against bit-rot. Although I would have preferred to use OpenBSD due to its straightforward configuration and sane defaults, I was surprised to find that none of the typical NAS filesystems were supported.
OpenBSD does not support ZFS.
- hestefisk 4y agoTheo is, perhaps rightfully so, against importing what is effectively a paravirtualized Solaris kernel into the OpenBSD source code in order to run a file system.
- nix23 4y agoToo sad, because the partitioning of OpenBSD is why i don't use it, with ZFS you could just do a dataset throw x^w,nosuid etc on them and give them a quota, with ffs one can bet that you run out of space (earlier or later), in one of the partitions (Workstation NOT Server).
- hestefisk 4y agoYou can use your own partitioning though? One for /, one for swap. Done.
- nix23 4y agoYes you can but you cant set stuff lime nosuid etc on /
- anthk 4y agoI doubt it. Even for ports you can still symlink /usr/ports to $HOME/ports, for Scummvm with --enable-all-engines or Eduke32 (Build/GPLv2 license clash, can't be shared as a binary). /usr/local is not small at all by default.
- nix23 4y ago
- Beltalowda 4y agoI think they're trying to say is you can just link stuff to $HOME if some filesystem runs out of space (not an endorsement of that view, just an explanation).
- enbian 4y ago