ypwhich(1) on Solnix vs Linux and the BSDs
On Solnix, ypwhich is the illumos ypwhich at /usr/bin/ypwhich. Unlike FreeBSD, OpenBSD and NetBSD, it takes the host to query as a bare operand, with no -h, and it adds -V and -n to choose the ypbind protocol version.
The manual pages
- Solnix: ypwhich(1) from
pkgs.solnix.illumos-world-man· illumos.org - FreeBSD: ypwhich(1) 15.1-RELEASE
- OpenBSD: ypwhich(1) 8.0
- NetBSD: ypwhich(1) 11.0
What Solnix runs
A default Solnix system runs the illumos ypwhich at /usr/bin/ypwhich. No other variants are shipped. The page is published in pkgs.solnix.illumos-world-man. The OPTIONS text for the version option is garbled in the bundle (the dash characters are corrupted). The SYNOPSIS gives it as [-Vn] hostname, and the OPTIONS entry reads 'Version of ypbind, V3 is default.'
Differences
| Compared with | Topic | What differs |
|---|---|---|
| OpenBSD, NetBSD | -h host option | OpenBSD and NetBSD have -h host to name the machine to query. Solnix ypwhich has no -h: the host is a bare operand. With -m, Solnix allows no host at all.Source: OpenBSD ypwhich(1) -h, SYNOPSIS; NetBSD ypwhich(1) -h, SYNOPSIS; Solnix ypwhich(1) SYNOPSIS, -m |
| OpenBSD, NetBSD | querying a host with -m | On OpenBSD and NetBSD, ypwhich -m can query a non-default host through -h host. On Solnix, -m cannot be combined with a host; the page says no hostname can be specified with -m.Source: Solnix ypwhich(1) -m; OpenBSD ypwhich(1) SYNOPSIS, -m; NetBSD ypwhich(1) SYNOPSIS, -h |
| FreeBSD | -m and host | FreeBSD matches Solnix here: no host may be given with -m. The FreeBSD synopsis shows host as a bare operand, like Solnix.Source: FreeBSD ypwhich(1) SYNOPSIS, -m; Solnix ypwhich(1) SYNOPSIS, -m |
| FreeBSD, OpenBSD, NetBSD | -V and -n ypbind version | Solnix has -V n to choose the ypbind version; the page says V3 is the default. The FreeBSD, OpenBSD and NetBSD pages document no such option.Source: Solnix ypwhich(1) SYNOPSIS, OPTIONS (Version of ypbind); FreeBSD/OpenBSD/NetBSD ypwhich(1) SYNOPSIS |
| NetBSD | -T and -f | NetBSD has -T (use TCP instead of UDP) and -f (with -m, query the host directly without the local ypbind). Solnix documents neither.Source: NetBSD ypwhich(1) -T, -f; Solnix ypwhich(1) SYNOPSIS |
| NetBSD | exit status | NetBSD documents a non-zero exit when -m cannot determine the map master. The Solnix page has no EXIT STATUS section, so do not rely on a specific exit code there. FreeBSD and OpenBSD pages do not document one either.Source: NetBSD ypwhich(1) EXIT STATUS; Solnix ypwhich(1) (no EXIT STATUS section) |
| NetBSD | nickname table source | NetBSD documents that -x reads /var/yp/nicknames, with a built-in default table if the file is missing. The Solnix page says only that -x displays the nickname translation table.Source: NetBSD ypwhich(1) -x; Solnix ypwhich(1) -x |
| OpenBSD | terminology and -t placement | OpenBSD calls the service YP and puts [-t] [-d domain] in front of the host forms. On Solnix, -t is documented only together with -m: [-t] -m.Source: OpenBSD ypwhich(1) SYNOPSIS, DESCRIPTION; Solnix ypwhich(1) SYNOPSIS |
| Linux | Linux | No Linux counterpart page is in the bundle, so no Linux comparison is made. Source: bundle header (counterparts: freebsd, openbsd, netbsd) |
Standards
- POSIX: ypwhich is not a POSIX.1-2024 utility.
- Solnix: The page's SEE ALSO points to attributes(7), but the bundle text contains no ATTRIBUTES or interface stability table.
Writing portable scripts
- Do not use
-hor-Vin portable scripts:-hexists only on OpenBSD and NetBSD,-Vonly on Solnix. Plain ypwhich,-ddomain,-mmname,-tand-xare in all four pages. - To query a specific host, a bare operand works on Solnix and FreeBSD, and on OpenBSD and NetBSD via [
-h] host. Avoid combining a host with-m, since Solnix and FreeBSD forbid it.
Every difference here is taken from the manual pages linked above: Solnix's published page, Linux (man-pages and the GNU and util-linux manuals), FreeBSD, OpenBSD and NetBSD. Each row names its source. Where a manual is silent, this page is too. Compiled 2026-10-26. Found a mistake? Mail hackers@lists.solnix.io.