From 1f2cfa5951b293599a9055f52ba9f5198f36a3d0 Mon Sep 17 00:00:00 2001 From: Simo Sorce Date: Mon, 31 Mar 2008 20:13:01 +0000 Subject: Better doc mount.cifs. Original commit msg from Jeff: This patch adds a section to the mount.cifs manpage to clarify how mount.cifs treats delimiters and when it autoconverts them from one type to another. It also has it state that the use of forward slash as a delimiter is preferred and why. Signed-off-by: Jeff Layton (This used to be commit ec87ae251bea2a8b63febcf3ceab8754d564bdeb) --- docs/manpages-3/mount.cifs.8.xml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/manpages-3/mount.cifs.8.xml b/docs/manpages-3/mount.cifs.8.xml index 4c86c45ffa..b62bd3c892 100644 --- a/docs/manpages-3/mount.cifs.8.xml +++ b/docs/manpages-3/mount.cifs.8.xml @@ -498,6 +498,17 @@ port 445 is tried and if no response then port 139 is tried. + + SERVICE FORMATTING AND DELIMITERS + + + It's generally preferred to use forward slashes (/) as a delimiter in service names. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\) unconditionally. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can't be automatically converted in the same way. + + + mount.cifs will attempt to convert backslashes to forward slashes where it's able to do so, but it cannot do so in any path component following the sharename. + + + ENVIRONMENT VARIABLES -- cgit