Bananymous/banan-os: Mirror of banan-os, my hobby operating system

This is my hobby operating system written in C++. Currently supports x86_64 and i686 architectures.

You can find a live demo here

Each major component and library has its own subdirectory (kernel, userspace, libc, …). Each directory contains directory include, which has all of the header files of the component. Every header is included by its absolute path.

# apt install build-essential git ninja-build texinfo bison flex libgmp-dev libmpfr-dev libmpc-dev parted qemu-system-x86 cpu-checker

# pacman -S --needed base-devel git wget cmake ninja parted qemu-system-x86

To build the toolchain for this os. You can run the following command.

NOTE: The following step has to be done only once. This might take a long time since we are compiling binutils and gcc.

To build the os itself you can run one of the following commands. You will need root access for disk image creation/modification.

./bos qemu
./bos qemu-nographic
./bos qemu-debug
./bos bochs

You can also build the kernel or disk image without running it:

To build for other architectures set environment variable BANAN_ARCH=arch (e.g. BANAN_ARCH=i686).

To change the bootloader you can set environment variable BANAN_BOOTLOADER; supported values are BANAN (my custom bootloader) and GRUB.

To run with UEFI set environment variable BANAN_UEFI_BOOT=1. You will also have to set OVMF_PATH to the correct OVMF (default /usr/share/ovmf/x64/OVMF.fd).

If you have corrupted your disk image or want to create new one, you can either manually delete build/banan-os.img and build system will automatically create you a new one or you can run the following command.

I have also created shell completion script for zsh. You can either copy the file in script/shell-completion/zsh/_bos to /usr/share/zsh/site-functions/ or add the script/shell-completion/zsh to your fpath in .zshrc.

As the upstream is hosted on my server https://git.bananymous.com/Bananymous/banan-os, merging contributions is not as trivial as it would be on GitHub. You can still send PRs in GitHub in which case I should be able to download the diff and apply it manually. If you want, I can also provide you an account to my git server. In this case please contact me (email, discord).

As this is mostly a learning experience for me, I would appreciate if you first contacted me about adding new features (email, discord, issue, …). If you send a PR about something I was planning on doing myself and you didn’t ask me, I will probably just close it. Bug fixes are always welcome!

Commit message should be formatted followingly

1. First line is of the form “Subject: Description“, where Subject tells the area touched (Kernel, Shell, BuildSystem, …) and Description is brief description of the change done. First line should fit fully in 72 characters.
2. Body of the message should further describe the change and reasoning behind the change.

All commits should pass the pre-commit hook defined in .pre-commit-config.yaml. For instructions on how to setup pre-commit, please see https://pre-commit.com/#install.

Keep your files stored safely and securely with the SanDisk 2TB Extreme Portable SSD. With over 69,505 ratings and an impressive 4.6 out of 5 stars, this product has been purchased over 8K+ times in the past month. At only $129.99, this Amazon’s Choice product is a must-have for secure file storage.

Help keep private content private with the included password protection featuring 256-bit AES hardware encryption. Order now for just $129.99 on Amazon!