~to add to ve4ernik's website - Publications ( http://sites.google.com/view/ve4ernik ) :
(this file is humorously named after the file 'modest-proposal.txt' by http://cr.yp.to which is about: 'A modest proposal for reducing mail traffic 19961213 D. J. Bernstein, [email protected]' ... However, this proposal here is about an extending update to how the LINUX/UNIX/*NIX FHS (filesystem hierarchy standard) is implemented in the Linux kernel and all Linux-derived kernels.)
A Modest Proposal For An Extending Update to the Default Linux kernel filesystem-hierarchy, by [email protected] :
v0.2.2-BETA (this whole article is to be read as a semi-joke to be considered seriously...)
Add a built-in (&later backward-compatible, forwards-compatible, and even backported to older releases/versions/editions of the Linux kernel!) Linux kernel module that sets the user-preferred FHS/FSHS (LSB) - filesystem hierarchy (dir tree structure):
0 (default: default Linux FHS; UNIX/*NIX-compatible {possible POSIX & X11-server & maybe even Wayland/herbflustwm(?) compatibility, too?}),
1 (borrowed from GoboLinux ( http://en.wikipedia.org/wiki/GoboLinux ) & add ve4ernik's website links/Friends hyperlinks, influenced by MS Windows (XP? / 7+ / 8.1 / 10+) self-contained directories/folders filesystem hierarchy structure),
2 (same as 1) BUT with additional soft-linked(/hardlinked?/Linux-symlinked?) dirs to the default Linux FHS, and backup default-Linux-FHS dirs as they usually are - similar to system-protected (OS) files in the OS-folders 'win32'&'WoW64' dirs of MS Windows7(+) OS),
3 (new systemd-2020 user-management & /home/-dir management),
4 (user-programmed; including editable at pre-full-boot GRUB2-/etc.-CLI-menu),
5 (placeholder for non-systemd/systemd-free other initfreedom.org init-script (influenced by http://devuan.org , the systemd-less fork of Debian)...),
6 (same as 5) here, but with the 1) filesystem hierarchy),
7 (same as 5) but with the 2) filesystem hierarchy),
8-999999 = placeholders for user-specified, user-programmed (user-supplied, user-(in-)added) init scripts & user-supplied custom/mod Linux filesystem hierarchies (different from the default Linux FHS)...)...
(NOTICE: Should a user need more than 999999 init-scripts/FHS-alternatives, they/one/he/she may just hook one of these 9-999999 files to a bash Terminal shellscripting script that loads a table list of EVEN MORE deeper 'directory-depth-traversal' files that are symlinks to further datetime-stamped/custom-filetitles-format still-ASCII-alphanumeric-numbered files which contain even more init-scripts/FHS-alternatives...
(Thus may potentially require extensive use of rewrite rules such as use of many safe `$ alias`es commands & (rsynced-like git-diff-like) symlinks compiled in 1 master-file and dir-filepath rewrites to the standard Linux FHS via `ls`, `awk`, `sed`, or even... nah, no `perl5+`/ `python3` + `pcre2` in the pre-boot pre-init new Linux kernel module / kernel built-in hardcoded, etc. ...???)
IMPORTANT NOTE:
When and if this idea is possibly implemented in the Linux kernel (it may even be backported to older versions of Linux!),
one must also add a full-featured explanatory in-source-code-embedded comments-section which cites the expanded&modified&clarified version of the above attempt at standardization
of the default-or-custom-FHS bootstrapping mechanism of the Linux kernel.
This also applies to including a bilingual (default US English + some translated UTF-8-encoded version into some other language) specification text as the above within
the GRUB2 menu & possibly into modified versions of non-systemd OS init-scripts...
IMPORTANT NOTE #2:
These options (0 to 8-999999) should be available to users when installing or upgrading a (GNU/)Linux distro, provided that the user selects the 'ADVANCED (WARNING! BE CAREFUL ABOUT WHAT YOU ARE DOING!!!)' method of installation/upgrading, where the user has the expanded list of installation options and disk-partition & OS-settings customizations.
Furthermore, the default ( 0) , a.k.a. 0 ) Linux FHS is to be set as a fallback mechanism (with a text warning & a .log file being generated on the Desktop if that fallback happens) in case the rest of the numbered options fail to be activated/set/launched for some reason or some known/unknown error, etc.
In addition, it must be noted that one must also supply an auto-regeneration mechanism that auto-backups the main master-file with the above customize-FHS+init-script mechanism, and that auto-backup should be generated/copied in at least 3 different locations and be (possibly read-only unless you manually change the file permissions!) human-readable.
Lastly, it is highly recommended that the main master-file which is in some Linux kernel module (?) (or implemented as FUSE??? Or just hard-coded into the Linux kernel tree?)
always includes some universally-compatible .sh script that (re)translates the filepaths when a user switches between one of the numbered options in the above list of selectable/set-table
combos of 'FHS-alternatives + init-scripts (& /home/ dir(rectory) management mechanisms also added there - like with the 2020 systemd bloatware hacks that we are seeing being added in...)'. That .sh script must also utilize quotes in the absolute/relative filepath (re)translation mechanism that it represents - so as to avoid any CLI problems due to filepaths including non-standard or not-okay text characters (like whitespaces, tabs, Unicode characters, non-printable ASCII control characters, etc.)...
The last four pieces of recommended advice is to ensure backward(s)-compatibility and forward(s)-compatibility!!!
POSSIBLE CAVEATS:
- Can this kernel module load before the init script itself?
- Performance metrics in comparison to systemd and other init scripts from http://initfreedom.org , etc.
- Implement this as a small linux kernel module with an editable .conf/.sh script OR hardcore it into the Linux FHS???
- Is it a good idea to consider at all? If it is implemented, what are some possible problems beside synchronous vs. asynchronous, and parallelism & parallel computing, and how it plays with process scheduling and background processes and active foreground processes, easy of use as an editable .conf/.sh script or a C-script, all with a default read-only original copy existing beside the used rwx active editable copy, etc. Do I even know what the fuck I am trying to say with all this??? 😅🤣 Are you at least not mildly interested and are you not at least mildly entertained by reading all of this spaghetti-code-like idea that I pulled out of my ass because systemd has gone too far and so they forked Debian as http://devuan.org ? 🤣 Do you not like MX Linux, ArtiX Linux, Debian/Ubuntu/Linux Mint, ArchLinux, Gentoo, Slackware, SliTaZ Linux, Puppy Linux (Ubuntu/Debian-based editions) & EasyOS, MinimalLinuxLive, LFS, BusyBox/Hairloom toolkit, etc.?
When will we get a subcommand to 'LC=bg_BG_variant009.UTF8' each of our CLI commands'
manandinfopages? 😅
-
The dreaded behemoth mammoth of an init-script ---
systemd--- is taking over Linux (especially Debian&Debian-derived Linux distros!) like a feature-overbloat/feature-creepism&overengineering&spaghetti-code monster from the Church of the Flying Spaghetti Monster!!! :P OH NOES!!!
-
...
-
...
-
...
-
...
-
...
https://en.wikipedia.org/w/index.php?title=Linux_startup_process&oldid=947770059
Linux startup process is the multi-stage initialization process performed during booting a Linux installation. It is in many ways similar to the BSD and other Unix-style boot processes, from which it derives.
Booting a Linux installation involves multiple stages and software components, including firmware initialization, execution of a boot loader, loading and startup of a Linux kernel image, and execution of various startup scripts and daemons. For each of these stages and components there are different variations and approaches; for example, GRUB, LILO, SYSLINUX or Loadlin can be used as boot loaders, while the startup scripts can be either traditional init-style, or the system configuration can be performed through modern alternatives such as systemd or Upstart.
https://opensource.com/article/18/5/how-load-or-unload-linux-kernel-module
https://stackoverflow.com/questions/23741843/force-linux-kernel-to-load-before-processing-init
https://wiki.archlinux.org/index.php/Kernel_module
https://www.cyberciti.biz/faq/linux-how-to-load-a-kernel-module-automatically-at-boot-time/
https://unix.stackexchange.com/questions/342417/explicit-kernel-module-load-at-startup
https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch02.html
https://www.tldp.org/LDP/lkmpg/2.6/lkmpg.pdf
...