ISO/IEC 15068-2:1999
(Main)Information technology — Portable Operating System Interface (POSIX) System Administration — Part 2: Software Administration
Information technology — Portable Operating System Interface (POSIX) System Administration — Part 2: Software Administration
Technologies de l'information — Administration du système de l'interface du système opératoire portable (POSIX) — Partie 2: Administration du logiciel
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 15068-2
ANSI/IEEE
Std 1387.2
First edition
1999-03-15
Information technology — Portable
®
Operating System Interface (POSIX )
system administration —
Part 2:
Software administration
Technologies de l'information — Administration du système de l'interface du
®
système opératoire portable (POSIX ) —
Partie 2: Administration du logiciel
Reference number
ISO/IEC 15068-2:1999(E)
ANSI/IEEE
bc
Std 1387.2, 1995 edition
---------------------- Page: 1 ----------------------
International Standard ISO/IEC 15068-2: 1999 (E)
Information technology —
Portable Operating System Interface
(POSIX )
system administration —
Part 2:
Software administration
Copyright 1999 by the Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street
New York, NY 10017, USA
All rights reserved.
---------------------- Page: 2 ----------------------
Ò
Abstract: This standard is part of the POSIX series of standards for applications and user
interfaces to open systems. It defines a software packaging layout, a set of information
maintained about software, and a set of utility programs to manipulate that software and
information.
Keywords: data processing, open systems, operating system, packaging, portable applica-
Ò
tion, POSIX , software, system administration, utilities
POSIX is a registered trademark of the Institute of Electrical and Electronics Engineers, Inc.
The Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street, New York, NY 10017-2394, USA
Copyright ã 1999 by the
Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 1996.
Printed in the United States of America.
ISBN 0-7381-1568-1
No part of this publication may be reproduced in any form,
in an electronic retrieval system or otherwise,
without the prior written permission of the publisher.
26 February 1999 SH94725
---------------------- Page: 3 ----------------------
IEEE Standards documents are developed within the Technical Committees of
the IEEE Societies and the Standards Coordinating Committees of the IEEE
Standards Board. Members of the committees serve voluntarily and without com-
pensation. They are not necessarily members of the Institute. The standards
developed within IEEE represent a consensus of the broad expertise on the sub-
ject within the Institute as well as those activities outside of IEEE that have
expressed an interest in participating in the development of the standard.
Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard
does not imply that there are no other ways to produce, test, measure, purchase,
market, or provide other goods and services related to the scope of the IEEE Stan-
dard. Furthermore, the viewpoint expressed at the time a standard is approved
and issued is subject to change brought about through developments in the state
of the art and comments received from users of the standard. Every IEEE Stan-
dard is subjected to review at least every five years for revision or reaffirmation.
When a document is more than five years old and has not been reaffirmed, it is
reasonable to conclude that its contents, although still of some value, do not
wholly reflect the present state of the art. Users are cautioned to check to deter-
mine that they have the latest edition of any IEEE Standard.
Comments for revision of IEEE Standards are welcome from any interested party,
regardless of membership affiliation with IEEE. Suggestions for changes in docu-
ments should be in the form of a proposed change of text, together with appropri-
ate supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of por-
tions of standards as they relate to specific applications. When the need for
interpretations is brought to the attention of the IEEE, the Institute will initiate
action to prepare appropriate responses. Since IEEE Standards represent a con-
sensus of all concerned interests, it is important to ensure that any interpretation
has also received the concurrence of a balance of interests. For this reason, the
IEEE and the members of its technical committees are not able to provide an
instant response to interpretation requests except in those cases where the matter
has previously received formal consideration.
Comments on standards and requests for interpretations should be addressed to:
Secretary, IEEE Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855-1331
____________________________________________________________________________
LLIEEE Standards documents may involve the use of patented technology. Their
LL
approval by the Institute of Electrical and Electronics Engineers does not mean
LL
that using such technology for the purpose of conforming to such standards is
LL
authorized by the patent owner. It is the obligation of the user of such technol-
LL
ogy to obtain all necessary permissions.
_LL___________________________________________________________________________LL
---------------------- Page: 4 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
Contents
PAGE
Section 1: General . 1
1.1 Scope . 1
1.2 Normative References . 3
1.3 Conformance . 3
1.4 Test Methods . 8
Section 2: Terminology and General Requirements. 9
2.1 Conventions . 9
2.2 Definitions. 12
2.3 Dependencies on Other Standards . 27
Section 3: Software Structures . 29
3.1 Software_Collection . 30
3.2 Distribution . 32
3.3 Media . 33
3.4 Installed_Software . 33
3.5 Vendor . 34
3.6 Software . 35
3.7 Products . 36
3.8 Bundles. 39
3.9 Filesets . 42
3.10 Subproducts . 44
3.11 Software_Files . 45
3.12 Files . 46
3.13 Control_Files . 48
Section 4: Software Administration Utilities . 51
4.1 Common Definitions for Utilities . 51
4.2 sswwaasskk — Ask for user responses . 90
4.3 sswwccoonnffiigg — Configure software . 93
4.4 sswwccooppyy — Copy distribution . 97
4.5 sswwiinnssttaallll — Install software . 102
4.6 sswwlliisstt — List software catalog . 114
4.7 sswwmmooddiiffyy — Modify software catalog . 118
4.8 sswwppaacckkaaggee — Package distribution . 121
4.9 sswwrreemmoovvee — Remove software . 125
4.10 sswwvveerriiffyy — Verify software . 131
Section 5: Software Packaging Layout . 137
5.1 Directory Structure . 137
5.2 Software Definition File Format . 141
5.3 Serial Format and Multiple Media . 158
Annex A (informative) Bibliography . 161
ii
---------------------- Page: 5 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
Annex B (informative) Rationale and Notes . 165
B.1 General. 165
B.2 Terminology and General Requirements . 167
B.3 Software Structures . 172
B.4 Software Administration Utilities . 188
B.5 Software Packaging Layout . 234
Annex C (informative) Sample Files . 243
C.1 Defaults File . 243
C.2 Product Specification File . 245
C.3 Software Packaging Layout . 247
C.4 INDEX File . 248
C.5 INFO File . 249
C.6 Control Script . 250
Annex D (informative) Portability Considerations . 251
D.1 User Requirements. 251
D.2 Portability Capabilities . 253
D.3 Profiling Considerations . 254
Alphabetic Topical Index. 257
FIGURES
Figure 5-1 −− Example of Software Packaging Layout . 138
Figure B-1 −− Roles in Software Administration . 168
Figure B-2 −− Example of Software Structure . 172
Figure B-3 −− Software Object Containment . 175
Figure B-4 −− Software Object Inheritance . 176
Figure B-5 −− Fileset State Transitions (Within Distributions) . 208
Figure B-6 −− Fileset State Transitions (Within Installed Software) . 209
Figure B-7 −− Installation State Changes . 216
Figure B-8 −− Order of Install Operations . 220
Figure B-9 −− Order of Remove Operations . 231
Figure B-10 −− SDU INFO file format. 237
Figure B-11 −− SVR4 pkgmap file format . 237
TABLES
Table 2-1 −− Typographical Conventions . 9
Table 3-1 −− Attributes of the Software_Collection Common Class . 31
Table 3-2 −− Attributes of the Distribution Class . 32
Table 3-3 −− Attributes of the Media Class. 33
Table 3-4 −− Attributes of the Installed Software Class . 34
Table 3-5 −− Attributes of the Vendor Class . 34
Table 3-6 −− Attributes of the Software Common Class . 35
Table 3-7 −− Attributes of the Product Class . 37
iii
---------------------- Page: 6 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
Table 3-8 −− Attributes of the Bundle Class . 40
Table 3-9 −− Attributes of the Fileset Class . 42
Table 3-10 −− Attributes of the Subproduct Class . 44
Table 3-11 −− Attributes of the Software_Files Common Class . 45
Table 3-12 −− Attributes of the File Class . 47
Table 3-13 −− Attributes of the Control File Class. 49
Table 4-1 −− Software_spec Version Identifiers . 56
Table 4-2 −− Script Return Codes . 73
Table 4-3 −− Event Status . 74
Table 4-4 −− General Error Events . 75
Table 4-5 −− Session Events. 76
Table 4-6 −− Analysis Phase Events . 78
Table 4-7 −− Execution Phase Events . 83
Table 4-8 −− Return Codes . 89
Table 4-9 −− Default Levels . 116
Table 5-1 −− File Attributes for INFO File . 153
Table B-1 −− Possible Attributes of a Host Class . 177
Table B-2 −− Mapping from Software to DMTF Component ID . 180
Table B-3 −− Comparison of Some Existing Practices . 192
Table B-4 −− Comparison of Software Administration Packages . 217
Table B-5 −− Comparison of Existing Practice for Software Packaging . 228
Table B-6 −− Packaging Layout Comparisons . 236
Table D-1 −− 1387.2 Portability Capability Summary . 253
iv
---------------------- Page: 7 ----------------------
International Standard ISO/IEC 15068-2:1999(E)
ISO (the International Organization for Standardization) and IEC (the Interna-
tional Electrotechnical Commission) form the specialized system for world-
wide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical
committees established by the respective organization to deal with particular
fields of technical activity. ISO and IEC technical committees collaborate in
fields of mutual interest. Other international organizations, governmental and
non-governmental, in liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted by
the joint technical committee are circulated to national bodies for voting. Pub-
lication as an International Standard requires approval by at least 75% of the
national bodies casting a vote.
International Standard ISO/IEC 15068-2 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC22, Pro-
gramming languages, their environments and system software interfaces.
ISO/IEC 15068 consists of the following parts, under the general title Informa-
tion technology — Portable Operating System Interface (POSIX):
Ñ Part 1: (reserved for future use)
Ñ Part 2: Software administration
Ñ Part 3: User and group account administration
Ñ Part 4: Print administration
Annexes A to D of this part of ISO/IEC 15068 are for information only.
v
---------------------- Page: 8 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
Introduction
(This Introduction is not a normative part of ISO/IEC 15068-2 Information technology — Portable
Operating System Interface (POSIX) system administration — Part 2: Software administration, but
is included for information only.)
System administration utilities vary widely between vendors, being an area where
there are currently no formal standards that have proved to be significant in prac-
tice. This makes the task of system administration difficult. The objective of this
part of ISO/IEC 15068 is to address this problem for software administration, a
specific area of system administration, and to contribute to the overall solution of
administering computing environments, both stand-alone and distributed.
In pursuit of this goal, this part of ISO/IEC 15068 defines a software packaging lay-
out, a set of information maintained about software, and a set of utility programs
to manipulate that software and information. These definitions provide the flexi-
bility necessary for system administrators to enforce policies suitable to their
environments.
Organization of the Standard
The standard is divided into the following sections:
(1) General
(2) Terminology and General Requirements
(3) Software Structures
(4) Software Administration Utilities
(5) Software Packaging Layout
Also included are the following annexes:
— Bibliography (Annex A)
— Rationale and Notes (Annex B)
— Sample Files (Annex C)
— Portability Considerations (Annex D)
This introduction and the annexes are not considered a normative part of the
standard.
Conformance Measurement
In publishing this part of ISO/IEC 15068, both IEEE and the POSIX.7.2 developers
simply intend to provide a yardstick against which various operating system
implementations may be measured for conformance. It is not the intent of either
the IEEE or POSIX.7.2 developers to measure or rate any products or to reward or
sanction the product of any vendor as standard by these or any other means. The
responsibility for determining the degree of conformance or lack thereof with this
part of ISO/IEC 15068 rests solely with the individual evaluating the product
claiming to be in conformance with the standard.
vi Introduction
---------------------- Page: 9 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
Base Documents
Much of the original text came to the developers of this part of ISO/IEC 15068 from
UNIX System Laboratories (the ppkkgg∗ utilities) and Hewlett-Packard (HP
Software Distribution Utilities). For further details and comparisons of various
existing practices, see B.4 and B.4.5.
Extensions and Supplements to This Standard
Activities to extend this standard to address additional requirements are in pro-
gress and similar efforts can be anticipated in the future. This is an outline of
how these extensions will be incorporated and how users of this document can
keep track of that status.
Extensions are approved as supplements to this document following the IEEE
standards procedures and eventually as International Organization for
Standardization/International Electrotechnical Committee (ISO/IEC) standards.
Approved supplements are published separately and distributed with orders from
the IEEE for this document until the full document is reprinted and such supple-
ments are incorporated in their proper positions.
If there are any questions about the completeness of your version, you may con-
tact the IEEE Computer Society, (202) 371-0101, or the IEEE Standards Office,
(908) 562-3800, to determine what supplements have been published.
Supplements may contain either required functions or optional facilities. Supple-
ments may add additional conformance requirements (see 1.3, which defines new
classes of conforming systems or applications).
It is undesirable (but perhaps unavoidable) for supplements to change the func-
tionality of the already defined facilities.
If you are interested in participating in addressing IEEE 1387 issues and develop-
ing the IEEE P1387 standards, please send your name, address, and phone
number to the Secretary, IEEE Standards Board, P.O. Box 1331, 445 Hoes Lane,
Piscataway, NJ 08844-1331, USA.
When writing, ask to have your letter forwarded to the chairperson or appropriate
reviewer/developer of IEEE Std 1387.2-1995.
vii
---------------------- Page: 10 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995
ISO/IEC 15068-2 was prepared by the IEEE P1387.2 Working Group, sponsored by
the Portable Applications Standards Committee of the IEEE Computer Society.
At the time this part of ISO/IEC 15068 was approved, the membership of the IEEE
P1387.2 Working Group was as follows:
Portable Applications Standards Committee
Chair: Lowell Johnson
Vice-Chair: Charles Severance
Functional
Chairs: Andy Bihain
Jon Spencer
Andrew Josey
Jay Ashford
Barry Needham
Treasurer: Peter Smith
Secretary: Charles Severance
IEEE P1387 Working Group Officials
Chair: Martin Kirk
Steve Carter (1988-1990)
Vice-Chair: Jay Ashford
David Hinnant (1988-1991)
Technical Editor: Matt Wicks (1991-1993)
Robert Robillard (1991-1993)
Shoshana O’Brien (1989-1991)
Bob Baumann (1988-1990)
Secretary: Bernard Kinsler (1990-1995)
John Pokladnik (1990)
Mark Colburn (1989)
IEEE P1387.2 Working Group Officials
Chair: Jay Ashford
Technical Editors: Jay Ashford, George Williams
Matt Wicks (1991-1993)
IEEE P1387.2 Technical Reviewers
Jay Ashford Jerry Rubin George Williams
Matt Wicks
IEEE P1387.2 Working Group
Richard Alexander Louis Imershein Ken Nicholson
Barrie Archer John Jobs Per Pedersen
Jay Ashford Jim Johnson Daryl Roberts
Shane Claussen Judy Kale Helmut Roth
Jim Darling Martin Kirk Jerry Rubin
Frances Dodson Esti Koen Nigel Titley
Frank Dogil Steve Lamotte Stephe Walli
Janet Frazer Sean Landis Matthew Wicks
Jay Goldberg Fu-Tin Man George Williams
Michael Gutmann Norbert Marrek Neil Winton
Steve Howell Laura Micks Jane Zysk
David Humphreys Tom Murphy
viii Introduction
---------------------- Page: 11 ----------------------
ISO/IEC 15068-2: 1999 (E)
The following persons provided valuable input during the balloting period:
Francesco Borgna Shane P. McCarron Mike Ryan
Theodore Collins Brenda Parsons Larry Spieler
Cheng Hu Dieter Putatzki Marc J. Stephenson
Walter Wong
The following persons were on the balloting committee:
Barrie Archer Geoff Hall John S. Morris
Jay Ashford Barry Hedquist Mo Oloumi
Jason Behm Joseph Hungate Paul Rabin
Michael E. Browne Louis Imershein David Radford
Dana Carson Hal Jespersen Rick Roelling
Shane Claussen Judy S. Kerner Frank Rone
Frances Dodson Lawrence Kilgallen Jerrold Rubin
Ron Elliott Martin J. Kirk James G. Tanner
Michael E. Falck Esti Koen Mark-Rene Uchida
David Fiander George Kriger Matthew Wicks
Dan Geer Thomas M. Kurihara George Williams
Michel Glen Sean Landis Walter Wong
Dave Grindeland Jim Moore Oren Yuen
When the IEEE Standards Board approved this standard on June 14, 1995, it had
the following membership:
E. G. "Al" Kiener, Chair Donald C. Loughry, Vice Chair
Andrew G. Salem, Secretary
Gilles A. Baril Richard J. Holleman Marco W. Migliaro
Clyde R. Camp Jim Isaak Mary Lou Padgett
Joseph A. Cannatelli Ben C. Johnson John W. Pope
Stephen L. Diamond Sonny Kasturi Arthur K. Reilly
Harold E. Epstein Lorraine C. Kevra Gary S. Robinson
Donald C. Fleckenstein Ivor N. Knight Ingo Rusch
Jay Forster* Joseph L. Koepfinger* Chee Kiow Tan
Donald N. Heirman D. N. "Jim" Logothetis Leonard L. Tripp
L. Bruce McClung
*Member Emeritus
Also included are the following nonvoting IEEE Standards Board liaisons:
Satish K. Aggarwal
Richard B. Engelman
Robert E. Hebner
Chester C. Taylor
Rochelle L. Stern
IEEE Standards Project Editor
ix
---------------------- Page: 12 ----------------------
_____________________________________________________________________________
INTERNATIONAL STANDARD ISO/IEC 15068-2: 1999
______________________________________________________________________
Information technology— Portable Operat-
ing System Interface (POSIX) system
administration— Part 2: Software adminis-
tration
1 Section 1: General
2 1.1 Scope
3 This part of ISO/IEC 15068 defines a software packaging layout and utilities that
4 operate on that packaging layout as well as software installed from that packaging
5 layout. The scope of this part of ISO/IEC 15068 is administration of software
6 across distributed systems. This administration includes, but is not limited to,
7 packaging of software for distribution, distribution of software to systems, instal-
8 lation and configuration of software on systems, and removal of software from sys-
9 tems.
10 This part of ISO/IEC 15068 is motivated by many factors, includinga desire by sys-
11 tem administrators and software suppliers to have a common way of installing
12 and removing software. To meet the needs of these groups, this part of ISO/IEC
13 15068 consists of several components, listed below. The readers of this part of
14 ISO/IEC 15068 include system administrators, suppliers of software that imple-
15 ment this part of ISO/IEC 15068, and suppliers of software that use implementa-
16 tions of this part of ISO/IEC 15068. Readers in each of these categories may find
17 their attention drawn to different sections.
18 The key components are listed below.
19 Software structures
20 This part of ISO/IEC 15068 defines a hierarchical set of structures
21 used to define software. Information is kept about the software
based on these structure definitions. The structure definitions apply
both to installed software and to software prepared for installation
1.1 Scope 1
---------------------- Page: 13 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995 INFORMATION TECHNOLOGY—POSIX SYSTEM ADMINISTRATION —
22 but not yet installed.
23 Software packaging layout
24 This part of ISO/IEC 15068 defines the organization of software on a
25 distribution medium, the information held about that software, and
26 the way in which such information is represented. This enables both
27 portability of software distributions across systems of different archi-
28 tecture, and the use of different media to distribute software (includ-
29 ing both file system and serial image forms).
30 Information kept about software
31 This part of ISO/IEC 15068 defines the information that is held about
32 software, both installed software and distributions. This provides a
33 consistent view of software, even when that software is provided from
34 various sources. The way in which the information is held is
35 undefined within this part of ISO/IEC 15068.
36 Utilities to administer software
37 This part of ISO/IEC 15068 defines a utility to convert software into
38 the packaging layout, known as a distribution. This part of ISO/IEC
39 15068 also contains utilities to examine the information in a distribu-
40 tion, copy software from one distribution to another, install software
41 from a distribution, remove software from a distribution, and verify
42 the integrity of a distribution. There are also utilities for configuring
43 installed software, verifying the integrity of installed software, exa-
44 mining and modifying the information held about installed software,
45 and for removing installed software from a system. This provides
46 administrators with a consistent method of dealing with software
47 across all conforming systems.
48 Distributed software administration
49 This part of ISO/IEC 15068 defines the concepts, and the utility syn-
50 tax and behaviors, for managing software in a distributed environ-
51 ment. This includes the concept of different software administration
52 roles (developer, packager, manager, source, target, and client).
53 Different utilities involve different roles, and different roles may be
54 distributed across multiple systems within a single command execu-
55 tion.
56 This part of ISO/IEC 15068 is based upon the knowledge of, and documentation
57 for, existing programs that assume an interface and architecture similar to that
1)
58 described by POSIX.1 {2} and POSIX.2 {3}. Any questions regarding the definition
59 of terms or the semantics of an underlying concept should be referred to
60 POSIX.1 {2} and POSIX.2 {3}. This part of ISO/IEC 15068 does not require the use
61 of any specific programming language and, in particular, does not require the use
62 of the C language. This part of ISO/IEC 15068 is based upon the knowledge of, and
63 documentation for, existing programs that utilize C-language interfaces. Any
64 questions regarding the definition of terms or the semantics of an underlying
________________
65
66 1) The numbers in curly brackets correspond to those of the references in 1.2. When preceded by a
67 ‘‘B,’’ the numbers correspond to those of the bibliography in Annex A.
2 1 General
---------------------- Page: 14 ----------------------
ISO/IEC 15068-2: 1999 (E)
PART 2: SOFTWARE ADMINISTRATION IEEE Std 1387.2-1995
68 concept in this language should be referred to C Standard {B13}.
69 1.2 Normative References
70 The following standards contain provisions that, through references in this text,
71 constitute provisions of this part of ISO/IEC 15068. At the time of publication, the
72 editions indicated were valid. All standards are subject to revision, and parties to
73 agreements based on this part of ISO/IEC 15068 are encouraged to investigate the
74 possibility of applying the most recent editions of the standards listed below.
75 Members of IEC and ISO maintain registers of currently valid International Stan-
76 dards.
77 {1} ISO/IEC 646: 1991, Information technology—ISO 7-bit coded character set
2)
78 for information interchange (International Reference Version).
79 {2} ISO/IEC 9945-1: 1996 (ANSI/IEEE Std 1003.1-1996), Information
80 technology — Portable Operating System Interface (POSIX ) — Part 1: Sys-
3)
81 tem Application Program Interface (API) [C Language].
82 {3} ISO/IEC 9945-2: 1993 (ANSI/IEEE Std 1003.2-1992), Information
83 technology — Portable Operating System Interface (POSIX ) — Part 2:
84 Shell and Utilities.
85 {4} ISO/IEC 10646-1: 1993, Information technology—Universal Multiple-Octet
86 Coded Character Set (UCS)—Part 1: Architecture and Basic Multilingual
87 Plane.
88 1.3 Conformance
89 1.3.1 Implementation Conformance
90 1.3.1.1 Conforming POSIX.7.2 Implementation
91 A Conforming POSIX.7.2 Implementation, also known as a ‘‘conforming imple-
92 mentation,’’ shall meet all the following criteria:
93 (1) The system shall support all interfaces defined within this part of ISO/IEC
94 15068. These interfaces shall support all the functional behavior
95 described herein. The interfaces covered by this definition of confor-
96 mance include, but are not limited to, utilities and their options and
97 extended options, the behavior of the utilities, including the generation of
98 events; events; structures; attributes and their values; and file formats.
________________
99
100 2) ISO/IEC documents can be obtained from the ISO Central Secretariat, Case Postale 56, 1 rue de
101 Varembe´, CH-1211, Gene`ve 20, Switzerland/Suisse.
102 3) IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445
103 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331, USA.
1.3 Conformance 3
---------------------- Page: 15 ----------------------
ISO/IEC 15068-2: 1999 (E)
IEEE Std 1387.2-1995 INFORMATION TECHNOLOGY—POSIX SYSTEM ADMINISTRATION —
104 (2) The system may provide additional or enhanced utilities, functions, or
105 facilities not required by this part of ISO/IEC 15068. Nonstandard exten-
106 sions should be identified as such in the system documentation. Nonstan-
107 dard extensions should conform to 2.10.2, of POSIX.2 {3}. Nonstandard
108 extensions, when used, may change the behavior of utilities, functions, or
109 facilities defined by this part of ISO/IEC 15068. In such cases, the confor-
110 mance document for the implementation (see 2.2.1.3) shall define an exe-
111 cution environment (i.e., shall provide general operating instructions) in
112 which a Strictly Conforming POSIX.7.2 Distribution may be operated
113 upon and yield the behavior specified by this part of ISO/IEC 15068. In no
114 case shall such an environment require modification of a Strictly Con-
115 forming POSIX.7.2 Distribution.
116 An implementation shall bea Conforming POSIX.7.2 Implementation if all the cri-
117 teria for such are met with the exception of those features that depend on the
118 existence of conforming implementations of either POSIX.1 {2} or POSIX.2 {3}. In
119 this case, the conformance document for the Conforming POSIX.7.2 Implementa-
120 tion shall describe the behavior of the implementation of all features of the imple-
121 mentation, or of a Strictly Conforming POSIX.7.2 Distribution, that depend on the
122 function of POSIX.1 {2} or POSIX.2 {3}. See 2.3.1 and 2.3.2.
123 1.3.1.2 Limited Conformance POSIX.7.2 Implementation
124 A Limited Conformance POSIX.7.2 Implementation shall meet all of the criteria
125 established for a Conforming POSIX.7.2 Implementation (see 1.3.1.1) with the fol-
126 lowing exception:
127 — For the value of HHOOSSTT in specifications of sources and targets (see 4.1.4.2),
128 the system may support only the local machine. While this type of limited
129 conformance removes support for remote operations, the syntax of all utili-
130 ties and files shall remain identical to that required for Conforming
131 POSIX.7.2 Implementations. The way in which this limitation is imposed
132 by the implementation shall be implementation defined.
133 1.3.1.3 Documentation
134 A conformance document with the following information shall be available for an
1
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.