From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Ali Akcaagac <aliakc@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] FAT broken in 2.6.7-bk15
Date: Mon, 05 Jul 2004 14:02:32 +0900 [thread overview]
Message-ID: <87smc7yrkn.fsf@ibmpc.myhome.or.jp> (raw)
In-Reply-To: <1088979061.1277.6.camel@localhost>
Ali Akcaagac <aliakc@web.de> writes:
> The only thing NLS changes in a filesystem is special charakters for
> filenames but it doesn't change the technical structure of the FS
> itself so in worst case I only get some strange characters shown in
> filenames.
No, it's very unuseful. Probably it can't lookup, and it has possible
of filesystem corruption if you write.
If you want to do it, just read/write the partition directly.
> CONFIG_FAT_DEFAULT_CODEPAGE=437
> CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
You configured these, so fatfs will try to use it.
> # CONFIG_NLS_CODEPAGE_437 is not set
> CONFIG_NLS_CODEPAGE_850=m
> # CONFIG_NLS_ISO8859_1 is not set
> CONFIG_NLS_ISO8859_15=m
But you didn't install these. So fatfs couldn't do what you specified,
then fatfs logged it and returns error.
Looks like you want to the following config.
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-07-05 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 22:11 Ali Akcaagac
2004-07-04 22:17 ` Jesse Stockall
2004-07-05 5:02 ` OGAWA Hirofumi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 6:08 Ali Akcaagac
2004-07-05 4:50 Ali Akcaagac
2004-07-04 14:34 Ali Akcaagac
2004-07-04 16:36 ` OGAWA Hirofumi
2004-07-04 11:28 Ali Akcaagac
2004-07-04 12:18 ` Andries Brouwer
2004-07-04 13:44 ` Jesse Stockall
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=87smc7yrkn.fsf@ibmpc.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=aliakc@web.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®