I don't object. However, if you go back in time to the early RTEMS days, executive and kernel were used interchangeably. Both were less full-featured than what was called an OS back in those days. Now that RTEMS has file systems, networking, etc, it is proper under those old conventions to use OS for RTEMS now but the concurrency and synchronization minimal subset is an executive/kernel.
But executive is better than kernel now as a term. Executives focus on services related to managing a thread set. --joel On Tue, Jan 22, 2019 at 10:32 AM Gedare Bloom <[email protected]> wrote: > I mean, yes let's call it executive. There is no "kernel" in RTEMS. > > On Tue, Jan 22, 2019 at 11:32 AM Gedare Bloom <[email protected]> wrote: > >> I think this is appropriate for terminology. >> >> On Tue, Jan 22, 2019 at 9:26 AM Sebastian Huber < >> [email protected]> wrote: >> >>> Hello, >>> >>> in the documentation sometimes the name "executive" and sometimes >>> "kernel" is used for RTEMS itself. I think "kernel" should be better >>> used for systems with a kernel/user space separation. I will use RTEMS >>> executive throughout the documentation if nobody objects. >>> >>> -- >>> Sebastian Huber, embedded brains GmbH >>> >>> Address : Dornierstr. 4, D-82178 Puchheim, Germany >>> Phone : +49 89 189 47 41-16 >>> Fax : +49 89 189 47 41-09 >>> E-Mail : [email protected] >>> PGP : Public key available on request. >>> >>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >>> >>> _______________________________________________ >>> devel mailing list >>> [email protected] >>> http://lists.rtems.org/mailman/listinfo/devel >> >> _______________________________________________ > devel mailing list > [email protected] > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list [email protected] http://lists.rtems.org/mailman/listinfo/devel
