4 ms·
I don't think the person you replied to was asking for it to be enabled out of the box. Them talking about using a Chromebook as a dev machine makes me think th
by calgarymicro 3y ago
I don't think the person you replied to was asking for it to be enabled out of the box. Them talking about using a Chromebook as a dev machine makes me think they'd be okay with having to enable developer mode to run Linux binaries.
- sillywalk 3y agoMy understanding is that is what developer mode allows you to do - treat a Chromebook as a regular laptop, install any Linux distro you wish to. ChromeOS isn't a general purpose Linux distro, so in order to actually run a lot of things you'd need to install all their dependencies anyways.
- calgarymicro 3y ago> treat a Chromebook as a regular laptop, install any Linux distro you wish to Apparently this is via a VM, with limitations (no hardware acceleration, for example); presumably the original commenter wants to be able to run Linux binaries natively. > ChromeOS isn't a general purpose Linux distro But based on the article, it seems Google is taking steps towards making it one (switching to Wayland, using standard Chrome for Linux, etc.).
- sillywalk 3y agoI should note I am no expert on anything of this, I have a Chromebook as a sort of backup/alternative. FlipC434 Developer mode basically unlocks the r/w firmware, so you can boot from USB and replace the firmware etc, but the Read-only Google Root of Trust stays there, however as far as I know the ChromeOS 'distro' exists only to support running the Chrome Web Browser, and also Android and Linux VMs, +audio/video/input/etc. So if you have root on a ChromeOS device in developer mode, and you are dropped into a shell and want to run firefox, how would you do that? There are no packages for running on 'ChromeOS'. You can't just apt-get. I don't know if ChromeOS is self-hosted, ie. it is compiled and generated on itself and not some other Linux distro. which I don't think adopting Wayland or using the 'Linux' Chrome makes it move towards being a 'general purpose' distro. This just lessens the amount of change between ChromeOS and Linux so no more Freon library. It also seems to greatly reduce the difference between the CHROME_BROWSER_FOR_CHROMEOS and THE_CHROME_BROWSER_FOR_LINUX builds.
- pjmlp 3y agoThat is a VM, similar in concept to WSL on Windows, with the difference that the host is also Linux based. "Linux for Chromebooks: Secure Development" https://www.youtube.com/watch?v=pRlh8LX4kQI https://www.youtube.com/watch?v=pRlh8LX4kQI https://chromium.googlesource.com/crosvm/crosvm/ https://chromium.googlesource.com/crosvm/crosvm/ https://chromeos.dev/en/posts/making-android-more-secure-with-arcvm https://chromeos.dev/en/posts/making-android-more-secure-wit...
- sillywalk 3y agoI guess I wasn't clear about how I thought this stuff worked. WSL is like the Chromebook Official Linux Developer thing -(he last time I updated it), Debian, inside a container, inside a VM, running under ChromeOS. You can run what Debian can run. Inside the container. I thought ChromeOS as a distro is more like a runtime - it has the stuff to let it boot a Chrome Browser and VMs. etc +hardware support. There wouldn't be much point (other than fun) for Running random software on ChromeOS. It would be like OpenWRT, but without the package manager.
- whyagaintango 3y agoI would avoid using dev mode for production. If you press <space> during boot all is lost. + no guarantee that update will not fail.