yes, the easy definition is acceptable does not produce any errors at all, no exceptions, when sufficient machine resources are available. This is not precise as to the metadata necessary to indicate which resources there needs to be sufficient amounts of, and which parts of a file are code or data. The standard only requires a serial port capable of supporting the general terminal interface and a file system be provided as non-RAM resources. Everything else is optional, and other standards define which metadata needs to be accommodated during the linking phases for those options. The file system can consist of only a RAM disk too, populated at boot from an otherwise hidden ROM with the standard utilities and data files they use, so even a hard drive is not required. Neither is a clock, as this can be emulated in software. I expect Issue 8 to only require as an additional 'device' a graphics page buffer, to support Unicode compositing. It's in quotes because something like this can be emulated in RAM also, so no additional hardware will be necessary.
On Thursday, November 24, 2016 Mark Galeck <[email protected]> wrote: >There is no precise definition of "acceptable" Yes currently there isn't , but it would be easy to make such a definition, simply, for various failure errno numbers (which are enumerated in the standard), say "acceptable", "not acceptable", or perhaps "unspecified".
