From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14439 invoked by alias); 13 Dec 2007 06:15:36 -0000 Received: (qmail 14372 invoked by uid 22791); 13 Dec 2007 06:15:36 -0000 X-Spam-Check-By: sourceware.org Received: from outgoing3.asmpt.com (HELO aaants127.aaaex.asmpt.com) (202.0.181.227) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Dec 2007 06:15:26 +0000 Received: from aaants96.aaaex.asmpt.com ([10.1.1.96]) by aaants127.aaaex.asmpt.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Dec 2007 14:15:21 +0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Dec 2007 09:50:00 -0000 Message-ID: From: "Loginov Alexander" To: "Grant Edwards" , , X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] Re: Is eCos project still alive? X-SW-Source: 2007-12/txt/msg00053.txt.bz2 Message-ID: <20071213095000.6_4dvQ0mLwKlS86sgb4ew12PckQrEtan_L9o_C2KAqs@z> ......... > Because that's the last time somebody paid developers to do the > work involved in a public "release". Thanks for your comments. Now a bit clearer why the releases are not available. But it is quite strange: there is eCosCentric but no releases. Normally the commercial companies that are at the back of the open-source project, do this job. Check RTEMS for example.=20 ........ > If you don't want to hear answers, then don't ask questions. Irrelevant note. Not all the phrases are to be understood directly. There are idioms in each language. That was one of them. Don't take it out of the context. In that context it meant: "I don't think so" if you wish ........ > Utter bullshit. They do have bugs, but so do releases. Neither > is "supposed to have bugs". My mistake, I meant to say "expected to have bugs". Here is the standard note from a standard open-source project CVS tree: "...the CVS code is always moving in features and stability. While very attempt is made to keep the CVS head working on all targets, but there are no any guarantees".=20 ....... > Bah. Nobody intentionally checks in bugs. Depends. In the area of safety-critical systems, it is a standard debugging methodology: you intentionally introduce bugs in the systems to see how it can recover itself .=20 ... ... > 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. Linux itself - yes. But not its distros. The new releases are normally produced every 3-6 months. ... ... > 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. That is your personal experience and your personal area of expertise in particular commercial product area. Products that are expected to have high reliability standards are rarely developed from CVS software snapshots. > 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 Thanks. I have already checked it. Definitely, if we stick to eCos we will buy the support from eCosCentric. > Perhaps one of those RTOSes will meet your privilege management > requirement better than eCos. Unfortunately, they are either too expensive (the royalty fees would cost us thousand or even millions of dollars) and most of them normally don't provide source code. If they do provide it, then it costs another hundreds of thousands. By the way, do you now any more-or-less free RTOS that provides support for privilege levels and process protection? Thanks. Best, Alex -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss