The system
It never surprises you.
sutraOS explains itself, and it can undo anything it did. Everything else on this page follows from those two sentences.
Ask it why.
why answers from the machine's own records. It names a cause only when those records connect it to what happened. Each link in an answer is marked recorded, measured or worked out, with a command to look it up yourself.
When the records do not reach, it says what is not known and what would have had to be recorded.
~> why not backup.timer The backup did not run because a condition was not met: the laptop was on battery. recorded the timer fired at 02:00 recorded the condition that skipped it look it up journalctl -u backup.service
~> why is /etc/system/power.toml
Changed on this machine, on Friday at 18:40.
Who changed it is not known.
An illustration of the answers. The wording in the shipped command may differ.
The four questions of the first version
| You ask | It tells you |
|---|---|
why not <unit> | The unmet condition, the requirement that failed first, or that the timer has not fired |
why failed <service> | Whether a file the service names changed after its last good start |
why is <file> | As the system ships it, changed on this machine and when, or added on this machine |
why slow | The one app or service using the processor and what started it, or that several are busy and none stands out |
Not answered yet: a full disk, who made a change, the fan, battery, heat and sleep, graphics stutter, and questions typed in plain words. Each of these waits for a recorder the system does not have yet.
Undo anything.
An install, an update, a changed setting: each lands in a timeline with what it touched. Undo is not a trip back to an old snapshot, which would erase your later work. It puts back only what that one change touched.
- TimelineSaturday 14 November
- 14:02You installed Blender1 app, 2 permissions
- 09:15The system updated itselfThe old system is kept for 30 days
- 08:30You changed the power settingsPartly undone. power.toml was edited again later, so it was left alonePartly undone
Nothing is lost silently.
Before you choose, the timeline names the files that would go back.
Partly undone is a real state.
What has changed since is left alone, and named.
30 days by default.
The timeline shows what each entry costs in disk, and you can change the number.
A drawing of the design. The first proof ran in a virtual machine and passed with conditions. The undo timeline and its config file have since worked in the Preview's image, in a virtual machine; nothing of it runs on a laptop yet.
A desktop that frames the work, then gets out of the way.
Glass belongs to the frame and never sits behind what you read. One menu bar, one dock, windows that snap, and a right-click menu on everything you can point at.
It does not freeze
A watchdog keeps the screen alive when an app stops answering, and force quit is one shortcut away. An app that hangs never takes the system with it.
Secure from the first boot
Disk encryption, verified boot, sandboxed apps that ask in context, and a firewall that watches what leaves as well as what arrives.
Updates that roll back
The system is a signed, read-only image. An update that fails goes back to the system that worked, by itself.
The design's aims for the first release. Signed updates and rolling back after a failed check have worked in the Preview's image in a virtual machine. A graphics proof on the Dell kept the screen alive through a reset of the whole graphics chip, but one app's hung shader froze it for 7.5 seconds, so that part of the design is still open.
Fourteen apps in the box.
Enough to live on the machine. Everything else comes from the Store, which carries Flathub.
- Files
- Browser
- Settings
- Store
- Terminal
- Text Editor
- Viewer
- Passwords
- Help
- Activity Monitor
- Console
- Disk Utility
- Calculator
- Clock
The planned contents of the first release. Three of these have no design yet: Text Editor, Calculator and Clock.