systemd

2️⃣1️⃣ Here's the 21st post highlighting key new features of the recently released v259 release of systemd. #systemd259 #systemd

In episode 16 we already talked about systemd-firstboot, systemd's little configuration console tool that can run on first boot and ask the user for a few simple basic questions regarding keymap or locale or such.

With v259 it received a small facelift of a kind. First of all, we'll now turn off concurrent log output from the kernel and from PID 1…

2️⃣0️⃣ Here's the 20th post highlighting key new features of the recently released v259 release of systemd. #systemd259 #systemd

systemd's unit ordering dependencies implement a directed graph, which is supposed to be acyclic, i.e. contain no cycles, so that it's always clear which units to activate before which other units.

But given that units are typically written by humans, the graph quite often actually does have cycles, and if that happens systemd has to break them somehow, …

2️⃣2️⃣ Here's the 22nd post highlighting key new features of the recently released v259 release of systemd. #systemd259 #systemd

In v258 systemd-nspawn gained support for running unpriviled containers from directories owned by the "foreign" UID range. To get container images owned by that you had to manually chown() the images (recursively), for example via systemd-dissect --shift. And while the systemd-nspawn invocation is not privileged, that re-chown()-ing definitely has requires privileges.

2️⃣3️⃣ Here's the 23rd post highlighting key new features of the recently released v259 release of systemd. #systemd259 #systemd

As you probably know sysemd-udevd processes notification events received from the kernel ("uevents") with a set of rules that match properties, set properties and execute code. Debugging these can be a bit annoying, since – of course – these notifications are typically result of hardware events, and hence attempts to correctly reproduce any issues in a controlled…

2️⃣ Here's the 2nd post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

systemd is adopting the IPC system in more and more places. One nice thing about Varlink is that it is conceptually close to HTTP, in its request/response semantics. This is on purpose to make bridging the web world and the low-level system world easy.

@michaelvogt has beeing working on a Varlink/HTTP bridge in Rust, with various bells and whistles, including…

3️⃣ Here's the 3rd post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

In the previous episode we talked about the Varlink/HTTP bridge and the protocol plugins for sd-varlink/varlinkctl. Closely related to this is another new addition in v260: the special /run/varlink/registry/ directory, where any "well-known" varlink services can symlink their sockets into.

Right now, systemd's various Varlink sockets are bound in a variety of service-specific…

5️⃣ Here's the 5th post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

One of the fundamental operations one can execute on a systemd service is "reload", i.e. asking the service to reload its configuration, for example via "systemctl reload foobar.service". What precisely this triggers in the service code, is up to the developers to decide, but the assumption is that it rescans and parses its configuration files, without any interruptions…

4️⃣ Here's the 4th post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

When running code from OS trees, for example in containers, or when booting a full OS in a VM or on bare-metal it's often very useful to put together the basic OS from multiple overlayfs-style layers (directory-backed or backed by DDIs), plus some additional bind mounts, and possibly a tmpfs or two mounted to the right places to get ephemeral or partially ephemeral behaviour.

RE: https://mastodon.social/@amutable/115967747219090945

Today, we announce Amutable, our ✨ new ✨ company. We – @blixtra, @brauner, @davidstrauss, @rodrigo_rata, @michaelvogt, @pothos, @zbyszek, @daandemeyer, @cyphar, @jrocha and yours truly – are building the 🚀 next generation of Linux systems, with integrity, determinism, and verification – every step of the way.

→ https://amutable.com/blog/introducing-amutable ←

#amutable #linux #systemd #⊼mutable #integrity

From Debian Unstable changelog:

systemd-resolved is going away!

#Debian #linux #systemd

ALT

as an xorg-bro: what made worse impact on linux?

#linux #systemd #wayland #bsd

#FOSS is all about options:
- I chose not to use #RedHat systems 28 years ago.
- I chose not te use #GNOME 15 years ago
- I chose not to use #SystemD 6 years ago.
- I choose to accelerate the migration of all the #Linux based systems I can to #BSD systems because:
- I choose to keep up with the #UNIX way
- I choose to use stable systems which don't change for the sake of change
- I choose to be part of healthier communities, that don't promote monoculture or fall so easily into arrogance