From: ANDRE Sebastien <sebastien.andre@sxb.bsf.alcatel.fr>
To: eCos Discussion Mailing List <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] EL/IX discussion
Date: Mon, 21 May 2001 05:56:00 -0000 [thread overview]
Message-ID: <3B091066.8EBDDE12@sxb.bsf.alcatel.fr> (raw)
In-Reply-To: <200105211246.f4LCkiU30883@sheesh.cambridge.redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
Hello,
Thanks, yes i see that eCos is a single process system with a complete thread
activity gestion !!
it's not a major problem for us but now we must see with caution
what EL/IX level 1 functions we need and if we can use it !
So our goal is to ports few POSIX.1 applications ( Linux world applications) into
eCos and e don't know yet all features we need in POSIX functions.
best regards
ANDRE Sébastien.
Bart Veer a écrit :
> >>>>> "Andre" == ANDRE Sebastien <sebastien.andre@sxb.bsf.alcatel.fr> writes:
>
> Andre> So, i see that the current implementation of EL/IX Layer
> Andre> under eCos work only at level 1 (without all functions)
>
> Andre> So i want know if because it we can't create more than 1
> Andre> processus !? and if in 1 processus we can create
> Andre> differrents threads ?
>
> eCos was designed for systems where there is a single process
> containing multiple threads. In other words pthread_create() is
> supported, but not fork() or execve(). If you need multiple processes
> then you will need an OS that supports higher levels of EL/IX, for
> example some embedded Linux variant.
>
> Similarly, if you want to develop an application for Linux with the
> eventual goal of porting it to eCos, you need to restrict yourself to
> the appropriate level of EL/IX functionality.
>
> Bart
prev parent reply other threads:[~2001-05-21 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 5:14 ANDRE Sebastien
2001-05-21 5:46 ` Bart Veer
2001-05-21 5:56 ` ANDRE Sebastien [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=3B091066.8EBDDE12@sxb.bsf.alcatel.fr \
--to=sebastien.andre@sxb.bsf.alcatel.fr \
--cc=ecos-discuss@sources.redhat.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).