public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] JFFS2 alternative
Date: Tue, 30 Jun 2009 08:47:00 -0000	[thread overview]
Message-ID: <4A49D0F8.4060807@mlbassoc.com> (raw)
In-Reply-To: <c09652430906292347u624c3d93u4724bf1b56b9df40@mail.gmail.com>

Øyvind Harboe wrote:
> JFFS2 is fine for smaller file systems, but it breaks down completely
> on large file systems.
> 

What do you mean "it breaks down completely"?

> Does anyone know of viable eCos alternatives to JFFS2?
> 
> LogFS is GPL v2 without exception, so that would make the application
> linked with eCos GPL. Ditto for UBIFS.
> 
> I guess it's no good to create a loadable eCos module either. Even
> if that would allow our application to work with any filing system. It would
> be a poorly veiled attempt at circumventing GPL, wouldn't it?
> 
> GPL is problematic because the work in question is under NDA.
> 

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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:[~2009-06-30  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  6:47 Øyvind Harboe
2009-06-30  7:37 ` Andrew Lunn
2009-06-30  8:47 ` Gary Thomas [this message]
2009-06-30  8:52   ` Øyvind Harboe

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=4A49D0F8.4060807@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=oyvind.harboe@zylin.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).