From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1718 invoked by alias); 13 Dec 2007 14:01:28 -0000 Received: (qmail 1705 invoked by uid 22791); 13 Dec 2007 14:01:26 -0000 X-Spam-Check-By: sourceware.org Received: from mail-dub.bigfish.com (HELO mail161-dub-R.bigfish.com) (213.199.154.10) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Dec 2007 14:01:11 +0000 Received: from mail161-dub (localhost.localdomain [127.0.0.1]) by mail161-dub-R.bigfish.com (Postfix) with ESMTP id AF246290C4D for ; Thu, 13 Dec 2007 14:01:07 +0000 (UTC) X-BigFish: VP X-MS-Exchange-Organization-Antispam-Report: OrigIP: 141.131.3.20;Service: EHS Received: by mail161-dub (MessageSwitch) id 1197554465612862_17308; Thu, 13 Dec 2007 14:01:05 +0000 (UCT) Received: from mail1.cirrus.com (mail1.cirrus.com [141.131.3.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail161-dub.bigfish.com (Postfix) with ESMTP id 08D50174008F for ; Thu, 13 Dec 2007 14:01:04 +0000 (UTC) Received: from CLMSG-01.ad.cirrus.com ([198.61.95.37]) by mail1.cirrus.com (8.12.11.20060308/8.12.11) with ESMTP id lBDE0OAs005244 for ; Thu, 13 Dec 2007 08:00:24 -0600 Received: from [198.61.92.105] ([198.61.92.105]) by CLMSG-01.ad.cirrus.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Dec 2007 08:01:00 -0600 From: Brian Austin Cc: ecos-discuss@sources.redhat.com In-Reply-To: References: Content-Type: text/plain Date: Thu, 13 Dec 2007 15:08:00 -0000 Message-Id: <1197554343.23701.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit 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/msg00059.txt.bz2 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 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