ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
SELinux and LUKS Integration in Rocky Linux 9.x Rocky Linux 9.4 supports LUKS full-disk encryption via systemd-hibernate and cryptsetup, with XFS as the default filesystem and ext4 on /boot for bootloader compatibility. SELinux enforces mandatory access controls beyond traditional Unix permissions, but the interaction between encrypted volume mounting and SE
Rocky Linux ships DNF (DNF4 on releases 8 and 9) with per-repository metadata cached on disk, and that cache can go stale relative to mirror content. The symptom pattern needing diagnosis: package lookups or downloads can fail with HTTP 404 errors or metadata download failures when cached repomd or primary data still references package files or checksums a m
Goal Ensure that critical services in a Rocky Linux system only start once the network stack is fully operational, preventing repeated failures that appear in journalctl and systemctl status. Constraint NetworkManager controls IP assignment, but its “wait‑online” feature is optional. Without it, units that declare After=network-online.target may start before
On a Rocky Linux server, firewalld is enabled by default with the public zone, which permits only a small set of services such as ssh and dhcpv6-client . The goal is to make sure that services installed later are never reachable externally unless deliberately allowed, while keeping remote administration access intact. The uncertainty is which strategy the de
For Rocky Linux hosts that must recover quickly after a failed update while still supporting occasional ad-hoc local RPMs, the documented update models present a trade-off. Traditional DNF transactions allow per-package installs and third-party RPMs built for the matching RHEL minor release, but dnf history rollback does not reliably restore a prior kernel,
Implementing a low-noise alerting system on Rocky Linux 9 requires a specific configuration of dnf-automatic to ensure that only critical security patches trigger notifications, rather than every available package update. The goal is to utilize the upgrade_type = security setting within /etc/dnf/automatic.conf while maintaining apply_updates = no to prevent
DNF Module Stream Consistency Rocky Linux 8 and 9 utilize AppStream modules to provide multiple versions of the same software package. While these distributions target binary compatibility with RHEL, the default module streams may vary between minor releases or differ when transitioning from version 8 to 9. When automating deployments across these versions,
rockylinux