1️⃣4️⃣ Here's the 14th post highlighting key new features of the upcoming v261 release of systemd. #systemd261 #systemd
When running a data center one typically has two conflicting goals: on one hand payloads should have maximum uptime, and not be interrupted in service if at all possible, on the other hand software should be updated quickly whenever security vulnerabilities become public. Security updates mean service interruptions, but those you do not want.
Updating an OS comprehensively…
1️⃣6️⃣ Here's the 16th post highlighting key new features of the upcoming v261 release of systemd. #systemd261 #systemd
/etc/hosts is a really powerful concept: it allows assigning a hostname to addresses in a local fashion, without having to ask anyone. But it's also a very old and basic concept: these days we are accustomed to drop-in configuration files (i.e. in an /etc/hosts.d/* sense), and DNS RRs exist, hence a bit more expressiveness than just the equivalent of A/AAAA/PTR would be great.
1️⃣5️⃣ Here's the 15th post highlighting key new features of the upcoming v261 release of systemd. #systemd261 #systemd
In a previous episode of this series we already talked a lot about installing operating systems, and the new features systemd v261 brings for that. There's one more item in this area I'd like to talk about:
You know systemd-repart is that dynamic partitioner that can also be used for building disk images and as an installer for image-based operating systems. In the latter…
1️⃣3️⃣ Here's the 13th post highlighting key new features of the upcoming v261 release of systemd. #systemd261 #systemd
In the first episode of this series for v261 we discussed the new El-Torito/CD-ROM support in systemd-repart. As a reminder, the main problem with having a unified image that boots from both regular disks and CD-ROMs is the different sector sizes: regular disks typically use 512 byte sectors, CD-ROMs use 2048 byte sectors. The sector size dictates where…
2️⃣6️⃣ Here's the 26th post highlighting key new features of the recently released v261 release of systemd. #systemd261 #systemd
When dealing with VMs, you have to think about dealing with storage, too: how do you connect your block devices and file systems to your VMs.
For a while now systemd has been shipping systemd-vmspawn, a small wrapper around qemu, which integrates it in various ways into the system, for example registers it with systemd-machined and a variety of other things.
2️⃣7️⃣ Here's the 27th post highlighting key new features of the recently released v261 release of systemd. #systemd261 #systemd
systemd-oomd is systemd's subsystem for optimizing system behaviour under memory pressure (i.e. shut down services to remedy memory pressure and similar). So far it has been applying very similar policies for dealing with pressure on all workload services on the system.
With v261 we are extending the concepts around this considerably. systemd-oomd can now read a number…
2️⃣5️⃣ Here's the 25th post highlighting key new features of the recently released v261 release of systemd. #systemd261 #systemd
The systemd-socket-proxy tool has been part of the systemd toolset for a long long time, but is probably not known by many. It was originally created to add "fake" socket activation support to daemons that do not support it natively: the tool implements the socket activation, can be wrapped in appropriate socket activation unit files, and when activated…
It's that time again! The systemd v262 release is coming closer. Let's restart the "what's new" series of posts for this iteration! Hence:
1️⃣ Here's the 1st post highlighting key new features of the upcoming v262 release of systemd. #systemd262 #systemd
Back in systemd v258 we added support for a special "?" character in /etc/hostname.
5️⃣ Here's the 5th post highlighting key new features of the upcoming v262 release of systemd. #systemd262 #systemd
systemd-sysupdate is a tool for updating files and partitions from a source typically on the Internet, to implement OS updates or updates of container, VM, extension or service images. It's mostly built around the concept of a "transfer" file, that does primarily one thing: it declares where to find new resources on the internet and where to place them locally. The tool then…
6️⃣ Here's the 6th post highlighting key new features of the upcoming v262 release of systemd. #systemd262 #systemd
In systemd v260 we added the "systemd-report" subsystem that provides a unified way to gather metrics from running services, that would like to offer them. Many of systemd's own subsystems implement providers for this now, and the systemd-report tool can compile them into a single report JSON document.
With v262 this functionality is upgraded in one fundamental way:
4️⃣ Here's the 4th post highlighting key new features of the upcoming v262 release of systemd. #systemd262 #systemd
In systemd v261 we introduced the concept of "machine tags", i.e. a set of free-form, user chosen strings you can attach to a host. They are stored in /etc/machine-info along with some other metadata fields about the host.
In v262 the concept is further extended. First of all, the strings may now also have the form "key=value" in addition to simple strings without "=", as…
