2 ms·
It is important to realize that it does have some gaping holes, though. For example: I was recently unable to unearth from it exactly when the BSD ps command c
by JdeBP 8y ago
It is important to realize that it does have some gaping holes, though.
For example: I was recently unable to unearth from it exactly when the BSD ps command changed to using getopt() and minus signs for arguments. The entire history of the FreeBSD repository back to the original 4.4BSD commits has ps using getopt(), and minus signs have been the only option syntax documented in the ps(1) manual page for all of that time, too.
* https://svnweb.freebsd.org/base/head/bin/ps/ps.c?revision=1556&view=markup#l133 https://svnweb.freebsd.org/base/head/bin/ps/ps.c?revision=15...
* https://svnweb.freebsd.org/base/head/bin/ps/ps.1?revision=1556&view=markup#l42 https://svnweb.freebsd.org/base/head/bin/ps/ps.1?revision=15...
This repository, alas, does not yield very much further information.
- JdeBP 8y agoFor the curious: The furthest back that I have managed to trace it so far is 1986, using Usenet archives. A patch that was posted to mod.sources on 1986-08-01 (v06i083, Michael A. Callahan) apparently references getopt() argument parsing and mentions "ps -U", implying that 4.2 BSD ps was using getopt() by then. (Although there's no direct mention of getopt and this may be wrong.) * https://groups.google.com/d/msg/mod.sources/H-shkbdVIbs/VJUIw_L2hb8J https://groups.google.com/d/msg/mod.sources/H-shkbdVIbs/VJUI...