From: "Markus Thiesmeyer" <mthi@gmx.de>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <mtd@infradead.org>
Subject: Is JFFS a full featured filesystem?
Date: Tue, 1 Aug 2000 18:15:31 +0200 [thread overview]
Message-ID: <002a01bffbd5$6e5da560$fd8907d4@gallien> (raw)
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
Hello,
I've integrated the JFFS into a 2.2.16 kernel and it works almost fine.
But I cannot use an editor like pico to create a file on a JFFS-filesystem. It leads to an serious error. Other operations like copying or moving files are no problem.
So I've written a small program which uses file-mapping to change given files. And the results were very strange: When I run this application it should open a file called map.txt and change the first bytes into the sequence "abcdef...xyz". But when I read the file after I've run that application, the file seems to be unchanged. Changes appear first when I unmount that fs and mount in again. Then the file looks like a concatenation of the unchanged and the changed version.
Is this a bug? And if it is a bug, is this a known bug?
regards
Markus Thiesmeyer
[-- Attachment #2: Type: text/html, Size: 1491 bytes --]
next reply other threads:[~2000-08-01 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 16:15 Markus Thiesmeyer [this message]
2000-08-01 18:08 ` Is JFFS a full featured filesystem? Philipp Rumpf
2000-08-02 11:13 ` Alexander Larsson
2000-08-02 12:11 ` David Woodhouse
2000-08-02 12:24 ` David Woodhouse
2000-08-02 13:45 ` Alexander Larsson
2000-08-02 13:52 ` David Woodhouse
2000-08-02 14:20 ` David Woodhouse
2000-08-02 15:33 ` Alexander Larsson
2000-08-02 16:58 ` Philipp Rumpf
2000-08-02 14:13 ` Alexander Larsson
2000-08-02 16:50 ` Philipp Rumpf
2000-08-02 18:06 ` Alexander Larsson
2000-08-02 19:36 ` Philipp Rumpf
2000-08-02 19:57 ` Alexander Larsson
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='002a01bffbd5$6e5da560$fd8907d4@gallien' \
--to=mthi@gmx.de \
--cc=dwmw2@infradead.org \
--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