maux
Star on GitHub Buy me a coffee

Conformance

A Unix tool is only useful if it does what you expect. When you type sort -n or sed s/a/b/, you want the answer you would get on any other Unix. So the tools in maux are tested against real ones.

At a glance

Commands on the disk91
Standard utilities compared with a real Unix, command by command62
Tests run on them837
Same answer823
Known differences, each named below14

The shell, sed, vi, ex and the regular-expression engine have references of their own and are counted separately in the table further down.

How closely

The headline: most of the command set follows POSIX, and is tested that way. Some of it is older on purpose. The shell is the Version 7 Bourne shell with the POSIX parts that fit. ed is a small version of the original editor. vi and ex come from Berkeley, and have been brought up to the POSIX text. The table says which is which.

How it is checked: most tests run a command on maux and run the same command on a Mac, then compare the output and the exit status byte for byte. Where the Mac’s tool and the POSIX text disagree, the POSIX text wins. The Mac’s own tools are BSD tools, and its vi and ex are Vim. The counts below come from test runs on 2026-10-24. maux runs on an emulated enhanced IIe for those runs, not on a real machine: they establish what the software does, not how the original hardware behaves.

How to read the counts

A test is one command, run on maux and run again on the reference. It counts only if maux gave the same answer, byte for byte, including the exit status. Something maux does not do, such as grep -E, is a difference, not a match, and is listed by name under “Where it differs”. 823 of the 837 tests on the standard utilities gave the same answer, and 14 are known differences. (The test run itself prints 837 of 837, because it also counts a known difference as a pass for as long as it stays different. That is a check on the list of differences, not a match.)

Not every test has a running reference to compare with. Of the 823 that agreed, 522 compare maux with the Mac’s own tool. The other 301 check maux against an expected answer written by hand, where the Mac has no tool to compare with (cal, for one) or its tool disagrees with the POSIX text. Those are assertions, not comparisons. The shell, sed, vi, ex and regular-expression counts are separate runs against their own references, named in the table.

Tool by tool

“Where it comes from” is the design maux follows. “Same answer” counts the tests whose output and exit status matched the reference exactly; a known difference is not counted as agreeing.

ToolWhere it comes fromChecked againstSame answerNotable differences
viSecond Berkeley Software Distribution (2BSD). Bill Joy's visual mode for ex, first installed under the name vi.macOS vi (Vim in vi mode)72 of 72Brought up to the POSIX vi text. No normal-mode filter command (use :%!cmd), no R replace mode, no crash recovery; a file holds a limited number of lines.
exFirst Berkeley Software Distribution (1BSD), where it shipped as ex. Bill Joy's extended ed; its second version came with 2BSD.macOS ex (Vim in ex mode)92 of 92Brought up to the POSIX ex text. No tags, no multi-file next list, no crash recovery.
sedVersion 7 Unix.macOS sed (BSD sed); only constructs BSD and GNU sed agree on137 of 137Rewritten to the POSIX sed text. Very long input lines are cut short.
Regular expressionsPOSIX basic regular expressions, as in ed and grep. One engine serves grep, sed, ed, ex and vi.the AT&T (Fowler) and Spencer regular-expression test files109 of 109Extended regular expressions are not provided. A malformed pattern quietly matches nothing instead of being reported as an error (28 test rows expect an error and are not counted).
shVersion 7 Bourne shell, by design. eval, set -e and prefix assignments are Version 7 already. The POSIX additions that fit: getopts, $( ), ${V%pat}, command.macOS /bin/sh (bash in POSIX mode), construct by construct54 of 56Not a full POSIX shell. No functions (they came after Version 7), no backquotes, no $(( )) arithmetic (use expr). What differs is listed below.
grepVersion 4 Unix, written by Ken Thompson so a colleague could analyse the Federalist Papers. The manual page maux follows is the Version 6 one.macOS grep15 of 16Basic regular expressions only: grep -E is not provided, and that counts as a difference, not a match.
makeVersion 7 make, plus the POSIX inference rules and macros.macOS make (comparing what each would run), and the POSIX text40 of 40No shell between make and the command, so no pipes, redirection or globbing in a recipe. No include, no parallel jobs.
edThe original Unix line editor (Version 1), as a small subset.not scored against a reference—Smaller than the original ed on purpose. No undo, marks, backward search or shell escape. Version 1 already had backward search and the shell escape; ex has them all.
The other standard utilitiesMostly Research Unix: cat, ls, cp, mv, rm, wc, od, sort, find, tr, uniq, tail and more. csplit is from PWB/UNIX. Newer ones (cut, paste, printf, nl, timeout) were written from the POSIX text.the host’s own utilities (macOS BSD tools); the POSIX text where those disagree823 of 837, across 62 utilities14 known differences are counted as differences, and listed below. Some can never close because ProDOS has no owners, groups or modes.
man, moreman dates from the Second Edition. more is BSD; Version 7 had no pager.man: the POSIX text. more: not scored6 of 6 (man)Manual pages are plain text, paged through more.
bye, mount, umount, chvt, vidmode, nulib2, tipmaux and Apple II specific. (tip is a BSD tool, adapted to the serial card.)nothing: no other Unix has these—They exist because of the machine: running a ProDOS program, mounting disk images, switching consoles, ShrinkIt archives.

Where it differs

The known differences from the reference, as the test runs reported them: the 14 utility differences counted above, then the shell. Each is something a script might trip over. Some are choices (no extended regular expressions), some are the machine (no floating point, no file owners), and some are work not done yet.

Utilities

The shell

Every utility

The same answers, utility by utility, in the run above. A utility with a known difference shows less than its full count.

Show all 62 utilities

The test runs are kept in evidence/.