Chris's Wiki :: blog/unix/UnixAPIMoreThanSyscalls Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/UnixAPIMoreThanSyscalls?atomcommentsDWiki2022-07-11T05:38:37ZRecent comments in Chris's Wiki :: blog/unix/UnixAPIMoreThanSyscalls.By Edgewood on /blog/unix/UnixAPIMoreThanSyscallstag:CSpace:blog/unix/UnixAPIMoreThanSyscalls:2a41036473f23bbf2a8d021d320e8f345383ab8eEdgewood<div class="wikitext"><p>I've written shell scripts for IBM's POSIX environment on their mainframes. It <em>is</em> POSIX compliant, but not a keystroke more (at least not at the time).</p>
<p>It felt very foreign, in a way I didn't feel writing for Solaris, AIX (by IBM!) or HPUX.</p>
<p>I got the job done by opening the POSIX shell reference and assuming anything that was optional wasn't implemented, but it was just very odd in a way I had never experienced on Unix before.</p>
</div>2022-07-11T05:38:37ZBy Random Guy on /blog/unix/UnixAPIMoreThanSyscallstag:CSpace:blog/unix/UnixAPIMoreThanSyscalls:24bb7b348ef0549af700168e8829a2bebcf2fd51Random Guy<div class="wikitext"><p>"A 'Unix' without a useful $HOME environment variable and /tmp may be specification compliant (I haven't checked POSIX)"</p>
<p>In fact, both the value of $HOME and the writability of /tmp are required by POSIX. It may not be a great standard but it does cover much more than just syscalls.</p>
</div>2018-03-12T16:51:28Z