Timeline for unix, difference between path starting with '/' and '//'
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2016 at 20:42 | comment | added | Mr. Lance E Sloan | Python's posixpath.normpath() function also retains double leading slashes. I tried to find out why, which brought me here. It's unfortunate that it does this, because what I've read indicates that double leading slashes is no longer important. | |
| Nov 8, 2011 at 11:52 | comment | added | janm | @jlliagre: I remember that from AT&T RFS. (Remote File System) Was in System V. | |
| Jul 10, 2011 at 23:58 | history | edited | sarnold | CC BY-SA 3.0 | bash, not Linux. D'oh. |
| Apr 29, 2011 at 10:11 | comment | added | Gilles 'SO- stop being evil' | Linux doesn't do anything about //, it's bash. | |
| Apr 29, 2011 at 9:39 | comment | added | jlliagre | I remember that double slash to allow remote file system access in an early system V implementation (Utek V & DFS). The syntax was //servername/path. Just like Solaris automounter would use now /net/servername/path. | |
| Apr 29, 2011 at 8:50 | history | migrated | from stackoverflow.com (revisions) | ||
| Apr 29, 2011 at 2:23 | history | answered | sarnold | CC BY-SA 3.0 |