jsmeix

I like to have a Linux system that completely runs on an USB stick (read and write also for persistent storage) so that it can run

I like to try out if it is possible to write a program that does not have any kind of the traditionally separated documentation (like external files that contain the documentation texts or comments in the program code). Instead all documentation must be implemented as code at the same place where the matching functiomnality is implemented (i.e. each function implements also its documentation). In the end the user should get only the executable that he can run to let it do the intended functionality and also to provide any kind of documentation. What I do not want is a dumb '--help' option that lets the program spit out its built-in documentation. What I would like to have is that the user can run the executable in some kind of self-inspecting way. I mean: While it does the intended functionality, it can also provide documentation so that the user can explore the program while running it. In the end the user experience should be more like a text adventure ;-)

Basically the idea is to boot inst-sys but to not run YaST and instead run a selfmade script that does the usual disaster recovery steps:

The basic idea is is to boot the plain SUSE installation system (inst-sys) but to not let it run YaST. Instead inst-sys runs Relax-and-Recover (rear) as generic installer that does the system installation.

For Relax-and-Recover (abbr. ReaR, RPM package rear) I like to implement a new kind of "backup" method:

I need to get a basic understanding about MD software RAID setup only via command line tools to be able to understand,

Create a new generic CUPS wrapper backend /usr/lib/cups/backend/monitor that runs in parallel with the actual backend to monitor it.

Relax-and-Recover (ReaR) is used to recreate a destroyed system on compatible replacement hardware, see https://en.opensuse.org/SDB:Disaster_Recovery Currently ReaR requires basically 100% compatible replacement hardware.