4 ms·

Yes, you can run any Linux program on it. It has Wayland which converts x11 to the Chromeos windowing metaphor. You can install things using apt-get on your loc

by xrd 8y ago

Yes, you can run any Linux program on it. It has Wayland which converts x11 to the Chromeos windowing metaphor. You can install things using apt-get on your local instance of Linux or use -X with ssh and it just works. It's amazing. But the sound issues, sigh.

giancarlostoro 8y ago
Is it regular x11 apps with ChromeOS' own window manager / skin theme or some weird hack?
- derekp7 8y ago
  x11 apps talk to XWayland, which then talks to Sommelier (a Wayland forwarding agent), which then talks to the Wayland server running on Chrome OS. Other communications between Chrome OS and the Crostini system happens using the gRPC protocol. There is a program called Concierge on the Chrome OS side, that talks to Maitred inside the VM, to get it to do things. And apps inside the container use Garcon to talk to a service called Cicerone on the Chrome OS side (again, both these are over the gRPC protocol). All this is layed out here: https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md https://chromium.googlesource.com/chromiumos/docs/+/master/c...
  - giancarlostoro 8y ago
    That sounds a little saner though still convoluted. I hope they eventually don't have to run through so many hoops to run Linux apps.
    - xrd 8y ago
      Hey, it's still less of a hack than using crouton was!
- xrd 8y ago
  I don't fully understand it all but I don't think it is a hack. It's the "new way" to do x11 type applications. I'm not at liberty to read the article on Wayland right now (alone with the three kids tonight and bedtime looms...). But I remember reading and thinking it wasn't complicated to understand and that this way of doing things is the future. It makes ChromeOS into a really powerful terminal. You can run stuff locally that's best to be run locally. Then you can run applications that don't run locally (like that need access to special hardware like a gpu) on the machine itself via x11 forwarding. It's very flexible and works. As a separate issue from mine (faulty ChromeOS sound), currently you can't use the sound hardware inside the container. But that'll get fixed soon. Just means there is no way to run Linux music making apps yet.

by xrd 8y ago

giancarlostoro 8y ago

Is it regular x11 apps with ChromeOS' own window manager / skin theme or some weird hack?

derekp7 8y ago
x11 apps talk to XWayland, which then talks to Sommelier (a Wayland forwarding agent), which then talks to the Wayland server running on Chrome OS. Other communications between Chrome OS and the Crostini system happens using the gRPC protocol. There is a program called Concierge on the Chrome OS side, that talks to Maitred inside the VM, to get it to do things. And apps inside the container use Garcon to talk to a service called Cicerone on the Chrome OS side (again, both these are over the gRPC protocol). All this is layed out here: https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md https://chromium.googlesource.com/chromiumos/docs/+/master/c...
- giancarlostoro 8y ago
  That sounds a little saner though still convoluted. I hope they eventually don't have to run through so many hoops to run Linux apps.
  - xrd 8y ago
    Hey, it's still less of a hack than using crouton was!
xrd 8y ago
I don't fully understand it all but I don't think it is a hack. It's the "new way" to do x11 type applications. I'm not at liberty to read the article on Wayland right now (alone with the three kids tonight and bedtime looms...). But I remember reading and thinking it wasn't complicated to understand and that this way of doing things is the future. It makes ChromeOS into a really powerful terminal. You can run stuff locally that's best to be run locally. Then you can run applications that don't run locally (like that need access to special hardware like a gpu) on the machine itself via x11 forwarding. It's very flexible and works. As a separate issue from mine (faulty ChromeOS sound), currently you can't use the sound hardware inside the container. But that'll get fixed soon. Just means there is no way to run Linux music making apps yet.