> The problem root lies in the fact in some languages (notably russian)
> there is more then one widely used charset. In russian for example
> there are koi8-r, iso8859-5, cp866 and the infamous but widely used
> ms cp1251.
>
> Once you need to have access to some data with names using the second
> half of the ascii table the trouble arises. For example the situation
> i have here is that smbd provides the public share and people creates
> there some files originating with the cp1251 encoding. Myself having
> koi8-r as the system default charset naturally observe crap.
>
> The proposed and seemingly natural solution is to add a possibility
> to mount --bind the subtree with a filename charset conversion applied.
Will not work. Bindings do _NOT_ create extra superblock/dentry tree/etc.
and they are invisible to filesystem. E.g. to ->readdir().
(besides, filesystems playing with case conversions are bad enough, now
let's VFS try charset ones?)
-
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/