Man pages › Compared with Linux and the BSDs

`pod2texi(1)` on Solnix vs Linux and the BSDs

pod2texi is not in the Solnix base system; install pkgs.solnix.texinfo to get it. The Solnix page is an older revision of the Linux (texinfo-7.2) page: it lacks --generate-setfilename and --outdir, and --setfilename and --subdir are described differently.

The manual pages

Solnix: pod2texi(1) from pkgs.solnix.texinfo
Linux: pod2texi(1) texinfo-7.2

What Solnix runs

Not installed by default: add pkgs.solnix.texinfo. The bundle lists no other illumos variants and no BSD counterparts.

Differences

Compared with	Topic	What differs
Linux	`--generate-setfilename` missing	The Linux page documents `--generate-setfilename` (negatable with `--no-generate-setfilename`) to emit a @setfilename line for standalone manuals. The Solnix page has no such option, and its default output has no @setfilename. Source: Linux pod2texi(1) --generate-setfilename; Solnix pod2texi(1) OPTIONS and --setfilename
Linux	`--outdir` missing	The Linux page documents `--outdir=NAME`, which puts the generated Texinfo files in directory NAME. The Solnix page has no `--outdir`, so it documents no way to choose the output directory apart from `--subdir` and `--output`. Source: Linux pod2texi(1) --outdir; Solnix pod2texi(1) OPTIONS
Linux	`--subdir` meaning	On Solnix, `--subdir=NAME` is the directory where the include files are put. On Linux, `--subdir=NAME` is the directory the include files are included from. It should normally be the relative path from the main manual to the `--outdir` argument. The same flag gives different results. Source: Solnix pod2texi(1) --subdir; Linux pod2texi(1) --subdir, --outdir
Linux	`--setfilename` scope	Linux `--setfilename` applies to the main manual only when `--base-level` is not 0, and is ignored when `--base-level` is 0. The Solnix page states no such condition and says only that no @setfilename is output by default. Source: Solnix pod2texi(1) --setfilename; Linux pod2texi(1) --setfilename
Linux	same tool, older page	Both pages share the same synopsis, modes of operation and most options (`--base-level`, `--headings-as-sections`, `--menus`, `--output`, `--preamble`, `--top` and others). Solnix and Linux look like the same program at different revisions. The Solnix page does not state its version. Source: Solnix and Linux pod2texi(1) SYNOPSIS, DESCRIPTION, OPTIONS
FreeBSD, OpenBSD, NetBSD	no BSD counterpart in bundle	The bundle includes no FreeBSD, OpenBSD or NetBSD pod2texi page, so the manuals here say nothing about its presence or behaviour on those systems. Source: Bundle header: only a linux counterpart is listed

Standards

POSIX: pod2texi is not a POSIX.1-2024 utility.

Writing portable scripts

Do not rely on --outdir or --generate-setfilename in scripts that must also run on Solnix; the Solnix page does not document them.
Avoid --subdir when you need the same result on Solnix and Linux: it is documented as the output directory on Solnix and as the include path on Linux.

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.