/is the very top of your filesystem. One notable example is cp which has a different behavior when using the -r option on OS X (BSD cp) and Linux (GNU cp).cp -r src/ dest will only copy the contents of src into dest when using BSD cp but will copy the direcory src itself into dest when using GNU cp. Even simple commands, like ls , mkdir , rm , and others are just small programs that usually live … Let's break it down: Line 4 - Let's see if the first command line argument is greater than 100; Line 6 and 7 - Will only get run if the test on line 4 returns true. For that matter case $1 in /*) ;; esac also works in bash and is a damn sight clearer than ${1:0:1} . If you type cd home/directory, that will only work if you are in location /, similarly, if you are in /home, you could type cd directory, but not cd /directory (because that doesn't exist, it's either /home/directory, or just directory from /home) * @param lower if non-zero, filename should be made lower-case. * Add support to dpkg-deb for reading the archive from standard input, except for --raw-extract which does not yet support it. the stringification of the proxied location looks like it was normalizing the path and prepending a slash. You can have as many commands here as you like. Usage Note 60745: Errors contain a double slash in the path when using DBMS=XLSX New WordPress 3.5.2 multisite (subdirectory) install is missing a slash when creating new blogs. * @param dir a directory path to prepend to the output filename. Since search engines are using a regular expression to decide that a non trailing slash extension is a directory reference, the results can be unpredictable and you are therefore better off using the proper directory path with a trailing slash. If non-zero, UNIX path seperators are used. Even though the OP asked specific for Linux, it may be worth noting that the OS or flavor of tools used may make a difference. * @param utf8 if non-zero, the internal CAB filename is encoded in UTF8. It's pretty straightforward. When you type a command into the command prompt in Linux, or in other Linux-like operating systems, all you're doing is telling it to run a program. If you want to get rid of "Removing leading `/' from member names" being printed to STDERR, but still want to leave off those leading slashes as tar wisely does by default, I saw an excellent solution here by commenter timsoft.. Furthermore, if both the slash and non-slash URLs are reachable, this breaks down. – mikeserv Jan 20 '16 at 7:03 * @param isunix if zero, MS-DOS path seperators are used in the internal * CAB filename. If you type cd /home/directory, you can do that from anywhere, because it is the full path.. Also, @ Maybe you should think about what your decision would mean for files. * Add ‘.mailmap’ to the default dpkg-source ignore lists. For the most part, repeated slahes in a path are equivalent to a single slash.This behavior is mandated by POSIX and most applications follow suit. The exception is that “a pathname that begins with two successive slashes may be interpreted in an implementation-defined manner” (but ///foo is equivalent to /foo).. Line 6 - The backslash ( \ ) in front of the single quote ( ' ) is needed as the single quote has a special meaning for bash and we don't want that special meaning. Closes: #616614 Based on a patch by Johannes Schauer . With ${1%"${1#/}"} if the first char is not a slash the expansion is null, but if it is a slash it expands only to the slash. It's pretty straightforward. that commit switched to copying the incoming request (which was being manually constructed from the parsed subresource path) as-is, which left the path missing a leading / Most unices don't do anything special with two initial slashes. * Set the SE Linux context on «dpkg-statoverride …