tmp/tmptnwbzinv/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,30 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
#### POSIX conformance <a id="fs.conform.9945">[[fs.conform.9945]]</a>
|
| 2 |
+
|
| 3 |
+
Some behavior is specified by reference to POSIX ([[fs.norm.ref]]). How
|
| 4 |
+
such behavior is actually implemented is unspecified.
|
| 5 |
+
|
| 6 |
+
[*Note 1*: This constitutes an “as if” rule allowing implementations to
|
| 7 |
+
call native operating system or other APIs. — *end note*]
|
| 8 |
+
|
| 9 |
+
Implementations are encouraged to provide such behavior as it is defined
|
| 10 |
+
by POSIX. Implementations shall document any behavior that differs from
|
| 11 |
+
the behavior defined by POSIX. Implementations that do not support exact
|
| 12 |
+
POSIX behavior are encouraged to provide behavior as close to POSIX
|
| 13 |
+
behavior as is reasonable given the limitations of actual operating
|
| 14 |
+
systems and file systems. If an implementation cannot provide any
|
| 15 |
+
reasonable behavior, the implementation shall report an error as
|
| 16 |
+
specified in [[fs.err.report]].
|
| 17 |
+
|
| 18 |
+
[*Note 2*: This allows users to rely on an exception being thrown or an
|
| 19 |
+
error code being set when an implementation cannot provide any
|
| 20 |
+
reasonable behavior. — *end note*]
|
| 21 |
+
|
| 22 |
+
Implementations are not required to provide behavior that is not
|
| 23 |
+
supported by a particular file system.
|
| 24 |
+
|
| 25 |
+
[*Example 1*: The FAT file system used by some memory cards, camera
|
| 26 |
+
memory, and floppy disks does not support hard links, symlinks, and many
|
| 27 |
+
other features of more capable file systems, so implementations are not
|
| 28 |
+
required to support those features on the FAT file system but instead
|
| 29 |
+
are required to report an error as described above. — *end example*]
|
| 30 |
+
|