A path (or filepath, file path, pathname, or similar) is a text string that uniquely specifies an item in a hierarchical file system. Generally, a path is composed of directory names, special directory specifiers and optionally a filename, separated by delimiting text. The delimiter varies by operating system and in theory can be anything, but popular, modern systems use slash/, backslash\, or colon :.
A path can be either relative or absolute. A relative path includes information that is relative to a particular directory whereas an absolute path indicates a location relative to the system root directory, and therefore, does not depends on context like a relative path does. Often, a relative path is relative to the working directory. For example, in command ls f, f is a relative path to the file with that name in the working directory.
Paths are used extensively in computer science to represent the directory/file relationships common in modern operating systems and are essential in the construction of uniform resource locators (URLs).
Around 1970, Unix introduced the slash character ("/") as its directory separator.
Originally, MS-DOS did not support directories, but when adding the feature, using the Unix standard of slash was not a good option since many existing commands used slash as the switch prefix. For example, dir /w. In contrast, Unix uses dash - as the switch prefix. In this context, MS-DOS version 2.0 used backslash \ for the path delimiter since it is similar to slash but did not conflict with existing commands. This convention continued into Windows in its shell Command Prompt. Eventually, PowerShell, was introduced to Windows that is slash-agnostic, allowing the use of either slash in a path.[2][3]
Path syntax
The following table describes the syntax of paths in notable operating systems and with notable aspects by shell.
\ (relative to current working directory root) or [drive_letter]:\ or \\[server]\[sharename]\ or \\?\[drive_spec]:\ or\\?\UNC\[server]\[sharename]\ or \\.\[physical_device]\[4]
Japanese and Korean versions of Windows often display the '¥' character or the '₩' character instead of the directory separator. In such cases the code for a backslash is being drawn as these characters. Very early versions of MS-DOS replaced the backslash with these glyphs on the display to make it possible to display them by programs that only understood 7-bit ASCII (other characters such as the square brackets were replaced as well, see ISO 646, Windows Codepage 932 (Japanese Shift JIS), and Codepage 949 (Korean)). Although even the first version of Windows supported the 8-bit ISO-8859-1 character set which has the Yen sign at U+00A5, and modern versions of Windows supports Unicode which has the Won sign at U+20A9, much software will continue to display backslashes found in ASCII files this way to preserve backward compatibility.[8]
macOS, as a derivative of UNIX, uses UNIX paths internally. However, to preserve compatibility for software and familiarity for users, many portions of the GUI switch "/" typed by the user to ":" internally, and switch them back when displaying filenames (a ":" entered by the user is also changed into "/" but the inverse translation does not happen).
Paths in programming languages
Programming languages also use paths. E.g.: When a file is opened. Most programming languages use the path representation of the underlying operating system:
This direct access to the operating system paths can hinder the portability of programs. To support portable programs Java uses File.separator to distinguish between / and \ separated paths. Seed7 has a different approach for the path representation. In Seed7 all paths use the Unix path convention, independent of the operating system. Under windows a mapping takes place (e.g.: The path /c/users is mapped to c:\users).
Universal Naming Convention
The Microsoft universal naming convention (UNC), a.k.a. uniform naming convention, a.k.a. network path, specifies a syntax to describe the location of a network resource, such as a shared file, directory, or printer. A UNC path has the general form:
\\ComputerName\SharedFolder\Resource
Some Windows interfaces allow or require UNC syntax for WebDAV share access, rather than a URL. The UNC syntax is extended[9] with optional components to denote use of SSL and TCP/IP port number, a WebDAV URL of http[s]://HostName[:Port]/SharedFolder/Resource becomes
\\HostName[@SSL][@Port]\SharedFolder\Resource
When viewed remotely, the "SharedFolder" may have a name different from what a program on the server sees when opening "\SharedFolder". Instead, the SharedFolder name consists of an arbitrary name assigned to the folder when defining its "sharing".
Some Windows interfaces also accept the "Long UNC":
\\?\UNC\ComputerName\SharedFolder\Resource
Windows uses the following types of paths:
local file system (LFS), such as C:\File
universal naming convention (UNC), such as \\Server\Volume\File or /<internet resource name>[\Directory name] (at least in Windows 7 and later)
"long" device path such as \\?\C:\File or \\?\UNC\Server\Volume\File.[10] This path points to the local file namespace and \\.\ is a similar one that points to the local DOS device namespace. This format is also the "raw" or "uninterpreted" path, since it sends paths straight to the file system without converting / to \ and interpreting names like ...[4]
Since UNCs start with two backslashes, and the backslash is also used for string escaping and in regular expressions, this can result in extreme cases of leaning toothpick syndrome: an escaped string for a regular expression matching a UNC begins with 8 backslashes – \\\\\\\\ – because the string and regular expression both require escaping. This can be simplified by using raw strings, as in C#'s @"\\\\" or Python's r'\\\\', or regular expression literals, as in Perl's qr{\\\\}.
POSIX pathname definition
Most Unix-like systems use a similar syntax.[13]POSIX allows treating a path beginning with two slashes in an implementation-defined manner,[14] though in other cases systems must treat multiple slashes as single slashes.[15] Many applications on Unix-like systems (for example, scp, rcp, and rsync) use resource definitions such as:
hostname:/directorypath/resource
or URI schemes with the service name (here 'smb'):
smb://hostname/directorypath/resource
Examples
Unix
The following examples are for typical, Unix-based file systems:
Given the working directory is /home/mark/ and it contains subdirectory bobapples, relative paths to the subdirectory include ./bobapples and bobapples, and the absolute path is /home/mark/bobapples. A command to change the working directory to the subdirectory:
$ cdbobapples
If the working directory was /home/jo, then the relative path ../mark/bobapples specifies the subdirectory. The double dots .. indicates a move up the directory hierarchy one level to /home, the rest indicates moving down to mark and then boapples.
Unlike Unix that always has a single root directory, a Windows file system has a root for each storage drive. An absolute path includes a drive letter or uses the UNC format.
A UNC path (starting with \\?\) does not support slashes.[4]
A:\Temp\File.txt is an absolute path that specifies a file named File.txt in the directory Temp which is in the root of drive A::
C:..\File.txt is a relative path that specifies file File.txt located in the parent of the working directory on drive C::
Folder\SubFolder\File.txt is a relative path that specifies file File.txt in directory SubFolder which is in directory Folder which is in the working directory of the current drive:
File.txt is a relative path that specifies File.txt in the working directory:
The following uses a path with slashes for directory delimiter:
C:\>more < C:/Windows/system.ini ; for 16-bit app support[386Enh]woafont=dosapp.fonEGA80WOA.FON=EGA80WOA.FONEGA40WOA.FON=EGA40WOA.FONCGA80WOA.FON=CGA80WOA.FONCGA40WOA.FON=CGA40WOA.FON...
A path with forward slashes may need to be surrounded by double quotes to disambiguate from command-line switches. For example, dir /windows is invalid, but dir "/window" is valid. And cd is more lenient by allowing cd /windows.
Fully qualified file name– unambiguous name for an entity in a computing language containing an identifier and all enclosing namespacesPages displaying wikidata descriptions as a fallback
↑ Daley, R.C.; Neumann, P.G. (1965). "A general-purpose file system for secondary storage". Proceedings of the November 30--December 1, 1965, fall joint computer conference, Part I on XX - AFIPS '65 (Fall, part I). Vol.Part I. pp.213–229. doi:10.1145/1463891.1463915. S2CID16236414.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
