From 838c0e44942e55847d64612e50c708bb55e8e36a Mon Sep 17 00:00:00 2001 From: Philippe Pittoli Date: Sat, 1 Feb 2025 15:08:35 +0100 Subject: [PATCH] Minor update. --- paper/Makefile.in | 1 + paper/paper.ms | 11 +++++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/paper/Makefile.in b/paper/Makefile.in index 7afea14..29a49e1 100644 --- a/paper/Makefile.in +++ b/paper/Makefile.in @@ -47,6 +47,7 @@ REFER_OPTS ?= -PS -e -p $(BIBLIOGRAPHY) REFER = refer $(REFER_OPTS) # -k => iconv conversion (did it ever worked?) +# -t => tbl preprocessor # -ms => ms macro # -U => unsafe (because of PDF inclusion) # -Tpdf => output device is PDF diff --git a/paper/paper.ms b/paper/paper.ms index 82edf17..8af7d17 100644 --- a/paper/paper.ms +++ b/paper/paper.ms @@ -1132,12 +1132,12 @@ For example, several applications with networking features might run on a comput If one of these applications is successfully attacked, the attacker shouldn't be able to access other services data or user data. Same thing for shared computers, one user shouldn't be able to see other users' data. Therefore, the most widespread form of security comes from filesystem permissions, enabling a user (or a group of users) to access (or to be denied from accessing) specific data (files and directories). -Those permissions include the right to read, to modify or to execute a file, to list or to remove files from a directory, to create or remove directories and a few other permissions. +Those permissions include the right to read, to modify or to execute a file, to list or to remove files from a directory, to create or to remove directories and a few other permissions. Extended permissions and attributes exist but are out-of-scope. Beside permissions, encryption also brings some kind of security. In this case, the point is to prevent attackers from accessing protected data despite retrieving files. -Some advanced filesystems can encrypt file individually, others provide the encryption of a whole partition, both methods having their pros and cons. +Some advanced filesystems can encrypt files individually, others provide the encryption of a whole partition, both methods having their pros and cons. .BULLET .KS @@ -1147,10 +1147,13 @@ While storage devices mostly impose physical limitations, a filesystem may be wa .KE Depending on the scenario, the filesystem might become wasteful or slow. -Some filesystems cannot handle a huge number of small files (from hundreds of millions to billions) without wasting a lot of space, such as ext4 which doesn't have block suballocation: once a file and has at least one byte in it, it takes a 4kB block size and 4k-1 bytes are wasted. +Some filesystems cannot handle a huge number of small files (from hundreds of millions to billions) without wasting a lot of space, such as ext4 which doesn't have block suballocation: once a file and has at least one byte in it, it takes a 4kB block size and 4kB-1 bytes are wasted. So, worst case scenario, data rate is .FRAC 1 4000 -(huge waste) meaning that a 1GB of data would require an entire 4TB hard drive (without even taking the inodes' size into account). +(huge waste) meaning that a 1GB of data would require an entire 4TB hard drive\*[*] (without even taking the inodes' size into account). +.FOOTNOTE1 +Ext4 can integrate up to 60 bytes of data into an extended inode. +.FOOTNOTE2 .BULLET .KS