Even attempting to install crouton is not recommended: it will mess up your sleep settings, and the brightness keys will quit working. Fixing your Chromebook will require a powerwash.
In verified mode, an external program cannot gain access to your Chromebook. But in developer mode, all bets are off.
Crouton has not been updated to address the current situation. In fact, there may be no way to do so. The author of crouton has moved on, and no longer has the time or energy to fix it, assuming that is even possible.
Either dual boot or use Crostini. Good luck.
I recently installed it on an old arm based chromebase that I had no other alternative. It works fine in that situation, I can run an older version of Ubuntu with xfce.
But for newer setups there are definitely better alternatives.
Yeah, crouton will work on older releases. I'm glad you were able to find something which works for you. The author is leaving crouton "as is" specifically so it will still work on older Chromebooks.
that's absolute bs
You think?
Yeah, but for oversimplified precaution for new or unexperinced chrome os users I think it's fine.
In developer mode access to the host is protected by password, sudo prompts for password too, user, usb media and temporary dir all has noexec flag so nothing can be executed from it.
devmode doesnt mean writable root fs, by default it is readonly & verified(signed by google keys)
even in unverified rw root fs it can be configured to be mounted as readonly by default to minimize accidential changes
Well, attempting to install crouton corrupts your Chromebook. I've tried twice, just to be sure, and each time required a powerwash to reset it.
If you don't believe me, try it yourself.
I think it's just how chromeos processes transition from devmode to verified, it require powerwash unconditionally and it doesn't mean that os has been corrupted previously
You're not understanding me. After I tried to install crouton recently, the brightness keys quit working, and half the power settings disappeared. The only cure was a powerwash.
The powerwash didn't create the problem, it fixed it.
omg that sounds awful, does crouton mutate rootfs?
I mean, I don't know what happens. This is brand new, as of 126.x. I just read on the GitHub that someone was able to install on version 129.x by using a small mod of the initialization instructions. I'm still researching it.
Thanks for your feedback. If I come up with anything new, I'll post it here.
i can't! nowadays all my chromebooks are running linux...
Okay
damn, I was trying to use crouton today! no wonder it didnt work, lol. such a shame...
Check your settings. Make sure the brightness keys still work, and check the power settings to be sure the screensaver still works.