Editing Filename (section)

==Number of names per file==
Unix-like file systems allow a file to have more than one name; in traditional Unix-style file systems, the names are [[hard link]]s to the file's [[inode]] or equivalent. Windows supports hard links on [[NTFS]] file systems, and provides the command <code>fsutil</code> in Windows XP, and <code>mklink</code> in later versions, for creating them.<ref>{{cite web|title=Fsutil command description page|publisher=Microsoft.com|access-date=September 15, 2013|url=http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true|archive-url=https://web.archive.org/web/20131006013745/http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true|archive-date=October 6, 2013|url-status=dead}}</ref><ref>{{cite web|title=NTFS Hard Links, Directory Junctions, and Windows Shortcuts|url=http://www.flexhex.com/docs/articles/hard-links.phtml|work=Flex hex|publisher=Inv Softworks|access-date=March 12, 2011|archive-url=https://web.archive.org/web/20110711005950/http://www.flexhex.com/docs/articles/hard-links.phtml|archive-date=July 11, 2011|url-status=usurped}}</ref> Hard links are different from Windows [[Computer shortcut|shortcuts]], classic Mac OS/macOS [[Alias (Mac OS)|aliases]], or [[symbolic link]]s. The introduction of [[Long filename|LFN]]s with [[VFAT]] allowed filename aliases. For example, <code>longfi~1.???</code> with a maximum of eight plus three characters was a filename alias of "<code>long file name.???</code>" as a way to conform to 8.3 limitations for older programs.

This property was used by the move command algorithm that first creates a second filename and then only removes the first filename.

Other filesystems, by design, provide only one filename per file, which guarantees that alteration of one filename's file does not alter the other filename's file.