Bug 9472 - some files cannot be created with mfsymlinks
Summary: some files cannot be created with mfsymlinks
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: libsmbclient (show other bugs)
Version: unspecified
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-06 15:21 UTC by Marcus Moeller
Modified: 2012-12-20 13:11 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Moeller 2012-12-06 15:21:15 UTC 
I am using mfsymlinks to be able to use a basic set of functionality on a share that does not support Unix Extensions.

Sadly, it's not possible to create files like this:

touch '"foo"'

touch 'foo:bar' (which is even worse as it results in a file called foo)
Comment 1 Volker Lendecke 2012-12-13 16:31:51 UTC 
Well, " and : are illegal characters in the SMB world. Without Unix extensions I do not see how this could work. I know that the OS/X finder plays very nasty tricks to map : to some otherwise unused Unicode character. If you create a file with : in Finder and then ls -l that file in a terminal, something else shows up. That's exactly to work around the : " <> and so on being illegal chars.
Comment 2 Michael Adam 2012-12-20 13:10:55 UTC 
mount.cifs has the "mapchars" option that maps the characters : ? | * < > to the unicode remap range above 0xF000 (see the mount.cifs) manpage.

For the : character, this should help.

The " character might be a different problem.