lkml.org 
[lkml]   [2004]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [BUG] FAT broken in 2.6.7-bk15
From
Date
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>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [W:0.055 / U:0.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site