Linked by Thom Holwerda on Thu 16th Nov 2017 22:47 UTC

Well, I've really done it. I've taken a pure and unsullied Google Pixelbook, which at one time was fast and secure in all ways, and made it into a crashy mess. My crime? The desire to code.

I'm going to walk you through my process for converting this machine into something that's marginally desirable for programming, but I just wanted to warn you before I begin: this isn't easy, clean, intuitive, or practical. There are rumors that Google is working on better ways to make Chrome OS a host for other flavors of Linux or Linux apps, but right now we're basically working with hacks, and hacks hurt.

Because these hacks hurt, I'd implore you to read this entire guide before attempting any of the steps so you know what you're getting yourself into, and if you, in fact, desire the results.

I think the PixelBook is a stunningly beautiful and fast machine, and while Chrome OS isn't nearly as useless as people often think it is, it clearly isn't the kind of operating system many OSNews readers would prefer. This is a guide to getting a traditional Linux setup up and running.

Permalink for comment 651072
To read all comments associated with this story, please click here.
RE[4]: This... is wrong tool
by l3v1 on Sun 19th Nov 2017 09:31 UTC in reply to "RE[3]: This... is wrong tool"
Member since:

Actually, it's not. I've been using a Chromebook for development work since the first one

No. From all your descriptions it shows that you've been using your chromebooks as thin clients. All nice and easy if you don't have to pay for it, you can afford paying for all the services you need, you always have access to high speed unlimited connections. Also, in my book, this doesn't really qualify as usage as a dev machine since you can use almost everything as a thin client.

There's no way I'd work from/on a thin client for dev work if I can buy a good laptop with equally good battery life for similar - or less even - price.

Reply Parent Score: 4