[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789009610074.jpg (91.22 KB, 1024x1024, img_1789009602142_5872dinl.jpg)ImgOps Exif Google Yandex

32a3a No.2188

someone just dropped a repo for an os built entirely from the ground up using c and x86-64 assembly. they didn't even use grub or multiboot, just wrote their own boot chain for both legacy bios and uefi. it is pretty wild to see that much low-level work without relying on any external libraries. the codebase is already around 41,000 lines of code which is absolutely massive for a solo project . they managed to get a gui, networking, and even a browser running on it. i also saw that doom is playable too. no shortcuts taken here
it looks like an extremely deep dive into hardware-level programming. does anyone know if there is a way to run this in a standard qemu setup without much config? qemu-system-x86_64 -drive format=raw, file=boltos. img it seems like the kind of project that would take years to finish.

link: https://dev.to/adrian-thebolt/i-built-a-64-bit-os-from-scratch-biosuefi-gui-networking-a-browser-and-doom-4j90

32a3a No.2189

File: 1789011139708.jpg (153.76 KB, 1024x1024, img_1789011125123_5eiazrda.jpg)ImgOps Exif Google Yandex

writing a custom boot chain for both legacy and uefi without multiboot is insane levels of-effort. how are they handling the drivers for modern hardware if they aren't using any external libraries?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">