From: Brian Austin <brian.austin@cirrus.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: Is eCos project still alive?
Date: Thu, 13 Dec 2007 15:08:00 -0000 [thread overview]
Message-ID: <1197554343.23701.1.camel@localhost.localdomain> (raw)
In-Reply-To: <fjqdba$7o2$1@ger.gmane.org>
Large technology companies release snapshots of OSS all the time.
Are you trying to promote something "better"?
troll.
On Thu, 2007-12-13 at 04:44 +0000, Grant Edwards wrote:
> On 2007-12-13, Loginov Alexander <aloginov@asmpt.com> wrote:
>
> > The question was very simple: why is the latest eCos release 5
> > years old?
>
> Because that's the last time somebody paid developers to do the
> work involved in a public "release".
>
> > Don't tell me about snapshots.
>
> If you don't want to hear answers, then don't ask questions.
>
> > This is just for eCos itself, for its further development,
>
> Nonsense.
>
> > because snapshots are always supposed to have bugs,
>
> Utter bullshit. They do have bugs, but so do releases. Neither
> is "supposed to have bugs".
>
> > sometimes even intentional, to help to debug other bugs.
>
> Bah. Nobody intentionally checks in bugs.
>
> > Have you ever heard about commercial companies that install
> > the latest Linux snapshots to their offices or to the
> > expensive products? Never. Just stable releases.
>
> There are no "stable releases" of Linux any more. Active
> development is being done in the "stable" tree. There are no
> more stable and development versions of Linux like there used
> to be.
>
> > I guess, you are not from the world of the commercial products
> > development.
>
> On the contrary, we are all from the world of commercial
> products development. That's what eCos is used for: developing
> commercial products. I've been using eCos to develop
> commercial products for 7+ years, and the lack of "releases"
> hasn't been even the least bit of a problem.
>
> If you feel you're not capable of working from a CVS repository
> and really want a "released" version, then that's what eCosPro
> is:
>
> http://www.ecoscentric.com/ecos/ecospro.shtml
>
> > The considerations here are a bit different than that in the
> > world of open-source software community.
>
> No, not really.
>
> > By the way, Linux is not RTOS and never will be. We have very
> > tough hard real-time requirements. So it is not for us. Many
> > great RTOSes in aviationa and military actually distinguish
> > between privilege levels (QNX, Integrity, LynuxOS, pikeOS,
> > etc). MMU usage is Ok in real-time if you use it properly (no
> > page swapping, page locking, etc.).
>
> Perhaps one of those RTOSes will meet your privilege management
> requirement better than eCos.
>
> --
> Grant
>
>
--
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:[~2007-12-13 14:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 3:31 Loginov Alexander
2007-12-13 8:07 ` Grant Edwards
2007-12-13 15:08 ` Brian Austin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 9:07 Loginov Alexander
2007-12-14 8:28 Loginov Alexander
2007-12-14 11:09 ` Chris Zimman
2007-12-13 9:46 Loginov Alexander
2007-12-13 9:50 ` Loginov Alexander
2007-12-13 15:15 ` Grant Edwards
2007-12-13 15:43 ` Chris Zimman
2007-12-13 17:40 ` Grant Edwards
2007-12-14 0:48 ` Bob Koninckx
2007-12-14 1:41 ` Grant Edwards
2007-12-14 6:38 ` Frank Pagliughi
2007-12-14 11:15 ` Chris Zimman
2007-12-14 11:20 ` Andrew Lunn
2007-12-14 12:00 ` Paul D. DeRocco
2007-12-14 17:11 ` Grant Edwards
2007-12-14 18:10 ` Brian Austin
2007-12-17 11:29 ` Jonathan Larmour
2007-12-14 16:34 ` Brian Austin
2007-12-14 16:39 ` Sergei Organov
2007-12-14 18:47 ` Grant Edwards
2007-12-13 20:06 ` Mike Arthur
2007-12-14 13:47 ` Ilija Koco
2007-12-13 4:27 [ECOS] " Loginov Alexander
2007-12-13 6:15 ` [ECOS] " Grant Edwards
2007-12-13 3:02 Anthony Tonizzo
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=1197554343.23701.1.camel@localhost.localdomain \
--to=brian.austin@cirrus.com \
--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).