Upstream software project

fhs

Filesystem Hierarchy Standard

About fhs

Filesystem Hierarchy Standard

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.fhs: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
fhs
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
SUSE-FHS
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support application interoperability, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package fhs

    leap-15.6 (openSUSE Leap 15.6) (Documentation/Other): Filesystem Hierarchy Standard

    3.0-bp156.1.1: noarch

    Source: fhs

openSUSE Tumbleweed

  1. Package fhs

    tumbleweed (openSUSE Tumbleweed) (Documentation/Other): Filesystem Hierarchy Standard

    3.0-1.13: noarch

    Source: fhs

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.