ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #almalinux
Goal The objective is to validate the behavior of the AlmaLinux-Deploy migration tool in a non‑production environment, ensuring that critical security configurations are preserved without exposing real credentials. Constraints Because the test system lacks valid Red Hat subscription data, the migration must rely solely on community repositories and local pol
Context AlmaLinux 9 manages languages, databases, and tools through modular streams in the AppStream repository, each with a published end-of-life date. When a stream expires, dnf automatically switches to the default stream for that module, which can also change between minor releases such as 9.2 and 9.3. Problem In a pinned development environment—containe
<p>Apache HTTPD UserDir on AlmaLinux 9 should serve requests to "~/public_html" while SELinux remains in enforcing mode under the targeted policy.</p> <p>The "httpd_read_user_content" boolean governs whether httpd can read content labeled "user_home_t", but it applies globally and is not tied to individual "VirtualHost" or "UserDir" directi
AlmaLinux 8 glibc 2.34 Compatibility Limits Many applications today depend on glibc 2.34, but AlmaLinux 8 ships with glibc 2.32. After the distribution’s official end‑of‑life on 31 December 2024, the AlmaLinux team has no plans to deliver security or bug‑fix updates for the platform, and the upstream RHEL 8 support cycle ended in June 2024. This creates a ga
Background AlmaLinux 8 and 9 ship SSSD 2.8.x as the default service for centralized authentication against LDAP, Active Directory, or FreeIPA. SSSD caches password hashes locally to support offline login; the cache lifetime is governed by offline_credentials_expiration (default 0, meaning unlimited). When a user's password expires in the backend directory, S
Context AlmaLinux 9 ships dnf module streams for language runtimes such as Node.js, Python, and Go, allowing version selection via dnf module install nodejs:18 . Switching streams requires dnf module reset followed by dnf module enable , a non‑transactional sequence that can leave orphaned packages or unresolved dependencies. The AlmaLinux Build System publi
AlmaLinux 9 fully deprecates the legacy network-scripts package, shifting network management from shell scripts in /etc/sysconfig/network-scripts/ to INI-based keyfiles located in /etc/NetworkManager/system-connections/ . While nmcli serves as the primary interface for modern configurations, legacy environments relying on custom routing logic or ifup command
Snapshot Restoration and Integrity AlmaLinux 9 supports the Btrfs filesystem, enabling the use of btrfs send and btrfs receive for incremental backups and snapshot restoration. While these tools facilitate the movement of subvolumes between disks or hosts, the restoration process focuses on the transfer of data blocks rather than an integrated verification o
Goal I want a reliable way to detect, before patching or provisioning, whether any enabled AppStream module stream on an AlmaLinux 9 system has passed its end-of-life date, so I can plan a stream switch before security updates stop. Constraints and uncertainty From what I understand, only one stream per module can be enabled at a time, and an EOL stream rema
podman