<P> In UNIX - like operating systems, each 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 chroot system call . This is typically done to create 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 . FreeBSD offers a stronger jail () system call that enables operating - system - level virtualization and also serves security purposes to restrict which files a process may access to just a subset of the file system hierarchy . </P> <P> Some Unix systems support a directory below the root directory . Normally, "/ ..." points back to the same inode as "/", however, under MUNIX (de), this can be changed to point to a super-root directory, where remote trees can be mounted . 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". </P> <Dl> <Dt> / root </Dt> <Dd> On many Unixes, there is also a directory named / root . Confusingly, it is not a root directory in the sense of this article, but rather the home directory of the superuser (conventionally known as "root"). It is sometimes referred to as "slash root". </Dd> </Dl> <Dd> On many Unixes, there is also a directory named / root . Confusingly, it is not a root directory in the sense of this article, but rather the home directory of the superuser (conventionally known as "root"). It is sometimes referred to as "slash root". </Dd>

The top level of a linux directory structure can be represented by