Live data from Hacker News

Show HN: Banan-OS, an Unix-like operating system written from scratch

github.com

1–10 of 65 posts

Show HN: Banan-OS, an Unix-like operating system written from scratch

#1
This is my operating system that I've been working for the past 2 years. All of the code is written exclusively by me except from ported software. banan-os has a monolithic kernel targeting x86 (i686) and x86_64 architectures. The project consists of bootloader, kernel and userspace libraries (libc, libGUI, libFont, ...). It also uses my custom C++ standard library partly based on stdc++.

Currently I have basic TTY and GUI environment with some of the basic UNIX utilities like cp, ls and stat. I have basic support for USB (keyboard/mouse/storage), disks (NVMe, AHCI), custom networking stack with TCP and UDP support, and a UNIX-like filesystem with /dev /tmp /proc filesystems.

The whole project is written in C++ except for my BIOS bootloader that is written in 16-bit real mode assembly. I have been testing the OS mainly on virtual machines but also frequently on real hardware.

Show HN: Banan-OS, an Unix-like operating system written from scratch
github.com

Re: Show HN: Banan-OS, an Unix-like operating system written from scratch

#6
post #2

This is really cool! I like the name, too. Of all the things you've implemented for this, what has been the most difficult part? And have you hit any serious roadblocks along the way?

I read it thinking "banyan tree" until I saw the ASCII art and realized it's a banana reference.

Re: Show HN: Banan-OS, an Unix-like operating system written from scratch

#9
Very cool! How much time do you dedicate to this, in terms of hours per week? Looks like a lot of work has gone into it!

You say you're a student on your profile - does that mean university? If so, have you also worked on the OS directly as part of your studies?

Re: Show HN: Banan-OS, an Unix-like operating system written from scratch

#10
post #2

This is really cool! I like the name, too. Of all the things you've implemented for this, what has been the most difficult part? And have you hit any serious roadblocks along the way?

There hasn't been any overly difficult parts. I'd say the most difficult one has to be either AML interpreter because the ACPI specs are very badly written or the USB stack just because the size of the specifications is so large with a lot of cross referencing.

There hasn't been any major roadblocks. Sometimes I give up on a feature and come back to it maybe month or two later though.

Post reply on HN