Filesystem Hierarchy Standard - Revision history

NeilArmstrong: Added glossary link to Configuration~

2012-11-01T20:02:15Z

Added glossary link to Configuration~

← Older revision		Revision as of 20:02, 1 November 2012
Line 128:		Line 128:
	in /var/opt. See the section on /var/opt for more information.		in /var/opt. See the section on /var/opt for more information.

	Host-specific configuration files must be installed in /etc/opt. See the		Host-specific [[configuration~\|Configuration]] files must be installed in /etc/opt. See the
	section on /etc for more information.		section on /etc for more information.

Line 222:		Line 222:
	<pre>Directory Description		<pre>Directory Description
	bin Local binaries		bin Local binaries
	etc Host-specific system configuration for local binaries		etc Host-specific system [[configuration~\|Configuration]] for local binaries
	games Local game binaries		games Local game binaries
	include Local C header files		include Local C header files

NeilArmstrong: Added Glossary Link to Historical~

2012-03-03T00:56:24Z

Added Glossary Link to Historical~

← Older revision		Revision as of 00:56, 3 March 2012
Line 34:		Line 34:
	• Enumerating exceptions to the principles, and		• Enumerating exceptions to the principles, and

	• Enumerating specific cases where there has been historical conflict.		• Enumerating specific cases where there has been [[historical~\|Historical]] conflict.

	The FHS document is used by:		The FHS document is used by:
Line 78:		Line 78:
	Shareable files can be stored on one host and used on several others. Typically, however, not all files in the filesystem hierarchy are shareable and so each system has local storage containing at least its unshareable files. It is convenient if all the files a system requires that are stored on a foreign host can be made available by mounting one or a few directories from the foreign host.		Shareable files can be stored on one host and used on several others. Typically, however, not all files in the filesystem hierarchy are shareable and so each system has local storage containing at least its unshareable files. It is convenient if all the files a system requires that are stored on a foreign host can be made available by mounting one or a few directories from the foreign host.

	Static and variable files should be segregated because static files, unlike variable files, can be stored on read-only media and do not need to be backed up on the same schedule as variable files. Historical UNIX-like filesystem hierarchies contained both static and variable files under both /usr and /etc. In order to realize the advantages mentioned above, the /var hierarchy was created and all variable files were transferred from /usr to /var. Consequently /usr can now be mounted read-only (if it is a separate filesystem). Variable files have been transferred from /etc to /var over a longer period as technology has permitted.		Static and variable files should be segregated because static files, unlike variable files, can be stored on read-only media and do not need to be backed up on the same schedule as variable files. [[Historical~\|Historical]] UNIX-like filesystem hierarchies contained both static and variable files under both /usr and /etc. In order to realize the advantages mentioned above, the /var hierarchy was created and all variable files were transferred from /usr to /var. Consequently /usr can now be mounted read-only (if it is a separate filesystem). Variable files have been transferred from /etc to /var over a longer period as technology has permitted.

	Here is an example of a FHS-compliant system. (Other FHS-compliant layouts are possible.)		Here is an example of a FHS-compliant system. (Other FHS-compliant layouts are possible.)

NeilArmstrong: Added glossary link to Application~

2012-02-22T14:57:05Z

Added glossary link to Application~

← Older revision		Revision as of 14:57, 22 February 2012
Line 38:		Line 38:
	The FHS document is used by:		The FHS document is used by:

	• Independent software suppliers to create ~~applications~~ which are FHS		• Independent software suppliers to create [[application~\|Application]]s which are FHS
	compliant, and work with distributions which are FHS complaint,		compliant, and work with distributions which are FHS complaint,

Line 51:		Line 51:

	• FHS addresses issues where file placements need to be coordinated between		• FHS addresses issues where file placements need to be coordinated between
	multiple parties such as local sites, distributions, ~~applications~~,		multiple parties such as local sites, distributions, [[application~\|Application]]s,
	documentation, etc.		documentation, etc.

Line 96:		Line 96:
	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━		━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
	== The Root Filesystem ==		== The Root Filesystem ==
	=== /opt : Add-on application software packages ===		=== /opt : Add-on [[application~\|Application]] software packages ===

	==== Purpose ====		==== Purpose ====

	/opt is reserved for the installation of add-on application software packages.		/opt is reserved for the installation of add-on [[application~\|Application]] software packages.

	A package to be installed in /opt must locate its static files in a separate /		A package to be installed in /opt must locate its static files in a separate /
Line 142:		Line 142:

	==== Rationale: ====		==== Rationale: ====
	The use of /opt for add-on software is a well-established practice in the UNIX community. The System V Application Binary Interface [AT&T 1990], based on the System V Interface Definition (Third Edition), provides for an /opt structure very similar to the one defined here.		The use of /opt for add-on software is a well-established practice in the UNIX community. The System V [[Application~\|Application]] Binary Interface [AT&T 1990], based on the System V Interface Definition (Third Edition), provides for an /opt structure very similar to the one defined here.

	The Intel Binary Compatibility Standard v. 2 (iBCS2) also provides a similar structure for /opt.		The Intel Binary Compatibility Standard v. 2 (iBCS2) also provides a similar structure for /opt.

Ssw0213: Cut down and create TOC

2008-11-18T18:57:01Z

Cut down and create TOC

Show changes

Ssw0213: Text version

2008-11-13T03:47:19Z

Text version

Show changes

DavidWhitten at 02:12, 11 November 2008

2008-11-11T02:12:26Z

← Older revision		Revision as of 02:12, 11 November 2008
Line 1:		Line 1:
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">		<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
	<HTML		<HTML>
	><HEAD		<HEAD
	><script>function PrivoxyWindowOpen(){return(null);}</script><TITLE		><script>function PrivoxyWindowOpen(){return(null);}</script><TITLE
	>Filesystem Hierarchy Standard</TITLE		>Filesystem Hierarchy Standard</TITLE

Ssw0213 at 17:14, 10 November 2008

2008-11-10T17:14:00Z

Show changes