Keep in mind that PatchworkOS is currently in a very early stage of development.
Patchwork is a 64 bit monolithic hobbyist OS built from scratch in C for the x86_64 architecture, it is intended as an easy-to-modify toy-like Unix-inspired OS (not Unix-like) it takes many ideas from Unix while simplifying them and removing some of the fat. Made entirely for fun.
- Multiroot filesystem, with labels not letters
home:/usr/fonts
- Replaced
fork(), exec()
withspawn()
- Single-User
- Non POSIX standard library
- GUI centric design
- Lost of other stuff...
- Easy to understand Unix inspired architecture (Not Unix-like)
- Monolithic preemptive 64-bit kernel
- SMP (Symmetric Multiprocessing)
- Multithreading (Kernel Level Threads)
- O(1) scheduler
- Custom standard library
- Custom UEFI bootloader
- SIMD
- Custom image format (.fbmp)
- More to be added...
- Ram disks only
- Only x86_64
- Lenovo Thinkpad E495
- Ryzen 5 3600X | 32GB 3200MHZ Corsair Vengeance
Currently untested on Intel hardware.
1. Cloning
To clone this repository, you can either use the Code
button at the top left of the screen on GitHub, or if you have Git installed, run the git clone --recursive https://github.com/KaiNorberg/PatchworkOS
command.
2. Building
Before building Patchwork, ensure you have make, gcc, nasm and mtools installed, you will need to use Linux.
Once everything is installed, navigate to the cloned repository and run the make all
command. You should then find a PatchworkOS.img
file in the newly created bin directory.
3. Running
There are three ways to run Patchwork.
- Create a Bootable USB: Use a tool like balenaEtcher to create a bootable USB using the created .img file.
- Use QEMU: Download QEMU and use the
make run
command. - Other Virtual Machine: Run the created .img file in a virtual machine of your choice.
Documentation will eventually be found on the wiki page.
Patchwork is intended as a personal project, therefor contributions are unwanted. However if you find any bugs, issues or just have a suggestion for something i could do better, then feel free to open an issue. This might change in the future.