Difference between revisions of "File"
m (Avoid dab page) |
m (Correct cat) |
||
| 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}} |
Revision as of 20:30, 18 October 2018
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 records.
Although the file system may break up the contents of a file into different physical 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.)
