Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 3
    The lack of a POSIX compliant awk is a POSIX conformance failure. A system that doesn't have a POSIX compliant awk can't run POSIX compliant scripts. Those small-solaris-server are not POSIX let alone Unix systems. And I suppose they're not covered by the certificate Solaris obtained from the Open Group. Commented Apr 21, 2017 at 14:02
  • 1
    @StéphaneChazelas Yes, these systems are not qualified so are obviously not covered. Same would happen if Solaris is installed on a non qualified hardware. POSIX/Unix compliance is not a prerequisite for Solaris to work properly. Solaris itself makes no use of POSIX utilities when they differ from its own ones. Commented Apr 21, 2017 at 14:11
  • @StéphaneChazelas In any case, a POSIX awk is always present on a Solaris system or non global zone so the issue is not about availability but limited to the name of the command (nawk vs awk). docs.oracle.com/cd/E53394_01/html/E54763/nawk-1.html Commented Apr 23, 2017 at 7:18
  • 1
    nawk is almost POSIX (it doesn't support CONVFMT for instance), but yes, at least that's not as bad as grep (that doesn't have the POSIX -e/-E for instance) or tr (that doesn't have tr a-f A-F). Commented Apr 23, 2017 at 7:53
  • @StéphaneChazelas Indeed, clarification added to my reply. Thanks. Commented Apr 23, 2017 at 8:13