BibTeX
@MISC{Graupner96sash--,
author = {Sven Graupner},
title = {sash -- A stand-alone Shell for the CHEOPS-Kernel},
year = {1996}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Developing software for stand-alone environments requires the availability of an interactive test support at an early stage of work. But rough conditions close to hardware force the test support to be content with minimal assistance by infrastructure. Sash (stand-alone shell) is the test support for developing the CHEOPS-Kernel and is presented in this paper. Sash is based on a yacc- grammar and serves as the counterpart for interactive kernel-testing. An essential design goal is migration of sash through various execution environments according to incremental growth of the kernel. 1. Introduction Stand-alone Software is different to regular software because typical bottom-up implementation is not possible up to a certain point of development. The first -- and most difficult -- part for building a new kernel is the "bottom chunk" of software which must be settled on hardware and run properly in one step. Up to this stage, there is no debug support or any other assistance for getting ...
Keyphrases
stand-alone shell test support yacc grammar new kernel debug support stand-alone environment interactive kernel-testing difficult part early stage certain point various execution environment introduction stand-alone software rough condition interactive test support typical bottom-up implementation bottom chunk incremental growth regular software essential design goal minimal assistance
