public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Juan Gonzo <kayemmess@yahoo.ca>
To: MTD Mailing List <mtd@infradead.org>
Subject: persistence of files using jffs
Date: Thu, 13 Jul 2000 16:09:52 -0400 (EDT)	[thread overview]
Message-ID: <20000713200952.1875.qmail@web5302.mail.yahoo.com> (raw)

Me again.  More questions.  Oy!

Our system is using a ramdisk (with a prebuilt image)
as its root device.  Before I boot up the system I burn
a small image into flash (this image was created with
mkfs.jffs and contains a couple of files and one directory).

So, the system boots up and I do the following:
   (1) mknod /dev/mtd3 b 31 3   (mtd3 is where the fs 'partition' is,
                                 using examples from nora.c)
   (2) mount -t jffs /dev/mtd3 /mnt

The mount is successful and after this I can see the files and
directory I burned into flash.  I can copy another file from the
ramdisk to this mount.  And I can 'umount /mnt' successfully as
well.

However, when I cycle power on the system,
any *new* files I create or copy into this space are lost.

Everytime I restart the system I have to 'mknod /dev/mtd3', does
this have something to do with that?  What am I missing to
get the new files to be present when I remount JFFS?

Thanks,
   -- kelly



_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2000-07-13 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-13 20:09 Juan Gonzo [this message]
2000-07-14  7:37 ` persistence of files using jffs David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-07-14 23:09 Juan Gonzo
2000-07-15 13:26 ` 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=20000713200952.1875.qmail@web5302.mail.yahoo.com \
    --to=kayemmess@yahoo.ca \
    --cc=mtd@infradead.org \
    /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