From 1966574e65d7558e354e16e1e8212d7637e9533f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 13 Jul 2025 16:57:11 +0300 Subject: Update content for html --- gemfeed/atom.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'gemfeed/atom.xml') diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 5488b4e1..adcfa57e 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-07-13T16:50:30+03:00 + 2025-07-13T16:55:45+03:00 foo.zone feed To be in the .zone! @@ -1801,7 +1801,8 @@ Jul 06 10:Flexible redundancy: Configure different replication levels per directory or file, optimising storage efficiency.
  • FreeBSD support: MooseFS has native FreeBSD support, making it a natural fit for the f3s project.

    • -Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS).
    +Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS). What about Ceph and GlusterFS? Unfortunately, there doesn't seem to be great native FreeBSD support for them. However, other alternatives also appear suitable for my use case.
    +

    I'm looking forward to the next post in this series, where we will set up k3s (Kubernetes) on the Linux VMs.

    -- cgit v1.2.3