LintabOS 0.3.9

LintabOS 0.3.9 (pre-release)

Two new things: more ways into Windows' own repair tools, and a terminal where the Files app alone isn't enough.

Restart into Windows: Recovery and Safe Mode

"Restart into Windows" now opens a small chooser instead of rebooting immediately: a normal restart (unchanged),
Restart into Windows Recovery, and Restart into Windows Safe Mode.

Recovery sets the UEFI OsIndications variable's documented "start OS recovery" bit before rebooting — a real,
specification-defined mechanism, and exactly as safe as the already-established "reboot to firmware setup" feature
(the same variable, a different bit). Whether Windows' own boot manager actually honors this bit was not
confirmed despite real research effort — if it doesn't, the tablet simply boots into Windows normally. The real,
manual way in (Settings → Recovery → Advanced startup, or holding Shift while choosing Restart) is shown as part of
the choice itself, not hidden as a silent fallback for if the automatic attempt does nothing.

Safe Mode makes the same attempt, since Safe Mode lives inside Windows' own recovery menu rather than being a
separate boot choice. Reaching it directly would need editing Windows' Boot Configuration Data — a binary registry
hive LintabOS does not write to anywhere, for the same reason LinWinMod's registry browser is read-only: a wrong
edit could leave Windows unable to boot at all, and that risk can't be ruled out without a real Windows BCD store
to test against.

WinTermMod

A terminal, positioned at your mounted Windows drive — the same Fast-Startup/BitLocker safety checks as LinWinMod's
Files tab — for find, grep, bulk renames and other command-line work against Windows files directly.

It is not Windows cmd.exe. A native Windows program can't run outside Windows at all, and running one against
the real Windows system drive through a compatibility layer would be, in effect, a way to act on Windows without
logging into it — the same risk LinWinMod's registry browser was built to avoid. What you get is an ordinary Linux
shell, just already in the right place.

What was checked

32 new tests: the UEFI variable read/write logic (including that it never raises when unsupported, and never loses
a bit that was already set), that a failed grub-reboot can never still trigger an actual reboot, and every
WinTermMod failure path (no partition, unclean drive, refused mount, no terminal installed) reporting a message
instead of silently doing nothing. One of those tests caught a real bug in the test setup itself (a Python
default-argument late-binding mistake) before it could hide a future regression.

Files: lintabos-0.3.9-amd64.iso, lintabos-core_0.3.9_all.deb + .minisig, SHA256SUMS.