File - Revision history

Jnc: +cat

2025-04-18T16:03:22Z

+cat

← Older revision		Revision as of 16:03, 18 April 2025
Line 12:		Line 12:

	[[Category: Basics]]		[[Category: Basics]]
			[[Category: File Systems]]

Jnc: /* See also */ +UNIX file system

2025-04-18T16:01:48Z

Jnc: Avoid redir

2025-04-16T12:04:04Z

Avoid redir

← Older revision		Revision as of 12:04, 16 April 2025
Line 1:		Line 1:
	A '''file''' is an agglomeration of information - perhaps data (including [[source code]], which is data from the perspective of the computer), sometimes [[object code]] - saved on [[secondary storage]], usually in a [[file system]].		A '''file''' is an agglomeration of information - perhaps data (including [[source code]], which is data from the perspective of the computer), sometimes [[object code]] - saved on [[secondary storage]], usually in a [[file system]].

	Depending on the [[operating system]], a file may be presented to the user as a simple array of bytes or words (as in all [[~~Unix~~]] systems), or it may have a more structured form, with [[record]]s.		Depending on the [[operating system]], a file may be presented to the user as a simple [[array]] of bytes or words (as in all [[UNIX]] systems), or it may have a more structured form, with [[record]]s.

	Although the file system may break up the contents of a file into different physical [[disk\|blocks]], scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)		Although the file system may break up the contents of a file into different physical [[disk\|blocks]], scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)

Jnc: +cat

2018-12-16T21:06:48Z

+cat

← Older revision		Revision as of 21:06, 16 December 2018
Line 6:		Line 6:

	{{semi-stub}}		{{semi-stub}}

			[[Category: Basics]]

Jnc: Correct cat

2018-10-18T19:30:48Z

Correct cat

← Older revision		Revision as of 19:30, 18 October 2018
Line 5:		Line 5:
	Although the file system may break up the contents of a file into different physical [[disk\|blocks]], scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)		Although the file system may break up the contents of a file into different physical [[disk\|blocks]], scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)

	{{stub}}		{{semi-stub}}

Jnc: Avoid dab page

2018-05-14T21:38:30Z

Avoid dab page

← Older revision		Revision as of 21:38, 14 May 2018
Line 3:		Line 3:
	Depending on the [[operating system]], a file may be presented to the user as a simple array of bytes or words (as in all [[Unix]] systems), or it may have a more structured form, with [[record]]s.		Depending on the [[operating system]], a file may be presented to the user as a simple array of bytes or words (as in all [[Unix]] systems), or it may have a more structured form, with [[record]]s.

	Although the file system may break up the contents of a file into different physical [[~~block~~]]s, scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)		Although the file system may break up the contents of a file into different physical [[disk\|blocks]], scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)

	{{stub}}		{{stub}}

Jnc: An OK start

2017-09-29T13:16:32Z

An OK start

New page

A '''file''' is an agglomeration of information - perhaps data (including [[source code]], which is data from the perspective of the computer), sometimes [[object code]] - saved on [[secondary storage]], usually in a [[file system]].

Depending on the [[operating system]], a file may be presented to the user as a simple array of bytes or words (as in all [[Unix]] systems), or it may have a more structured form, with [[record]]s.

Although the file system may break up the contents of a file into different physical [[block]]s, scattered across a [[disk]], this is purely internal, to simplify space allocation, and not visible to the user, to whom the file still appears as a unitary object. (In fact, some file systems, such as the [[BSD Fast File System]] do make an effort to keep the blocks of a file in close physical proximity, for access speed reasons.)

{{stub}}

← Older revision		Revision as of 16:01, 18 April 2025
Line 6:		Line 6:

	{{semi-stub}}		{{semi-stub}}

			==See also==

			* [[UNIX file system]]

	[[Category: Basics]]		[[Category: Basics]]