Comment 1 for bug 455381

This is intentional: since we don't support pseudo-versioned pathnames and unix doesn't provide real ones, we rahter signal an error than do something lossy.

The error message should be better, though, and explain the situation.

From CLHS: "The various file systems in existence today have widely differing capabilities, and some aspects of the file system are beyond the scope of this specification to define. A given implementation might not be able to support all of these options in exactly the manner stated. An implementation is required to recognize all of these option keywords and to try to do something ``reasonable'' in the context of the host file system. Where necessary to accomodate the file system, an implementation deviate slightly from the semantics specified here without being disqualified for consideration as a conforming implementation. If it is utterly impossible for an implementation to handle some option in a manner similar to what is specified here, it may simply signal an error."

While this bug has been marked as confirmed, I would consider it fixed once the error message tells what is actually going on.

Cheers,

 -- Nikodemus

 status confirmed
 priority low
 tag streams documentation