DEWOLF.IT / TECHNICAL KNOWLEDGE BASE

Enterprise Linux from an operations perspective.

Practical guidance for Linux administrators, platform engineers and teams working with Red Hat Enterprise Linux. From a RHEL migration to a failing service, start with evidence and verify the outcome.

From a problem to an evidence-based solution

This knowledge base connects diagnosis, configuration and enterprise constraints. The articles help you interpret measurements, limit the scope of changes and verify whether a solution works. Examples are generic and contain no customer information.

Choose the topic that matches your question. Each article provides context, practical steps, commands or configuration examples, common pitfalls and links to related guidance.

Topics for manageable Linux platforms

AI and enterprise vulnerability management

AI can discover more vulnerabilities, leaving more findings to review. It can also help teams relate scanner data, vendor information, exploit context and asset criticality as part of a manageable vulnerability workflow.

Read the article →

When df and du disagree because a deleted ISO is still mounted

When df reports hundreds of megabytes in use and du finds almost nothing, the cause can lie outside the visible directory structure. This case follows the diagnosis of a deleted ISO that remained mounted and continued to hold disk blocks.

Read the article →

RHEL 8 to 9 with Leapp

A RHEL 8 to 9 migration starts with a supported upgrade path and a tested recovery plan. Leapp helps with the technical transition. The migration design also needs to account for application compatibility, software content and acceptance.

Read the article →

Controlled patch management with Red Hat Satellite content views

Satellite patch management relies on reproducible content. Content views and lifecycle environments allow you to promote the same tested package set to production in a controlled way.

Read the article →

Idempotent RHEL management with Ansible

Reliable Ansible management defines the intended state and makes deviations visible. Playbooks need to be repeatable, report accurately and stop dependent work when a step fails.

Read the article →

Diagnosing SELinux AVC denials

An AVC denial tells you which action SELinux blocked. Match the process domain, target type and requested permission to the intended service behaviour to identify an appropriate fix.

Read the article →

Diagnosing systemd services and restart loops

A failed unit is the start of the diagnosis. The problem might be in the application, service account, mount, unit configuration or dependency. Gather evidence first to decide whether a restart will help.

Read the article →

Rootless Podman, Quadlet and Docker migration

Rootless Podman and Quadlet let you manage containers under a dedicated account with systemd. A Docker migration needs to account for storage, networking, permissions and the lifetime of the user session.

Read the article →

Systematic Linux performance diagnosis

A useful performance investigation starts with the slow operation and the time it occurred. CPU, memory and storage are possible causes. Read measurements together to find the component that limits performance.

Read the article →

Enterprise Linux operations with tmpfiles, journald, NFS and versionlock

A temporary directory, journal limit, Kerberos ticket or package lock can affect an application without a change to its configuration. This guide shows how to define and verify the policies behind them.

Read the article →

A route through the knowledge base

Preparing a change? Start with RHEL lifecycle and migration, establish the content chain in Satellite and capture repeatable steps in Ansible.

Investigating an incident? Build a timeline with systemd and journald. Then check SELinux or performance where the errors and measurements point.

Designing an operating standard? Combine the Podman guide with policies for temporary files, logging, NFS and package versions. Record who approves changes and how the team detects drift.

Use the examples in context

Applicability depends on the release, architecture, security policy and application dependencies. Each article describes its scope and links to official sources. Read the validation and recovery steps before making a change.

Need help with implementation? See Linux Consultancy, Red Hat Enterprise Linux, Automation & Ansible and Migration & Lifecycle.