This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. (PC)NFS

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 General (PC)NFS Issues

1.1.1 Personal Computer NFS Daemon

Question 1: Do you support the Personal Computer NFS Daemon?

Response

Yes   No

Rationale

The Personal Computer NFS Daemon provides a personal computer NFS client with the authentication and network printing services. Whilst the Personal Computer NFS Daemon is not required by a conforming system it is highly desirable.

Reference

X/Open Developers' Specification, Protocols for X/Open PC Interworking: (PC)NFS, Section 6.3, PCNFSD Protocol Definition.

1.2 NFS Protocol

1.2.1 Server Procedures

Question 2: Which of the following return codes, that may be the result of an NFS RPC call, are available on your system?

Response

For each entry in the table select either "Yes", "No" or "For some interfaces" "For some interfaces" should be used when the error occurs for some but not all interfaces that can return this error.

Return Code	Meaning	Provided
NFSERR_ACCES	Permission denied	Yes No For some interfaces
NFSERR_DQUOT	Disk quota exceeded	Yes No For some interfaces
NFSERR_EXIST	File exists	Yes No For some interfaces
NFSERR_IO	Some sort of hard error	Yes No For some interfaces
NFSERR_ISDIR	Is a directory	Yes No For some interfaces
NFSERR_NAMETOOLONG	File name too long	Yes No For some interfaces
NFSERR_NOENT	No such file or directory	Yes No For some interfaces
NFSERR_NOSPC	No space left on device	Yes No For some interfaces
NFSERR_NOTDIR	Not a directory	Yes No For some interfaces
NFSERR_NOTEMPTY	Directory not empty	Yes No For some interfaces
NFSERR_NXIO	File handle does not refer to a symbolic link	Yes No For some interfaces
NFSERR_PERM	Not Owner	Yes No For some interfaces
NFSERR_ROFS	Read-only filesystem	Yes No For some interfaces
NFSERR_STALE	Invalid filehandle	Yes No For some interfaces

If you selected "For some interfaces" for any entry, please supply a description of the manner in which variations occur.

Rationale

These are the recommended return codes to indicate the various error conditions.

Reference

X/Open Developers' Specification, Protocols for X/Open PC Interworking: (PC)NFS, Section 5.5.3, NFSPROC_SETATTR Specification through Section 5.5.18, NFSPROC_STATFS Specification.

Question 3: Does your NFS server implementation support symbolic links?

Response

Yes   No

Rationale

A conforming system that does not support symbolic links should return a PROC_UNAVAIL error if a client invokes NFSPROC_READLINK or NFSPROC_SYMLINK.

Reference

X/Open Developers' Specification, Protocols for X/Open PC Interworking: (PC)NFS, Section 5.2, NFS Protocol Definition.

1.3 NFS Implementation

1.3.1 General Issues

Question 4: Do you provide a mechanism to change the mapping of user id zero?

Response

Yes   No

Rationale

An X/Open-compliant server, by default, maps user id 0 to -2 (0xfffffffe) before doing its access checking. A server implementation may provide a mechanism to change this mapping.

Reference

X/Open Developers' Specification, Protocols for X/Open PC Interworking: (PC)NFS, Section 5.4, NFS Implementation Issues, Permission Issues.

1.4 Mount Protocol

1.4.1 Return Codes

Question 5: Which of the following return codes, that may be the result of an MNTPROC_MNT call, are available on your system?

Response

For each entry in the table select either "Yes", "No" or "For some interfaces" "For some interfaces" should be used when the error occurs for some but not all interfaces that can return this error.

Return Code	Meaning	Provided
MNT_EPERMIT	Permission denied, possible server configuration error	Yes No For some interfaces
MNT_EACCESS	Access denied	Yes No For some interfaces
MNT_ENOENT	Specified directory doesnot exist	Yes No For some interfaces
MNT_EINVAL	Invalid Pathname	Yes No For some interfaces

If you entered "For some interfaces" for any entry, please supply a description of the manner in which variations occur.

Rationale

These are the recommended return codes to indicate the various error conditions possible with the MNTPROC_MNT call.

Reference

X/Open Developers' Specification, Protocols for X/Open PC Interworking: (PC)NFS, Section 6.6.6, MNTPROC_MNT Specification.

2. Appendix

Copyright © 
All rights reserved.

3. Change History