hayzamI just realized an article one of our users wrote (and I reposted) https://iptechnics.com/blogs/from-proxmox-to-freebsd-and-sylve-in-our-office-lab, just hit the frontpage on hackernews!
So happy to see the new influx of users to https://sylve.io ! We are so, so back folks. 2026 is the year of vanilla FreeBSD in the homelab scene!
Feedback from a new Sylve user (from our discord) ๐๐
BSD NLYesterday, 42 days to go to the next BSD-NL Conference - Early 2026 ๐ก๐โณ
You can still get tickets!
https://tickets.bsdnl.nl/bsdnl/
You can still submit your talk!
https://events.bsdnl.nl/
(CfP closes on 2026-04-12)
๐ 2026-05-09 / May 9th 2026
๐ 10:00-23:00 CEST
๐ Brouwerij Maximus (Utrecht)
๐ https://bsdnl.nl
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
๐น๐๐๐ ๐ฒ๐๐๐๐๐ โ ๐คชdmesg or it didn't happen: https://dmesgd.nycbug.org/dmesgd?do=view&id=8878
picture or it didn't happen.
HenryMy #FreeBSD #HomeLab adventures continue. With some basic shell scripts and mtree I've added a rudimentary intrusion detection system. Do others do something similar, is there a much better solution I should be aware of?
https://henryleach.com/2026/03/basic-intrusion-detection-system-with-mtree/
Basic Intrusion Detection System with mtree
After the very basic server setup, having some kind of simple Intrusion Detection System (IDS) seems like a good idea. While all the previous steps were designed to prevent someone taking control of your server, if someone has managed to tamper with something, short of being locked out - how would you know?
RubenWhat's the fuss about FreeBSD? Read about my first impressions here, after playing with it these past three months on my servers (and, since a few weeks, on my laptop):
https://kedara.eu/playing-freebsd/
My special thanks to the awesome and kind #BSDCafe Barista @stefano for writing the posts that introduced me to the BSDs, and for fostering such a positive and welcoming community!
BSDTVNext NYC*BUG: Wednesday April 1st
What's Changed Since The Last Time I Came this Way - a talk that was supposed to be about OpenZFS, by Michael W Lucas
2026-04-01 @ 18:45 local (22:45 UTC) - Backroom of Brass Monkey 55 Little West 12th St
https://www.nycbug.org/
Hear how the newest ZFS book is going and what @mwl has planned.
Flyer: https://www.nycbug.org/media/2026-04-01_Lucas_Flyer.pdf
Ember in the Pattern BufferI finally have a second-hand computer fast enough to be capable of things like having a window manager.
TionislaOld: "Zaonce" - Dell Inspiron 1525
Kernel: 14.3-RELEASE-p8 amd64
Operating System: GhostBSD 25.02-R14.3p8
Desktop: LXQT 2.3.0
Windowmanager: XFWM4
Qt Version: 6.10.1
Graphics Platform: X11
https://bsd-hardware.info/?probe=2904d8ae09
#runbsd #freebsd #ghostbsd #unix #foss #lxqt #desktop #screenshot
Root MooseThere's one last thing I need to get my head around with respect to using FreeBSD jails as a replacement for docker/podman.
I generally configure containers as totally ephemeral. Any data or individual files that a container uses, and that I care to keep, resides outside the container. It is linked inside via volumes defined in the run shell script or compose file. In some cases even dumb things like root's .bashrc gets linked in so that nuking a container doesn't lose the shell history the next time something needs hand fettling (mediawiki, maintenance scripts, composer, bootstrap, and friends - yes, needs more automation).
Any time a container gets restarted, step one may be to delete the container (and associated volumes it creates), re-pull latest and instantiate fresh. This is pretty typical for Jellyfin for example.
Also, working this way means that the entire backup process can exist outside the container volumes and nothing redundant in /var/lib/docker needs to get backed up.
Anyway, I need to figure out how to achieve something similar under FreeBSD jails. I'm assuming there is something in ZFS that provides a similar type of functionality during jail startup but haven't dug into it yet.
Then there's the 'correct' and easy way on how to upgrade the software inside a jail (os components and services the container runs) that needs experimentation on my side. Some scripting to do.
Jails seem much more elegant but there is lot of old cruft and 'finger memory' to work around. Ha. A lot of stuff is pre-wired and ready to go for regular usage in Linux containers in comparison, I think.
The journey continues.