I believe some things are being confused here. The moment you mention Samba shares, you get into the realm of URIs. These are well defined and do have requirements about the early slashes. These are specified in RFC 3986 Section 3, where you have either one or two slashes as part of the syntax following the scheme name. Then, everything between there and the question mark or hash mark is scheme specific.
This is separate from the question of what is a valid path that can be passed to open(2) or any of the other system calls that operate on paths. These take an arbitrary number of slashes as equivalent to one slash. For example you can do ls -l ///////////////// and get the same result as ls -l /. And finally, if you invoke the file scheme with file:/ , as defined by RFC 1738 Section 3.10, the syntax after that is another slash, optional hostname, slash, path, so would fall under the above rule. This is easily tested if you open file:////////etc/////asound.conf in a browser. http://www.ietf.org/rfc/rfc3986.txt http://www.ietf.org/rfc/rfc1738.txt ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
