Content deleted Content added
IznoRepeat (talk | contribs) m →File types: clean explicit et al, gen fixes |
Citation bot (talk | contribs) m Alter: title, isbn. Add: title-link, citeseerx. Removed parameters. | You can use this bot yourself. Report bugs here. | User-activated. |
||
Line 4:
[[File:Standard-unix-filesystem-hierarchy.svg|thumb|An overview of a [[Unix]] filesystem layout]]
In [[Unix]] and [[operating system]]s inspired by it, the [[file system]] is considered a central component of the operating system.<ref name=" Ritchie">{{cite journal |last1= Ritchie |first1= D.M. |authorlink1= Dennis Ritchie |last2= Thompson |first2= K. |authorlink2= Ken Thompson |title= The UNIX Time-Sharing System |journal= Bell System Tech. J. |volume= 57 |issue= 6 |pages= 1905–1929
As in other operating systems, the filesystem provides information storage and retrieval, and one of several forms of [[interprocess communication]], in that the many small programs that traditionally form a Unix system can store information in files so that other programs can read them, although [[Pipeline (Unix)|pipes]] complemented it in this role starting with the [[Research Unix|Third Edition]]. Also, the filesystem provides access to other resources through so-called ''[[device file]]s'' that are entry points to [[computer terminal|terminals]], [[computer printer|printers]], and [[computer mouse|mice]].
Line 20:
{{Main |Unix file types}}
The original Unix file system supported three types of files: ordinary files, [[Directory (computing)|directories]], and "special files", also termed device files.<ref name="Ritchie"/> The [[Berkeley Software Distribution]] (BSD) and [[UNIX System V|System V]] each added a file type to be used for [[interprocess communication]]: BSD added [[Berkeley sockets|sockets]],<ref name="43bsd">{{cite book |last1= Leffler|first1= Samuel J. |authorlink1= Samuel J Leffler |last2= McKusick |first2= Marshall Kirk|authorlink2= Marshall Kirk McKusick |last3= Karels |first3= Michael J. |authorlink3=Michael J. Karels |last4=Quarterman |first4= John S. |authorlink4= John Quarterman |title= The Design and Implementation of the
BSD also added [[symbolic link]]s (often termed "symlinks") to the range of file types, which are files that refer to other files, and complement hard links.<ref name="43bsd"/> Symlinks were modeled after a similar feature in [[Multics]],<ref name="FFS">{{cite web|last1=McKusick|display-authors=etal|first1=Marshall Kirk|title=A Fast Filesystem for Unix|url=https://docs.freebsd.org/44doc/smm/05.fastfs/paper.pdf|website=Freebsd.org|publisher=CSRG, UC Berkeley|accessdate=16 November 2016}}</ref> and differ from hard links in that they may span filesystems and that their existence is independent of the target object. Other Unix systems may support additional types of files.<ref>{{man|2|stat|Linux}}</ref>
Line 51:
|
:<code>/etc</code>
|Contains system-wide configuration files and system databases; the name stands for ''[[et cetera]]''.<ref name="upe">{{cite book |first1=Brian W. |last1=Kernighan |authorlink1=Brian Kernighan |first2=Rob |last2=Pike |authorlink2=Rob Pike |title=
|-
|
|