> It's BROKEN -- it breaks the semantics of true(1) and false(1), which
> among other things is that they ignore any arguments. Hence it is a
> BUG.
It can be called BUG ONLY if you can show some POSIX specification where
said that true(1) and false(1) must ignore any arguments. Till not shown
otherwise it's FEATURE. You can like or dislike this FEATURE but you can
not clain that it's BUG !
Hmm - probably I shouldnt answer, but now that I have POSIX.2 here next to me:
4.23 false:
Options: None.
Operands: None.
Exit Status: The false utility always shall exit with a value other than zero.
Since GNU false sometimes does `exit 0' it certainly is not POSIX compliant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/