You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user enabled the read-only filesystem and then performs an update, the system will reboot and go back to the pre-update state, which is not what the user wants or expects.
This issue is related to #1206, but this is a block in the install script itself, whereas that bug is a check before the update can even be initiated. The two complement each other, but this bug is higher priority because it will block both UI and terminal-based install flows.
The text was updated successfully, but these errors were encountered:
If the user enabled the read-only filesystem and then performs an update, the system will reboot and go back to the pre-update state, which is not what the user wants or expects.
We should add a check for the overlay filesystem in
./bunder/bundle/install
that aborts the script with a failing exit code if the overlay filesystem is turned on. It should print a message to stderr telling the user that their read-only filesystem is enabled, and they can disable it with the instructions on the website: https://tinypilotkvm.com/faq/read-only-filesystem#disabling-the-read-only-filesystemThis issue is related to #1206, but this is a block in the install script itself, whereas that bug is a check before the update can even be initiated. The two complement each other, but this bug is higher priority because it will block both UI and terminal-based install flows.
The text was updated successfully, but these errors were encountered: