ypinit(8) on Solnix vs Linux and the BSDs
On Solnix, ypinit is the illumos script at /usr/sbin/ypinit. It sets up an NIS client (-c) and also builds masters (-m) and slaves (-s). FreeBSD and OpenBSD ypinit only set up servers and have no -c; NetBSD has -c.
The manual pages
- Solnix: ypinit(8) from
pkgs.solnix.illumos-world-man· illumos.org - FreeBSD: ypinit(8) 15.1-RELEASE
- OpenBSD: ypinit(8) 8.0
- NetBSD: ypinit(8) 11.0
What Solnix runs
A default Solnix system runs the illumos ypinit at /usr/sbin/ypinit. No other variants are shipped. The NIS client service is svc:/network/nis/client:default, managed with svcadm(8) and queried with svcs(1).
Differences
| Compared with | Topic | What differs |
|---|---|---|
| FreeBSD, OpenBSD | client setup (-c) | Solnix ypinit -c sets up an NIS client. FreeBSD and OpenBSD ypinit have no -c and describe only master and slave server setup, plus -u.Source: Solnix ypinit(8) SYNOPSIS, -c; FreeBSD ypinit(8) SYNOPSIS; OpenBSD ypinit(8) SYNOPSIS |
| FreeBSD, OpenBSD | -u missing on Solnix | FreeBSD and OpenBSD ypinit -u updates the ypservers map on the master. Solnix ypinit has no -u.Source: FreeBSD ypinit(8) -u; OpenBSD ypinit(8) -u; Solnix ypinit(8) SYNOPSIS |
| NetBSD | -l server list | NetBSD -l takes a comma-separated server list and skips the interactive prompt. Solnix has no -l: server names are given as arguments to -c (replacing the configured list), or ypinit prompts for them.Source: NetBSD ypinit(8) -l; Solnix ypinit(8) -c, DESCRIPTION |
| FreeBSD, OpenBSD, NetBSD | domainname argument | The BSD synopses accept an optional domainname argument. The Solnix synopsis has none. Solnix ypinit works on the current system domain, the one sysinfo(2) returns for SI_SRPC_DOMAIN. Source: FreeBSD, OpenBSD, NetBSD ypinit(8) SYNOPSIS; Solnix ypinit(8) BUGS |
| NetBSD | client binding file location | Solnix stores the server list in /var/yp/binding/domain/ypservers, used by ypbind when run without -broadcast. NetBSD -c writes /var/yp/binding/<domain>.ypservers, a different path form.Source: Solnix ypinit(8) DESCRIPTION; NetBSD ypinit(8) -c |
| FreeBSD, OpenBSD, NetBSD | -s argument | On Solnix the -s master_server argument is optional in the synopsis, though the option text shows it as required. The master must match the one in the YP maps and returned by ypwhich -m. FreeBSD, OpenBSD and NetBSD synopses show it as required.Source: Solnix ypinit(8) SYNOPSIS, -s; FreeBSD, OpenBSD, NetBSD ypinit(8) SYNOPSIS |
| FreeBSD, NetBSD | what -m does | FreeBSD -m creates /var/yp/$DOMAINNAME and the ypservers file, then runs /var/yp/Makefile to build maps. NetBSD -m generates maps from local files. The Solnix page says only 'Build a master ypserver data base'.Source: FreeBSD ypinit(8) DESCRIPTION; NetBSD ypinit(8) -m; Solnix ypinit(8) -m |
| FreeBSD, OpenBSD, NetBSD | ypinit not required for clients | Solnix ypinit need not be used if ypbind(8) runs with -broadcast. The svc:/network/nis/client:default service starts it that way. The BSD pages do not say this.Source: Solnix ypinit(8) DESCRIPTION; FreeBSD, OpenBSD, NetBSD ypinit(8) DESCRIPTION |
Standards
- POSIX: ypinit is not a POSIX.1-2024 utility.
Writing portable scripts
- Do not rely on shared ypinit flags.
-cexists only on Solnix and NetBSD,-uonly on FreeBSD and OpenBSD, and-lonly on NetBSD. Check each system's page first. - Do not pass a domainname argument to ypinit on Solnix. Set the system domain first, since ypinit uses the current one.
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.