public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: Bob Brusa <roe.werner@outlook.com>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Does FreeBSD stack support multiple IP addresses?
Date: Wed, 24 Feb 2016 16:47:00 -0000	[thread overview]
Message-ID: <20160224164703.GA30439@grante> (raw)
In-Reply-To: <DUB109-W90FA10A08EE609DF0BB91393A50@phx.gbl>

On Wed, Feb 24, 2016 at 01:31:51PM +0100, Bob Brusa wrote:

> Hi,I am kind of misusing this email for the following reason:I sent
> a question to ecos-discuss@ecos.sourceware.com - and got it back as
> undeliverable. Then I sent a mail to their help desk and got it back
> as undeliverable. Third then, I sent a mail to
> ecos-maintainers@ecos.sourceware.com. It came back as well.This
> triggers the question:
>
> Is the open source version of eCos dead?

I'd have to say pretty much yes.  There is very little development or
maintenance work being done on the open-source tree.  Browsing the CVS
repository via the web doesn't appear to work (the entire "net" tree
seems to have vanished), though I think checking out a copy via CVS on
the command line does still work.

I've been using eCos in one product line for 15 years, and that
product line is still being updated and still doing well.  We'll stick
with eCos as we continue to maintain/update those products.  But, I
wouldn't recommend the open-source version of eCos for a brand-new
product.  One area where several people have expressed concern is the
FreeBSD-based network stack.  It's based on a very old FreeBSD
snapshot and hasn't seen much in the way of updates since then.  I've
commited fixes for a few problems and to keep GCC happy, but AFAIK,
nobody has ever made any consistent effort to bring over fixes and
updates made by the "upstream" FreeBSD maintainers.

That said, I don't know anything about the commercial version from
eCos Centric and have no experience with it.

> Do you know something about this?

If you're asking about the mailing list problem you encountered, I
don't know anything about that...

-- 
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

  parent reply	other threads:[~2016-02-24 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 16:35 [ECOS] " Grant Edwards
2016-02-19 18:12 ` [ECOS] " Grant Edwards
2016-02-22  8:50   ` Lambrecht Jürgen
2016-02-22 15:05     ` Grant Edwards
2016-02-23  8:09       ` Lambrecht Jürgen
2016-02-23 15:59         ` Grant Edwards
     [not found]           ` <DUB109-W90FA10A08EE609DF0BB91393A50@phx.gbl>
2016-02-24 16:47             ` Grant Edwards [this message]
2016-03-15 11:10           ` Lambrecht Jürgen
2016-03-15 14:56             ` Grant Edwards

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=20160224164703.GA30439@grante \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=roe.werner@outlook.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).