Home • About Us •A-Z Index• Search •

1. Commands and Utilities v3

Product Information

Environment Specification

Temporary Waivers

1.1 POSIX.2 Supported Features

Question 1: Which of the following options, specified in the <unistd.h> header, are available on the system?

Response

Macro Name	Meaning	Provided
_POSIX2_C_BIND	Implementation supports the C language binding option.	Yes
_POSIX2_C_DEV	Implementation supports the C language development utilities option.	Yes
_POSIX2_CHAR_TERM	Implementation supports at least one terminal type.	Yes
_POSIX2_FORT_DEV	Implementation supports the FORTRAN Development Utilities Option.	No
_POSIX2_FORT_RUN	Implementation supports the FORTRAN Run-time Utilities.	No
_POSIX2_LOCALEDEF	Implementation supports the creation of locales by the localedef utility.	Yes
_POSIX2_SW_DEV	Implementation supports the Software Developments Utilities Option.	Yes
_POSIX2_UPE	Implementation supports the User Portability Utilities Option.	Yes

Rationale

For a Commands and Utilities V3 conformant implementation, _POSIX2_C_BIND, _POSIX2_CHAR_TERM, _POSIX2_LOCALDEF and _POSIX2_UPE must be supported. The other constants identify optional functionality that an implementation may or may not choose to support.

1.2 Development Utilities

1.2.1 Supported Commands

Question 2: Which of the development utilities are not provided with the implementation?

Response

All development utilities are provided.

Rationale

The development utilities are required to exist on designated DEVELOPMENT systems but may not be present on all XSI-conformant systems. The dis utility is defined as optional and need not be present even on systems that support the remainder of the development utilities.

1.3 FORTRAN Option

1.3.1 FORTRAN Utility

Question 3: Is the FORTRAN fort77 utility provided?

Response

No

Rationale

The fort77 utility is the command level interface to the FORTRAN compiler, which need not be provided.

1.4 Possibly Unsupportable Utilities and Options

Question 4: Which of the following utilities and utility options are not supported on the implementation?

Response

Utility	Option	Supported
ar	-s	Yes
lp	-m	Yes
	-o	Yes
	-t	Yes
	-w	Yes
sort	-z	Yes
tabs	+m	Yes
uucp	-C	Yes
	-f	Yes
	-j	Yes
	-n	Yes
	-r	Yes
uustat	-q	Yes
	-r	Yes
uux	-j,--	Yes

Rationale

A number of utilities and utility options are marked as possibly unsupportable features, and the functionality associated with these need not be present in a conforming implementation.

1.5 Legacy Option

Question 5: Which of the following Legacy utilities are provided?

Response

All of the legacy utilities are provided.

Rationale

The Legacy utilities are optional on XSI-conformant systems.

1.6 Specific Commands and Utilities

1.6.1 at

Question 6: How does the at command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable.

Rationale

The interpretation of the SHELL environment variable can cause at to invoke different versions of the shell on some implementations.

1.6.2 awk

Question 7: What is the limit on the number of open streams provided by awk?

Response

60 open streams.

Rationale

The number of open streams that are available to awk may differ between implementations, possibly depending on the number of streams that are available to a process ({FOPEN_MAX}).

1.6.3 batch

Question 8: How does the batch command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable.

Rationale

The interpretation of the SHELL environment variable can cause batch to invoke different versions of the shell on some implementations.

1.6.4 c89

Question 9: Which defined names are automatically provided by the compiler?

Response

__STDC__
__DATE__
__TIME__
__LINE__
__FILE__
__sun
__unix
__SUNPRO_C=0x500
__`uname -s`_`uname -r`
__sparc (SPARC)
__sparcv9 (SPARC)
__x86 (X86)
__BUILTIN_VA_ARG_INCR
__SVR4
__PRAGMA_REDEFINE_EXTNAME

Rationale

The automatic provision of defined names by the compiler can cause these names to be unavailable in the name space for defined names.

Question 10: When multiple input files are specified, where does c89 direct identification messages designating the start of each input file processing?

Response

Standard error.

Rationale

These messages, if produced, must be written to one or the other of standard output and standard error, but not to both. The destination of these messages is useful in determining redirections that are necessary to identify the input files from which warning messages are generated.

Question 11: What are the limits associated with external symbols imposed by c89?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31	1023
Number of external symbols per source or object file	511	No limit
Total number of external symbols	4095	No limit

Rationale

These limits vary between implementations and cannot be reset by the user. The XCU definition gives the minimum maximum value for each of the values. Some applications may require larger limits than these minimum maxima.

1.6.5 cp

Question 12: What is the affect of alternate access control mechanisms on file copies?

