NayuOS – Chromebooks without Google

Re:NayuOS – Chromebooks without Google by hollerith on Friday January 29, 2016 @11:56AM (#10996378)

I always wondered why I saw many dozens of references to the Wayland project (from writers who think it might be a good idea to replace X) and no references, until today, to the idea of turning ChromeOS into something more like a regular Linux-based desktop/laptop OS.

(ChromeOS does not rely on X but rather has its own windowing system developed by Google.)

Writers hopeful about Wayland love to talk about how Gnome or KDE already supports of will soon support Wayland, despite the fact that for a desktop/laptop OS, support from one of the major browsers is much more important than support from Gnome or KDE. (Yes, I know that Gnome includes a web browser: that browser will not work however with all or even most of the sites a typical user needs to visit.) And it is far from certain whether any of the major browsers will ever run on Wayland (without XWayland or some other large X-compatibility library that relies on X) whereas of course one of the major open-source browsers already runs reliably on the windowing system and low-level graphical libraries in ChromeOS.

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by baghira on Friday January 29, 2016 @12:39PM (#10996819)

Firefox works on Wayland now. So, unless you have redefined Firefox as a non-major browser, "is far from certain whether any of the major browsers will ever run on Wayland" is flatly wrong. Also: https://github.com/01org/ozone-wayland

And the obvious point is that turning ChromeOS into a full linux distribution defeats the point of ChromeOS itself: to have very few "moving parts", and only those necessary to launch Chrome. Also, the bulk of the work "for wayland" is not wayland itself: it is KMS/Mesa/glamor/libinput, which are already used by ChromeOS (except for libinput, I think).

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by hollerith on Saturday January 30, 2016 @03:06AM (#11001055)

Can I run Firefox on Wayland without X, i.e., without XWayland or some other compatibility layer which includes most of X's source code files?

If so, do you know where I can download it?

>turning ChromeOS into a full linux distribution defeats the point of ChromeOS itself: to have very few "moving parts".

Just because that is why Google created ChromeOS does not mean that those of us uninterested in Google's vision cannot bend it or parts of it to other purposes. It is after all distributed under open-source licenses.

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by pepijndevos on Friday January 29, 2016 @12:13PM (#10996545)

As far as I know ChromeOS does use Xorg, but does its own window management. So basically everything you see is INSIDE one single X window.

I think the Crouton project has a section with more details about the setup, because people want to mix chroot windows and Chrome windows. Maybe relevant: https://github.com/dnschneid/crouton/wiki/crouton-in-a-Chrom...

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by smbarber on Friday January 29, 2016 @12:33PM (#10996762)

This used to be true; freon came in 2015 and eliminated the X server on most Chrome OS devices.

http://tech.slashdot.org/story/15/03/09/0220205/google-intro...

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by gtk40 on Friday January 29, 2016 @01:25PM (#10997252)

Isn't Gnome's browser Epiphany ("Web") which uses Webkit?

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by qwertyuiop924 on Friday January 29, 2016 @02:03PM (#10997606)

Wayland has a systemd dependancy, and i3 has gone on record to say they won't support it, so I'm not exactly hyped.

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by JupiterMoon on Friday January 29, 2016 @02:37PM (#10997895)

That is a shame. Given that Wayland should be a huge improvement over X this will lead to either: i3 withering and eventually ceasing to exist, or a fork of i3 that works with Wayland.

Also what is wrong with systemd (with regards Linux - the BSD's can handle their own init systems just fine on their own)? On my systems systemd has been wonderful.

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by qwertyuiop924 on Monday February 01, 2016 @11:30AM (#11012748)

...But wayland can't replace X. As I understand it, wayland is linux specific, and so saying X will die is saying that no other unix needs graphics.

As for what's wrong with systemd: Where to start! Journald is the root of all evil, it puts way to much stuff in to pid 1, the developers want dbus in the kernel (which is an awful, awful, awful idea), and the project is encouraging higher level software, that has to business being system dependent, link to a library that is linux-only by design. And that's only to tip of the iceburg. Its default's animostiy, its design is an atrocity, the implementation a catastrophe, the only question left to ask is: Where did they go RIGHT?

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by tobik on Friday January 29, 2016 @02:52PM (#10997989)

I'm tracking this i3/Wayland fork which seems to be pretty active too: https://github.com/SirCmpwn/sway

[ Parent | on HN ]

Re:NayuOS – Chromebooks without Google by sevensor on Friday January 29, 2016 @03:37PM (#10998302)

Likewise. I've been very impressed. The one place it seems to have trouble consistently is with X applications that want to have floating dialog windows. So many moving parts there, I'm hesitant to lay the blame on Sway.

[ Parent | on HN ]