Beta v8.22.1 #6628
Merged
Beta v8.22.1 #6628
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- RPi | Align own raspberrypi-sys-mods with recent upstream commit: RPi-Distro/raspberrypi-sys-mods#79
- DietPi-Installer | Skip entropy daemon on all devices but those with old kernel, as recent Linux versions use hardware random generators on their own as well as use HAVEGE-like algorithm if required. Tested on various devices with Linux 6.x.y as well as Debian Bullseye VM with Linux 5.10.191: RPi-Distro/raspberrypi-sys-mods#77
- Bookworm | Resolved an issue where poweroff/reboot/halt commands did throw errors about missing dbus or logind. DietPi ships without dbus and with logind masked by default, as we do not see their features being used on a typical DietPi system. Instead, dbus is installed and logind unmasked on demand on certain software installs or when chosen via dietpi.txt. However, the newer systemd version since Bookworm attempts dbus > logind communication in any case when calling poweroff/reboot/halt, despite no wall message being sent, e.g. to handle shutdown inhibitors (like open SSH session being able to prevent shutdown), and throws errors if either dbus is not reachable or logind not running. Until in case dbus or logind are further tied into common system commands or features, we solved the issue by creating shell functions for poweroff/reboot/halt which call the respective systemd target directly to bypass logind (and hence dbus), but fall back to the original commands, depending on given command-line parameters.
- CHANGELOG | Images: Most of our images, those with do not ship with a very old Linux version, have no entropy daemon pre-installed anymore. Either rngd or haveged were required previously to assure that the system entropy pool remained sufficiently filled, otherwise boot, service starts, cryptography tasks or anything using random character from /dev/random could have hung. Recent Linux versions however fill the entropy pool from hardware random generators sufficiently by themselves, and have a HAVEGE-like fallback as well if no hardware random generator is available.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Beta v8.22.1
(2023-09-18)
Enhancements since v8.22.0
rngdorhavegedwere required previously to assure that the system entropy pool remained sufficiently filled, otherwise boot, service starts, cryptography tasks or anything using random character from/dev/randomcould have hung. Recent Linux versions however fill the entropy pool from hardware random generators sufficiently by themselves, and have a HAVEGE-like fallback as well if no hardware random generator is available.Bug fixes since v8.22.0
poweroff/reboot/haltcommands did throw errors about missingdbusorlogind. DietPi ships withoutdbusand withlogindmasked by default, as we do not see their features being used on a typical DietPi system. Instead,dbusis installed andlogindunmasked on demand on certain software installs or when chosen viadietpi.txt. However, the newer systemd version since Bookworm attemptsdbus>logindcommunication in any case when callingpoweroff/reboot/halt, despite no wall message being sent, e.g. to handle shutdown inhibitors (like open SSH session being able to prevent shutdown), and throws errors if eitherdbusis not reachable orlogindnot running. Until in casedbusorlogindare further tied into common system commands or features, we solved the issue by creating shell functions forpoweroff/reboot/haltwhich call the respective systemd target directly to bypasslogind(and hencedbus), but fall back to the original commands, depending on given command-line parameters.