Response

If the source file has an associated access control mechanisms, the access control mechanisms will be copied to the destination file. If the access control mechanisms cannot be associated with the destination file, the copy will fail.

Rationale

Because of the additional restrictions on creating files and reading data from files, the cp utility may not behave as described when alternate access control mechanisms are in use.

1.6.6 date

Question 13: Does date permit the setting of the date and time?

Response

Yes

Rationale

Some systems, particularly those that are hosted as part of a total system environment, do not allow the date command to set the date. On such systems, the setting of the date can only be accomplished from the host environment.

1.6.7 ex

Question 14: What restrictions are imposed on the set of commands within the rhs of the map command?

Response

None.

Rationale

Implementations may impose restrictions on the commands that can be used by macros in visual mode.

1.6.8 fc

Question 15: Is the history list mechanism disabled for users with appropriate privileges who do not set HISTFILE?

Response

No

Rationale

The specification states that an implementation may, in certain circumstances, disable the history list mechanism for users with appropriate privileges who do not set HISTFILE. This could have some security implications.

1.6.9 fort77

Question 16: When multiple input files are specified, where does fort77 direct identification messages designating the start of each input file processing?

Response

Not applicable.

Rationale

These messages, if produced, must be written to one or the other of standard output and standard error, but not to both. The destination of these messages is useful in determining redirections that are necessary to identify the input files from which warning messages are generated. If the response is not applicable then the fort77 utility is not supported.

Question 17: What are the limits associated with external symbols imposed by fort77?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31	not applicable
Number of external symbols per source or object file	511	not applicable
Total number of external symbols	4095	not applicable

Rationale

These limits vary between implementations and cannot be reset by the user. The specification gives the minimum maximum value for each of the values. Some applications may require larger limits than these minimum maxima. If the responses are not supported then the fort77 utility is not supported.

1.6.10 lex

Question 18: Where are error messages sent when the lex -t option is not specified?

Response

Standard error.

Rationale

These messages can be directed to either standard output or standard error, though the messages are not allowed to be directed to both. An application may wish to redirect these messages to a file.

1.6.11 ln

Question 19: Can ln create links to a directory?

Response

No

Rationale

Implementations may disallow the creation of hard links to a directory, even though the executing process has the appropriate privileges.

1.6.12 localedef

Question 20: What is the default character mapping used when the localedef -f option is not specified?

Response

The characters from the Portable Character Set as defined in XBD Issue 5, Version 2 are mapped using the ISO 8859-1 character set.

Rationale

The specification does not define a specific character mapping as the default for conforming systems. This character mapping provides encoding information for the members of the portable character set.

1.6.13 lp

Question 21: What lp option or operator command is used to suppress the printing of a banner page?

Response

-o nobanner

Rationale

The user may require that banner pages are suppressed in cases where pre-printed forms are used and the stationary is of a non-standard length.

1.6.14 ls

Question 22: How many bytes are in a block as reported by ls?

Response

512

Rationale

The block size used by ls to report the number of blocks occupied by a file varies from system to system; often this depends on the underlying file system architecture.

1.6.15 make

Question 23: What additional variables does make add to its environment?

Response

None

Rationale

The implementation of make may set certain environment variables on invocation of make. These variables may not be set by the user, thus reducing the name space for environment variables.

Question 24: Does the default MAKEFLAGS environment variable contain additional implementation-dependent options?

Response

MAKEFLAGS may contain the -E, -V, -v and -x options if they appeared on the original make command line.

Rationale

The implementation of make may set certain default MAKEFLAGS options on invocation of make. These variables are in addition to those set by the user on the command line and could affect the processing of make.

1.6.16 newgrp

Question 25: Does newgrp allow users who are not listed as a member of a group which has no password to change to that group?

Response

No

Rationale

On some implementations, a user who is not listed as a member of a group may change to that group in the case that there is no password associated with the group.

Question 26: Are there any other implementation-specific authorisation restrictions that affect newgrp?

Response

None.

Rationale

Some implementations may impose accounting or other restrictions that could cause newgrp to deny activity to a group member. For example, a resource quota system could be implemented on a group basis that would limit the ability to join a group until the resources were available to the group.

1.6.17 nice and renice

Question 27: What are the limits and default values used by nice and renice?

Response

Maximum nice value	19
Minimum nice value	-20
Default nice value	10

Rationale

Each of these values differs between implementations and the range of values gives the user some control over the relative priority of processes.

1.6.18 pax

Question 28: What is the default archive format used by pax?

Response

Extended tar.

Rationale

The implementation has the choice as to which format it shall use as the default when it is creating files. When it is reading an archive created in either extended tar or extended cpio format (or any other format that it understands), the pax utility will read the archive in the format as written.

