fhs-lsb-uid-gid

Interpret FHS 3.0, LSB 5.0, and systemd UID/GID ranges for UMRS deployments.

Updated Dec 4, 2025

Search Tags:#uid #filesystem #systemd #lsb #gid #fhs #umrs

Ready to run

npx skills add https://github.com/jamieadams-nerd/umrs-project --skill fhs-lsb-uid-gid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fhs-lsb-uid-gid
Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/skills/fhs-lsb-uid-gid
Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill fhs-lsb-uid-gid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UMRS filesystem and account decisions often suffer from misapplied FHS 3.0, LSB 5.0 UID/GID allocations, and systemd UID/GID conventions. This Skill consolidates authoritative references and UMRS-specific ranges to guide path choices, user creation, and configuration placements such as /opt/umrs, /etc/keys/umrs, and /var/opt/umrs.

Core Features & Use Cases

Centralized data from FHS 3.0, systemd UID/GID, LSB 5.0, and RHEL 10 login.defs to drive compliant UMRS deployments.
Use Case: When planning filesystem hierarchy or system accounts, reference UID_MIN/MAX, GID ranges, and conventional path layouts to ensure predictable, auditable decisions.

Quick Start

Consult this skill when planning UMRS filesystem paths and UID/GID allocations to ensure FHS/LSB compliance.

Frequently Asked Questions about fhs-lsb-uid-gid

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I ensure FHS 3.0 and LSB 5.0 compliance when allocating UID and GID ranges?▼

To ensure FHS 3.0 and LSB 5.0 compliance for UID and GID allocation, reference centralized standards data alongside RHEL 10 login.defs to enforce deterministic, policy-aligned system account creation decisions.

What filesystem paths should I use for UMRS deployments on RHEL?▼

For UMRS deployments, use conventional filesystem paths like /opt/umrs, /etc/keys/umrs, and /var/opt/umrs to align with FHS 3.0 hierarchy standards and ensure predictable configuration placements.

How do systemd UID and GID conventions affect system account creation?▼

Systemd UID and GID conventions affect system account creation by defining specific reserved ranges, which must be cross-referenced with LSB 5.0 allocations to avoid conflicts and maintain auditable deployments.

Can I use standard login.defs settings to manage UMRS user accounts?▼

Yes, you can use RHEL 10 login.defs settings to manage UMRS user accounts by validating UID_MIN and GID ranges against systemd and LSB conventions before finalizing filesystem path planning.

What are the limitations of relying solely on LSB 5.0 for UID and GID allocation?▼

Relying solely on LSB 5.0 for UID and GID allocation ignores systemd-specific conventions and RHEL 10 login.defs parameters, risking non-compliant system accounts and unpredictable filesystem path conflicts.

When do I need to consult FHS and LSB standards for filesystem planning?▼

You need to consult FHS and LSB standards for filesystem planning whenever you are defining UMRS directory structures or creating system accounts to guarantee deterministic, auditable configuration choices.