public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "leeyang" <leeyang@ycig.com>
To: <linux-mtd@lists.infradead.org>
Subject: mmap on jffs2(2.4.19)
Date: Mon, 21 Apr 2003 14:01:55 +0800	[thread overview]
Message-ID: <002a01c307cb$86dad630$cc00a8c0@ycigrnd> (raw)

I need mmap a "writable" file,
and it fails.My code is as below:

 fd = open("/usr/dat/sot.dat",O_RDWR,FILEMODE);
 
 ptr1=mmap(NULL,filesize,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0);

fd returns 3,but ptr1 returns -1 and 
mmap errno says invalid agrument.
These codes runs well on ext2.

Then I checked the old maillist and source code.
It seems jffs2 currently not support mmap writable.
Am I right?

In
http://lists.infradead.org/pipermail/linux-mtd/2002-July/005436.html
dw said "some kind of mtd_remap()",
Has it been implemented now? 


BTW:
My last msg was blocked by 
"Message has a suspicious header"

I'm not sure the reason,I guess 
the smtp server I used is broken,
and I change to another one,
hope this one works.

leeyang

                 reply	other threads:[~2003-04-21  6:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='002a01c307cb$86dad630$cc00a8c0@ycigrnd' \
    --to=leeyang@ycig.com \
    --cc=linux-mtd@lists.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