I’ve mostly automated the setup of the software for the Life display frame software. You can find the scripts here on GitHub . Running this requires a Linux system with ansible and git installed.
I am running this on a Raspberry Pi ZeroW , but it should work on just about anything running Debian Linux .
This uses the lite version of Raspberry Pi OS without a GUI. You should download the correct one for your hardware, expand the image, and write it to an SD Card:
Last year I wrote about my sdl2-life program, adding color to it, and seeding it with data from my website logs. This time I’ve decided to make a dedicated wall display for it using an Adafruit touchscreen display and a Raspberry Pi Zero that I bought back before they became unobtainable.
After a bunch of experiments with the design I managed to make a display that won’t fall off the wall and it looks reasonably nice.
This is a followup to the qemu with PXE boot post I wrote a few years back. In this post I will cover the creation of a live filesystem using livemedia-creator, and PXE booting it with qemu and UEFI. I am assuming that you have some familiarity with using Anaconda to install Fedora, CentOS, and Red Hat Enterprise Linux. As well as with my previous posts about livemedia-creator .
Building the image with livemedia-creator The creation process is similar to creating live isos but instead of an iso we will create the live root filesystem.
DigiTemp is a simple to use program for reading values from 1-wire devices. Its main use is for reading temperature sensors, but it also reads counters, and understands the 1-wire hubs with devices on different branches of the network.
See the digitemp.com page for more information.
After letting the life server I wrote about last month run for a bit I decided that all white cells are a bit boring and I started exploring ways to add some color to it. First step was to keep track of the age of the cells, and I decided that new cells should inherit the age of the cells that created it in the hope that it would be more visually snazzy.
A few years back I was experimenting with Go and SDL2, I wrote a dead-simple Conway's Game of Life program with it, added loading of a couple popular pattern file formats, and was pretty much finished with it. The other day I came across this cool project while preparing for Thanksgiving by browsing infosec.exchange . Brett has an e-ink display running life and is seeding it from tarpit data which struck me as a really neat idea to keep the world from becoming static as most of the more complex ones tend to do.
Back in 2017 I mentioned that the API I have been using for my Roku Home Media Server project was going to be replaced by SceneGraph and that I would need to rewrite things. That day finally arrived when my newer Roku players updated themselves to v11.5.0 and HMS quit loading.
SceneGraph has lots of documentation, and lots of examples . Most of them are either too simplistic to be useful, or too complex to untangle for someone new to the framework, but experienced with the previous API.
One of the projects that I work on is osbuild-composer . This is an operating system image builder, written in Go, and is the replacement for the lorax-composer project. I’m going to skim over the details since this post is about profiling things, but you can read more about it at osbuild.org and the [GitHub repository].
Behind the scenes it uses DNF to handle depsolving and package queries. A few weeks back I wrote a patch to cache the results from the dnf-json program in order to speed up the response time when listing all the packages (over 63000 of them in Fedora 35!
It has been quite some time since I wrote about one of my longest running projects, MovieLandmarks . The UI hasn’t changed much in the intervening years. But the backend has been rewritten in Go, and the covers now come from TMDB instead of IMDB .
Recently I decided I wanted the map to open to a view of the landmarks related to the move being passed to it using the #mv-XXXX hash.
