Originally posted by jrch2k8
View Post
Originally posted by starshipeleven
View Post
What I see as being the purpose of this is to allow you to easily and seamlessly run normal Linux apps in ChromeOS on your Chromebook. You can use ChromeOS and run some other Linux distro in a virtual machine and have the various gui apps running in there show seamlessly like normal windows in ChromeOS.
Although I still fail to see why they prefer a virtual machine over a chroot / lightweight container. It should be easier to install the distro of your choice in a chroot (like what you can already do with crouton) and expose a connection to the wayland compositor into it, so that you can then launch wayland apps from within the chroot and they will just connect to ChromeOS's wayland compositor. I don't understand why they are instead going for the complexity of dealing with virtual machines and having to use special drivers to cross the boundary between two operating systems.
Comment