Rocky Linux Documentation

To ensure new documentation renders correctly before publication, developers can preview it in a local environment. Rocky Linux documentation is written in Markdown and converted to HTML using MkDocs, a Python-based static site generator.

To avoid conflicts between documentation dependencies and the host system's Python modules, this guide recommends using the Python venv module (available in Python 3.6+) to create an isolated environment. This method provides isolation without requiring complex containerization systems.

Rocksmarker is an experimental Neovim configuration designed as a specialized IDE for Markdown-based documentation. It is built for technical writers and developers to create structured content, code documentation, and tutorials in a unified environment.

Key features include:

• Real-time Markdown rendering: Visualizing headings, code blocks, and lists directly in the editor.
• LSP-powered intelligence: Robust syntax validation, style enforcement, and code linting.
• Modular plugin management: Uses rocks.nvim for declarative, Lua-driven dependency management via Luarocks.
• Unified workflow: Integrates writing, coding, and formatting into a single interface to eliminate tool switching.

NvChad is a configuration framework for Neovim designed to transform it from a basic text editor into a fully functional Integrated Development Environment (IDE). It uses Lua for configuration and employs Lazy loading techniques to ensure high performance and fast startup times.

Key features include:

• Speed: Optimized through Lua and lazy loading.
• Modern UI: A clean, attractive command-line interface.
• Extensibility: Designed as a base for users to build their own IDE via plugins.
• Automatic Updates: Uses Git to allow quick updates via the :NvChadUpdate command.
• Theming: Includes numerous built-in themes, switchable using the <leader> + th key combination.

GNU/Linux distributions are highly versatile and excel in several domains:

• Servers: Hosting HTTP, mail, groupware, and file sharing.
• Security: Acting as gateways, firewalls, routers, or proxies.
• Mainframes/Critical Infrastructure: Used in banking, insurance, and industrial sectors.
• Embedded Systems: Powering routers, Internet boxes, and SmartTVs.

DNF is the default package manager for Rocky Linux. It manages RPM packages by comparing installed software against defined repositories and automatically resolving dependencies. It is the successor to YUM and is functionally similar for most common commands.

Common tasks include installing, removing, searching, and inspecting packages using the dnf command.

dnf [install|remove|list|search|info] package_name

The System.map file is a lookup table that maps kernel symbol names to their corresponding hexadecimal addresses.

Use Case: When the kernel encounters a critical error (often called an "Oops", similar to a Windows BSOD), it generates error messages containing hexadecimal numbers. System.map allows the system (and developers) to translate these hex addresses into human-readable function names, which is essential for debugging kernel bugs or hardware issues.

EPEL (Extra Packages for Enterprise Linux) is a free, community-managed repository that provides software packages from Fedora sources for RHEL-based distributions like Rocky Linux.

Important Support Note: EPEL packages do not receive official support from RHEL. While they are widely used, their availability is tied to the Fedora development lifecycle; there is a remote possibility that packages could disappear if they are not maintained as Fedora evolves.

RPM (Red Hat Package Manager) is the software management system used by Rocky Linux and other Red Hat-based distributions (such as Fedora and CentOS). It is used to install, uninstall, update, or query software.

Key distinctions in terminology:

• RPM (capitalized): Refers to the package management system.
• rpm (lowercase): Refers specifically to the rpm command-line tool.
• .rpm: Refers to the file format suffix used for the packages themselves.

NFS (Network File System) allows sharing files and directories across a network between Linux systems (and Windows systems with appropriate software).

NFS operates on a client-server model:

• Server side: The system that exports (shares) the file systems.
• Client side: The systems that access the exported file systems.

NFSv4 requires the following daemons to function:

• portmap: Maps RPC programs to standard network ports.
• mountd: Manages incoming mount requests.
• nfsd: The primary NFS program that handles actual file transfers.