public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Cfowler <cfowler@outpostsentinel.com@>
To: Wil Taphoorn <wil@wtms.nl>,  <linux-mtd@lists.infradead.org>
Subject: RE: How to protect DoC 2000 from power fail?
Date: Mon, 18 Mar 2002 7:28:26 -0000	[thread overview]
Message-ID: <E16mwFW-0006c2-00@host3.hosting4everyone.com> (raw)


I do not use a journalling file system.  I load a ext2 fs into memory from a
raw file on DOC2000.  If you loose power then you just reboot.  No loss of
data.  Of course only config changes not the root fs.  I store config in a
shared memory sgement.  I only write it to DOC when the user issues the
'save' command.


--------- Original message --------
From: "Wil Taphoorn" <wil@wtms.nl>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: How to protect DoC 2000 from power fail?
Date: 03-18-02 12:23

Gentlemen,

I am looking for some rigid means of power fail protection
for a DoC 2000 based embedded system. From what I have read
so far I understand that almost any brand of journalling file
system should do well but, then again, those readings also
mention raw FLASH and not DoC, in other words, I think I am
lost. Would someone be so kind to enlighten me?

The system in question runs on a customized 486 SoC, boots
from EEPROM and loads LILO from DoC. The kernel uses initrd
to load the M-sys supplied DoC driver.

Thanks,
Wil

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2002-03-18 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18  7:28 Cfowler [this message]
2002-03-18 13:54 ` How to protect DoC 2000 from power fail? Wil Taphoorn
  -- strict thread matches above, loose matches on Subject: below --
2002-03-18 12:10 Wil Taphoorn
2002-03-18 13:10 ` David Woodhouse
2002-03-19 11:57   ` Charles Manning
2002-03-19 15:32     ` David Woodhouse

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=E16mwFW-0006c2-00@host3.hosting4everyone.com \
    --to=cfowler@outpostsentinel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wil@wtms.nl \
    /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