@ -122,6 +122,7 @@ BaguetteOS does not suffer from cumbersome historical decisions: no overly engin
Online documentation and man pages are written in Markdown (thanks to `zola` and [scdoc][scdoc]).
Every tool has a man page: no man page = no integration in base.
<aname="inspiration"></a>
## Inspiration
- [CRUX][crux], [alpine][alpine]: simple-to-understand Linux systems
@ -131,6 +132,7 @@ Every tool has a man page: no man page = no integration in base.
- [suckless][suckless] and [cat-v][cat-v]: documentation and tools, all about simplicity, code readability and re-usability
- [morpheus][morpheus]: OS based on statically compiled tools
<aname="why-not-x"></a>
## Why not use another system?
An operating system is mostly a kernel handling the hardware and a bunch of small programs (named `coreutils`) doing basic tasks (copy a file, list the content of a directory, print the date, etc.).
The usual way to provide software is to package it into a distribution, then provide it as *the* OS version of the software.
> Packages can support having multiple versions installed simultaneously.
> This is useful for libraries which may have changed interfaces between versions.
> For example, the python compiler can be installed in both versions 2.7 and 3.5 in parallel.
> This feature is called slotting.
The usual way to provide a software is to package it into a distribution, then provide it as *the* OS version of the software.
In the long run, software and libraries change, which is no big deal since maintainers verify the consistency of the different versions provided by the OS.
Maintainers' job is to verify that all programs have the right library versions under their OS.
