Installer hesiod avec Homebrew, apt

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• hesinfo

Historique du projet

MIT's Athena Technical Plan lists the Hesiod Name Service section as July 22, 1987, by Steven P. Dyer and Felix S. Hsu. RFC 1035's bibliography references an April 1987 Project Athena Hesiod name-service document and notes that it describes the fundamentals of the Hesiod name service.

The MIT Athena description explains Hesiod as a simple string lookup service on top of DNS: a client combines a name and type into a DNS name such as `name.type.ns.athena.mit.edu`, queries TXT records, and receives one or more result strings.

The maintained GitHub package identifies itself as release 3.2.1 of the Hesiod name service library, says Hesiod can provide general name service for many applications, and notes its basis in the Berkeley Internet Name Daemon. The repository was created on March 28, 2013, preserving the library in a conventional autotools-style source tree.

Historique d'adoption

Hesiod's first adoption context was Project Athena, MIT's distributed workstation environment. MIT's own Athena overview says Athena used Hesiod for user account information, locker information, post office box information, workstation cluster information, and printer information.

The DNS protocol itself records Hesiod's historical footprint: IANA's DNS parameters registry assigns DNS class 4 to Hesiod (HS), citing the Project Athena name-service work. The modern library later moved its wire protocol toward class IN for deployability, but the HS class remains part of DNS history.

In package-manager terms, Hesiod survived as a niche but instructive Unix networking library. It appears in Homebrew, Debian, and Ubuntu not because most sites deploy it broadly, but because old Athena-style environments, compatibility code, and network-service historians still need a maintained implementation.

Modes d'utilisation

The README documents client configuration through `hesiod.conf`, with `rhs` and `lhs` values that build the DNS lookup suffix. It notes `/usr/local/etc/hesiod.conf` as the default sysconfdir path in that build configuration and explains that `HES_DOMAIN` can override the right-hand side at run time.

Administrators publish Hesiod data by making name servers authoritative for a domain such as `ns.your.domain` and adding TXT and CNAME records for data types like groups, service locations, and IDs. Clients then use the library or utilities to translate `(name, type)` pairs into strings.

The library's NEWS file documents evolution from imake to Autoconf, reentrant interfaces, a context-based `hesiod_*` API, shared-library installation, Debian packaging, automake, pkg-config metadata, and relicensing MIT material under the 2-clause BSD license.

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

Hesiod is package-nerd catnip because it is a tiny package with a deep systems lineage. It shows how DNS was once stretched into campus directory service, before LDAP, NSS modules, cloud identity providers, and configuration-management systems took over many of the same roles.

It also demonstrates a recurring packaging theme: old infrastructure survives when a clean library, man pages, and distribution packaging keep it buildable. The Homebrew package is therefore less about trendy usage and more about preserving a historically important network abstraction in a form modern Unix systems can compile.

Chronologie

• 1987-04: RFC 1035 bibliography references Dyer and Hsu's Project Athena Hesiod name-service document.
• 1987-07-22: MIT Athena Technical Plan lists the Hesiod Name Service section by Steven P. Dyer and Felix S. Hsu.
• 1987-11: RFC 1035 assigned DNS class HS value 4 for Hesiod.
• 2013-03-28: `achernya/hesiod` repository creation date recorded by GitHub.
• 2018: Hesiod 3.2.1 NEWS documented pkg-config support and 2-clause BSD relicensing work.

Related projects

• Project Athena siblings include Kerberos for authentication, Zephyr for notification, Moira/SMS for service management, and Athena locker/file-service infrastructure.
• DNS and BIND are the underlying transport and server infrastructure. LDAP, NIS, and NSS occupy related directory and name-service territory in Unix environments.

Sources

• GitHub README and NEWS for maintained library behavior, configuration, and release evolution.
• MIT Athena Technical Plan and Athena overview for origin and production usage context.
• RFC 1035 and IANA DNS parameters for protocol-level Hesiod class history.