| Build Configuration | Status |
|---|---|
| I386 |  |
| AMD64 |  |
Showcase of Vali to get an idea of how the userspace will be once it's finished.
BIG UPDATE TO LAYOUT AND FEATURES - NEW IMAGES COMING SOON
| Project | Link | Description |
|---|---|---|
| Gracht | github | Open source protocol library heavily featured in MollenOS/Vali. |
| Vioarr | github | Open source window manager with terminal and launcher built ontop of Gracht. |
Before you setup anything you must setup environmental variables that are used by the project.
| Variable | Required | Description |
|---|---|---|
| CROSS | Yes | Points to where the cross-compiler is installed. |
| VALI_APPLICATION_PATH | No* | Points to where the Vali applications/libraries are built. |
* Can be supplied to include built applications in the kernel image
The only thing you need to get started is a succesfully built toolchain of llvm/clang/lld. To help make this easier I have made a fully automated script, which downloads all the neccessary components, and initiates a full build of llvm/lld/clang. Make note that a full build of llvm/clang/lld need to run, and that this takes a couple of hours.
Toolchain scripts are located here. You should run the scripts in this order:
- depends.sh
- checkout.sh
- build-cross.sh
Remember to checkout all the submodules with the command git submodule update --init --recursive
The last step is now to run the depends.sh script that is located in this repository which installs the final pre-requisites (nasm, mono-complete, cmake platform script). The script is located in tools/depends.sh.
After this, you are essentially ready to start developing on the operating system. When/if you make pull requests when contributing, please follow the pull template that is provided.
If you want to build applications for Vali, you will need to install the sdk and ddk by using make install. This will install the required headers and libraries in a shared location that you specify during cmake configuration by using the CMAKE_INSTALL_PREFIX.
Then follow the instructions located here to get the sources for the applications.
These are highlighted build configuration options for the cmake generation, there are more options, but these are the most often configured.
| Option | Default Value | Description |
|---|---|---|
| VALI_ARCH | i386 | Which architecture you will build the OS and applications for. Supported are i386 and amd64. |
| VALI_ENABLE_KERNEL_TRACE | ON | Enable debug tracing in the kernel. |
| VALI_ENABLE_SMP | ON | Enable multicore support in the kernel. |
There is a series of build commands available.
| Command | Description |
|---|---|
| make | Builds the operating system and support libraries |
| make install | Installs the SDK and DDK to the location pointed by CMAKE_INSTALL_PREFIX. This is needed for app and driver development. |
| make install_img | Creates a harddisk image with bootloader, kernel, libraries and built apps of format .img |
| make install_vmdk | Creates a harddisk image with bootloader, kernel, libraries and built apps of format .vmdk |
The uhci driver in bochs (2.6.9) defers packages when communicating with MSD devices to fake a seek delay, however this results in issues with reading from the harddisk, since bochs does not correctly store the number of deferred packages. See this issue description here.
I appreciate any form for contribution you want to make to the project! The project is purely driven by passion, and I dedicate any and all available spare time to this project. But to take this project to the next level I need support! Contributions of any kind are deerly welcome, but should follow the below guidelines.
You can start contributing on any aspect of the operating system, and if you should ever be in doubt, feel free to send me an email at [email protected].
When submitting issues, please take care that the issue is not a dublicate of an already existing, open issue. Please follow the templates specified for issues. Issues can be either a bug report or a feature request. If you feel like the feedback/issue you have does not fall into either category, pick the one you feel it fits the most.
If you want to contribute as a developer on the project please fork the repository, and contribute via pull requests. There is a pull request template you can use when creating a pull request. Please allow for a day or two for me to review the pull request before accepting, as I will take a look as quickly as possible and submit your pull request.
The basic features of the kernel is completed, and the road to the 0.7 release will include mostly bugfixes to kernel or any missing implementations. Some implementations in relation to cleanup of resources and coordination of cleanup are postponed and we now seem to slowly encounter those issues as we continue to port applications and functionality to the operation system. The goal for the 0.7 release are described in the milestone 0.7 Pearl.
MollenOS uses it's own filesystem (MFS), it is not booted by the more traditional way of GRUB. Instead it has it's own faily complete bootloader for BIOS (only atm, we are planning to implement UEFI soon), which can be found in the /boot directory. mBoot is written specifically for MollenOS, and supports booting from both FAT32 & MFS.
The Vali kernel is far from feature-complete, but it currently is in a state where it supports our use-cases. The kernel itself provides some of the basic system management functions like;
- Memory management
- Thread management
- IPC
- Module support system
- ACPI
Rest of the system functionality exists as drivers and services.
The current services that are implemented (and at some point when we implement RiscV/ARM architectures) should be included as configurable in the build system, so we can choose exactly which services are relevant for the platform.
- Device manager (g_handles discovery and management of devices on the platform)
- File manager (Is responsible for both storage and file management)
- Net manager (Network stack and management of sockets)
- Process manager (Provides the process protocol that allows spawning and management of processes on the system)
- Session manager (Provides management of user sessions)
- Usb manager (The usb stack implementation that manages usb devices, hubs and controllers)
- AHCI
- ACPICA
- MFS
- HPET
- USB Stack (OHCI, UHCI, EHCI)
- USB Hub
- USB MSD
- USB HID
- (x86) PCI/PCIe
- (x86) CMOS
- (x86) PIT
- (x86) RTC
- (x86) PS2 Mouse & Keyboard
- (x86) APIC
All documentation about design and implementation, and the theory behind is stored in the /docs folder. Right now there isn't any documentation, but it'll all come with the Documentation milestone.
- /boot (Contains bootloaders and anything boot-related)
- /cmake (CMake configuration files required to build the OS with cmake)
- /docs (Documentation and related resources about the project and the OS)
- /kernel (Contains the Vali kernel source code)
- /librt (Contains all support and runtime libraries needed for Vali)
- /modules (Contains drivers for Vali)
- /protocols (All the libgracht protocols used in the OS for services and modules)
- /services (Contains system services like the filemanager for Vali)
- /resources (Contains the deploy folder for installing the OS)
- /tools (Contains tools for building and manipulating)
- /tests (Contains example applications for the OS)