Editing Root directory (section)

==Unix-like systems==
Unix abstracts the nature of this tree hierarchy entirely and in Unix and Unix-like systems the root directory is denoted by the <code>/</code> (slash) sign. Though the root directory is conventionally referred to as <code>/</code>, the directory entry itself has no name{{snd}}  its path is the "empty" part before the initial directory separator character (<code>/</code>). All file system entries, including mounted file systems are "branches" of this root.<ref name=":1" />

===chroot===
In UNIX-like operating systems, each [[Process (computing)|process]] has its own idea of what the root directory is.  For most processes this is the same as the system's actual root directory, but it can be changed by calling the {{mono|[[chroot]]}} [[system call]].  This is typically done to create a secluded environment to run software that requires legacy libraries and sometimes to simplify software installation and debugging. Chroot is not meant to be used for enhanced security as the processes inside can break out.<ref>{{cite web |url=https://lwn.net/Articles/252794/ |title=What chroot() is really for |website=LWN.net |access-date=2014-02-12 |archive-date=2020-11-12 |archive-url=https://web.archive.org/web/20201112024828/https://lwn.net/Articles/252794/ |url-status=live }}</ref>

===Super-root===
{{See also|Newcastle Connection}}

Some Unix systems support a directory below the root directory. Normally, "/.." points back to the same [[inode]] as "/", however, under {{Interlanguage link multi|MUNIX|de}}, this can be changed to point to a super-root directory, where remote trees can be mounted.<ref name="Newcastle_1982">{{cite journal |title=The Newcastle Connection |author-last1=Brownbridge |author-first1=David R. |author-last2=Marshall |author-first2=Lindsay F. |author-last3=Randell |author-first3=Brian |author-link3=Brian Randell |journal=Software: Practice and Experience |volume=12 |year=1982 |doi=10.1002/spe.4380121206 |pages=1147–1162 |s2cid=1840438 |url=http://www.cs.ncl.ac.uk/publications/articles/papers/399.pdf |access-date=2016-08-16 |url-status=dead |archive-url=https://web.archive.org/web/20160816184205/http://www.cs.ncl.ac.uk/research/pubs/articles/papers/399.pdf |archive-date=2016-08-16 }}</ref><ref name="Callaghan_2000">{{cite book |author-last=Callaghan |author-first=Brent |title=NFS Illustrated |publisher=[[Addison Wesley]] |year=2000 |isbn=0-201-32570-5}}</ref>  If, for example, two workstations "pcs2a" and "pcs2b" were connected via "connectnodes" and "uunite" startup script, "/../pcs2b" could be used to access the root directory of "pcs2b" from "pcs2a".