News for hackers. Stuff that matters.
Re:NASA mistakenly severs communication to Voyager 2 by hutzlibu on Monday July 31, 2023 @12:33PM (#36945143)
After trying to optimize my laptops energy settings under linux, I once also ended up with a device that was operating low level autonomously for some time. It just would not accept commands from me, nor the power button, nor anything else. The CPU also wasn't running, but something was.

In other words it was effectivly a brick to me.

But since it was not a surface pro (I considered buying instead of that one), I could open it and disconnect the battery.

And in effect, unbricking it. Quite trivial fix sure, but nearly impossible with many modern devices, where the battery is glued in.

My point is, not every mode of operation is desired, especially if you cannot change it. Then you might as well have a brick in terms of usefulness.

Re:NASA mistakenly severs communication to Voyager 2 by nomel on Monday July 31, 2023 @12:38PM (#36945214)
No. Your laptop was not operating autonomously, by definition.

It was not making its own decisions, to achieve some goal.

Re:NASA mistakenly severs communication to Voyager 2 by hutzlibu on Monday July 31, 2023 @12:46PM (#36945342)
Parts of it were. To make some checks for some hardware (as part of an automatic comand line tool). They just got into an infinite loop. Down on the hardware level.
Re:NASA mistakenly severs communication to Voyager 2 by kfrzcode on Monday July 31, 2023 @06:15PM (#36949619)
That's not autonomous that's automatic