David Tardon

I think this is a duplicate of #901.

> When using the `network` module, or any module which depends on it, on an `OpenRC` system the `network` module cannot be installed. > > ``` > dracut: dracut module...

> If you boot with resume off, for one reason or another, you can turn it on later by echoing maj:min into `/sys/power/resume` to get your host to its normal...

> Writing `uninitialized\n` to it, according to https://systemd.io/BUILDING_IMAGES/ I think the first boot semantics makes no sense in initrd, hence `etc/machine-id` should be _empty_ (https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Boot%20Semantics).

> > Seems like this is actually a systemd bug? systemd's system-shutdown > > https://github.com/systemd/systemd/blob/main/src/shutdown/shutdown.c > > should set the `DRACUT_SYSTEMD=1` environment variable because that runs `/run/initramfs/shutdown`? > > This...

> Yes, 8-year old code added by Harald, good old days. So, do you really think that nowadays systemd is willing to add to its code an export of a...

That aside, the main point is if it even makes any sense to export `DRACUT_SYSTEMD` in exitrd. At boot, it signifies that initrd is is started with `systemd` (instead of...

> dracut-lib.sh looks at the DRACUT_SYSTEMD environment variable. For example, the info and warn functions of dracut-lib.sh require a properly set DRACUT_SYSTEMD. Otherwise, the info and warn function do not...

> No output visible in console during shutdown. Because they don't write to kmsg. They do, if DRACUT_SYSTEMD is *unset*. You pasted the code here yourself...

Oops, I've completely forgotten about this one... I'll try to return to it in the next few days.