Upstream software project

smc-tools

Shared Memory Communication Tools

About smc-tools

Shared Memory Communication Tools

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

smc-tools repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.smc-tools: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
smc-tools
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
EPL-1.0
Source repository
Open source repository

Source-reported description

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

The Shared Memory Communication Tools (smc-tools) package enables usage of SMC sockets in Linux.

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.

Fedora 43

  1. Package smc-tools

    43 (Fedora 43) (Unspecified): Shared Memory Communication Tools

    1.8.5-2.fc43: aarch64 i686 x86_64

    Source: smc-tools

Fedora 44

  1. Package smc-tools

    44 (Fedora 44) (Unspecified): Shared Memory Communication Tools

    1.8.6-2.fc44: aarch64 i686 x86_64

    Source: smc-tools

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.