From: David Woodhouse <dwmw2@infradead.org>
To: Jarkko Lavinen <jarkko.lavinen@nokia.com>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 case insensitivity
Date: Tue, 27 Jan 2004 11:13:28 +0000 [thread overview]
Message-ID: <1075202008.1633.26.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20040127100613.GA16078@angel.research.nokia.com>
On Tue, 2004-01-27 at 12:06 +0200, Jarkko Lavinen wrote:
> How difficult it would be to add support for file name case
> insensitivity to JFFS2?
Fairly, It's ugly, evil and painful when FAT tries to do it, and it
wouldn't be any less so in JFFS2. I suspect you'd be far better off
doing it in userspace.
In the kernel, you end up with 'interesting' dcache coherency problems
and charset problems and generally end up going insane.
What precisely is the problem you're trying to solve?
--
dwmw2
next prev parent reply other threads:[~2004-01-27 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 10:06 JFFS2 case insensitivity Jarkko Lavinen
2004-01-27 11:13 ` David Woodhouse [this message]
2004-01-27 13:48 ` Jarkko Lavinen
2004-01-27 15:18 ` David Woodhouse
2004-01-27 22:49 ` Charles Manning
2004-01-28 6:13 ` David Woodhouse
2004-02-20 21:01 ` David Woodhouse
2004-01-27 13:48 ` 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=1075202008.1633.26.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=jarkko.lavinen@nokia.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