because I can.

Having a good time is my drive for this project + I learn a lot of cool low level stuff alongside that!

The cavOS kernel is a monolithic x86_64 one written in relatively simple C with a few bits of Intel assembly here and there. It uses the Limine bootloader and leverages the FAT32 filesystem for booting along with Ext2 for the root partition. I try to keep the code structure clean and fairly easy to understand, while avoiding too much abstraction. Hence, code quality and clarity are sometimes prioritized over performance gains.

Userspace is my primary focus at the time being, with the kernel being quite stable. I'm trying to make this OS as close to Linux as I can, while adding my own stuff on top of it. This is visible with the system calls that are exactly like Linux's. That isn't random, I want cavOS to be as binary compatible with it as possible!

No! The cavOS kernel does not share source code or headers with Linux. The Linux source code is pulled during userspace assembly, but only because some third party (ported) programs depend on it's headers. Even then, no actual code is shared.

Important to mention these goals may never be satisfied, take a very long time to be completed (we're talking years down the road) or may never be done at all. Furthermore, this list won't include every feature implemented or planned and can be changed at any time...

• Life
  • Lose my sanity
• Architecture: x86_64 (amd64)
  • Interrupts: ISR, IRQ, GDT
  • Ring3: Scheduling, ELF64, SSE, paging, systemcall
  • Generic: RTC
• Filesystems
  • VFS: Mountpoints, special files
  • FAT32: Read
  • Ext2: Read
  • FAT32: Write
  • Ext2: Write
• Device drivers
  • Storage: AHCI
  • Networking: RTL8139, RTL8169
  • Generic: PS/2 Keyboard, serial port
  • Generic: Mouse
• Networking stack
  • Generic: Rethink everything networking-related
  • Layer3: IPv4, ARP, ICMP
  • Layer4: UDP, TCP
  • Layer5: DHCP
  • Layer6: TLS
  • Layer7: DNS, HTTP
  • OS Interface: Sockets
  • Generic: Improve reliability & security
• Userspace
  • Toolchain: cavOS-specific
  • Libraries: musl(libC)
  • Linking: Dynamic
  • System calls: signals, sockets, filesystem, etc...
• Interfaces
  • Kernel: Embedded shell
  • Kernel: Good panic screens
  • Ports: Bash, coreutils, vim, binutils, gcc
  • Desires: Cool fetch, some damn IRC client
• Graphics
  • Framebuffer: Use in kernel
  • Framebuffer: Pass to userspace
  • Xorg or smth? idk (seriously)

Everything about this can be found over at install.md. Go there for more info about building the OS correctly, cleaning unused binaries and other stuff.

• G-9: ASCII art on fetch!

Saturday March 2nd of 2024. Through many workarounds, "bad" decisions and an overbearing "just-works" mentality, I had pieced together a purely x86 (32-bit) kernel that could unreliably fuel userspace applications. Still holding onto old code (from back when I barely understood simple concepts, like say paging), outdated libraries and a lot of other stuff. It sometimes worked, but I was not satisfied.

5:00PM; That afternoon I decided to start a lengthy process of migrating everything to the x86_64 architecture and ironing out plenty of reliability issues, which made for actual nightmares to debug. I basically reached a certain point to understand that quick & dity solutions only lead to completely avoidable mistakes, which were extremely hard to pinpoint after tremendous amounts of abstractions were added.

This project is licensed under GPL v3 (GNU General Public License v3.0). For more information go to the LICENSE file.