It looks like they ginned them up from relevant specs they stuffed in and and the model’s latent knowledge of QEMU VirtIO and the absurd GPU-managed system architecture that is the Pi.
The models have seen several IP stacks before, plus many copies of the Linux, BSD, etc. source trees.
It’s not actually hard to write a network stack, just tedious.
At some point in the USB keyboard/mouse code the model has loudly proclaimed PRINTF NOT ALLOWED, in the style it does when overcompensating after its obvious mistakes are pointed out to it for the third time. So I suspect that part might be implemented by brute force.
Unfortunately, the talking horse’s OS hasn’t bothered with syscalls and lacks any notion of memory protection, and has a terrible userspace API which e.g. puts waiting for a ping response entirely in kernel.
How much scratch? It’s hard to believe they wrote device drivers, ip stack, codecs etc from scratch
Edit: there’s doom on the task bar !?!
It looks like they ginned them up from relevant specs they stuffed in and and the model’s latent knowledge of QEMU VirtIO and the absurd GPU-managed system architecture that is the Pi.
The models have seen several IP stacks before, plus many copies of the Linux, BSD, etc. source trees.
It’s not actually hard to write a network stack, just tedious.
At some point in the USB keyboard/mouse code the model has loudly proclaimed
PRINTF NOT ALLOWED, in the style it does when overcompensating after its obvious mistakes are pointed out to it for the third time. So I suspect that part might be implemented by brute force.Unfortunately, the talking horse’s OS hasn’t bothered with syscalls and lacks any notion of memory protection, and has a terrible userspace API which e.g. puts waiting for a ping response entirely in kernel.
* Programs call kernel functions directly - no syscalls needed. * Win3.1 style!Usually people don’t manage to produce an entire operating system without knowing why this is a bad idea.
There’s a Doom button on the task bar. I imagine it doesn’t work
I’d take OG doom being bundled with the OS and forever pinned to the taskbar over whatever Windows has been doing with candy crush tbh
No no, you misunderstand. No FROM scratch. IN scratch.
www.scratch.mit.edu
oh god no, cs teacher made us use this thing even though most of us could already write code. it was painful
It’s likely like the exFAT driver for FreeBSD, which was just a regeneration of the Linux exFAT driver, thus broke license terms.
mhm its in the repository: https://github.com/kaansenol5/VibeOS/blob/main/doomgeneric/README.md
Given this is all going to be stolen and slightly modified code anyways, I don’t see why not. 64 sessions sounds like a lot.