The term
fully qualified file name (or
FQFN) means a file on a computer whose exact name is completely specified such that it is unambiguous and cannot be mistaken for any other file on that computer system.{{cite web • On
Unix-style systems,
MS-DOS, and
Windows, the name "sample" refers to a file in the
current directory named "sample". If the current directory is changed, then the file referred to by the name "sample" is different. If you start the filename with "/" indicating the
root directory as in "/Users/Name/sample", then on Unix this is a fully qualified file name. So, for example, instead of referring to ./foo/bar/baz.sh in /home/user/quz, which uses a relative pathname, the fully qualified name would be /home/user/quz/foo/bar/baz.sh.{{cite book • Also on the above systems, some programs such as the command-line shell will search a
path for a file. Inserting a leading (back)slash, as in "./name", will stop the searching of the path. This is a
partially qualified name, but not a fully qualified name as it still depends on the current directory. A fully qualified name, because it contains (back)slashes, will always stop a path search. • On the
mainframe operating system
MUSIC/SP, if one asks for the file name "X", one is making an unqualified reference either to the file X in the user's library, or to the file X in the common library if the user does not have a file named X and one does exist in the common library. If, however, one were to refer to "*COM:X" one is using a fully qualified file name reference to the file X in the common library even if they have a different file named X in their library. Similarly, a reference to "*USR:X" would mean the file in their own library, and "MA45:X" would be a fully qualified file name referring to the specific file X in the library of user MA45. • On the
RSTS/E operating system on the
PDP-11 minicomputer, specifying a file "X.X" would refer to a file in one's own directory. Referring to "$X.X" would be referring to the file "[1,2]X.X" but to fully qualify the file name, one would have to indicate the device, so "SY:[46,145]MYFILE.TXT", "SY:$X.X", or "SY:[1,2]X.X" (the last two examples meaning the same thing) would be a fully qualified file name under RSTS/E. • On the
UNIVAC Series 90 mainframe operating system
VS/9, specifying a file "X" could mean either the file X in the account of that user, or could mean the file X in the library of the system manager, $TSOS. However, specifying "$S0103.X" would be a fully qualified file name. • This term can also include the case where one prefixes a fully qualified file name with a specific computer name as a prefix to a file name (where the particular system permits referencing a file on another system), so long as the exact name is unambiguous.
Path names Fully qualified path name (
FQPN) is the full path of a resource, directory or file, stored in a
computer. It is composed by the full path to the resource and its syntax depends on the
operating system. In
Unix-like operating systems it is represented in the following form: /root/path-to/file[OR]directory, while in
DOS and
Microsoft Windows it is represented in the following form: [Drive]:\path-to\file.ext[OR]directory. FQPN is also used in
Networking and takes the following form: \root\
FQDN\path-to\file.ext[OR]directory, where /root/ is the
root directory, the first or top-most directory in a hierarchy, and, in this case, the rooted
tree; FQDN is the fully qualified domain name or node. It is also used in
bootstrapping,
computer programming and in
computer science referencing. == Domain names ==