public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Tim Riker <Tim@Rikers.org>
To: Herman Oosthuysen <Herman@WirelessNetworksInc.com>
Cc: Abraham vd Merwe <abraham@2d3d.co.za>,
	Vipin Malik <mtd-linux@embeddedlinuxworks.com>,
	MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: safe flash filesystem
Date: Thu, 21 Jun 2001 11:54:38 -0600	[thread overview]
Message-ID: <3B3234DE.7497B63C@Rikers.org> (raw)
In-Reply-To: 001a01c0fa64$7bb97840$1501a8c0@Herman

Hmm... would it not be easier to just use ext2 on a CF card?

less $$ and more flexibility no?

Herman Oosthuysen wrote:
> 
> Hi guys,
> 
> We are currently exploring a product by Tevero in Norway:
> http://www.tevero.no/products/fdc/ to use instead of the still buggy JFFS2.
> Price is USD2500, which isn't bad.  It appears to be the cheapest commercial
> FFS available.
> 
> Cheers,
> 
> Herman
> http://www.WirelessNetworksInc.com
> 
> ----- Original Message -----
> From: Abraham vd Merwe <abraham@2d3d.co.za>
> To: Vipin Malik <mtd-linux@embeddedlinuxworks.com>
> Cc: MTD for Linux <linux-mtd@lists.infradead.org>
> Sent: Thursday, June 21, 2001 8:35 AM
> Subject: Re: safe flash filesystem
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

  reply	other threads:[~2001-06-21 18:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 10:54 safe flash filesystem Abraham vd Merwe
2001-06-21 13:43 ` Vipin Malik
2001-06-21 13:57   ` Abraham vd Merwe
2001-06-21 14:29     ` Vipin Malik
2001-06-21 14:35       ` Abraham vd Merwe
2001-06-21 15:05         ` Vipin Malik
2001-06-21 15:36           ` Chris Read
2001-06-21 15:09         ` Joakim Tjernlund
2001-06-21 15:34           ` Vipin Malik
2001-06-21 19:34             ` Joakim Tjernlund
2001-06-21 19:47             ` Joakim Tjernlund
2001-06-21 15:11         ` Herman Oosthuysen
2001-06-21 17:54           ` Tim Riker [this message]
2001-06-21 19:43             ` Vipin Malik
2001-06-21 19:35               ` Tim Riker
2001-06-21 19:56                 ` Vipin Malik
2001-06-21 21:17                   ` Kyle Harris
2001-07-03 23:53                     ` On the "safe filesystem" and write() topic Bjorn Wesen
2001-07-04 14:10                       ` Vipin Malik
2001-07-05 18:16                         ` Bjorn Wesen
2001-07-06 13:40                           ` Vipin Malik
2001-07-07  9:25                             ` Bjorn Wesen
2001-07-07 13:06                               ` Vipin Malik
2001-06-21 21:26         ` safe flash filesystem Russ Dill
2001-06-22  8:22           ` Abraham vd Merwe
     [not found]           ` <20010622102154.E1828@crystal.2d3d.co.za>
2001-06-22 17:23             ` Russ Dill
2001-06-25  7:45               ` Abraham vd Merwe
2001-06-25  7:59                 ` Russ Dill
2001-06-25 14:11                   ` Vipin Malik
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 16:05 Vipin Malik

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=3B3234DE.7497B63C@Rikers.org \
    --to=tim@rikers.org \
    --cc=Herman@WirelessNetworksInc.com \
    --cc=abraham@2d3d.co.za \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mtd-linux@embeddedlinuxworks.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