max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-15 10:46:15 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update content-address.md (#11771)

Browse source 
Correct a few typos. Make explicit that FSO acronym refers to File System Object.
This commit is contained in:
Emil Petersen 2024-10-31 00:31:03 +01:00 committed by GitHub
parent 7362987182
commit 78aedda6bd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/manual/source/store/file-system-object/content-address.md
View file

@ -1,13 +1,13 @@
# Content-Addressing File System Objects # Content-Addressing File System Objects
For many operations, Nix needs to calculate [a content addresses](@docroot@/glossary.md#gloss-content-address) of [a file system object][file system object]. For many operations, Nix needs to calculate [a content addresses](@docroot@/glossary.md#gloss-content-address) of [a file system object][file system object] (FSO).
Usually this is needed as part of Usually this is needed as part of
[content addressing store objects](../store-object/content-address.md), [content addressing store objects](../store-object/content-address.md),
since store objects always have a root file system object. since store objects always have a root file system object.
But some command-line utilities also just work on "raw" file system objects, not part of any store object. But some command-line utilities also just work on "raw" file system objects, not part of any store object.
Every content addressing scheme Nix uses ultimately involves feeding data into a [hash function](https://en.wikipedia.org/wiki/Hash_function), and getting back an opaque fixed-size digest which is deemed a content address. Every content addressing scheme Nix uses ultimately involves feeding data into a [hash function](https://en.wikipedia.org/wiki/Hash_function), and getting back an opaque fixed-size digest which is deemed a content address.
The various *methods* of content addressing thus differ in how abstract data (in this case, a file system object and its descendents) are fed into the hash function. The various *methods* of content addressing thus differ in how abstract data (in this case, a file system object and its descendants) are fed into the hash function.
## Serialising File System Objects { #serial } ## Serialising File System Objects { #serial }
@ -25,7 +25,7 @@ For example, Unix commands like `sha256sum` or `sha1sum` will produce hashes for
### Nix Archive (NAR) { #serial-nix-archive } ### Nix Archive (NAR) { #serial-nix-archive }
For the other cases of [file system objects][file system object], especially directories with arbitrary descendents, we need a more complex serialisation format. For the other cases of [file system objects][file system object], especially directories with arbitrary descendants, we need a more complex serialisation format.
Examples of such serialisations are the ZIP and TAR file formats. Examples of such serialisations are the ZIP and TAR file formats.
However, for our purposes these formats have two problems: However, for our purposes these formats have two problems: