From 42233f5c5876c1fde9ada8aaac0f1f568aacc4df Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Wed, 9 Apr 2003 15:53:41 +0000 Subject: Finish conversion of Filenames (This used to be commit 8e0f0dbbbcb3179f1a868c72720e4eaf530e0a79) --- docs/docbook/smbdotconf/filename/mangledmap.xml | 41 +++++++------ docs/docbook/smbdotconf/filename/manglednames.xml | 71 ++++++++++++---------- docs/docbook/smbdotconf/filename/maparchive.xml | 32 +++++----- docs/docbook/smbdotconf/filename/maphidden.xml | 24 ++++---- docs/docbook/smbdotconf/filename/mapsystem.xml | 24 ++++---- docs/docbook/smbdotconf/filename/statcache.xml | 21 ++++--- docs/docbook/smbdotconf/filename/vetofiles.xml | 60 +++++++++--------- .../smbdotconf/filename/vetooplockfiles.xml | 43 ++++++------- 8 files changed, 170 insertions(+), 146 deletions(-) (limited to 'docs/docbook') diff --git a/docs/docbook/smbdotconf/filename/mangledmap.xml b/docs/docbook/smbdotconf/filename/mangledmap.xml index abe6c031e0..e790fa877d 100644 --- a/docs/docbook/smbdotconf/filename/mangledmap.xml +++ b/docs/docbook/smbdotconf/filename/mangledmap.xml @@ -1,23 +1,26 @@ - - mangled map (S) - This is for those who want to directly map UNIX - file names which cannot be represented on Windows/DOS. The mangling - of names is not always what is needed. In particular you may have - documents with file extensions that differ between DOS and UNIX. - For example, under UNIX it is common to use .html - for HTML files, whereas under Windows/DOS .htm - is more commonly used. + + + This is for those who want to directly map UNIX + file names which cannot be represented on Windows/DOS. The mangling + of names is not always what is needed. In particular you may have + documents with file extensions that differ between DOS and UNIX. + For example, under UNIX it is common to use .html + for HTML files, whereas under Windows/DOS .htm + is more commonly used. - So to map html to htm - you would use: + So to map html to htm + you would use: - mangled map = (*.html *.htm) + mangled map = (*.html *.htm) - One very useful case is to remove the annoying ;1 - off the ends of filenames on some CDROMs (only visible - under some UNIXes). To do this use a map of (*;1 *;). + One very useful case is to remove the annoying ;1 + off the ends of filenames on some CDROMs (only visible + under some UNIXes). To do this use a map of (*;1 *;). - Default: no mangled map - Example: mangled map = (*;1 *;) - - + Default: no mangled map + + Example: mangled map = (*;1 *;) + + diff --git a/docs/docbook/smbdotconf/filename/manglednames.xml b/docs/docbook/smbdotconf/filename/manglednames.xml index 41592b3159..4ec088d16f 100644 --- a/docs/docbook/smbdotconf/filename/manglednames.xml +++ b/docs/docbook/smbdotconf/filename/manglednames.xml @@ -1,21 +1,26 @@ - - mangled names (S) - 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. + + + 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. - See the section on - NAME MANGLING for details on how to control the mangling process. + See the section on NAME MANGLING for + details on how to control the mangling process. - If mangling is used then the mangling algorithm is as follows: + If mangling is used then the mangling algorithm is as follows: - - The first (up to) five alphanumeric characters + + + 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. + of the mangled name. + - A tilde "~" is appended to the first part of the mangled + + 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 @@ -24,35 +29,39 @@ Note that the character to use may be specified using the mangling char - option, if you don't like '~'. + option, if you don't like '~'. + - The first three alphanumeric characters of the final + + 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). + in the case of "hidden files" - see below). + - Files whose UNIX name begins with a dot will be + + 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). - + underscores). + + - The two-digit hash value consists of upper case - alphanumeric characters. + The two-digit hash value consists of upper case alphanumeric characters. - 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. + 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. - 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. + 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. - Default: mangled names = yes - - + Default: mangled names = yes + + diff --git a/docs/docbook/smbdotconf/filename/maparchive.xml b/docs/docbook/smbdotconf/filename/maparchive.xml index 18f39791aa..b44088efe3 100644 --- a/docs/docbook/smbdotconf/filename/maparchive.xml +++ b/docs/docbook/smbdotconf/filename/maparchive.xml @@ -1,17 +1,19 @@ - - map archive (S) - This controls whether the DOS archive attribute - should be mapped to the UNIX owner execute bit. The DOS archive bit - is set when a file has been modified since its last backup. One - motivation for this option it to keep Samba/your PC from making - any file it touches from becoming executable under UNIX. This can - be quite annoying for shared source code, documents, etc... + + + This controls whether the DOS archive attribute + should be mapped to the UNIX owner execute bit. The DOS archive bit + is set when a file has been modified since its last backup. One + motivation for this option it to keep Samba/your PC from making + any file it touches from becoming executable under UNIX. This can + be quite annoying for shared source code, documents, etc... - Note that this requires the create mask - parameter to be set such that owner execute bit is not masked out - (i.e. it must include 100). See the parameter - create mask for details. + Note that this requires the create mask + parameter to be set such that owner execute bit is not masked out + (i.e. it must include 100). See the parameter + create mask for details. - Default: map archive = yes - - + Default: map archive = yes + + diff --git a/docs/docbook/smbdotconf/filename/maphidden.xml b/docs/docbook/smbdotconf/filename/maphidden.xml index 2b0266c23e..4c1a932788 100644 --- a/docs/docbook/smbdotconf/filename/maphidden.xml +++ b/docs/docbook/smbdotconf/filename/maphidden.xml @@ -1,13 +1,15 @@ - - map hidden (S) - This controls whether DOS style hidden files - should be mapped to the UNIX world execute bit. + + + This controls whether DOS style hidden files + should be mapped to the UNIX world execute bit. - Note that this requires the create mask - to be set such that the world execute bit is not masked out (i.e. - it must include 001). See the parameter - create mask for details. + Note that this requires the create mask + to be set such that the world execute bit is not masked out (i.e. + it must include 001). See the parameter + create mask for details. - Default: map hidden = no - - + Default: map hidden = no + + diff --git a/docs/docbook/smbdotconf/filename/mapsystem.xml b/docs/docbook/smbdotconf/filename/mapsystem.xml index ead629971a..7fe50bb19f 100644 --- a/docs/docbook/smbdotconf/filename/mapsystem.xml +++ b/docs/docbook/smbdotconf/filename/mapsystem.xml @@ -1,13 +1,15 @@ - - map system (S) - This controls whether DOS style system files - should be mapped to the UNIX group execute bit. + + + This controls whether DOS style system files + should be mapped to the UNIX group execute bit. - Note that this requires the create mask - to be set such that the group execute bit is not masked out (i.e. - it must include 010). See the parameter - create mask for details. + Note that this requires the create mask + to be set such that the group execute bit is not masked out (i.e. + it must include 010). See the parameter + create mask for details. - Default: map system = no - - + Default: map system = no + + diff --git a/docs/docbook/smbdotconf/filename/statcache.xml b/docs/docbook/smbdotconf/filename/statcache.xml index ee94081483..ee2a48732e 100644 --- a/docs/docbook/smbdotconf/filename/statcache.xml +++ b/docs/docbook/smbdotconf/filename/statcache.xml @@ -1,10 +1,13 @@ - - stat cache (G) - This parameter determines if smbd - 8 will use a cache in order to - speed up case insensitive name mappings. You should never need - to change this parameter. + + + This parameter determines if smbd + 8 will use a cache in order to + speed up case insensitive name mappings. You should never need + to change this parameter. - Default: stat cache = yes - - + Default: stat cache = yes + + diff --git a/docs/docbook/smbdotconf/filename/vetofiles.xml b/docs/docbook/smbdotconf/filename/vetofiles.xml index faef2040b9..073645c611 100644 --- a/docs/docbook/smbdotconf/filename/vetofiles.xml +++ b/docs/docbook/smbdotconf/filename/vetofiles.xml @@ -1,36 +1,38 @@ - - veto files(S) - This is a list of files and directories that - are neither visible nor accessible. Each entry in the list must - be separated by a '/', which allows spaces to be included - in the entry. '*' and '?' can be used to specify multiple files - or directories as in DOS wildcards. + + + This is a list of files and directories that + are neither visible nor accessible. Each entry in the list must + be separated by a '/', which allows spaces to be included + in the entry. '*' and '?' can be used to specify multiple files + or directories as in DOS wildcards. - Each entry must be a unix path, not a DOS path and - must not include the unix directory - separator '/'. + Each entry must be a unix path, not a DOS path and + must not include the unix directory + separator '/'. - Note that the case sensitive option - is applicable in vetoing files. + Note that the case sensitive option + is applicable in vetoing files. - One feature of the veto files parameter that it - is important to be aware of is Samba's behaviour when - trying to delete a directory. If a directory that is - to be deleted contains nothing but veto files this - deletion will fail unless you also set - the delete veto files parameter to - yes. + One feature of the veto files parameter that it + is important to be aware of is Samba's behaviour when + trying to delete a directory. If a directory that is + to be deleted contains nothing but veto files this + deletion will fail unless you also set + the delete veto files parameter to + yes. - Setting this parameter will affect the performance - of Samba, as it will be forced to check all files and directories - for a match as they are scanned. + Setting this parameter will affect the performance + of Samba, as it will be forced to check all files and directories + for a match as they are scanned. - See also hide files - and - case sensitive. + See also hide files + and + case sensitive. - Default: No files or directories are vetoed. - + Default: No files or directories are vetoed. + Examples: ; Veto any files containing the word Security, @@ -42,5 +44,5 @@ veto files = /*Security*/*.tmp/*root*/ ; creates. veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ - - + + diff --git a/docs/docbook/smbdotconf/filename/vetooplockfiles.xml b/docs/docbook/smbdotconf/filename/vetooplockfiles.xml index 0c817c97f8..e7c683a518 100644 --- a/docs/docbook/smbdotconf/filename/vetooplockfiles.xml +++ b/docs/docbook/smbdotconf/filename/vetooplockfiles.xml @@ -1,24 +1,25 @@ - - veto oplock files (S) - This parameter is only valid when the oplocks - parameter is turned on for a share. It allows the Samba administrator - to selectively turn off the granting of oplocks on selected files that - match a wildcarded list, similar to the wildcarded list used in the - veto files - parameter. + + + This parameter is only valid when the + oplocks + parameter is turned on for a share. It allows the Samba administrator + to selectively turn off the granting of oplocks on selected files that + match a wildcarded list, similar to the wildcarded list used in the + veto files + parameter. - Default: No files are vetoed for oplock - grants + Default: No files are vetoed for oplock grants - You might want to do this on files that you know will - be heavily contended for by clients. A good example of this - is in the NetBench SMB benchmark program, which causes heavy - client contention for files ending in .SEM. - To cause Samba not to grant oplocks on these files you would use - the line (either in the [global] section or in the section for - the particular NetBench share : + You might want to do this on files that you know will + be heavily contended for by clients. A good example of this + is in the NetBench SMB benchmark program, which causes heavy + client contention for files ending in .SEM. + To cause Samba not to grant oplocks on these files you would use + the line (either in the [global] section or in the section for + the particular NetBench share : - Example: veto oplock files = /*.SEM/ - - - + Example: veto oplock files = /*.SEM/ + + -- cgit