From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Chris Gray <gray@acunia.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos API
Date: Fri, 20 Apr 2001 06:22:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010420090447.00b35cd0@mail.larwe.com> (raw)
In-Reply-To: <3ADFE04B.1A85BF68@acunia.com>
> > eCos does not support user-installable applications. It is a monolithic,
> > statically-linked OS+application.
>
>One interesting case is the one where the application includes a Java(TM)
>compatible Virtual Machine (I think that's the approved formula; doubtless
Question: If the only reason you want to support dynamic executable loading
is to load a JVM, then why don't you just roll the JVM into the
"monolithic, statically-linked OS+application"?
>VM Architect, ACUNIA
>(draw your own conclusions)
(sotto voce) concludes: "This person works for an acronym I don't know" :)
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"... a man who is endowed with real qualities of leadership will be tempted
to refrain from taking part in political life; because [...] the situation
does not call for a man who has a capacity for constructive statesmanship
but rather for a man who is capable of bargaining for the favour of the
majority. Thus the situation will appeal to small minds and will attract
them accordingly."
next prev parent reply other threads:[~2001-04-20 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 21:00 james chen
2001-04-18 21:37 ` Lewin A.R.W. Edwards
2001-04-19 7:43 ` Grant Edwards
2001-04-19 23:50 ` Fredrik Hederstierna
2001-04-19 23:57 ` Chris Gray
2001-04-20 0:06 ` Jonathan Larmour
2001-04-20 6:22 ` Lewin A.R.W. Edwards [this message]
2001-04-19 1:01 Nielsen Linus
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=4.3.2.7.2.20010420090447.00b35cd0@mail.larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gray@acunia.com \
/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).