From d127a1d4ef39ee9d4989c82b08b5d4abaed2f87e Mon Sep 17 00:00:00 2001 From: Thiago Kenji Okada Date: Thu, 22 Aug 2024 07:33:15 +0100 Subject: [PATCH] poss/2024-08-21/01: paper -> role --- .../01-an-unordered-list-of-hidden-gems-inside-nixos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-08-21/01-an-unordered-list-of-hidden-gems-inside-nixos.md b/posts/2024-08-21/01-an-unordered-list-of-hidden-gems-inside-nixos.md index e66adc5..55a10aa 100644 --- a/posts/2024-08-21/01-an-unordered-list-of-hidden-gems-inside-nixos.md +++ b/posts/2024-08-21/01-an-unordered-list-of-hidden-gems-inside-nixos.md @@ -142,7 +142,7 @@ start init system (`systemd`). It may surprising that this `initrd` image does **not** generally include `systemd`. Traditionally `initrd` is composed by a bunch of shell scripts and a minimal runtime (e.g.: [busybox](https://www.busybox.net/)), however `systemd` -can also do this job since a long time ago. It is just the paper of the distros +can also do this job since a long time ago. It is just the role of the distros to integrate `systemd` inside the `initrd`. This is what `boot.initrd.systemd` does: enable `systemd` inside the `initrd`.