public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Luis Friedrich <fernando@inf.ufsc.br>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Anthony Tonizzo <atonizzo@gmail.com>,   ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Any shell available?
Date: Wed, 31 May 2006 11:51:00 -0000	[thread overview]
Message-ID: <447D8356.6060804@inf.ufsc.br> (raw)
In-Reply-To: <20060531083743.GD2478@lunn.ch>

Andrew Lunn wrote:

>On Tue, May 30, 2006 at 06:02:28PM -0700, Anthony Tonizzo wrote:
>  
>
>>Andrew:
>>
>>    
>>
>>>Now eCos has no concept of loading a program from secondary storage
>>>and executing it. It has no concept of a program. It has no concept of
>>>a process.
>>>      
>>>
>>I am not sure I agree 100% with this statement.
>>
>>eCos has both the concept of file system (and hence we can extrapolate
>>the concept of secondary storage) as well as the concept of process, given
>>that a process can be loaded by the objloader package and executed.
>>    
>>
>
>I did wounder if anybody would bring up the objloader packege.
>
>Yes, we have a filesystem. However we don't have processes. 
>
>We have threads, but not processes. To me there is a big
>difference. For one, a process has resource management associated to
>it. If a process dies, or is killed, all the resources associated to
>it are released. Memory is put back into the pool, file handles are
>closed etc. Also, a process contains one or more threads. Killing a
>process kills all the threads in the process. 
>
>Without having processes, from a pratical standpoint, you cannot have
>programs which run to completion and exit. Thus you cannot have a
>shell.
> 
>  
>
>>I do not see anything wrong with an application (call it shell) that
>>is capable of both accessing a file system as well as loading from
>>that file system a file and running it.
>>    
>>
>
>To me, that is more like a boot loader and less like a shell, although
>what you describe is somewhere between the two. To be a shell, what
>has been loaded must be able to exist and be unloaded, and you must be
>able to load something else which can exist and be unloaded,
>add-infinitum. For this you need processes, not threads.
>
>               Andrew
>
>  
>
In other words you might say that you have only one process with the 
application threads and the OS code all running together on the same 
address space, and this could be called the program.
Therefore, in order to load a program you'll have to start all over 
again, OS functionality plus application.

Friedrich


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-05-31 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  1:02 Anthony Tonizzo
2006-05-31  8:37 ` Andrew Lunn
2006-05-31 11:51   ` Luis Friedrich [this message]
2006-05-31 12:20     ` Andrew Lunn
2006-05-31 16:42     ` Anthony Tonizzo
2006-05-31 21:47     ` David N. Welton
2006-05-31 18:28 Zimman, Chris
2006-06-02 10:47 ` Ilija Koco
     [not found]   ` <44805E04.2040400@mindspring.com>
2006-06-02 16:19     ` Ilija Koco
     [not found] <3B530EF12E388B408ECC3162BA8C00F401BBE726@ny2526.corp.bloomberg. com>
     [not found] ` <3B530EF12E388B408ECC3162BA8C00F401BBE726@ny2526.corp.bloomberg .com>
2006-05-31 22:28   ` John Carter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447D8356.6060804@inf.ufsc.br \
    --to=fernando@inf.ufsc.br \
    --cc=andrew@lunn.ch \
    --cc=atonizzo@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).