Editing 1912: Thermostat
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 19: | Line 19: | ||
Part of the humor is in the problem being only a slight exaggeration of real software issues. The symptoms are unlikely, yet possible (a thermostat could be running Android and could generate a report as a .doc file; given some data corruption, the name of the .doc file could get into the boot script and a volume could appear unpartitioned). It would take an expert Android or Unix engineer to fix, particularly on an embedded device with no obvious way to connect remotely or attach a keyboard. In real life, it would probably be easier to just replace an embedded device whose software was this broken. | Part of the humor is in the problem being only a slight exaggeration of real software issues. The symptoms are unlikely, yet possible (a thermostat could be running Android and could generate a report as a .doc file; given some data corruption, the name of the .doc file could get into the boot script and a volume could appear unpartitioned). It would take an expert Android or Unix engineer to fix, particularly on an embedded device with no obvious way to connect remotely or attach a keyboard. In real life, it would probably be easier to just replace an embedded device whose software was this broken. | ||
β | This is explored further in [[2083 | + | This is explored further in [[2083|Laptop_Issues]] |
==Transcript== | ==Transcript== |