[lkml]   [2000]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectNLS handling in Filesystem code
   From: Meelis Roos <>
Date: Sun, 20 Aug 2000 13:27:40 +0200

TTo> * If all the ISO NLS's are modules, there can be an
TTo> undefined ref to CONFIG_NLS_DEFAULT in inode.c (Dale Amon)

Somebody please recheck Config in about NLS. ISOFS has different
condition than other FS'es IIRC (noticed it in test7-pre5 smb nls
support patch).

While updating the Linux 2.4 issues list (a new updated list will be out
shortly), it looks like this item has still not been addressed. To
whomever is maintainning the NLS, ISOFS, FAT, and SMBFS filesystems:
(I wasn't able to identify maintainers for all of these)

ISOFS ignores CONFIG_NLS_DEFAULT, and hardcodes the use of iso8859-1 as
the default. Is this the correct behaviour?

The FAT and SMBFS filesystems will fail to compile of CONFIG_NLS_DEFAULT
is not defined which will be the case if the user answers "no" to
CONFIG_NLS question. I assume there should be some better fallbacks for
this case?

- Ted
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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