Re: RTEMS Executive vs. Kernel

2019-01-29 Thread Joel Sherrill
On Tue, Jan 29, 2019, 9:02 AM Gedare Bloom > > On Mon, Jan 28, 2019 at 4:49 PM Chris Johns wrote: > >> On 26/1/19 11:22 am, Joel Sherrill wrote: >> > >> > >> > On Fri, Jan 25, 2019, 5:15 PM Chris Johns > > wrote: >> > >> > On 26/1/19 9:43 am, Joel Sherrill wrote: >>

Re: RTEMS Executive vs. Kernel

2019-01-29 Thread Gedare Bloom
On Mon, Jan 28, 2019 at 4:49 PM Chris Johns wrote: > On 26/1/19 11:22 am, Joel Sherrill wrote: > > > > > > On Fri, Jan 25, 2019, 5:15 PM Chris Johns > wrote: > > > > On 26/1/19 9:43 am, Joel Sherrill wrote: > > > We have a full shelf of old reports. A few would

Re: RTEMS Executive vs. Kernel

2019-01-28 Thread Chris Johns
On 26/1/19 11:22 am, Joel Sherrill wrote: > > > On Fri, Jan 25, 2019, 5:15 PM Chris Johns wrote: > > On 26/1/19 9:43 am, Joel Sherrill wrote: > > We have a full shelf of old reports. A few would be good to have  > > mirrored at ftp.rtems.org

Re: RTEMS Executive vs. Kernel

2019-01-25 Thread Joel Sherrill
On Fri, Jan 25, 2019, 5:15 PM Chris Johns On 26/1/19 9:43 am, Joel Sherrill wrote: > > We have a full shelf of old reports. A few would be good to have > > mirrored at ftp.rtems.org if DTIC has them. > > Sebastian and I have been discussing using .. > > https://ftp.rtems.or

Re: RTEMS Executive vs. Kernel

2019-01-25 Thread Chris Johns
On 26/1/19 9:43 am, Joel Sherrill wrote: > We have a full shelf of old reports. A few would be good to have  > mirrored at ftp.rtems.org if DTIC has them. Sebastian and I have been discussing using .. https://ftp.rtems.org/pub/contrib/docs for these type of documents. We

Re: RTEMS Executive vs. Kernel

2019-01-25 Thread Joel Sherrill
On Fri, Jan 25, 2019 at 7:03 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 24/01/2019 00:24, Joel Sherrill wrote: > > > > > > On Wed, Jan 23, 2019 at 2:01 AM Sebastian Huber > > > > wrote: > > > > On 23/01/2019 08:11, Chris Joh

Re: RTEMS Executive vs. Kernel

2019-01-25 Thread Sebastian Huber
On 24/01/2019 00:24, Joel Sherrill wrote: On Wed, Jan 23, 2019 at 2:01 AM Sebastian Huber > wrote: On 23/01/2019 08:11, Chris Johns wrote: > On 23/1/19 5:50 pm, Sebastian Huber wrote: >> On 22/01/2019 23:42, Chris Johns wrote: >>> On

Re: RTEMS Executive vs. Kernel

2019-01-23 Thread Joel Sherrill
On Wed, Jan 23, 2019 at 2:01 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 23/01/2019 08:11, Chris Johns wrote: > > On 23/1/19 5:50 pm, Sebastian Huber wrote: > >> On 22/01/2019 23:42, Chris Johns wrote: > >>> On 23/1/19 5:34 am, Joel Sherrill wrote: > I don't object. >

Re: RTEMS Executive vs. Kernel

2019-01-23 Thread Joel Sherrill
On Wed, Jan 23, 2019 at 2:25 AM Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > Am 23.01.19 um 08:11 schrieb Chris Johns: > [...] > > > >> The "OS repo" is also good. > > > > What about "RTOS", eg RTOS repo? This leave 'OS' as the collective term > of the > > pieces we have an

Re: RTEMS Executive vs. Kernel

2019-01-23 Thread Christian Mauderer
Am 23.01.19 um 08:11 schrieb Chris Johns: [...] > >> The "OS repo" is also good. > > What about "RTOS", eg RTOS repo? This leave 'OS' as the collective term of the > pieces we have and I think that is a good thing to have. Just a note regarding that term: Although RTOS is a generic term, it's qu

Re: RTEMS Executive vs. Kernel

2019-01-23 Thread jameszxj
iginal -- From: "Chris Johns"; Date: Wed, Jan 23, 2019 03:11 PM To: "Sebastian Huber";"joel";"Gedare Bloom"; Cc: "RTEMS"; Subject: Re: RTEMS Executive vs. Kernel On 23/1/19 5:50 pm, Sebastian Huber wrote: > On 22/01/201

Re: RTEMS Executive vs. Kernel

2019-01-23 Thread Sebastian Huber
On 23/01/2019 08:11, Chris Johns wrote: On 23/1/19 5:50 pm, Sebastian Huber wrote: On 22/01/2019 23:42, Chris Johns wrote: On 23/1/19 5:34 am, Joel Sherrill wrote: I don't object. Is executive the right abstraction? Both terms are an abstraction because we have a single address space and lite

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Chris Johns
On 23/1/19 5:50 pm, Sebastian Huber wrote: > On 22/01/2019 23:42, Chris Johns wrote: >> On 23/1/19 5:34 am, Joel Sherrill wrote: >>> I don't object. >> Is executive the right abstraction? Both terms are an abstraction because we >> have a single address space and literal or formal interpretation br

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Sebastian Huber
On 22/01/2019 23:42, Chris Johns wrote: On 23/1/19 5:34 am, Joel Sherrill wrote: I don't object. Is executive the right abstraction? Both terms are an abstraction because we have a single address space and literal or formal interpretation breaks down. I see the physical separation as an impleme

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Chris Johns
On 23/1/19 5:34 am, Joel Sherrill wrote: > I don't object. Is executive the right abstraction? Both terms are an abstraction because we have a single address space and literal or formal interpretation breaks down. I see the physical separation as an implementation detail. Which term is the bette

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Joel Sherrill
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

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Gedare Bloom
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 wrote: > I think this is appropriate for terminology. > > On Tue, Jan 22, 2019 at 9:26 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> Hello, >> >> in the docu

Re: RTEMS Executive vs. Kernel

2019-01-22 Thread Gedare Bloom
I think this is appropriate for terminology. On Tue, Jan 22, 2019 at 9:26 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > in the documentation sometimes the name "executive" and sometimes > "kernel" is used for RTEMS itself. I think "kernel" should be better > used fo