rpc.bootparamd(8) on Solnix vs Linux and the BSDs

On Solnix, rpc.bootparamd is the illumos server at /usr/sbin/rpc.bootparamd, run as an SMF service. It takes only -d and has no -f, -r, -s or -i. Where the OpenBSD and NetBSD daemons read /etc/bootparams, the Solnix page says the database source comes from nsswitch.conf(5).

What Solnix runs

A default Solnix system runs the illumos rpc.bootparamd at /usr/sbin/rpc.bootparamd. No other variants are shipped. The page gives the alias bootparamd and the SMF service identifier svc:/network/rpc/bootparams.

Differences

Compared withTopicWhat differs
OpenBSD, NetBSDdatabase sourceSolnix reads the bootparams database from the source set in nsswitch.conf(5) on the server. OpenBSD and NetBSD read the file /etc/bootparams by default, and the Solnix page names no such file.
Source: Solnix rpc.bootparamd(8) DESCRIPTION; OpenBSD rpc.bootparamd(8) DESCRIPTION, -f; NetBSD rpc.bootparamd(8) DESCRIPTION, -f
OpenBSD, NetBSD-f file optionSolnix has no -f option to choose a different parameter file. OpenBSD and NetBSD -f names the file to read instead of /etc/bootparams.
Source: Solnix rpc.bootparamd(8) SYNOPSIS; OpenBSD rpc.bootparamd(8) -f; NetBSD rpc.bootparamd(8) -f
OpenBSD, NetBSD-r default routerSolnix has no -r option. OpenBSD and NetBSD -r sets the default router, a hostname or IP address, which defaults to the machine running the server.
Source: Solnix rpc.bootparamd(8) SYNOPSIS; OpenBSD rpc.bootparamd(8) -r; NetBSD rpc.bootparamd(8) -r
OpenBSD, NetBSD-s syslog optionSolnix has no -s option. On OpenBSD and NetBSD, -s sends debugging information to syslog.
Source: Solnix rpc.bootparamd(8) OPTIONS; OpenBSD rpc.bootparamd(8) -s; NetBSD rpc.bootparamd(8) -s
NetBSD-i interface optionSolnix has no -i option. NetBSD -i chooses the interface used to obtain the default router address, and -r overrides it.
Source: Solnix rpc.bootparamd(8) SYNOPSIS; NetBSD rpc.bootparamd(8) -i
OpenBSD, NetBSD-d and forkingOn OpenBSD and NetBSD, -d also stops the daemon forking. The Solnix page says only that -d displays debugging information and does not mention forking.
Source: Solnix rpc.bootparamd(8) -d; OpenBSD rpc.bootparamd(8) -d; NetBSD rpc.bootparamd(8) -d
OpenBSD, NetBSDhow the daemon is startedOn Solnix the service is managed by SMF as svc:/network/rpc/bootparams, using svcadm(8) and svcs(1). OpenBSD and NetBSD say it should normally be started from /etc/rc.
Source: Solnix rpc.bootparamd(8) NOTES; OpenBSD rpc.bootparamd(8) DESCRIPTION; NetBSD rpc.bootparamd(8) DESCRIPTION
OpenBSD, NetBSDaliases and YP lookupOpenBSD and NetBSD document hostname aliases in /etc/bootparams, returning the name as written in the file, and a line containing only + that triggers a YP bootparams map search. The Solnix page documents neither.
Source: OpenBSD rpc.bootparamd(8) DESCRIPTION; NetBSD rpc.bootparamd(8) DESCRIPTION; Solnix rpc.bootparamd(8) DESCRIPTION
OpenBSD, NetBSDhostname case and subnetThe Solnix page warns that some hostname comparisons are case-sensitive, so a failed request may need the file's hostname case checked. It also says a client needs a server on the same IP subnetwork. The OpenBSD and NetBSD pages say neither.
Source: Solnix rpc.bootparamd(8) NOTES; OpenBSD rpc.bootparamd(8); NetBSD rpc.bootparamd(8)

Standards

  • POSIX: rpc.bootparamd is not a POSIX.1-2024 utility.
  • Solnix: The bundle's Solnix page text has no STANDARDS or ATTRIBUTES section for this command.

Writing portable scripts

  • Use only -d if a script must work on all three systems, since -f, -r, -s and -i are missing on Solnix, and -i exists only on NetBSD.
  • Do not assume /etc/bootparams exists on Solnix. The database source is set in nsswitch.conf(5) there.

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.