diff options
| author | s-ol <s-ol@users.noreply.github.com> | 2019-12-18 16:29:29 +0000 |
|---|---|---|
| committer | s-ol <s-ol@users.noreply.github.com> | 2019-12-18 16:29:29 +0000 |
| commit | a1923464f33480eed90d69e4f54cf3c4b6274599 (patch) | |
| tree | 05b15fa1d6a1d65982830ec5755d4878e7864c15 /root/articles | |
| parent | fix server-side CORS HTTP requests (diff) | |
| download | mmm-a1923464f33480eed90d69e4f54cf3c4b6274599.tar.gz mmm-a1923464f33480eed90d69e4f54cf3c4b6274599.zip | |
more sidenote/reference formatting
Diffstat (limited to 'root/articles')
| -rw-r--r-- | root/articles/mmmfs/mmmfs/text$markdown.md | 6 | ||||
| -rw-r--r-- | root/articles/mmmfs/references/$order | 1 | ||||
| -rw-r--r-- | root/articles/mmmfs/references/linux-exec/text$bibtex | 7 |
3 files changed, 12 insertions, 2 deletions
diff --git a/root/articles/mmmfs/mmmfs/text$markdown.md b/root/articles/mmmfs/mmmfs/text$markdown.md index 214a720..c40b5db 100644 --- a/root/articles/mmmfs/mmmfs/text$markdown.md +++ b/root/articles/mmmfs/mmmfs/text$markdown.md @@ -18,14 +18,16 @@ Some metadata, such as file size and access permissions, is associated with each but notably the type of data is generally not actually stored in the filesystem, but determined loosely based on multiple heuristics depending on the system and context. Some notable mechanism are: + + - Suffixes in the name are often used to indicate what kind of data a file should contain. However there is no standardization over this, and often a suffix is used for multiple incompatible versions of a file-format. - Many file-formats specify a specific data-pattern either at the very beginning or very end of a given file. On unix systems the `libmagic` database and library of these so-called *magic constants* is commonly used to guess the file-type based on these fragments of data. -- on UNIX systems files to be executed are checked by a variety of methods to determine which format would fit. +- <div class="sidenote"><mmm-embed raw path="../references/linux-exec"></mmm-embed></div> + on UNIX systems files to be executed are checked by a variety of methods to determine which format would fit. for script files, the "shebang" (`#!`) can be used to specify the program that should parse this file in the first line of the file. - [@TODO: src: https://stackoverflow.com/questions/23295724/how-does-linux-execute-a-file] It should be clear already from this short list that to mainstream operating systems, as well as the applications running on them, the format of a file is almost completely unknown and at best educated guesses can be made. diff --git a/root/articles/mmmfs/references/$order b/root/articles/mmmfs/references/$order index 0360e6f..59baea4 100644 --- a/root/articles/mmmfs/references/$order +++ b/root/articles/mmmfs/references/$order @@ -1,2 +1,3 @@ xerox-star unix +linux-exec diff --git a/root/articles/mmmfs/references/linux-exec/text$bibtex b/root/articles/mmmfs/references/linux-exec/text$bibtex new file mode 100644 index 0000000..6d52aa8 --- /dev/null +++ b/root/articles/mmmfs/references/linux-exec/text$bibtex @@ -0,0 +1,7 @@ +@web{23295968, + title = {How does Linux execute a file?}, + url = {https://stackoverflow.com/a/23295724/1598293}, + publisher = {stackoverflow.com}, + note = {answered by osgx}, + visited = {2019-12-18}, +} |
