Explore chapters and articles related to this topic
Task Management and Timekeeping, POSIX API
Published in Gedare Bloom, Joel Sherrill, Tingting Hu, Ivan Cibrario Bertolotti, Real-Time Systems Development with RTEMS and Multicore Processors, 2020
Gedare Bloom, Joel Sherrill, Tingting Hu, Ivan Cibrario Bertolotti
When the flag is set, signal handling is performed on an alternate, dedicated stack instead of the regular stack of the thread to which the signal is delivered. The function: can be used to set up the alternate stack and/or retrieve the current settings. The function uses the same underlying logic as . It can retrieve the current signal handling stack information (and store it into the data structure referenced by , if it is not a pointer), and/or set up a new signal handling stack (according to the contents of the data structure referenced by , if it is not a pointer). This function must be present only if the operating system supports the XSI (Single UNIX Specification) POSIX option. It is not implemented by RTEMS and will not be further discussed here for this reason.
Scripting Layers
Published in Cliff Wootton, Developing Quality Metadata, 2009
Most operating system variants now conform to POSIX. This isn’t a UNIX-specific standardization activity. Windows supports POSIX, too. More recently, standardization work has resulted in the Single UNIX Specification, which is administered by the Austin Group, and the Linux Standard Base specification. Both of these are meaningful attempts to unify all the different versions of operating systems so that vendor applications can be recompiled across a wider range of target operating systems with the minimum of OS-specific code being required.
The Impact of Geographic Location on the Subjective Assessment of System Usability
Published in International Journal of Human–Computer Interaction, 2019
Philip Kortum, Claudia Ziegler Acemyan
The primary dependent measure was the modified SUS (Bangor et al., 2008). The SUS is designed to generate a scale score ranging from 0 to 100. As described in Bangor, Kortum, and Miler (2009), acceptable SUS scores range from 70 to 100. Marginal SUS scores run from 50 to 70, and anything less than 50 is deemed to be unacceptable. A significant advantage of using the SUS is that the resulting scores can be interpreted to determine the perceived usability of a system. Studies have confirmed both the scale’s reliability (α = .91) and validity (with a correlation of .81 between the SUS and a single-item user-friendliness scale [Bangor et al., 2008]).