From: "David N. Welton" <davidw@dedasys.com>
To: ecos-discuss@ecos.sourceware.org
Cc: Luis Friedrich <fernando@inf.ufsc.br>,
Andrew Lunn <andrew@lunn.ch>,
Anthony Tonizzo <atonizzo@gmail.com>
Subject: Re: [ECOS] Re: Any shell available?
Date: Wed, 31 May 2006 21:47:00 -0000 [thread overview]
Message-ID: <447E0E9F.4090108@dedasys.com> (raw)
In-Reply-To: <447D8356.6060804@inf.ufsc.br>
>> 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.
A system like Erlang manages to have "processes", a shell, and a lot of
other things typically associated with real processes all inside one big
process...
--
David N. Welton
- http://www.dedasys.com/davidw/
Linux, Open Source Consulting
- http://www.dedasys.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-31 21:47 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
2006-05-31 12:20 ` Andrew Lunn
2006-05-31 16:42 ` Anthony Tonizzo
2006-05-31 21:47 ` David N. Welton [this message]
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=447E0E9F.4090108@dedasys.com \
--to=davidw@dedasys.com \
--cc=andrew@lunn.ch \
--cc=atonizzo@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=fernando@inf.ufsc.br \
/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).