From: Bart Veer <bartv@cygnus.co.uk>
To: Stephane.Conversy@lri.fr
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: the hurd
Date: Wed, 22 Sep 1999 11:36:00 -0000 [thread overview]
Message-ID: <199909221835.TAA31005@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <37E8E569.178E445F@lri.fr>
>>>>> "Stephane" == Stephane Conversy <Stephane.Conversy@lri.fr> writes:
Stephane> Could ecos be the microkernel for the hurd, instead of
Stephane> mach ?
Not really. eCos is aimed at deeply embedded systems, so for example
there is no support for multiple processes, only multiple threads. The
hurd is intended as a fully-fledged Unix system. The basic
requirements are different and conflicting.
Stephane> Is it comparable to qnx ?
This would be a closer comparison than the hurd (even more so for
Neutrino), but there are still major differences. QNX still supports
multiple processes, memory protection, etc. and there are overheads
associated with those. Also qnx was developed mainly for PC-style
hardware, and support for other platforms is relatively new. eCos has
been designed right from the start to go into custom embedded hardware
and already supports quite a wide range of target processors.
There are also some rather significant differences when it comes to
licensing and open source issues.
Stephane> Would it be difficult to port posix apps on ecos ?
Right now we do not have a POSIX compatibility layer for eCos, so
porting POSIX apps is non-trivial. Such a layer is under
consideration, I cannot provide any more details just yet.
Bart Veer // eCos net maintainer
prev parent reply other threads:[~1999-09-22 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <938009717.11238.ezmlm@sourceware.cygnus.com>
1999-09-22 7:21 ` [ECOS] " Stephane Conversy
1999-09-22 11:36 ` Bart Veer [this message]
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=199909221835.TAA31005@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=Stephane.Conversy@lri.fr \
--cc=ecos-discuss@sourceware.cygnus.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).