Question 29: How does pax handle reading and writing of archives that span multiple files?

Response

The pax utility writes a prompt to the tty and reads a response from /dev/tty. If /dev/tty cannot be opened, then pax exits.

Rationale

In many cases pax will take actions, such as prompting the user for the device name to use for the next archive file, when the current archive file is full. There may be extensions to the syntax of pax which allow the user to specify the address to use to access subsequent files.

Question 30: How does pax handle invalid filenames when it is extracting files from an archive?

Response

All filenames in an archive are valid in the filesystem.

Rationale

An implementation may either extract the data associated with these files into files named in an implementation-defined manner or may issue an error indicating that the file is being ignored. If pax extracts the file, it is necessary for the user either to be informed of the file that is used or to know the algorithm that pax uses in generating these filenames.

1.6.19 printf

Question 31: Does printf support the e, E, f, g and G floating point conversion specifications?

Response

Yes

Rationale

The support of these conversions is optional.

1.6.20 sh

Question 32: Is the environment variable IFS ignored when the shell is invoked?

Response

Yes

Rationale

The specification allows that the sh command ignore the setting of the IFS environment variable on invocation. The setting of this variable has been used to breach security on systems which use the shell to interpret a call to the system() and execvp() interfaces.

1.6.21 touch

Question 33: What is the latest date after the Epoch that can be used by touch?

Response

January 18, 2038

Rationale

Because of the limitations on the storage of times in the stat structure associated with a file, there is a limitation on the valid dates that can be specified to touch. This is directly related to the value that can be stored in the integral type time_t.

1.6.22 yacc

Question 34: What are the limits of yacc's internal tables?

Response

Description	Minimum Maximum	Implementation Maximum
Number of tokens	126	No limit
Number of non-terminals	200	No limit
Number of rules	300	No limit
Number of states	600	No limit
Length of rules	5200	No limit
Number of actions	4000	No limit

Rationale

These internal table sizes vary between implementations and cannot be reset by the user. The specification gives the minimum maximum value for each of the table values.

1.7 C-language Programming Environments

1.7.1 Supported Environments

Question 35: What C-language programming environments are provided?

Response

Programming Environment	Provided
The implementation provides a C-language programming environment with 32-bit int, long, pointer and off_t types.	Yes
The implementation provides a C-language programming environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits.	Yes
The implementation provides a C-language programming environment with 32-bit int, and 64-bit long, pointer and off_t types.	Yes
The implementation provides a C-language programming environment with int using at least 32-bits, and long, pointer and off_t types using at least 64 bits.	Yes

Rationale

Commands and Utilities, Issue 5 defines these scenarios as possible C-language programming environment offerings.

1.7.2 Default Environment

Question 36: What C-language programming environment is the default?

Response

The implementation provides a C-language programming environment with 32-bit int, long, pointer and off_t types.

Rationale

Commands and Utilities, Issue 5 specifies that one of these must be supported as the default.

2. Appendix

Question 35 (1.7.1 Supported Environments) describes the supported programming environments for the implementation. The support described in this question is for 64-bit SPARC-based systems. Further clarification for both 32-bit and 64-bit SPARC-based and X86-based systems is as follows for both the Programming and Execution environments:

Programming Environment:

• The implementation provides a C-language programming environment with 32-bit int, long, pointer and off_t types on 32-bit and 64-bit SPARC and x86.
• The implementation provides a C-language programming environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits on 32-bit and 64-bit SPARC and x86.
• The implementation provides a C-language programming environment with 32-bit int, and 64-bit long, pointer and off_t types on both 32-bit and 64-bit SPARC.
• The implementation provides a C-language programming environment with int using at least 32-bits, and long, pointer and off_t types using at least 64-bits on both 32-bit and 64-bit SPARC.

Execution Environment:

• The implementation provides an execution environment with 32-bit int, long, pointer and off_t types on 32-bit and 64-bit SPARC and x86.
• The implementation provides an execution environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits on 32-bit and 64-bit SPARC and x86.
• The implementation provides an execution environment with 32-bit int, and 64-bit long, pointer and off_t types on 64-bit SPARC.
• The implementation provides an execution environment with int using at least 32-bits, and long, pointer and off_t types using at least 64-bits on 64-bit SPARC.

Copyright © 2003 Sun Microsystems, Inc.
All rights reserved.

3. Change History

---

 Copyright © 1998-2011 The Open Group. All Rights Reserved.

 The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.

---

[ Home ] [ The Open Brand ] [ Conformance Statement Library ] [ Search Conformance Statements ] [ Send Feedback ]