May 31, 2024
Many strategies can be employed to build resilience in IT systems.
Personally, I think one of the most critical yet overlooked ones - both in personal and corporate settings - is backups.
I recently had to back up a folder containing the state of a service running on a Fedora machine.
As often happens, an interesting aspect of this service is that the backups are consistent and, therefore, restorable only if the service is stopped while the configuration folder is backed up.
Due to the design of this host, I wanted to use Systemd as the backup driver and keep it as simple and obvious as possible.
Read More 
December 31, 2023
Since the merge of Quadlet in Podman, I’ve been moving multiple services to Podman Systemd services.
I find them to be easy to create, manage, and automate.
I recently migrated a complex system to Podman Systemd, where multiple processes write in a folder, and one process reads the folder’s content.
Before the migration, everything worked properly since all the processes were running natively on the machine with the same user.
After the migration, there were some permissions issues.
This issue allowed me to dive a little more deeply into the whole implementation of SELinux for containers and realize a few interesting things.
Read More 
May 17, 2023
Until a few months ago, the only option to start containers from Systemd was to create a Systemd unit which called podman (or docker) with the run sub-command.
Podman was also providing podman generate systemd to easily create such Systemd file.
This has now changed.
From version 4.4 of Podman, in addition to the mentioned method, it is possible to use Quadlet to simplify the execution of containers from Systemd.
Quadlet allows you to create additional kinds of Systemd units to manage your container needs:
Read More 
April 15, 2020
Yesterday, a controversial proposal got posted in the Fedora Devel mailing list: enable systemd-resolved by default.
I see this change favorably since I already enabled it a few weeks ago, and I find it a very sensible option.
First, I have to admit that I see systemd and its mission of standardizing the core of the Linux user-space very favorably.
At the current level of evolution of Linux, over time, this standardization and consistency will pay off much more than other alternatives.
Therefore, I see the introduction of systemd-resolved positively and as an excellent way to abstract many DNS-related problems the rest of the applications.
Read More 
February 14, 2014
The Debian Technical Committee questioned which direction they should go concerning which PID1 to use in the last couple of weeks.
Ian Jackson, former Debian Project Leader and currently standing in the Debian Technical Committee, asked to vote on the 5th of February on the matter.
Against Ian’s preference, the result of the vote is that Debian will use systemd as the default PID1.
The result is a very narrow one since it was 4:4 with Upstart.
The victory for systemd happened thanks to the tie-breaking vote of the Technical Committee chair, Bdale Garbee.
Read More 
(Fabio Alessandro Locati|Fale)'s blog