A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading.
The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/
A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading.
The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/