breath VS 8080-Remote

It disappeared without any visible explanations. Apparently, it was a a friendly fork of the Breath project (https://github.com/cb-linux/breath) by Apacelus (https://github.com/Apacelus/Apacelus). But Apacelus stopped working on it on May 26th (https://github.com/Apacelus/Apacelus/commit/c84ee94310144ec9...).

There's another project on Github with the same name: eupnea-linux-backup https://github.com/eupnea-linux-backup

As of now, audio on LARS works on GalliumOS Skylake out of the box and after some tricks on Ubuntu 18.04-based distributions and Ubuntu 20.04-based distributions. Furthermore, it may work on Breath Linux (discontinued).

Breath Linux might be you best bet - https://github.com/cb-linux/breath

Your best bet is probably the breath distro. It's not exactly Ubuntu, but it's probably as close as you're going to get.

I maybe wrong about this but few research on google suggest that sound isnt fully supported on that model, if its true then you may just be limited to Crostini, Crouton, Brioche or Breath https://github.com/cb-linux/breath but I suggest looking for someone here at reddit who had the same laptop and ask them if they have sound when running linux

Finally, there are packages like breath for more modern chromebooks that allow you to boot into native linux without flashing BIOS, but I haven't really tried using them.

But the actual difference can be achieved only with a dev mode rabbit hole. For example, you could try the Breath project that allows you to boot into Ubuntu from an sd card or a flash drive without messing with the system files. Since Ubuntu by default doesn't reserve so much RAM to itself, the games won't be begging for more ram and you'll see much better results. Everything said above is tested on a Celeron N4000-based 4GB Chromebook.

Did you see the site? There seems to be audio problems. https://github.com/cb-linux/breath/issues

I coded on a chromebook throughout college. It was the crucible of learning software development in the mid-2010s because you had to improvise. Most assignments were in Java back then (from what I understand, colleges teach mostly python now) and I couldn't run eclipse (the standard IDE used in college at the time). I ended up renting a VPS from Vultr for $5/mo and SSH'ing in. I coded everything in vim with no debugger or code completion, and compiled everything with makefiles.

Classes usually only required a single java file to turn in your work, which was then compiled and run automatically with the results being verified by another program, so as long as your individual java file output the same results as what was expected, it didn't matter what build system (if any) you used.

The only other class that didn't use java was systems programming, where we did C. I had been doing C since I was 12 at that point, and since I was already using ubuntu server via ssh, it wasn't a difficult class at all for me.

For my OS final, we had to write an operating system simulator (a program which simulated the kind of events that would occur in an OS: new processes, processes being deleted, memory paging). I didn't actually read the instructions and ended up writing a kind of hypervisor(?) which ran programs in 8080 ISA with some of my own custom instructions for memory banking to meet the requirements of the class (your program had to be able to do memory paging up to something like 512mb of RAM).

You had to have some kind of user interface, so I wrote it as a web server in C with a custom HTTP server implementation. The program returned an HTML page which looked like a desktop. You could spawn terminal windows and run specific programs. I wrote a few long-running programs which printed out numbers to demonstrate memory paging and process pre-emption. There was a special instruction I made to fork the program so you could clone a process from another process, and I used one of the unused flag register bits to signify which fork the program was.

The professor was impressed by the implementation (and I implemented all the algorithms required to get 10 points extra credit), but because I didn't actually write an OS simulator (closer to an actual OS, but not quite there), he gave me 100%, but no extra credit. I was happy with that, because I'm not a grade chaser.

Unfortunately, I failed the class because I couldn't answer trivia on the exam like "What does GRUB stand for" because I spent the whole semester working on the hypervisor and not actually going to any of the lectures. I just read the textbook and coded in C at the library.

Here's the very rough code, with a slightly buggy 8080 emulator implementation:

https://github.com/ShortRoundDev/8080-Remote