public inbox for elix@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Andrew Lunn <lunn@ma.tech.ascom.ch>
Cc: elix@sourceware.cygnus.com
Subject: Re: EL/IX Stands for?
Date: Tue, 28 Sep 1999 05:40:00 -0000	[thread overview]
Message-ID: <37F0B5AC.B8E1447A@cygnus.co.uk> (raw)
In-Reply-To: <199909281222.OAA02495@biferten.ma.tech.ascom.ch>

Andrew Lunn wrote:
> 
> > Embedded Linux/POSIX.
> 
> This suggests its going to be tied to Linux when in fact the API could
> and will be implemented on other OSs such as eCos. I can see from a
> marketing and opensource viewpoint its good to have Linux in there but
> you don't want to make people think its limit to just Linux.

I'm sure there's an element of that :-). But there is a technical rationale
- there are areas of useful functionality in Linux that aren't in POSIX. Or
there are certain things where the implementation can behave in different,
but equally standards-compliant ways.

When that happens, the general principle would be to follow the behaviour of
Linux. Not Solaris, or SCO, or anything else. Linux.

Of course there would be times when maintaining 100% semantic compatibility
with Linux would be silly for an embedded system. That's one of the reasons
this list exists - to define and refine the API so we get a consensus on
what these types of things would be.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

      reply	other threads:[~1999-09-28  5:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-28  0:10 Andrew Lunn
1999-09-28  5:14 ` Jonathan Larmour
1999-09-28  5:22   ` Andrew Lunn
1999-09-28  5:40     ` Jonathan Larmour [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=37F0B5AC.B8E1447A@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=elix@sourceware.cygnus.com \
    --cc=lunn@ma.tech.ascom.ch \
    /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).