![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
I've removed the stub entry
Is there anything more to tell about true?
-- Carpetsmoker 04:56, 29 July 2006 (UTC)
Just possibly that in SCO (and probably other SYSV variants that /bin/true is (was) actually a 0 length file. With no "magic" in the header, the shell presumed it a script. Immediately hitting EOF and having executed no failing instructions, the shell returned "success" which is 0 which is "true."
Possibly too trivial--I'm new here.... —The preceding unsigned comment was added by 208.8.57.16 ( talk) 14:27, August 21, 2007 (UTC)
true(unix) and false(unix) should be merged, since they make antagon things. -- Fixman ( talk) 22:37, 2 April 2008 (UTC)
Investigate and tell —Preceding unsigned comment added by Foryourinfo ( talk • contribs) 18:07, 27 July 2010 (UTC)
Because, with apologies to Tolstoy, All successful program executions are alike, but each of up to 255 failed program executions may fail in their own fashion. 213.121.9.190 ( talk) 19:19, 19 April 2018 (UTC)
I think this section is misleading. "It is also used as a no-op dummy command for side-effects such as assigning default values to shell variables through the ${parameter:=word} parameter expansion form.[2]". Looking at the reference, there's nothing about ${parameter:=word} and whilst that does set the value of the variable if it's empty, I don't believe this colon has anything to do with the null command (except that it's also a colon). rmwiseman ( talk) 12:34, 8 August 2019 (UTC)
According to the standards here, the only requirement is for the return code to be non-zero. Linux seems to choose 1, as does the bash builtin, but on illumos (and Solaris?) it's 255. — Preceding unsigned comment added by 82.2.238.102 ( talk) 21:56, 12 February 2020 (UTC)