Talk:List of POSIX commands

'read' command?
read was listed as a command in the list. But I cannot find a single source which tells read is a unix command. It is a shell builtin in many linux shells. However, if someone wants to revert the change, please add a trustworthy source stating read a unix command. canaar (talk) 15:35, 2 August 2016 (UTC)


 * Read the POSIX standard, read must be available as command that can be called via exec. Schily (talk) 17:18, 2 August 2016 (UTC)

Proposed merge with Spl (Unix)
Its a dictionary definition of a computer term that is now practically historical. Dysklyver 13:05, 13 October 2017 (UTC)


 * Besides that, it lies outside the scope of this topic (and given the poor sourcing and absence of notability for that topic, someone should simply delete it) TEDickey (talk) 20:00, 13 October 2017 (UTC)
 * Oppose merge, given that, as Tedicky notes, it lies out of the scope of List of Unix commands given that it refers to kernel routines. I'd also keep rather than delete Spl (Unix) as it is referenced better than many short articles, and referencing is in-proportion to the text length. Klbrain (talk) 22:22, 10 January 2019 (UTC)

Questions
1. What is the rationale for using IEEE Std 1003.1-2008 as the justification for what to include as a "UNIX command"? I'm not questioning this decision: it's just unclear why, of all of the standards & authorities out there, this was selected. Considering that the only UNIXs still in active use & support are the BSDs & maybe Solaris -- Linux is "UNIX-like" -- the relevance of this standard is debatable. On the other hand, is there any other source one could use to include/exclude commands? (For example, a list of commands included out-of-box with the major BSD & commercial UNIX versions.)
 * Please see the long arguments about this above. Many people, including me, think that the rationale used here what is a Unix command is broken. Now even more than a decade ago when these arguments started, it is obvious that "Unix" is not the name of any current system, but rather the name of a family tree of historic systems. "Unix commands" should be a list of commands that existed on these historic systems - not commands which some modern standard decided to standardize or that are considered useful today. We could have a separate list of commands standardized by some specific standard - but the "List of Unix commands" should be about the commands available on classic systems actually called "Unix". Nyh (talk) 08:37, 23 January 2020 (UTC)
 * Then the fact that this article is part of wikiproject linux is questionable too... Regards, Comte0 (talk) 09:48, 23 January 2020 (UTC)

2. In the column "Status" there is a code after the words "Obsolete" & "Optional". What does this code signify?

-- llywrch (talk) 17:53, 2 March 2019 (UTC)

q* relevant?
Is the Portable Batch System really relevant? -- Polluks ★  15:30, 13 November 2020 (UTC)


 * Probably not (the topic gives no indication that it's relevant to this one) TEDickey (talk) 20:02, 13 November 2020 (UTC)

Updating to POSIX issue 8?
The table of contents for the section of the new POSIX release on "Shell and Utilities" has just went live:

https://pubs.opengroup.org/onlinepubs/9799919799/utilities/toc.html

The official POSIX version changed from 2017 (Which has identical commands to 2008) to 2024, which has removed and added commands from the 2008 list

Should this page be updated to match the most recent, and therefore most official version of POSIX? Vector2010Design (talk) 23:33, 20 July 2024 (UTC)