'/' is one of illegal filename characters on Windows.
So a filename containing '/' is always mangled regardless of your
character settings (including CAP settings).
This behavior comes from limitation of Windows filesystems and by
design.
From: Adam C?cile <adam.cecile@linbox.com>
Subject: Re: Samba VFS CAP, hope some help
Date: Fri, 08 Jun 2007 11:43:19 +0200
Hi,
I tried to create a file containing / through netatalk. It works fine
and the '/' is replaced by :2f on the filesystem.
My samba charsets settings are not set, I tried different settings but
it didn't change anything.
Which charset am I supposed to use ? My filesystem is using utf-8.
TAKAHASHI Motonobu a ?crit :> From: Adam C?cile wrote:
>
>> Hello,
>>
>> The problem is that when I enable vfs_cap, file containing
":xx"
>> characters are not available anymore on samba. When it's
disabled,their
>> filenames are mangled.
>> Do you think it could be a samba charset issue ?
>>
>
> I tested on Samba 3.0.25a with the smb.conf shown below:
>
> -----
> [share]
> vfs objects = cap
> writeable = yes
> path = /var/tmp/test1
> -----
>
> Writing a non-ascii filename, it becomes CAP-nized. For example,
> "<0x82be><0x82df>.txt" is encoded with
":82:be:82:df.txt".
>
> Please tell me what character you tried and what is your "dos
charset"
> and "unix charset" settings?
-----
TAKAHASHI, Motonobu (monyo) monyo@monyo.com
http://www.monyo.com/
