6 ms·
The developer mode warning only occurs on boot, as you say. Having owned by the ARM Chromebook and the Pixel since both were released, I've probably seen that w
by jdn 13y ago
The developer mode warning only occurs on boot, as you say. Having owned by the ARM Chromebook and the Pixel since both were released, I've probably seen that warning less than 8 times since install. The Chromebooks very rarely need to be turned off, and the one time that does happen often, on update restarts, actually bypasses that warning.
- avian 13y agoIt really depends what you want to do. If you just run a chroot inside the stock ChromeOS then what you say is true. But if you're dual-booting to another Linux distribution or just replace ChromeOS altogether (that's another issue with the linked article: what it describes is not a dual-boot) you can't escape frequent reboots. Especially due to flaky suspend/sleep mode support in other distros.
- jdn 13y agoTrue, but the chroot is by far the most common and most stable method, and the one targetted in the article. Though as you say, the title is wrong.