As the @bsdcan lists of talks and tutorials have been posted, I can officially announce my presentation:

Don't Freeze in the Cloud: Reclaiming Home Control with NetBSD

In 2010, I was taking more flights than cups of coffee. After a two-week trip, I returned home to a nasty, albeit expected, surprise: an indoor temperature of 7.8°C (46 F). Possessing more time than money, I decided to solve the problem my own way. I built a custom Python-based control system, accessible only via VPN, to manage my heating.

In 2015, after moving houses, this system was demoted to a secondary role, replaced by a shiny, commercial "smart" thermostat. However, I continued to maintain and update my custom solution for fun.

Fast forward to October 2025: major cloud providers faced significant outages. My commercial thermostat became dumber than a mechanical switch. I was reduced to manual two-hour overrides, with no visibility into settings or usage. It was a wake-up call: keeping my home warm should not depend on someone else's server.

I dusted off my solution and adapted it to modern needs - powered, of course, by NetBSD, running on the very same hardware that served my previous home for years.

In this talk, I will share the journey, the technical challenges, and the architectural decisions behind the project. I will demonstrate how NetBSD’s stability and low footprint make it the ideal operating system for long-term, "set-and-forget" home automation, allowing us to reclaim control from the cloud.

#NetBSD #BSDCan #BSDCan2026 #RunBSD #OwnYourData #Presentation #Talk

System Administration: Week 3: Resizing a file system

In these two videos, we show how to resize an existing filesystem. First on #NetBSD using the resize_ffs(8) tool, where we first increase the size of a 512MB partition to 1GB, then shrink it down to 256MB. Next we repeat the same exercise on #Debian Linux, using the resize2fs(8) tool.

https://youtu.be/9l-g3keN48g

https://youtu.be/4V15y5Klo9Y

#sysadmin #devops #sre

CS615 System Administration, Week 3, Warmup Exercise 1 - Resizing a filesystem on NetBSD

YouTube

On #Illumos, Joy vi is in /usr/src/cmd/vi:

https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi

On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi:

https://cgit.freebsd.org/src/tree/contrib/nvi/

FreeBSD has an nvi2 in ports:

https://freshports.org/editors/nvi2/

OpenBSD has elvis in ports:

https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR

Ritter's Heirloom vi is on SourceForge:

https://ex-vi.sourceforge.net

STEVIE was posted to comp.sources.unix in 1988:

https://sources.vsta.org/comp.sources.unix/volume15/stevie/

Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example.

https://guckes.net/vi/clones.html

But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available:

https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi

#vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom

illumos-gate/usr/src/cmd/vi at master · illumos/illumos-gate

An open-source Unix operating system -- this is a read-only mirror of the official repository at https://code.illumos.org/plugins/gitiles/illumos-gate - illumos/illumos-gate

GitHub

People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is.

There's only one family of operating systems where 'vi' will actually run the original vi program by Joy, Horton, et al.: #Illumos and its derivatives #Tribblix, #OmniOS, and #SmartOS.

*Everyone else* uses one of the ground-up clones.

On #FreeBSD, #OpenBSD, and #NetBSD, it's Bostic's early 1990s #nvi, which was derived from Kirkendall's elvis, a clone written some time around 1990.

On Linux-based operating systems, vi either is Bostic nvi, or is one of the derivatives of STEVIE (the middle-1980s vi clone for the Atari ST that inspired Kirkendall to write elvis in the first place): Moolenaar's VIM or NeoVIM.

On none of those will you get original Joy+Horton vi in base, or indeed packaged/in ports.

Yes, Heirloom vi exists, which is Ritter's 2002 fork of 1985 Joy+Horton vi. But it's not even available in Arch Linux nowadays.

#vi #retrocomputing #ComputerHistory

This is a clever use of secmodel+kauth to implement jail-like process isolation on #netbsd

https://www.petermann-digital.de/blog/netbsd-secmodel_jail/

Zwischen chroot und Xen: pragmatische Prozess-Isolation auf NetBSD

Ein technischer Deep-Dive in jailctl, secmodel_jail und jailmgr: wie NetBSD Prozessisolation ohne UID-Mapping und mit klarer Architektur umsetzt.

Amazingly, there appears to be a Rust compiler available on #NetBSD #riscv. I guess I will see tomorrow, once we have spent the night compiling LLVM.

PSA

Your "old" computer is probably NOT EWaste.

Especially not, if the provider of your commercial OS or other paid service says so.

#E_Waste_Conoisseur

#FreeBSD #OpenBSD #NetBSD #Linux #HAIKU_OS #HaikuOS

System Administration: Week 3: Files go hier(7)

In this video, we're wrapping up our discussion of filesystems and partitions with a look at file types and partitions and filesystems mounted by default on #NetBSD, #FreeBSD, #OmniOS, and Fedora Linux. We close with a look at the filesystem hierarchy as defined in the hier(7) manual page.

https://youtu.be/J0ontdqxpUg

#sysadmin #devops #sre

CS615 System Administration, Week 03, Segment 4 - Files go hier(7)

YouTube
Why run containers when we have microVMs? For example: " New MICROVM kernel for x86, supporting both i386 and amd64, NetBSD 11.0 introduces a dedicated MICROVM kernel designed for extremely fast virtual machines boot, leveraging PVH boot, VirtIO MMIO, and multiple kernel optimizations, it can boot in about 10 ms on 2020-era x86 CPUs." https://netbsd.org/releases/formal-11/NetBSD-11.0.html
#NetBSD #docker #podman
Announcing NetBSD 11.0 RC1 (february 6, 2026)

@thedarkener
Any reason you went specifically with #NetBSD?