__________ ........
| |----| OS 1 |
| computer | ````````
| | ........
|__________|----| docs |
| ````````
......|..... ........
| programs | | OS 2 |
```````````` ````````
Be wary about putting all of the eggs in the same basket. Discrete purposes with their own resources stay separate, thereby one is affected by its own needs or demise without draining other resources or damaging anything else.
In other words, rather than a large amount of memory in one container, consider smaller amounts in multiple containers. Dedicating resources sparingly minimizes corruption or loss, while freeing remaining resources for additional or simultaneous endeavors.
Everybody wants to rule the world, for the sake of personal comfort. It is possible to let everything remain as it has come to be, and move forward without bearing the wait of it all following along.
The end of "Overview".
Distinct from a dual-system, either "dual-boot" or "multi-boot" are singular systems. Those "boot" approaches are for having more than one operating system on the same storage device, and thereby either is a setup for multiple losses. The operating system is chosen by the person after starting (t.i. booting) the computer.
__________ ........
| |----| OS 1 |
| computer | ````````
| | ........
|__________|----| docs |
| ````````
......|..... ........
| programs | | OS 2 |
```````````` ````````
An operating system needs its own memory storage separate from other operating systems, because "operating" means automated programs are doing whatever without being monitored. They can readily corrupt anything on the remainder of the storage device.
For example, there has been one operating system (for a "hardware integrated with software" system) that replaces the partitions and filesystems of the whole storage device with its new and improved version of partitions and filesystems.
Unfortunately, any prior version of that same operating system on the same storage device was unable to properly recognize it anymore. That meant the prior versions were prone to corrupting that storage device and the new operating system on it might become unusable, too. Reliability comes from discrete use, rather than shared.
The end of section 1, "Discrete operating systems".
Replaceable modular units provide the means for restoration and extensibility. Simply plug or unplug for instant modifications.
Ideally, the operating system is always kept on removable storage, never permanently inside a personalizable computer. The computer is started after attaching an operating system compatible with its hardware. Keep a backup on a second external storage device, then that can be used to start the computer when the primary fails.
Backups separate
from originals.
Everything on (and maybe from
external memory. each other, too)
............ ............
| firmware | | firmware |
|(external)| | backup |
``````|````` ````````````
| ..........
_____|____ ...... | OS |
| |----| OS | | backup |
| | `````` ``````````
| computer | ............. ..........
|(only RAM)|----| documents | | docs |
|__________| ````````````` | backup |
| ``````````
......|..... ............
| programs | | programs |
```````````` | backup |
````````````
..............
| spare mem |
| for trying |
| new OS or |
| programs |
``````````````
Keep personal documents separate from the operating system, ideally on a separate storage device. Documents can be instantly plugged into any computer, and no need to turn on some other computer to access them.
Personal documents on external storage are never trapped inside a computer that fails to start. For example, they are easily taken to a computer located beyond a local electrical power outage, f.e. to a nearby computer that uses a battery.
One computer with two memory storage devices for an operating (or operatable) system, primary and backup. Two more storage devices for personal documents, primary and backup. Perhaps another set of storage devices for additional software.
The amount of memory per storage device can be minimized for each purpose, no need for terabtyes in one device. Operating systems tend to use only a few gigabytes, but some operating systems are only a few megabytes, f.e. TinyCore and piCore (The Core Project - Tiny Core Linux).
The end of section 2, "Discrete storage devices".
Never update nor upgrade an operating system, nor any software application. Instead, install the next version on a separate storage device, and try it out discretely without losing the currently working version.
Creating a new instance fits with one of the core principles of computing: make and work on a discrete copy.
The memory devices need only as much memory as required for that particular purpose, no need for terabytes. Separate memory devices for trial of updates or upgrades can be re-used for that specific purpose, discrete from personal documents and discrete from stable software.
Reliably customizing a computer requires using some other stable computer, which is how it was manufactured, too. That is, a primary computer is used to setup a secondary computer. Once the secondary computer has its new modifications stabilized, then the secondary computer is eligible as a replacement for the primary computer.
__________ ........ ___________ ........ | |----| OS 1 | | |----| OS 2 | | primary | ```````` | secondary | ```````` | computer | ........ | computer | | |----| docs | |___________| |__________| ````````
Adding another computer requires only enough (external) memory storage for an operating system compatible with its hardware. Eventually, two such memory devices: its primary storage and its backup copy.
Once again, very small amounts of memory rather than large amounts. Gigabytes or megabytes (or even less), instead of terabytes, allows for sensible and affordable personalization of computers. Separate memory provides stabilty.
A physical computer tends to have small amounts of special non-detachable memory (firmware) for itself on its circuitboard. The manufacturers usually never reveal how to customize that memory, but usually provide mysterious updates or upgrades for it, potentially removing features or causing corruption.
That is why it is important to have a second computer (hardware) for customizing, isolating the aforementioned possible corruption of its circuitboard memory (firmware) by operating systems or their updates.
Ideally, the firmware memory would be physically removable, thereby replacible and securable before turning on the computer. That aids in addressing incorrect or rogue programming in untested or unfamiliar firmware.
By using a primary system to customize a secondary system, whatever happens to one system (software or physical) can be assessed from the other system. Furthermore, some tasks can be off-loaded to the secondary computer (when it is stable enough) rather than stressing or slowing the priorities of the primary computer.
The end of section 3, "Discrete instability".
Almost any computer can be repurposed as a personalizable computer, just as long as the operating (or operatable) system needed for personalization can be installed on it.
Explicitly, a computer that has its operating system integrated with its hardware is less likely to be repurposable. Be aware of that about integrated computer systems or computerized appliances, f.e. pocket gadgets marketed as cellular telephones.
Personalize a computer by customizing the commands invoked with the buttonboard, f.e. rebinding keys (stumpwm.htm: Customize the buttonboard). Or, enable the computer with special software to repeat any sequence of actions, a peculiarly uncommon ability of commodity computers.
Use a program for enabling the personalizable computer as a VNC "client" or RDP "client" in order to control any other non-customizable computer. Many operating systems already have VNC "host" or RDP "host" capabilities, so it is only a matter of having that feature activated on the other computer.
<-- video
.:::::::::::::::::::.
________ :: button :: ________
| | :: presses --> :: | |
| | :: :: | |
| |:::/ \:::| |
|________| |________|
| /__\ /__\
|
|..............
| buttonboard |
```````````````
personalizable non-personalizable
computer as computer as
VNC or RDP "client" VNC or RDP "host"
In short: long distance keyboard. The personalized computer (VNC client) essentially acts like a buttonboard and motion remote control (t.i. keyboard and mouse) for another computer. That computer is either on the same desk or elsewhere, connected by ethernet or USB cable, or perhaps by radio signals (f.e. WiFi or cellular).
Transmitting the buttons pressed is the only connectivity needed from the personalized computer. Software for repeating tedious tasks has no need for excessive processor speeds nor excessive memory nor even the latest OS. A computer from the 1990's would be enough for controlling remotely a modern day computer; no need for a new product.
There is no need to replace the operating systems of all other computers on the planet. There is no need for a computer program to work on all operating systems. Simply connect with remote control software to the other computer, even on the same desk.
In other words, there is no need for a personalizable computer to have the fastest processor or lots of RAM (temporary memory) or recent hardware. It needs only just enough to personalize it, and to use the VNC "client" or RDP "client" computer program to transmit the buttons typed. Anything more is gravy.
The end of section 4, "A personalizable computer".