1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
<refentry id="vfs_catia.8">
<refmeta>
<refentrytitle>vfs_catia</refentrytitle>
<manvolnum>8</manvolnum>
<refmiscinfo class="source">Samba</refmiscinfo>
<refmiscinfo class="manual">System Administration tools</refmiscinfo>
<refmiscinfo class="version">4.1</refmiscinfo>
</refmeta>
<refnamediv>
<refname>vfs_catia</refname>
<refpurpose>translate illegal characters in Catia filenames</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>vfs objects = catia</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This VFS module is part of the
<citerefentry><refentrytitle>samba</refentrytitle>
<manvolnum>7</manvolnum></citerefentry> suite.</para>
<para>The Catia CAD package commonly creates filenames that
use characters that are illegal in CIFS filenames. The
<command>vfs_catia</command> VFS module implements a character
mapping so that these files can be shared with CIFS clients.
</para>
<para>This module is stackable.</para>
<para>The parameter "catia:mappings" specifies the mapping on a
per-character basis, see below.
</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<variablelist>
<varlistentry>
<term>catia:mappings = SERVER_HEX_CHAR:CLIENT_HEX_CHAR
</term>
<listitem>
<para>SERVER_HEX_CHAR specifies a 0x prefixed hexedecimal
character code that, when included in a Samba server-side
filename, will be mapped to CLIENT_HEX_CHAR for the CIFS
client.</para>
<para>The same mapping occurs in the opposite direction.
Multiple character mappings are separated by a comma.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>EXAMPLES</title>
<para>Map server-side quotation-marks (") to client-side diaeresis
(¨) on filenames in the [CAD] share:</para>
<programlisting>
<smbconfsection name="[CAD]"/>
<smbconfoption name="path">/data/cad</smbconfoption>
<smbconfoption name="vfs objects">catia</smbconfoption>
<smbconfoption name="catia:mappings">0x22:0xa8</smbconfoption>
</programlisting>
<para>Perform comprehensive mapping of common Catia filename characters:</para>
<programlisting>
<smbconfsection name="[CAD]"/>
<smbconfoption name="path">/data/cad</smbconfoption>
<smbconfoption name="vfs objects">catia</smbconfoption>
<smbconfoption name="catia:mappings">0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6</smbconfoption>
</programlisting>
<para>Server-side filename to be translated (Note that the path delimiter "/" is not used here):
</para>
<para>a\a:a*a?a"a<a>a|a</para>
<para>Resulting filename, as seen by the client:</para>
<para>aÿa÷a¤a¿a¨a«a»a¦a
</para>
</refsect1>
<refsect1>
<title>CAVEATS</title>
<para>Character mapping must work in BOTH directions (server ->
client and client -> server) to get unique and existing file names!
</para>
<para>A NOT working example:</para>
<programlisting>
<smbconfsection name="[CAD]"/>
<smbconfoption name="path">/data/cad</smbconfoption>
<smbconfoption name="vfs objects">catia</smbconfoption>
<smbconfoption name="catia:mappings">0x3a:0x5f</smbconfoption>
</programlisting>
<para>Here the colon ":" is mapped to the underscore "_".</para>
<para>Assuming a server-side filename "a:should_work", which is
translated to "a_should_work" for the client.</para>
<para>BUT the reverse mapping from client "a_should_work" to server
will result in "a:should:work" - something like "file not found"
will be returned.
</para>
</refsect1>
<refsect1>
<title>VERSION</title>
<para>This man page is correct for Samba versions from 3.5.0 to 4.0.6.
</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</para>
<para>New version written by Guenter Kukkukk kukks@samba.org</para>
</refsect1>
</refentry>
|
