2023-07-05 11:06:16 +02:00
|
|
|
# File
|
|
|
|
|
|
2024-04-02 23:19:23 +02:00
|
|
|
A file is a pool of data in the `filesystem`. On
|
2024-03-30 19:22:45 +01:00
|
|
|
userlevel, it's referenced using a name, a
|
2024-04-02 23:19:23 +02:00
|
|
|
[hardlink](hardlink.md) to the file.
|
2023-07-05 11:06:16 +02:00
|
|
|
|
|
|
|
|
If a file is not referenced anymore (number of hardlinks to it drops to
|
2024-04-02 23:19:23 +02:00
|
|
|
1) then the space allocated for that file is re-used, unless it's still
|
2023-07-05 11:06:16 +02:00
|
|
|
used by some process.
|
|
|
|
|
|
|
|
|
|
The file-data splits into actual payload (file contents) and some
|
|
|
|
|
metadata like filesize, filemode or timestamps. The metadata is stored
|
2024-04-02 23:19:23 +02:00
|
|
|
in the `inode`.
|
2023-07-05 11:06:16 +02:00
|
|
|
|
2024-04-02 23:19:23 +02:00
|
|
|
Strictly spoken, a [hardlink](hardlink.md) (also called
|
|
|
|
|
\"filename\") points to the `inode` which organizes a
|
2023-07-05 11:06:16 +02:00
|
|
|
file, not to the file itself.
|
|
|
|
|
|
|
|
|
|
## See also
|
|
|
|
|
|
2024-04-02 23:19:23 +02:00
|
|
|
- [filetimes](filetimes.md)
|
|
|
|
|
- [hardlink](hardlink.md)
|
