@ai-ecoverse/slicc-bios 1.52.0 → 1.52.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -93,7 +93,7 @@ A kernel process can still write to `/os/` and `/node_modules/` (any process whi
|
|
|
93
93
|
- **During an update**, while `slicc-packages` is held, a mismatch gets a 503 and isn't counted as a change.
|
|
94
94
|
- **A navigation** that fails the check goes to the BIOS too. So does any navigation while a tree has no hashes yet, which happens only on the first boot after integrity checks arrived.
|
|
95
95
|
- **The log:** every integrity event is appended to `/var/log/slicc/integrity.log`, one JSON line each, which the kernel shows as root's with mode 0644. Each line has `time`, `event` (`changed`, `restored`, `failed` or `stopped`), `path`, the `expected` and `actual` SHA-256 (`actual` is `null` for a removed file) and `changed`, when the change was found. The service worker writes `changed` and `stopped`, and the BIOS installer writes `restored` and `failed`.
|
|
96
|
-
- **When the UI'
|
|
96
|
+
- **When the UI doesn't start:** `os/start.js` imports the UI and catches whatever stopped it, a refused file or anything thrown while it runs. Instead of a blank page it then shows *Seven couldn’t start*, with **Reload**, which goes through the BIOS. It asks the service worker through `/__slicc/integrity`, which answers the stopped and changed paths as JSON, and says only what that shows. When seven stopped restoring a file, the message says which file and that seven tries again in about 10 minutes. When a file changed, it says so, though usually the service worker has already sent the tab to the BIOS. A page with no service worker says that. Anything else shows the error itself.
|
|
97
97
|
- **No restore loops:** seven stops restoring a path when restoring it failed, when it changes again within a minute of being restored, or when it changes three times in ten minutes. It keeps refusing the file, doesn't send tabs to the BIOS for it, and the BIOS leaves it as it is. The UI shows *Seven stopped restoring a file*: "Seven keeps finding <path> changed. It stopped restoring it and won’t run it. Something on this computer may be changing seven’s files." The list stays in `localStorage` (`slicc-bios.stopped`) until a BIOS run no longer reports it. Ten minutes after it was stopped, the next BIOS run tries again.
|
|
98
98
|
- **Putting it back:** the BIOS's packages step downloads again every package that owns a changed file, and the seed step copies the seed again. Both say how many changed files they put back. The UI then shows a warning notice, *Seven’s files were changed*, naming the files, from `localStorage` (`slicc-bios.repaired`), since the COOP switch from the BIOS to `os/` doesn't keep `sessionStorage`.
|
|
99
99
|
- **Not checked yet:**
|