AnyFS POSIX Quality: 31 tests: 31 passed, 0 failed, 0 skipped, 28 of 28 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the libraryAnyFS POSIX: its three layers as namespaces.#Entry pointssrc/mod.tssrc/governance/mod.tssrc/logical/mod.tssrc/physical/mod.tssrc/logical/conformance/mod.ts#Modulesgovernance/modThe Governance layer of AnyFS POSIX: what the view is, as data and types: the codes, the fidelity of an operation, the paths of POSIX, the policy a program gives, the operations by their cases and…governance/errnoThe codes a POSIX operation ends with, as a closed union: the fifteen a store can give cause for, each with the number Linux gives it and one sentence.governance/fidelityHow faithfully an operation is carried out, as a closed union: native where the store does what POSIX says, emulated where the library does it with other operations (and says what that costs),…governance/posix-pathThe paths a program of POSIX gives, and how they become the keys of a store.governance/policyWhat a program decides about the view before it opens it: whether an empty directory is kept (and as which marker object), who the objects belong to and with which mode, whether the ancestors of a…governance/opsThe operations of the view, by how they are carried out: a closed list whose members are the operations with the cases that carry them out differently (a file is renamed one way, a file over another…governance/typesWhat the operations of the view are given and give back: the kind of a name, what a stat says, an entry of a directory, the modes an object is opened in, the number of an open object and what an…logical/modThe Logical layer of AnyFS POSIX: the model it reasons with: the plan of each operation for the capabilities of a store, the table from a problem to a code, the directories derived from a list, the…logical/planThe plan of an operation: how a store of some capabilities carries it out, as data.logical/errno-tableWhat a store's problem is, as a code of POSIX: a total table from the five kinds of problem (and the seven reasons of a refusal) to the code a local file system would have given.logical/deriveDirectories, derived: a store has objects and no directories, so a directory exists where an object lies below it, and its names are the first segments of the paths below it.logical/modeThe mode of a name, made from what the store can do and what the program said about ownership: the bits of write are taken away where the store cannot be written, so that a store given as read-only…logical/handlesThe handles of the view: what an open object holds, and the table that gives each a number.re-exportsWhat AnyFS POSIX exports from elsewhere, so that its users need import nothing else.logical/posixThe view as a type: what a program that treats a store as a file system holds.physical/modThe Physical layer of AnyFS POSIX: what carries an operation out against a store, through the handler of the store and nothing else.physical/posixThe view of a store as a file system.physical/cacheThe read cache of the view: whole objects, kept by their path and their revision, so that an object read again while it has not changed costs a stat and no bytes.logical/conformance/kitThe small kit the cases of the suite are written with: a failure that says what differed, the bytes of a text, and the reading of an outcome, an error and a fidelity.logical/conformance/random-modelThe model cases of the suite: a seeded sequence of operations on a small set of names (so that names collide, move and are removed again) run against the view and against the reference model, with…logical/conformance/modelThe reference model the suite holds a view to: a tree of files in memory that follows the rules of a file system as this library states them (a directory is where a file lies below it, an empty…logical/conformance/casesThe cases of the conformance suite: what a view of any store does, written once.logical/conformance/modThe conformance suite of AnyFS POSIX: the cases every view of a store passes, each needing and lacking named capabilities, and the functions that choose and run them.