FreeBSD is a clean, powerful, secure, and reliable Unix-like Operating System built for performance and freedom, and that’s why I’ve been happily nerding out with it for almost 30 years.
Disk partitioning and filesystem management are among the most fundamental sysadmin skills. Understanding how storage is organized helps administrators troubleshoot systems, prepare new disks, recover environments, and deploy infrastructure with confidence.
In this post, I’ll walk through the basic workflow using gpart, newfs, and mount, which are essential tools for managing traditional UFS storage on FreeBSD.
This blog post is run-book how to deploy NGINX web server with Automatic TLS certificate issuance and renewal leveraging Let’s Encrypt DNS Challenge via Active24 DNS provider.
I need NFS 4.x storage for some tests. I would like to leverage FreeBSD 14.3 with ZFS and export two ZFS Datasets via NFS.
In this blog post, I will document how to setup NFS storage on FreeBSD.
ImpossibleCloud S3 storage is pretty interesting offering of European Object Storage. Cloud4com datacenters are located in Czechia, Prague and Impossible closest S3 Storage is in Frankfurt. ImpossibleCloud could be used for offsite backups or remote object repositories.
In this blog post, I will do a benchmark of ImpossibleCloud S3 storage accessed from Prague's Cloud4com datacenter. I have S3 client in Cloud4com vPDC in Prague and accessing ImpossibleCloud S3 Storage in Frankfurt.
Cloud4com physical datacenter is located at Prague, TTC
ImpossibleCloud S3 Storage is located at the “eu-central-2” region which corresponds to data centers in Germany (Europe / Frankfurt area).
Let's do some performance tests and report achieved results.
Why vmx0, vmx1, vmx2 interface names sometimes cause fear?
Anyone running FreeBSD as a router or firewall in a virtualized environment knows this situation well:
network interfaces are named vmx0, vmx1, vmx2, and critical configuration
(pf, routing, jails) depends on them. A small change can suddenly turn WAN into LAN and LAN into DMZ.
On physical hardware this is a common problem. Adding a PCI card can change device enumeration order. In VMware, the situation is much better, but it is still important to understand how to make interface naming stable and future-proof.