Installer lcdproc avec Homebrew, apk, apt, dnf, Nix, pacman

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• LCDd
• fortune.pl
• iosock.pl
• lcdexec
• lcdident.pl
• lcdmetar.pl
• lcdproc
• lcdvc
• tail.pl
• x11amp.pl

Historique du projet

The project README says LCDproc was originally written by William Ferrell and Selene Scriven. The credits file describes Ferrell as the project founder and author of the first versions, and Scriven as the main programmer for versions 0.2 through 0.4-pre9, turning the original small single-system utility into the recognizable LCDproc form.

LCDproc's early site history page was active by 2002, and its changelog shows the long 0.5 series adding and maintaining drivers for HD44780-style displays, serial devices, USB devices, graphical displays, Raspberry Pi and other embedded connections, curses and X11 output, and remote-control input.

Historique d'adoption

LCDproc spread through Linux and BSD hobbyist, server, HTPC, and embedded installations where small front-panel displays were useful for CPU load, uptime, network state, media-center status, or appliance feedback. Its README emphasizes that the client and server communicate over TCP, so the machine producing data and the machine connected to the display do not need to be the same host.

Package-manager adoption across Homebrew, Debian, Ubuntu, Fedora, Arch, Nix, and Alpine reflects its status as old-school system hardware glue: not glamorous, but reusable enough that distributions keep shipping both the daemon and example clients.

Modes d'utilisation

Typical deployments configure `LCDd.conf` for the display driver and connection type, run the `LCDd` daemon, then start clients such as `lcdproc`, `lcdexec`, or custom scripts that send screens and widgets to the daemon.

Pourquoi les passionnés de paquets s'y intéressent

LCDproc matters to package nerds because it is a classic hardware-support package: a daemon, many optional drivers, sample config files, init/service integration, and decades of compatibility work for devices that may only exist on one appliance or front panel.

It also shows why packaging hardware tools is messy: the same package can be a server daemon, a set of client utilities, Perl examples, config templates, and driver support for serial, parallel, USB, GPIO, I2C, framebuffer, curses, and X11 targets.

Chronologie

• 1998: README copyright range begins with the first LCDproc era.
• 2002-10-14: Official site history page recorded LCDproc website development by project developers.
• 2016: README described a migration from SourceForge to GitHub.
• 2017-05-27: v0.5.8 release tag published on GitHub.
• 2019-02-10: v0.5.9 release tag published on GitHub.

Related projects

• Related hardware and software include Matrix Orbital and Crystalfontz displays, HD44780-compatible controllers, LIRC/IR input, curses, X11 display output, Raspberry Pi GPIO and I2C display adapters, and monitoring clients that feed status text to `LCDd`.

Sources

• https://api.github.com/repos/lcdproc/lcdproc/tags?per_page=100
• https://github.com/lcdproc/lcdproc
• https://raw.githubusercontent.com/lcdproc/lcdproc/master/CREDITS.md
• https://raw.githubusercontent.com/lcdproc/lcdproc/master/ChangeLog.md
• https://raw.githubusercontent.com/lcdproc/lcdproc/master/README.md
• https://www.lcdproc.org/
• https://www.lcdproc.org/history.php3