tmp/tmph2rmtyd7/{from.md → to.md}
RENAMED
|
@@ -1,15 +1,17 @@
|
|
| 1 |
### Conformance <a id="fs.conformance">[[fs.conformance]]</a>
|
| 2 |
|
|
|
|
|
|
|
| 3 |
Conformance is specified in terms of behavior. Ideal behavior is not
|
| 4 |
always implementable, so the conformance subclauses take that into
|
| 5 |
account.
|
| 6 |
|
| 7 |
#### POSIX conformance <a id="fs.conform.9945">[[fs.conform.9945]]</a>
|
| 8 |
|
| 9 |
-
Some behavior is specified by reference to POSIX
|
| 10 |
-
|
| 11 |
|
| 12 |
[*Note 1*: This constitutes an “as if” rule allowing implementations to
|
| 13 |
call native operating system or other APIs. — *end note*]
|
| 14 |
|
| 15 |
Implementations should provide such behavior as it is defined by POSIX.
|
|
@@ -48,12 +50,11 @@ system.
|
|
| 48 |
#### File system race behavior <a id="fs.race.behavior">[[fs.race.behavior]]</a>
|
| 49 |
|
| 50 |
A *file system race* is the condition that occurs when multiple threads,
|
| 51 |
processes, or computers interleave access and modification of the same
|
| 52 |
object within a file system. Behavior is undefined if calls to functions
|
| 53 |
-
provided by subclause [[
|
| 54 |
-
race.
|
| 55 |
|
| 56 |
If the possibility of a file system race would make it unreliable for a
|
| 57 |
program to test for a precondition before calling a function described
|
| 58 |
herein, *Preconditions:* is not specified for the function.
|
| 59 |
|
|
|
|
| 1 |
### Conformance <a id="fs.conformance">[[fs.conformance]]</a>
|
| 2 |
|
| 3 |
+
#### General <a id="fs.conformance.general">[[fs.conformance.general]]</a>
|
| 4 |
+
|
| 5 |
Conformance is specified in terms of behavior. Ideal behavior is not
|
| 6 |
always implementable, so the conformance subclauses take that into
|
| 7 |
account.
|
| 8 |
|
| 9 |
#### POSIX conformance <a id="fs.conform.9945">[[fs.conform.9945]]</a>
|
| 10 |
|
| 11 |
+
Some behavior is specified by reference to POSIX. How such behavior is
|
| 12 |
+
actually implemented is unspecified.
|
| 13 |
|
| 14 |
[*Note 1*: This constitutes an “as if” rule allowing implementations to
|
| 15 |
call native operating system or other APIs. — *end note*]
|
| 16 |
|
| 17 |
Implementations should provide such behavior as it is defined by POSIX.
|
|
|
|
| 50 |
#### File system race behavior <a id="fs.race.behavior">[[fs.race.behavior]]</a>
|
| 51 |
|
| 52 |
A *file system race* is the condition that occurs when multiple threads,
|
| 53 |
processes, or computers interleave access and modification of the same
|
| 54 |
object within a file system. Behavior is undefined if calls to functions
|
| 55 |
+
provided by subclause [[filesystems]] introduce a file system race.
|
|
|
|
| 56 |
|
| 57 |
If the possibility of a file system race would make it unreliable for a
|
| 58 |
program to test for a precondition before calling a function described
|
| 59 |
herein, *Preconditions:* is not specified for the function.
|
| 60 |
|