Building a new FreeBSD poudriere jail, sometimes runs into the following error:
awk: can't open file /usr/local/poudriere/jails/aarch64/usr/include/sys/param.h
source line number 1
This is a bug in poudriere-devel-3.3.99.20210907_1 and it is fixed in
main already but not in a package yet.
Update: New package has been published with the fix.
Vault works well on FreeBSD, but there are a couple of quirks to be aware of. This guide will help take care of those.
Follow the normal install method:
pkg install vault
Using vault in a jail requires the option allow.mlock to be set.
Using ezjail and a jail called vault just modify the config file
/usr/local/etc/ezjail/vault on the host and set:
To make it easier to upgrade the various Raspberry Pis that are around, lets PXE boot them so they can be upgraded easily.
In this article we will use the following tools to create a shared base system and then individual mounts for each RPi:
To make cable management easier, each Raspberry Pi is connected to a PoE switch using one of these Adafruit PoE Splitter. Using PoE for power also has the additinal benefit of each Rasperry Pi being powered by the UPS that the switch is connected to.
Setting up FreeBSD to run cloudinit to make custom images is pretty easy.
The first step is to boot a basic image or the install ISO and install FreeBSD. Once it is up and running then install cloudinit:
pkg install net/cloud-init
And enable cloudinit:
sysrc cloudinit_enable=YES
Currently there is a bug in cloud-init where it does not try to mount the
correct filesystem with the correct type on FreeBSD.
It tries to use the old outdated vfat type, instead of mosdosfs.
For awhile now I have been meaning to evaluate Nomad and Consul for managing servers as well as batch jobs. It has lots of features that are attractive and would make managing services very easy using the Consul service mesh and health checks. One of the downsides is that it takes some configuration and setup to get it configured for maximum success, with multiple copies of the Nomad Server and Consul Server running in each datacenter. The other side of the coin is other solutions require setting up an external database that will then have to be managed and monitored.
Previously it has not been possible to use the camera module on FreeBSD due to the RPi tools not working on 64-bit architectures. I have recently added a version of the u-boot port for the Raspberry Pi 3 that is built in 32-bit mode.
For the past few years I have been operating a small number of Arduino Ethernets with DHT22 sensors, push data into Graphite. They have worked reasonably well, but had one major issue. Graphite required that the data flow include the Unix Epoch time and the Arduino time counter over flows every ~50 days.
For awhile I have been using a Tarsnap backup script written by Tim Bishop. It is very handy but recently I was setting up Tarsnap again on a new machine and I noticed that it is not designed to be run more frequently than daily. So I decided to take a stab at making it handle being run more often and keeping the number of daily/weekly/monthly backups that are actually desired.
Changing the delete portion to something like this should do the trick:
In the past we had to use the old SysV IPC sysctls and change the UID that each PostgreSQL server ran as under in each Jail. Which was annoying and error prone.
For some reason I could not find any pictures online of the awesome shirt from the EuroBSDCon 2013 DevSummit. So here it is!