Upstream software project

picocom

Minimal dumb-terminal emulation program

About picocom

Minimal dumb-terminal emulation program

This project links 10 native package records across 6 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

Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.picocom: recorded package coverageAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
picocom
Publisher
Not authoritatively mapped
Native package records
10
Operating systems
alpine-linux-3-22, alpine-linux-3-23, fedora-43, fedora-44, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Source repository
Not reported

Source-reported description

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

As its name suggests, [picocom] is a minimal dumb-terminal emulation program. It is, in principle, very much like minicom, only it's "pico" instead of "mini"! It was designed to serve as a simple, manual, modem configuration, testing, and debugging tool. It has also served (quite well) as a low-tech "terminal-window" to allow operator intervention in PPP connection scripts (something like the ms-windows "open terminal window before / after dialing" feature). It could also prove useful in many other similar tasks. It is ideal for embedded systems since its memory footprint is minimal (less than 20K, when stripped).

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.

Alpine Linux 3.22

  1. Package picocom

    v3.22 (Alpine Linux 3.22): Minimal dumb-terminal emulation program

    2024.07-r0: aarch64 x86_64

    Source: picocom

  2. Package picocom-doc

    v3.22 (Alpine Linux 3.22): Minimal dumb-terminal emulation program (documentation)

    2024.07-r0: aarch64 x86_64

    Source: picocom

Alpine Linux 3.23

  1. Package picocom

    v3.23 (Alpine Linux 3.23): Minimal dumb-terminal emulation program

    2024.07-r0: aarch64 x86_64

    Source: picocom

  2. Package picocom-doc

    v3.23 (Alpine Linux 3.23): Minimal dumb-terminal emulation program (documentation)

    2024.07-r0: aarch64 x86_64

    Source: picocom

Fedora 43

  1. Package picocom

    43 (Fedora 43) (Unspecified): Minimal serial communications program

    2024.07-4.fc43: aarch64 x86_64

    Source: picocom

Fedora 44

  1. Package picocom

    44 (Fedora 44) (Unspecified): Minimal serial communications program

    2024.07-5.fc44: aarch64 x86_64

    Source: picocom

openSUSE Leap 16.0

  1. Package picocom

    leap-16.0 (openSUSE Leap 16.0) (Hardware/Modem): Minimal dumb-terminal emulation program

    2024.07-bp160.1.3: aarch64 ppc64le s390x x86_64

    Source: picocom

  2. Package picocom-bash-completion

    leap-16.0 (openSUSE Leap 16.0) (Hardware/Modem): Bash Completion for picocom

    2024.07-bp160.1.3: noarch

    Source: picocom

openSUSE Tumbleweed

  1. Package picocom

    tumbleweed (openSUSE Tumbleweed) (Hardware/Modem): Minimal dumb-terminal emulation program

    2024.07-1.6: x86_64

    Source: picocom

  2. Package picocom-bash-completion

    tumbleweed (openSUSE Tumbleweed) (Hardware/Modem): Bash Completion for picocom

    2024.07-1.6: noarch

    Source: picocom

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.