Comment by jeffbee

Chromebooks make a pretty nice, Linux friendly machine. They're usually cost optimized given the market they address, but that's fine if it fits your needs. Sometimes they have "weird" hardware, keyboard/mouse controllers and stuff at least wasn't always "pc standard", audio controllers seem to be commonly outside mainstream as well.

It's nice to run Linux on a machine that was built to run Linux. No silly windows key, no fighting with firmware that was built for windows first. I have a Chromebox that was a great mini desktop and the pricing was nice. My first Chromebook ran FreeBSD pretty well once it was no longer needed for ChromeOS, etc.

You have to shop carefully, you want something that's easy to put a MrChromebox firmware on and doesn't have any known issues with the OS you want to run. It's been a while since I purchased a ChromeOS device and the current state is different than it was then; I'm not sure how easy it is to find reasonable options now, but there were plenty of good options in the past. You also want to be sure that it has enough ram and storage for you needs or that those are expandable, but I think soldering ram and storage is pretty common across the range.

Crostini is kind of a joke, but I use it to remote into real Linux boxes. For me, best of both worlds.

The number of people who have "installed linux" other than ChromeOS on a Chromebook is probably in the low single digits, while the ChromeOS installed user base is in the hundreds of millions. For any given thing someone is going to try to put linux on that thing, but it is not a common use case for Chromebooks that we need to discuss.

Having very recently (and unsuccessfully) tried to connect a printer to "real" Linux, that's not really a relevant point against ChromeOS.

In the end, after hours of frustration, my solution was to print the document from my (amusingly, Google Pixel Android) phone.

This is actually the perfect detail to discuss. ChromeOS printing is literally just CUPS, so it has the same functionality as any other Linux distro. If you have a modern IPP printer on a normal home Wi-Fi, you can expect it to just work. This covers most people's needs.

Where ChromeOS shines is that it has never been affected by severe and numerous CUPS security vulnerabilities like CVEs 2024-47175 through 2024-47177, which were unauthenticated remote vulnerabilities, while Ubuntu and Fedora (and all other major distros) were affected. Why? ChromeOS sandboxes the hell out of these kinds of subsystems. CUPS runs in a PID namespace, network namespace, mount namespace, on a read-only filesystem, with seccomp filters. It cannot use the network, ever. It can only communicate over a pipe with a network proxy. The proxy is only active if and when a user tries to print. The proxy is also in a seccomp jail that prevents it from doing anything except enumerated network traffic and the pipe. The proxy is written in a safer language than CUPS itself, and protects CUPS from malformed, malicious inputs by validating both PPDs and print requests.