Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1227 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1227.

Report 1227 Actions

    Problem Report Number 1227
    Submitter's Classification Specification problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0429
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.0
    Test Identification STREAMSconfiguration/STREAMS 1
    Problem Summary PG4U.00038 STREAMS are not a required part of the XSH specification.
    Problem Text
    The test suite requires that the implementation under test
    provides at least one STREAMS-based device. The standard
    does not specify that an implementation have STREAMS-based
    devices or modules; it only specifies standard behavior if
    STREAMS are implemented.

    The XSH, section 2.5, describes what STREAMS are, and their behavior,
    but does not make a normative requirement that STREAMS-based devices be
    present.

    The STREAMS interfaces and functions being tested are all discussed in
    terms of STREAMS-based file descriptors. If there are no STREAMS-based
    file descriptors to be had, the only functions that appear to be
    testable in association with STREAMS are those dealing with file
    desciptor validity (EBADF, ENOSTR).

    This is a very pervasive problem. The configuration needs
    to be changed and many tests are impacted.

    Chapter 5, configuring VSU, section 5.1.7, should allow a blank
    for the pathname for VSU_STREAM_DEV. Any tests that use this
    variable should be changed to return NOT_IMPLEMENTED when the
    variable name is blank.

    Chapter 5, configuring VSU, section 5.5.4, STREAMS Loopbacks and
    modules should be optional.
    Test Output

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused after review.

    The XSH spec, section 1.4.2 states

    The following list summarises the major changes that
    have been made in this document since Issue 4:

    o STREAMS have been added as part of the X/Open
    UNIX extension.

    Section 2.5 states

    UX

    STREAMS provides a uniform mechanism for implementing
    networking services and other character-based I/O.
    The STREAMS interface provides direct access to
    protocol modules. A STREAM is typically a full-duplex
    connection between a process and an open device or
    pseudo-device. However, since pipes may be STREAMS-
    based, a STREAM can be a full-duplex connection
    between two processes. The STREAM itself exists
    entirely within the implementation and provides a
    general character I/O interface for processes. It
    optionally includes one or more intermediate
    processing modules that are interposed between the
    process end of the STREAM (STREAM head) and a device
    driver at the end of the STREAM (STREAM end).

    We take this to mean that a STREAMS interface and the
    functionality specified to support it are a mandatory part of the
    specification. As with many other configuration items (file
    systems, etc.) a specific device is not required but the
    identification and use of STREAMS devices is necessary for
    testing and mandatory to demonstrate compliance.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    X/Open believes that it was clearly intended that STREAMS devices should be
    supported and therefore the request is refused.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    The Base WG, at the November meeting, felt unable to solve this question
    as it centres on the intent rather than the letter of the specification. They
    have referred the decision back to X/Open.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority