mirror of
https://github.com/samba-team/samba.git
synced 2025-01-08 21:18:16 +03:00
992f1e6b8f
add the 5 missing chapters from the HOWTO
and add jht's Samba by Example book.
(This used to be commit 9fb5bcb93e
)
68 lines
2.8 KiB
XML
68 lines
2.8 KiB
XML
<samba:parameter name="mangled names"
|
|
type="boolean"
|
|
context="S"
|
|
xmlns:samba="http://samba.org/common">
|
|
<description>
|
|
<para>This controls whether non-DOS names under UNIX
|
|
should be mapped to DOS-compatible names ("mangled") and made visible,
|
|
or whether non-DOS names should simply be ignored.</para>
|
|
|
|
<para>See the section on <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link> for
|
|
details on how to control the mangling process.</para>
|
|
|
|
<para>If mangling is used then the mangling algorithm is as follows:</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>The first (up to) five alphanumeric characters
|
|
before the rightmost dot of the filename are preserved, forced
|
|
to upper case, and appear as the first (up to) five characters
|
|
of the mangled name.</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>A tilde "~" is appended to the first part of the mangled
|
|
name, followed by a two-character unique sequence, based on the
|
|
original root name (i.e., the original filename minus its final
|
|
extension). The final extension is included in the hash calculation
|
|
only if it contains any upper case characters or is longer than three
|
|
characters.</para>
|
|
|
|
<para>Note that the character to use may be specified using
|
|
the <link linkend="MANGLINGCHAR"><parameter moreinfo="none">mangling char</parameter>
|
|
</link> option, if you don't like '~'.</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>The first three alphanumeric characters of the final
|
|
extension are preserved, forced to upper case and appear as the
|
|
extension of the mangled name. The final extension is defined as that
|
|
part of the original filename after the rightmost dot. If there are no
|
|
dots in the filename, the mangled name will have no extension (except
|
|
in the case of "hidden files" - see below).</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>Files whose UNIX name begins with a dot will be
|
|
presented as DOS hidden files. The mangled name will be created as
|
|
for other filenames, but with the leading dot removed and "___" as
|
|
its extension regardless of actual original extension (that's three
|
|
underscores).</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
|
|
<para>The two-digit hash value consists of upper case alphanumeric characters.</para>
|
|
|
|
<para>This algorithm can cause name collisions only if files
|
|
in a directory share the same first five alphanumeric characters.
|
|
The probability of such a clash is 1/1300.</para>
|
|
|
|
<para>The name mangling (if enabled) allows a file to be
|
|
copied between UNIX directories from Windows/DOS while retaining
|
|
the long UNIX filename. UNIX files can be renamed to a new extension
|
|
from Windows/DOS and will retain the same basename. Mangled names
|
|
do not change between sessions.</para>
|
|
</description>
|
|
<value type="default">yes</value>
|
|
</samba:parameter>
|