NanumOS

The OS improving itself (evolve)

NanumOS can change its own programs for better versions. A model (or a person) edits the source; NanumOS builds it inside itself, tests it in a separate small NanumOS (a child VM), and swaps it in if it passes. If not, the change is dropped, and a swap can be undone with one line. Today one program changes this way: the calculator (calc).

One turn

  1. Change — edit files there with vmx exec ub1 'command'. Raise the version line (such as ZEUSAPP calc 1.0.1) on every change.
  2. Build — evolve build calc builds inside the workbench VM and brings the file and its sha256 back to NanumOS.
  3. Test — evolve try calc FILE SHA256 (or evolve build calc --try in one go) starts a child NanumOS with no disk and no network and runs the 17 calculator tests on the current and the new version alike.
  4. Swap or drop — if every test passes and it is not slower or bigger, the new version is used at once (no restart). Otherwise you get the reason and nothing changes.
  5. Roll back — evolve rollback calc goes back to the version before; doing it again goes forward.

Commands

CommandWhat it does
evolveCurrent and previous version of each app.
evolve build calc [VM] [--try]Build in the workbench VM and bring it back; --try goes on to the test.
evolve try calc FILE SHA256Test in a child VM; swap if it passes.
evolve rollback calcBack to the version before.
vmx exec VM [-t SECONDS] 'command'Run one command in a VM; shows its output and exit status.
vmx pull VM GUESTFILE FILECopy a file out of a VM into NanumOS (sha256 checked).

The record

Every attempt writes a start line first and an end line last to /var/log/evolve.log. The end line has the result, the reason, the times, the source version (src=) and a place for the cost (`tokens=? The "진화" (evolve) row of the system check (os_check) shows the last attempt and the version in use; a start with no end is a warning (it was cut off).

Safety

NanumOS 0.1.8349 · 2026-11-16